Privacy notice
Fairloco Oy (business ID 3626342-7, VAT ID FI36263427, PL 999, 42011 YRITYSLOKERO) is the controller of the personal data processed in the Fairloco marketplace. We collect only what we need to run the marketplace, sign you in, take payments for the sellers, pay restaurants and couriers and meet our legal duties. We never sell personal data. Contact us about privacy at hola@fairloco.com.
Versions
- Version 3, in effect from 1 Oct 2026. You are reading this version
- Version 2, in effect from 27 Sep 2026 until 1 Oct 2026. Read the full text
Version
Version 3, in effect from 1 Oct 2026. We update this notice when our processing changes and show the new version here.
Controller and contact
Fairloco Oy (business ID 3626342-7, VAT ID FI36263427, PL 999, 42011 YRITYSLOKERO) runs the Fairloco marketplace and is the only controller of the personal data processed in it. Contact: hola@fairloco.com. Our geographic address is on the contact page.
We have not appointed a data protection officer. A named person at Fairloco leads privacy work and answers privacy questions at the same address.
Fairloco, Inc. (Delaware, USA), our parent company, publishes our apps in Google Play on behalf of Fairloco Oy.
The old Fairloco service (Fairloco, Inc.)
Fairloco, Inc. is the controller of the earlier Fairloco service until that service closes. You can send any request about the old service to hola@fairloco.com. When we move an account from the old service, we tell the person at least 7 days in advance, and we do not move the account if they object.
What we collect
We never ask for ID documents. A business ID is checked against public registers, which is not an identity check.
- Account: email address, name, password hash or your Google account ID, passkeys (only the public key), sign-in sessions and your devices. We do not store Google tokens or your profile photo.
- Customers: what you order, from which restaurant and courier, prices and tips, the delivery address, door code, delivery note and phone number for the delivery, an allergy note if you add one, order messages, claims, reviews, receipts, payment status, and the version of the customer terms you accepted, when, and the browser (user agent) you used. Stripe handles your card details, and we never see your full card number.
- Restaurants: business ID, company details from the public YTJ register and EU VIES and the result of those register checks, the restaurant phone number, the customer contact email address, the name of the payout account holder, venue address and hours, menu, payout IBAN, the bank name check (Verification of Payee) result, accepted terms, self-certifications and the browser (user agent) used to accept them.
- Couriers: name, phone number, home address, date of birth and your own confirmation that you are 18 or older, business ID and the register check result, vehicle, your price, payout IBAN, the bank name check result, accepted terms, self-certifications and the browser (user agent) used to accept them.
- For DAC7 reporting: the personal identity code of couriers and of restaurants run by a private trader, stored encrypted.
- Courier location: only while you are online in Fairloco Courier and during a delivery. It is kept in memory to show your distance class to customers who are choosing a courier and your position to the customer after pickup. We never store a location history.
- Support messages and emails you send us, and the replies.
- Technical data: IP address for rate limits and security, and device information for push notifications.
- Where you came from: if you open a partner sign-up link with campaign tags (src, v, post, ref), we save those tags once with your application to learn which posts and messages bring partners. We use no cookies, tracking pixels or third-party analytics for this.
Where we get data
Mostly from you. Company details come from the Finnish trade register (YTJ) and EU VIES, and the bank name check result from the payee's bank through Revolut. If we move your account from the old Fairloco service, we receive from Fairloco, Inc. only the details that our message to you lists.
Why and on what legal basis
- Contract, and steps before a contract (GDPR Article 6(1)(b)): accounts, partner applications, orders, deliveries, payouts, order messages and the notifications you turn on. A courier's location while online and during a delivery, and showing the courier's name, price, distance class and position to the customer who orders, are part of the courier's contract. We never ask consent for location.
- Legal obligation (Article 6(1)(c)): bookkeeping, DAC7 reporting with the personal identity code (Act 1267/2022 and section 29 of the Data Protection Act), and the seller details that the Consumer Protection Act requires us to show to customers.
- Legitimate interest (Article 6(1)(f)): register checks, the bank name check, sanctions screening, fraud prevention, security logs and rate limits, keeping the service running, measuring which of our posts and messages bring partners, support with our AI assistant, contacting companies at their general email address, and moving accounts from the old Fairloco service. We have written down the balancing of interests for each, and you can object.
- Explicit consent (Article 9(2)(a)): the allergy note on an order. You can withdraw consent for future orders at any time.
- Health information in a claim is handled only by a person, to establish or defend legal claims (Article 9(2)(f)).
Automated decisions
Some onboarding checks are automatic and follow published rules: the go-live checklist for restaurants and the activation rules for couriers. They use no AI, and couriers are never scored or ranked. Every automatic decision shows its reason and the rule behind it, and you can ask a person to review it. We answer within 2 weeks. A close or failed bank name check always goes to a person.
AI assistant
Our support uses an AI assistant built on models from Anthropic, together with people. The first AI reply in a conversation says that our AI assistant wrote it, and every AI reply is marked. Reply HUMAN at any time to reach a person. A person decides anything that affects money or your account, and only a person can decline a refund or a claim.
Allergy notes are never sent to the AI model, and messages about allergies or illness go straight to a person. In the apps we ask you before the first message goes to Anthropic, and you can choose to talk only to a person. Anthropic processes the messages in the United States and may keep content that its safety systems flag for up to 2 years.
Sorting incoming messages, which sends each message to the right handler, uses a model whose processing location cannot yet be limited to the United States. The sorting can therefore also take place outside the United States, and the same standard contractual clauses apply. We will limit the location when the model allows it.
Who receives data
| Recipient | What for | Role | Where and safeguard |
|---|---|---|---|
| Cloudflare | Hosting, databases, file storage and incoming email | Processor | USA. Databases and files are stored in the EU. Standard contractual clauses |
| Anthropic | AI assistant in support, sorting incoming messages and menu import | Processor | USA. Sorting incoming messages can also take place outside the USA. Standard contractual clauses |
| Resend | Sending emails such as sign-in codes and receipts | Processor | USA. Standard contractual clauses |
| Our email accounts and notifications to our Android apps (Firebase Cloud Messaging). Notifications contain no names, addresses or allergy details | Processor | USA. Standard contractual clauses | |
| Sign in with Google, if you use it | Independent controller | USA. Google's own terms apply | |
| GitHub | Our code, and one-off jobs that move accounts from the old service | Processor | USA. Standard contractual clauses |
| Expo | Building and updating our apps | Processor | USA. Standard contractual clauses |
| Fairloco, Inc. | Publishing our apps in Google Play | Processor for data shown in Google Play | USA. Standard contractual clauses |
| Your browser's push service | Delivering notifications you turn on. It cannot read them, because they are encrypted for your browser | Service provider | Depends on your browser |
| Stripe | Card and wallet payments for orders. Stripe also uses the data for its own fraud prevention and anti-money laundering duties | Processor for payments, independent controller for its own duties | Ireland (EEA) |
| Revolut Bank UAB | Fairloco's own business account, from which we pay restaurants and couriers, and the bank name check | Independent controller | Lithuania (EEA) |
| The payee's bank | Receiving a payout with the account holder name | Independent controller | EEA |
| Digitransit | Finding the location of an address. Only the address text is sent | Service provider | Finland |
| YTJ and EU VIES | Checking company details. Only the business ID or VAT number is sent | Public registers | Finland and EU |
| Finnish Tax Administration | DAC7 reports about restaurants and couriers | Authority, by law | Finland |
| Restaurants and couriers | The order details they need to prepare and deliver your order | Independent controllers, only for your order | Finland |
Every contract with a processor outside the EEA includes the European Commission's standard contractual clauses (2021/914). Where a company is also certified under the EU-US Data Privacy Framework, that is an extra safeguard. We have assessed each transfer.
Restaurants and couriers may use your order details only for your order. They must not use them for their own marketing or keep your door code or address after the order.
Public seller details
The Consumer Protection Act requires that customers see the seller's details before they order and on the receipt. The restaurant's company name, business ID, trade register (YTJ) address, restaurant phone number and customer contact email address are therefore shown publicly in the seller details on the restaurant page, at checkout and on the receipt. For a sole trader, the address and email address can be their own. The restaurant sees which details are published before it saves them.
How long we keep data
| Data | Kept for |
|---|---|
| Orders, receipts, ledger and payouts | 6 years for receipts and other vouchers, 10 years for bookkeeping |
| Exact delivery address and the phone number for the delivery | 120 days after the order ends, then only the postal code |
| Door code and delivery note | 24 hours after the order ends |
| Allergy note | 30 days after the order |
| Courier location | Not stored. Kept in memory only while online or delivering |
| DAC7 records and the personal identity code | 6 years from the end of the reporting year |
| Accepted terms | While the contract lasts and 3 years after |
| Security audit log | 7 years for money and DAC7, 2 years for the rest |
| Support conversations | 24 months after closing, then anonymised |
| Raw incoming email | 30 days |
| AI conversation transcripts, encrypted | 90 days |
| Content flagged by Anthropic's safety systems | Up to 2 years at Anthropic |
| Devices and push tokens | While active. For a removed device, and for a Fairloco Kitchen device not used for 90 days, the details are deleted 90 days after removal or last use |
| Server logs | 7 days |
| Partner application that is not finished or never activated | Anonymised 12 months after the last activity |
| Register check results (YTJ, VIES) | Kept with the application |
| IBAN and bank name check of an applicant who is never activated | Deleted with the application |
If you leave checkout without paying, we delete the exact address, the phone number, the door code, the delivery note and the allergy note 24 hours after the checkout expires. Only the postal code stays.
Deleted data can remain in database backups for up to 35 days. When you delete your account we anonymise it, except where the law requires us to keep records.
Cookies and device storage
The public pages of Fairloco set no cookies. We do not use advertising or analytics cookies, tracking pixels or third-party analytics.
- fl.session_token: keeps you signed in on the partner portal and when you order. If you choose Keep me signed in when you sign in, it lasts 30 days and renews while you use the service. Otherwise it is removed when you close the browser, and you are signed out after 12 hours at the latest. Signing out removes it.
- fl.dont_remember: remembers that you did not choose Keep me signed in, so that your sign-in is not extended. It is removed when you close the browser.
- fl_lang: remembers the language you chose on the partner portal, for one year.
- fl_last_sign_in: only if you choose Keep me signed in. Remembers on this device which sign-in method you used last and a masked email address, for example j•••@example.com. It lasts 180 days and the page can read it. Signing in without the choice removes it, and you can remove it with Not you? on the sign-in page or with Sign out and forget this device.
- fl_cart: your basket while you order, for 24 hours.
- fl_addr: the delivery address you entered, for 30 days, so that you do not need to type it again.
- fl.device: a random identifier for this browser when you pay without an account, for 400 days. Your orders join your account if you later sign in on this device with the same email address.
- Fairloco Courier and Fairloco Kitchen keep a sign-in token on the device so that offers and orders reach you. On a personal device the app also remembers your last sign-in method.
- If you turn on notifications, your browser or device stores a subscription that lets us send them.
Your rights
You can ask for a copy of your data, correct it, delete it, restrict processing and move your data to another service. You can object to processing based on legitimate interest, for example to support with our AI assistant. You can withdraw consent at any time, which does not affect earlier processing. You can delete your customer account yourself on your account page. For everything else, email hola@fairloco.com. We answer within one month.
If you think we handle your data wrongly, you can complain to the Finnish Data Protection Ombudsman (tietosuoja.fi).