Fairgo
Last updated: 18 August 2026
This policy covers the Fairgo: Book a Taxi Ride and Fairgo Driver: Earnings iOS apps and this website. It explains what data the apps handle and which companies receive it. If something here is unclear, ask us — the contact details are at the bottom.
Who is responsible for your data
The data controller decides why and how your data is used, and is the party you exercise your rights against. For Fairgo that is Hugo Moriceau, who operates Fairgo as an individual. Send a rights request, a question or a data-protection complaint to hugomoriceau@icloud.com; that address reaches the controller and a person answers it.
There is no company. Fairgo is not incorporated, so there is no registered name, no legal form, no registered office, no commercial-register number and no VAT number to give you — not because they are withheld, but because they do not exist. That is not a gap in this policy: under the GDPR a natural person who decides why and how personal data is processed is the controller in exactly the same way a company would be, and carries the same obligations. Article 13 asks for the controller's identity and contact details; a name and an address a person reads are both, and they are in the paragraph above. If Fairgo is ever incorporated, the entity's details will replace this paragraph and the date at the top of the page will change with them.
Three things a privacy policy often lists and Fairgo does not have. Their absence is itself a fact about how Fairgo is run, so it is written down rather than left out:
- No EU Article 27 representative. Article 27 requires one only of a controller established outside the EU and the EEA. None has been appointed. If the controller's place of establishment ever moves outside the EU/EEA, a representative will be named here before it does.
- No Data Protection Officer. Article 37 requires one where the core activity is large-scale systematic monitoring or large-scale processing of special-category data. Fairgo is one person and its processing is not at that scale today, so none is appointed. That is a judgement rather than an exemption, it is reviewed as the service grows, and if it changes a DPO will be appointed and named here. In the meantime the address above is the route for anything you would take to a DPO.
- No CNDP declaration. Moroccan Law 09-08 requires processing to be declared to the CNDP, which issues a receipt number. No declaration has been filed and there is no receipt number to publish. Morocco is open in the app's market data, but neither app has been released, so there is no Moroccan rider or driver whose data is being processed; the declaration will be filed, and its receipt number published in this list, before there is.
What we collect
- Account details. Your name, your phone number and your email. Signing in with a one-time code verifies your phone number, which is also what lets your driver or rider reach you during a trip. If you use Sign in with Apple and choose to hide your address, we only ever receive Apple's private relay address.
- Location. Riders: your location when you open the app, to work out which market you are in and to set your pickup. Drivers: your location while you are online, so riders can follow the vehicle and so we can offer you nearby trips. Drivers' location is not collected while offline.
- Trip information. Pickup, destination, route, fare and trip history.
- Documents (drivers only). Licence, identity and any documents your market requires, used solely to verify you may drive.
- Photos. Only the ones you choose to attach — a profile picture or a document. We do not browse your library.
- Diagnostics. Crash and error reports, so we can fix faults.
Why we are allowed to use it
Under the GDPR every use of your data needs a legal basis. This is ours, purpose by purpose. Where local law gives you an equivalent right — Morocco's Law 09-08, for example — the same table describes the purpose and the recipients.
| Purpose | Data | Legal basis (GDPR Art. 6) |
|---|---|---|
| Creating and running your account | Name, email (or Apple's private relay address), device push token | Performance of a contract — Art. 6(1)(b) |
| Working out which market you are in, and whether Fairgo is allowed to operate there | Your approximate location at launch | Performance of a contract — Art. 6(1)(b) |
| Matching a ride, setting the pickup, and letting the rider follow the car | Rider pickup and destination; driver location while online | Performance of a contract — Art. 6(1)(b) |
| Checking a driver may lawfully carry passengers | Licence, identity and the documents the market requires | Legal obligation — Art. 6(1)(c); and performance of a contract — Art. 6(1)(b) |
| Charging the 1% technology fee and keeping the records tax law requires | Completed trips, fares, fee and payment records | Legal obligation — Art. 6(1)(c) |
| Safety: the verification PIN, ratings, and acting on reported incidents | Trip records, ratings, reports you send us | Legitimate interests — Art. 6(1)(f): keeping riders and drivers safe from each other |
| Fixing faults | Crash and error reports | Legitimate interests — Art. 6(1)(f): keeping the app working |
| Marketing messages | Email address | Consent — Art. 6(1)(a). Off unless you switch it on, and withdrawable at any time. |
| Answering an email you send us | Your email address and whatever you choose to put in the message | Legitimate interests — Art. 6(1)(f): answering someone who has written to us |
Who else receives your data
We name every one of them. This list is part of the policy, not a summary of it.
| Who | What they receive | Why |
|---|---|---|
| Stripe | Payment details and amounts | To take card payments and pay drivers. Fairgo never sees your full card number and never holds your money. |
| Apple | Sign in with Apple identifiers; push notification tokens and message content | To sign you in and to deliver ride notifications. |
| Nobody — the map is ours | Nothing leaves Fairgo to draw the map | Until September 2026 the apps fetched map tiles from CARTO, which meant your IP address and the area you were looking at reached a company you had never heard of. Fairgo now builds and serves its own map, from OpenStreetMap data, on its own server. One fewer party sees where you are. |
| OpenStreetMap Foundation (Nominatim) | Addresses you type when searching, and your IP address | To turn an address into coordinates and back. |
| OSRM (project-osrm.org) | Pickup and drop-off coordinates | To calculate the driving route and estimated time. |
| Contabo (Germany) | Everything above, as our hosting provider | Our servers and database run there. |
| Apple Maps / Google Maps | The destination address, only when you tap "navigate" | To hand the trip to your navigation app of choice. |
Between a matched rider and driver we share only what the trip needs: the driver's first name, vehicle and plate; the rider's pickup point and first name.
Where your data goes
The database and the servers that run Fairgo are in Germany, inside the EU, at Contabo. Your trip and account data lives there.
Contabo aside, these recipients can be reached outside the EU/EEA, so sending them data is an international transfer:
- Stripe — card payments and driver payouts.
- Apple — Sign in with Apple, and push notifications through APNs.
- OpenStreetMap Foundation (Nominatim) — turning a typed address into coordinates and back.
- OSRM — calculating the driving route and the estimated time.
Each of those transfers takes place under that provider's own data-processing agreement.
What covers those transfers. Fairgo has negotiated no bespoke clauses with any of these providers. Each is used on the terms it publishes, and it is that provider's own data-processing addendum — accepted by using the service — that names the mechanism it relies on for a transfer out of the EEA: an adequacy decision, the EU–US Data Privacy Framework, or the European Commission's Standard Contractual Clauses. We do not restate provider by provider which of the three applies, because that would mean copying a document each of them can change without telling us, and a stale mechanism in a privacy policy is worse than none. Ask us about a specific recipient and we will point you at the clause in its current terms.
Morocco. Law 09-08 requires the CNDP's authorisation before personal data leaves Morocco. It has not been applied for and has not been granted. Morocco is open in the app's market data, but neither app has been released, so no Moroccan rider's or driver's data has been processed or transferred; the authorisation will be in place before any is.
What we never do
- We do not sell your personal data.
- We do not track you across other companies' apps or websites.
- We do not use your data for third-party advertising. There is no advertising SDK in either app.
How long we keep it
| What | How long |
|---|---|
| Detailed location trace of a completed trip (the metre-by-metre path) | 90 days after the trip, then deleted automatically by a job that runs every night. Deleting your account erases the traces of every trip you took or drove straight away, without waiting for the 90 days. |
| Account details (name, email, push tokens, saved places) | While your account is open. Deleting your account removes them. |
| In-trip messages, crash reports, saved places, scheduled rides | Deleted when you delete your account. |
| Driver documents (licence, identity, insurance) | While the driver account exists, and no longer. Deleting the account erases them at once — the document records and the uploaded files are both deleted, not archived. No statutory retention period is applied to them today. If a market's transport law turns out to require Fairgo to be able to show afterwards that a driver was checked, that period will be named in this row before it is applied. |
| Trip and invoice records (the ones tax law requires) | Kept after account deletion, detached from your name: the profile row is anonymised and the financial record survives, because it has to. There is no fixed number of years to publish here, and nothing in the system deletes an invoice on a schedule. The rule applied is the qualitative one: a financial record is kept for as long as the tax and commercial law binding the operator requires, is used for nothing else once the account is gone, and is not linked to a living person. The exact period is under review and will be stated here as a number once it is settled. |
Your rights
You can access, correct, export or delete your data, object to processing based on our legitimate interests, ask us to restrict processing, and withdraw any consent you have given. Deleting your account is built into both apps — Account → Delete account. It erases your personal data and anonymises what is attached to records the law makes us keep, such as invoices; those records stay, but they stop pointing at you. If you prefer, email us and we will do it for you.
You can also complain to a data-protection authority: in the EU, the supervisory authority of the country you live or work in; in Morocco, the CNDP. We would rather you told us first, but it is your right either way.
Children
Fairgo is not for anyone under 18 and we do not knowingly collect their data.
Changes
If this policy changes materially we will say so in the apps. The date at the top always reflects the current version.
Contact
Questions, requests, or a data-protection complaint: hugomoriceau@icloud.com.