VERSION 1.1 · IN FORCE SINCE 5 NOV 2026

Privacy Policy

This policy explains what personal data Allocate collects when you use the service, why we collect it, who we share it with, and the rights you have over it.

1. Who we are

Allocate is a service for booking and managing equipment, used by businesses. It is run by Joakim Svärd, a sole trader (enskild firma) registered in Sweden.

BusinessJoakim Svärd (trading as Allocate)
Organisation number19850808-0218
VAT numberSE850808021801
AddressOxelvägen 13, 138 31 Älta, Sweden
Privacy questionsprivacy@allocate.at
Other supportsupport@allocate.at

Who is responsible for which data

The law calls the party that decides why and how data is used the controller, and a party that handles data on someone else's instructions the processor.

  • We are responsible for your user account and sign-in, billing, support requests, the emails we send for our own purposes (such as account and billing emails) and our security logs. This policy covers that data.
  • Your company is responsiblefor the bookings, equipment, team list, roles and invitations inside its workspace. We handle that data on the company's behalf and on its instructions, under our Data Processing Agreement, including sending invitations and notices about team changes for the company. Your company should tell you how it uses that data, and questions about it go to your company first; we help them answer.

Allocate is a tool for businesses. It is not meant for consumers or for children.

2. What we collect

We collect the data described below, for the purposes in section 3.

Name, email address, password (stored only as a hash by Google), user ID and your settingsWhose: Everyone with an account. Where it comes from: You, when you sign up.
Company memberships, role (a standard role or a custom role your company has defined), join dateWhose: Members of a company. Where it comes from: You or your company’s admin.
Proof of what was confirmed: the versions of the Terms of Service and this policy you confirmed, and when. For a company: the versions of the Terms and the Data Processing Agreement it accepted, when, and which admin acceptedWhose: Everyone who confirms the terms; the admin who accepts for a company. Where it comes from: You, when you confirm or accept. We add the versions and the time.
Invitations: invitee’s email address, inviter’s name, role, status, datesWhose: People invited to a company. Where it comes from: The admin, or a member with the right to invite, who sends the invitation.
Bookings, equipment and the names attached to them (who booked, approved, cancelled or changed something), and any free text you typeWhose: Members of a company. Where it comes from: You and your colleagues.
Subscription and billing: company name, billing contact email, billing address, VAT number, payment methodWhose: The person who subscribes on behalf of the company. Where it comes from: You, through Stripe’s checkout.
Support requests: your name, your company, what you writeWhose: Anyone who contacts support. Where it comes from: You.
Our internal notes about a customer company, written while giving supportWhose: Customer companies and the people mentioned. Where it comes from: Us.
Service emails sent to you: your address, the content and the delivery statusWhose: Everyone we email. Where it comes from: Generated by the service.
Security and audit records: account and company deletions, and attempts to open the operator area (our support and administration area, open only to people we authorise), with user ID and email addressWhose: Everyone with an account. Where it comes from: Generated by the service.
Technical data: IP address, browser information, user and company IDs in server logsWhose: Everyone who visits. Where it comes from: Your browser, automatically.

Card details never reach us.You enter them on Stripe's own checkout page. We never receive full card numbers or security codes, but Stripe sends us payment and subscription details, such as amounts, status and dates.

Free text is up to you. Booking notes, project names, role names and descriptions, and support messages can hold anything you type. Please do not enter sensitive personal data there, such as health information, or information about criminal offences.

Invited people.If a colleague invites you, your company gives us your email address and we send the invitation on the company's behalf. The invitation email tells you who invited you and links to this policy.

3. Why we use it, and on what legal basis

Every use below has a legal basis under Article 6 of the GDPR. Where we rely on legitimate interests, we name the interest, and you have the right to object (section 6). You can contact us for more information about these interests.

Creating and running your account, signing you in, sending verification and password emailsLegal basis: Contract (6.1 b) where you yourself are our customer, for example as a sole trader. Otherwise legitimate interests (6.1 f): providing the service your employer or client pays for.
Providing the workspace to your company: bookings, equipment, team list, invitations and notices about team changesLegal basis: We act as processor on your company’s instructions (Art. 28). Your company chooses its own legal basis.
Subscriptions, payments and invoicesLegal basis: Contract (6.1 b) with the subscribing company, and legitimate interests (6.1 f) for the person who acts as its billing contact
Keeping invoices and accounting records for as long as the Bookkeeping Act requiresLegal basis: Legal obligation (6.1 c): the Swedish Bookkeeping Act
Keeping proof of which versions of the Terms, the Data Processing Agreement and this policy were confirmed or accepted, and whenLegal basis: Contract (6.1 b) with the company that accepts the Terms and the Data Processing Agreement. Legitimate interests (6.1 f) for the individual user: being able to show what was confirmed and when.
Answering support requests and keeping internal support notesLegal basis: Legitimate interests (6.1 f): helping customers and handling follow-ups
Security: session handling, the log of attempts to open the operator area, protecting against misuseLegal basis: Legitimate interests (6.1 f): keeping the service and your data secure
Keeping records that a deletion took placeLegal basis: Legitimate interests (6.1 f): being able to show that we deleted data as promised (Art. 5.2)
Deleting accounts and workspaces that no longer have a purposeLegal basis: Legitimate interests (6.1 f): not keeping data we no longer need (Art. 5.1 e)
Establishing, exercising or defending legal claims, for example keeping proof of what was agreedLegal basis: Legitimate interests (6.1 f): protecting our rights

We do not sell your data or make automated decisions with legal or similar effects on you.

Customer references. As the Terms of Service allow, we may name a customer company and show its logo as a customer of Allocate (legitimate interests, 6.1 f: showing who uses Allocate). If the customer is a sole trader, its name is personal data. Any customer can ask us to stop at support@allocate.at.

4. Who we share it with

We use five providers to run Allocate. Each has a data processing agreement with us, and none may use your data for its own purposes except where stated. Stripe and Resend are also independent controllers for some data, as described below.

Google Cloud / FirebaseProvider: Google Cloud / Firebase (Google Ireland Ltd and Google LLC). What they do for us: Database, sign-in, servers, scheduled jobs, logs. Where the data is: Database: EU (multi-region eur3). Servers and scheduled jobs: Belgium and the Netherlands. Application logs: Belgium. Sign-in (Firebase Authentication) runs only in the United States, where Google keeps sign-in IP addresses for a few weeks.
StripeProvider: Stripe (Stripe Payments Europe Ltd, Ireland, and Stripe, LLC). What they do for us: Payments, subscriptions, invoices, VAT. Where the data is: EU and the United States.
ResendProvider: Resend (Plus Five Five, Inc.). What they do for us: Sending service emails: your address and the content of the email. Where the data is: United States.
Google WorkspaceProvider: Google Workspace (Google Ireland Ltd and Google LLC). What they do for us: Email we receive at support@ and privacy@ and our other email. Where the data is: Google's data centres, including the United States.
BokioProvider: Bokio (Bokio AB, Sweden). What they do for us: Our bookkeeping: invoices, payments and the billing details on them. Where the data is: As described in Bokio's data processing agreement.

Stripe has two roles.It processes payments for us. It also acts as an independent controller for its own legal duties, such as fraud prevention and anti-money-laundering checks. Stripe's privacy policy covers that part. When you subscribe, you are sent to Stripe's own pages, where Stripe's cookies apply.

Resend is an independent controller for some data.Resend processes our emails on our behalf, but it is itself responsible for a few things, such as delivery data and protecting its service against misuse. This is described in Resend's own data processing terms.

Transfers outside the EU/EEA.Google LLC (including email through Google Workspace), Stripe, LLC and Resend process some data in the United States. These transfers rely on the EU Commission's Standard Contractual Clauses in each provider's data processing agreement, and also on the EU-U.S. Data Privacy Framework for providers certified under it. You can ask us for a copy of the safeguards at privacy@allocate.at.

Inside your company.Only admins can see members' email addresses. Admins, and members who have been given team rights, can see the team list with names. Members who can invite people can also see open invitations, including the invited email addresses. Members can see bookings and equipment, including who made a booking, as far as their role allows. A member without the right to see all bookings sees only their own. A member with no role yet cannot see company data. While an invitation is open (7 days), anyone who has the invitation link can see which email address it was sent to.

Our own access. People we authorise to work on Allocate can see customer accounts, team lists and support requests when needed for support, billing or security, and keep short internal notes about customer companies. They are bound by confidentiality. Attempts to sign in to that operator area are logged.

Authorities and advisers. We disclose data to authorities when Swedish or EU law requires it, and to our accountants and lawyers, who are bound by confidentiality, when needed for our bookkeeping or to establish, exercise or defend legal claims. Our providers may be required by the law that applies to them to disclose data; their data processing terms describe how they handle such requests.

5. How long we keep it

We keep data only as long as it is needed, and most of it is deleted automatically. Automatic deletion is done by scheduled jobs, some of which run once a week, so it normally happens within about a week after the time shown, not at the exact moment. A few records are kept for a fixed time to meet legal duties or to show that a deletion happened.

Your account

Your accountHow long: As long as you have it. What happens then: Deleted when you delete it yourself.
An account that no longer belongs to any companyHow long: 30 days after the last membership ends. What happens then: Deleted. We email you first, and joining or creating a company stops it.
A sign-up that was never completedHow long: 14 to 31 days after the sign-up was made or last used, whichever is later. What happens then: Deleted by a check that runs twice a month.
Proof that you confirmed the termsHow long: As long as you have your account. What happens then: Deleted with your account.
Undo links for an email address changeHow long: 7 days. What happens then: Deleted.

Your company's data

A company workspace (bookings, equipment, team)How long: As long as the company has an active subscription or trial, or an arrangement we have agreed with it. What happens then: See the next rows.
While a payment is overdueHow long: Until the subscription ends. We end a subscription that stays unpaid about 90 days after it became unpaid. What happens then: Then as after a paid subscription ends.
After a paid subscription endsHow long: At least 90 days, during which the workspace is locked. What happens then: Deleted. Admins are emailed at least 7 days before deletion, and normally also when it is locked. Subscribing again stops it.
After a trial ends without a subscriptionHow long: At least 30 days. What happens then: Deleted, with the same emails.
A company that never started a trial or subscriptionHow long: At least 30 days after it was created. What happens then: Deleted, with an email 7 days before.
When an admin deletes the companyHow long: A 7-day window in which the deletion can be cancelled. What happens then: Deleted. If you are the only member and delete your account, deletion of the company starts at once.
Proof that the company accepted the Terms and the Data Processing AgreementHow long: As long as the company exists. Each accepted version and when it was accepted are kept; who accepted is recorded only for the latest acceptance. What happens then: Deleted with the company. The reference to the admin who accepted is removed if that admin leaves the company or deletes their account.
InvitationsHow long: The link works for 7 days. What happens then: The record is deleted 30 days after it was accepted, revoked or expired.

If we have agreed a different arrangement with a company, the three periods for an ended or missing subscription (after a paid subscription ends, after a trial ends, and for a company that never started) start on the day that arrangement ends, not before. The period for an ended paid subscription (90 days) then applies from that day, and admins get the locked email and the email 7 days before deletion from then. The other rows do not depend on any arrangement. Deletion can also be postponed while we prepare a copy the company has asked for.

When you leave a company or delete your account, your name is removed from the company's bookings and equipment history. Names typed into free text, such as notes and project names, are not searched for and removed. The entries themselves stay with the company, because they are the company's records.

Billing

Invoices and accounting recordsHow long: Seven years after the end of the calendar year in which the financial year ended, as the Swedish Bookkeeping Act requires. What happens then: Kept by Stripe, our payment provider. They are not erased earlier, even on request.
The company’s customer record at StripeHow long: Kept with the invoices. What happens then: When a company is deleted, its name at Stripe is replaced with "Deleted Company", and its email address, phone number and addresses are removed. Details on saved payment methods and Stripe’s own records are kept by Stripe under its terms.

Support, emails and logs

Support requestsHow long: Open requests close automatically after 6 months without activity. Closed requests are kept 24 months. What happens then: Deleted. If you leave your company or delete your account, your name is removed but the text you wrote stays until then.
Our internal notes about a customer companyHow long: 24 months. What happens then: Deleted, or earlier if the company is deleted.
Service emails in our send queueHow long: 30 days after the email is sent, or after it was queued if it is never sent. What happens then: Deleted.
Service emails at our email provider (Resend)How long: For the period Resend’s terms set for our plan. What happens then: Deleted by Resend.
Emails to support@ and privacy@How long: 24 months after the last message in the conversation. What happens then: Deleted.
Record that an account was deletedHow long: 12 months. What happens then: Deleted. It holds a coded ID that cannot be linked to you without a secret key we keep, not your name or email.
Record of a company deletionHow long: Former members’ names and emails: 30 days after the deletion (90 days if it failed). The requester’s name and email: 24 months. The rest: 36 months after the deletion was requested. A deletion that has not finished is kept until it is resolved. What happens then: Deleted.
Note that an account deletion did not finishHow long: 90 days after the last attempt. What happens then: Deleted. It is removed as soon as the deletion succeeds. It holds your user ID, the step that failed and the IDs of your companies, not your name or email.
Record of a failed paymentHow long: 12 months. What happens then: Deleted, or earlier if the company is deleted. It holds Stripe’s customer ID for the company, the amount and the dates, not a name or email.
Record of a change we make by hand for a company (for example billing, plan limits, features or the deletion date)How long: 24 months. What happens then: Deleted, or earlier if the company is deleted. It holds the user ID and email address of the person at Allocate who made the change, and a short note.
Log of attempts to open the operator areaHow long: 90 days for refused attempts, 12 months for granted ones. What happens then: Deleted. Kept even if you delete your account, so the log cannot be wiped by deleting an account.
Application logsHow long: 30 days, stored in the EU (Belgium). What happens then: Deleted.
BackupsHow long: Up to 35 days in our backups; up to 180 days in Google’s internal deletion process. What happens then: Deleted. Backups are used only to restore the service after an error.

6. Your rights

You can export, correct and delete your own data yourself in Account settings. For anything else, email privacy@allocate.at. We answer within one month; if a request is complex we may extend that by up to two more months and tell you why. It is free of charge, unless a request is clearly unfounded or excessive.

Access and a copy (Art. 15) and portability (Art. 20)Account settings → Export my data downloads your data in a machine-readable file
Correction (Art. 16)Change your name and email address in Account settings. Your new name shows everywhere from then on; older history entries are not rewritten. Your billing contact at Stripe is separate: an admin can change it when managing billing, or you can write to us.
Erasure (Art. 17)Account settings → Delete account. In most cases we delete your account straight away. If a step fails, we keep working on it; if you can still sign in two days later, contact privacy@allocate.at. Section 5 lists what we must keep for a limited time and why.
Object to use based on legitimate interests (Art. 21)Email us. We stop unless we have compelling reasons, such as security or a legal claim.
Restriction (Art. 18)Email us
ComplainTo the Swedish Authority for Privacy Protection (IMY), imy.se, or the authority where you live or work

Export my data covers your own account, memberships (including your role in broad terms), your own bookings and your support tickets. It does not cover other members' bookings or internal support notes. The company's admin can ask us for a copy of the company's data, and you can ask us for anything else we hold about you under Art. 15.

If you are the last admin. You cannot delete your account while other members depend on you as admin. Make someone else admin first, or delete the company.

Data your company controls. Requests about bookings, equipment, team or role data go to your company, which decides. If you send them to us, we pass them on and help your company answer.

When we cannot delete at once. If you ask us to erase data we must keep by law, such as invoices, we tell you why and when it will be deleted.

We may ask you to confirm your identity before we act on an emailed request.

What you must give us. You need to give us your name and email address to have an account; without them we cannot give you access. To subscribe, Stripe needs billing details. Everything else is up to you.

7. Cookies and storage in your browser

Our terms, this privacy policy, the data processing agreement and the page where you ask for a password reset link do not make Allocate store anything in your browser. Signing in, signing up and the links in our account emails (such as setting a new password) use Google's Firebase, which stores two entries in your browser. We ask for your consent before they are stored; without it, these features are switched off in the current version of Allocate. The other entries below are needed for the service to work and are stored without asking. We use no analytics, advertising or tracking cookies.

To withdraw your consent, clear the site data for allocate.at in your browser. This also signs you out, and we ask again the next time you sign in. If you need help, contact privacy@allocate.at.

__sessionType: Cookie, set by us. Purpose: Keeps you signed in. How long: 14 days from sign-in, or until you sign out.
firebaseLocalStorageDbType: Browser database (IndexedDB), set by Google’s Firebase sign-in. Purpose: Stored only after you accept. Keeps the sign-in working in your browser. How long: Until you sign out or clear your browser data. If you leave without signing in, or your session simply expires, the entry can remain.
firebase-heartbeat-databaseType: Browser database (IndexedDB), set by Google’s Firebase software. Purpose: Stored only after you accept. Written automatically by Google’s Firebase software when you open sign-in or sign-up or use the app. It records which versions of the software run and on which days, holds no user ID or personal details, and cannot be switched off separately. We do not read it. Firebase may send this information to Google with its requests. How long: Until you clear your browser data.
storage_consentType: Cookie, set by us. Purpose: Remembers that you accepted the Firebase entries, so we don’t ask again. How long: 12 months, or until you clear your browser data.
terms_deferredType: Cookie, set by us. Purpose: Remembers that you chose “Answer later” for updated terms, so we don’t ask again on every page. It holds only the version of the terms. How long: 24 hours, or until you sign out.
Pending terms acceptanceType: Local storage, set by us. Purpose: Remembers that you ticked the terms box when signing up with an invitation, until the invitation is accepted. It holds only the version of the terms and when you ticked the box. How long: Until the invitation is accepted or you clear your browser data. After 7 days it is no longer used.
Account deletion confirmationType: Session storage, set by us. Purpose: Shows the confirmation screen after you delete your account. How long: Removed once the confirmation is shown, or when you close the tab. It is not used after 30 minutes.

When you subscribe or manage billing, you are sent to Stripe's website, where Stripe's own cookie policy applies.

8. Security, changes and contact

Security.Traffic is encrypted, and passwords are stored only as hashes. Access inside a company follows roles, and each company's data is separated from other companies' data by access rules. Deletion and access to the operator area are logged.

Changes to this policy. Each version has a number. For a significant change we tell you in advance, by email or in the app, and ask you to confirm you have read it. Small corrections, such as new contact details, take effect when published.

If Allocate changes owner. Allocate is planned to move from a sole trader to a limited company. If that happens, or if the business is sold, your data moves with the service under the same protections, and we tell you.

Contact. Email privacy@allocate.at, or write to Joakim Svärd, Oxelvägen 13, 138 31 Älta, Sweden.

Version 1.1