Privacy notice
Last updated 20 October 2026
Who we are
Tarlow is a private hire operator licensed by Oxford City Council. We are the data controller for the details described here — that is, we decide what is collected and why.
- Postal address: 11-12 Cornmarket Street, Oxford, OX1 3EX
- Email: info@tarlow.co.uk
- WhatsApp: message us
What we collect, and why
We collect only what a journey needs. There is no marketing list, no advertising network and no profiling.
Your name and home address
Our operator licence requires us to record the name and address of the person hiring the vehicle before the hiring begins, and to keep that record. We ask for it because we are obliged to, not because we chose to.
Lawful basis: legal obligation (UK GDPR Article 6(1)(c)), the obligation being Condition 2 of our Oxford City Council private hire operator licence.
Your telephone number and email address
The telephone number is how a chauffeur reaches you if you are not where you said you would be. The email address is where your booking confirmation is sent — from info@tarlow.co.uk, once your payment clears — and where we write if something changes.
Lawful basis: performance of a contract (Article 6(1)(b)).
Your journey
The collection and destination addresses, the date and time, the vehicle class, the fare and the quote the fare came from. If you are booking for someone else we also record the passenger’s name, so the chauffeur can hold the right name on the sign; a flight number, if you give one, is kept on the booking, printed on your confirmation and looked up by us before the car sets off.
Lawful basis: performance of a contract, and for the record of the journey itself, the same licence obligation as above.
What you tell us in “anything we should know”
The checkout has an optional box asking whether there is anything we should know, and suggesting a wheelchair, a child seat, skis, a cello, a dog, a passenger who needs a hand to the door. Whatever you write there is kept on the booking, and it is read by us and by the chauffeur who drives you before the car sets off. That is the purpose of the box: it decides which car is sent and what is in it, and a note nobody reads is worse than no note at all, because it also talks you out of mentioning it on the day.
Several of those examples say something about health or disability, which the law treats as a special category needing more care than the rest. So it is worth being plain about it. The box is optional and nothing is refused if you leave it empty; please tell us what the journey needs rather than why — that the chair folds, not what it is for. We do not ask for a diagnosis and would have no use for one.
Lawful basis: performance of a contract (Article 6(1)(b)). Where what you write concerns health or disability, we rely on your explicit consent under Article 9(2)(a), given by choosing to write it in an optional box that says what it is for. You can take that consent back at any time: ask us, and we delete the sentence from the booking. We can do that straight away, which is not true of anything else on the record.
Your payment
Card details are entered directly into Stripe’s own payment form and never reach our servers; we see only the outcome, the amount and the last four digits. So that a saved card works on your next booking, Stripe holds a customer record containing your name, email address and telephone number.
Paying with a wallet. If you choose Apple Pay, Google Pay, Revolut Pay, Amazon Pay, Alipay or WeChat Pay, that provider also processes your payment under its own privacy policy, and shares the outcome with our payment processor, Stripe. We receive the result of the payment, the amount and the method used. We never receive your card number or wallet login.
Your account
When a booking is paid, and only if the email address you gave does not already belong to an account, we open one for you so you can see that journey, and we copy across whichever of your name, telephone number and address you gave us so the next booking is already filled in. The way in is a single-use link inside your confirmation email; there is no password. If the address already belongs to an account we leave it alone and the booking simply stays unlinked, because an address typed into a form is not proof that you own it. You can ask us to delete the account at any time; see “Your rights” below for what happens to the booking record when you do.
Using the website
We set no advertising or analytics cookies and use no third-party analytics script, and nothing at all is stored on your device. Our servers use your IP address for a few seconds as a rate-limiting key, so that one visitor cannot exhaust the mapping and address-lookup services everyone else is using; it is not written to any database and not retained beyond that window. Stripe sets its own cookies within its payment frame to detect fraud, which are strictly necessary for taking a card payment safely.
We count how many pages are read, so that we can see how many people are using the site, roughly where in the world they are, and which language they read it in. Each count holds the page, the language, the website you came from if any, the town and country our host places the connection in, and whether it was read on a phone, a tablet or a computer. It holds no IP address, no cookie and no identifier of any kind — nothing is stored on your device and nothing joins one page to the next — so these are counts of pages read and not of people, and they cannot be traced to you. They are never passed to anybody outside the firm and are deleted automatically after six months. Our host also keeps its own server-side counts, which we see as totals.
When you ask the website for a price we keep a note of the journey itself, so that we can see which journeys people are asking for, where we are being asked to go that we do not yet serve, and whether our prices are being accepted. The note holds the collection and the destination as you gave them — the address you picked or the postcode you typed — the date and time you wanted the car, the prices we offered, and whether the quote was taken any further. It holds no name, no email address, no telephone number, no card details, no IP address, no cookie and no visitor identifier of any kind, so nothing in it joins one search to another, and nothing in it is ever used to contact you. It is never passed to anybody outside the firm, and it is deleted automatically after six months.
Lawful basis for the rate limiting and fraud prevention: our legitimate interests (Article 6(1)(f)) in keeping the service available and payments secure. Lawful basis for the count of pages read: our legitimate interests (Article 6(1)(f)) in knowing whether our own website is being used, which carries nothing that identifies anybody and nothing that is stored on your device. Lawful basis for the note of a journey: our legitimate interests (Article 6(1)(f)) in understanding what our own service is being asked for, which we have balanced against the fact that a full address can say something about a household — which is why the note carries nothing that identifies a person, is never used to contact anybody, is never shared, and is deleted after six months rather than kept. If you would rather we did not keep it for a journey you have asked about, write to us and we will remove it.
Who else sees it
We do not sell anything to anybody. These are the processors that handle data on our instructions, and the chauffeur who drives you.
- Your chauffeur — the passenger name, the collection and destination addresses, the time, the flight number if you gave one, and whatever you wrote in the “anything we should know” box, which is the whole reason for asking it. Never your card details; we do not hold them.
- Supabase — the database that holds the booking record, hosted in London.
- Stripe — card payments and refunds, and the customer record described above.
- Resend — delivery of the booking confirmation and any email we send you about a journey.
- Netlify — hosting of this website, and its own server-side visitor counts.
- Google Maps — the collection and destination addresses are sent to Google to suggest addresses as you type, to measure the route and to draw the map of it. Your name and contact details are not.
- postcodes.io — a postcode you enter is resolved to a set of coordinates so the journey can be priced.
To put the first of those exactly: a chauffeur who has an account with us and has been allocated your journey can read that booking’s record in full — which includes the name, address and telephone number of whoever hired the car, so that a driver can reach you if you are not where you said you would be. They can read no other booking, and they can change nothing on yours beyond reporting how it is going. Nothing in the running product allocates a journey to anybody, so in practice it is we who pass on what the driver needs for the day.
Some of these process data outside the UK. Where they do, the transfer is covered by the UK International Data Transfer Addendum or by adequacy regulations, and each provider’s own privacy notice sets out the detail.
We will also disclose a booking record to Oxford City Council or to the police where they are entitled to it — our licence requires us to produce these records on request, and that is one of the reasons they exist.
How long we keep it
The booking record — who hired the car, the address given, the journey and the fare — is kept for at least twelve months from the date of the booking, because our licence requires it. This is enforced by the database itself: a booking inside that window cannot be deleted, by us or by anyone.
After the twelve months we keep the record for no longer than six years, which is the period we may need it for tax and for any legal claim arising from the journey, and then delete it. Your account and the details on it are deleted whenever you ask.
The exception is the note you wrote in the “anything we should know” box, which we can clear from a booking at any time and will on request. It is deliberately not frozen with the rest of the record, because what you told us changes — the folding chair becomes a powered one, the child seat is no longer needed — and a record that could only ever hold the version that turned out to be wrong would send the true one back to a WhatsApp message nobody matches up in time.
Your rights
You have the right to ask for a copy of what we hold, to have it corrected, to have it erased, to restrict or object to how we use it, and to receive it in a portable form. Write to info@tarlow.co.uk and we will answer within one month.
One limit is worth stating plainly rather than burying: we cannot erase a booking record inside the twelve-month period described above, because we are required to keep it and the database will refuse. What we can do straight away is delete your account and unlink it from the booking, so the record stands as an operator record and nothing else about you remains. After twelve months the record itself can be erased on request.
There is no automated decision-making and no profiling. Prices are calculated by a published set of rules from the journey you enter, not from anything about you.
If you are unhappy with how we have handled your details you can complain to the Information Commissioner’s Office at ico.org.uk or on 0303 123 1113. We would rather you told us first, so we can put it right.
The Tarlow app (passengers)
Everything above applies to a booking made in the app as much as one made on the website. This section adds what the app itself does. We are the data controller for it, on the same terms as above.
What the app collects, and why
- Your account details — your name, email address, telephone number and postal address, the same details the website asks for, so that the next booking is already filled in. You can sign in with an email address, with Apple or with Google. If you use Apple or Google, they confirm your identity to us and tell us the name and email address you have chosen to share; we never see your Apple or Google password.
- Home and work places — the Home and Work shortcuts you save in the app are kept on your phone, not on our servers.
- Your location, only when you ask for it — if you choose to use your current location as the pickup, the app asks iOS for permission and reads your position while the app is open, to set the pickup point. It is not tracked, not recorded as a trail and not collected in the background. The position you confirm becomes the pickup address on the booking, like any address you type.
- Your booking and payment — as above. You pay through Stripe, including by Apple Pay or other wallets Stripe offers. Card details are entered into Stripe’s own payment sheet or your wallet and never reach us; we see only the outcome, the amount and the last four digits.
- A notification token — if you allow notifications, the app gives us a token that identifies your phone to the push service, so we can tell you your chauffeur has been assigned, is on the way or has arrived. It is removed when you sign out or delete your account.
- Messages with your chauffeur — once a chauffeur is on your booking you can message each other about that journey, for example where you are standing. The conversation closes two hours after the journey ends.
- Your rating — after a journey you can give one rating of one to five stars and tap a few short tags such as “On time”. It is read by us only, and not by the chauffeur.
- Add to calendar — if you tap this, the app asks permission to add the journey to your calendar. It can only add an entry; it does not read your calendar.
Lawful basis: performance of a contract (Article 6(1)(b)) for the account, booking, payment, notifications and messages, and our legitimate interests (Article 6(1)(f)) in knowing how our service is rated. Location is used only because you asked for it, for the purpose of setting the pickup. If you write something about your health or a disability in the “anything we should know” note, the explicit-consent basis described above applies in the app in the same way.
Who the app shares it with
- Your chauffeur — what is described under “Who else sees it” above for any journey allocated to them, which includes your name and the pickup, and the messages you exchange.
- Stripe — payment, as above.
- Google — the addresses you type, or the place you pick on the map, are sent to Google to suggest addresses, find the route and show the journey. Your name and contact details are not.
- Apple and Expo — notifications are delivered through Apple’s push service, using Expo’s service to send them. They receive your notification token and the short text of the notification.
- Apple and Google — only if you choose to sign in with them.
- Supabase — our database and sign-in service, hosted in London, which holds the account and booking records.
The app contains no advertising, no tracking and no analytics or crash-reporting software from anyone else. It does not ask to track you across other apps or websites, and nothing it collects is used for advertising.
How long we keep it
Your account details are kept until you delete the account. The booking record, including the message thread, the rating and the note on that journey, is kept for the periods set out under “How long we keep it” above: at least twelve months because our licence requires it, and no longer than six years. Messages and ratings are not used for anything other than that journey and the quality of the service.
Deleting your account in the app
Open the Account tab, choose Delete account and confirm. You will be asked for your password, or to sign in again with Apple or Google, so that nobody else can do it from your phone. Deleting the account removes your login, your profile (name, telephone number, postal address and company), your saved-card link and your notification token. The booking records we are required to keep stay, but are no longer connected to a login. An account cannot be deleted while a journey is still to come or has just finished; in that case write to us at info@tarlow.co.uk and we will help. You can also ask us by email at any time, and your other rights are the ones listed under “Your rights”.
Tarlow Drivers app (our chauffeurs)
This section is for the chauffeurs who use the Tarlow Drivers app. The app is not public; the office invites each chauffeur and there is no sign-up in it. It repeats, in the same words, the notice every chauffeur is shown and must read before any location is collected (version 4, 10 October 2026).
What the app collects
The chauffeur’s name, email address and mobile number; the badge number and its expiry, held by the office; a notification token so offers and messages reach the phone; the messages sent on a job; the events on each job (accepted, on the way, arrived, on board, complete); the record that the chauffeur read the location notice, with the version and the time; and, only while online, location.
Location: the chauffeur decides when the app knows where they are
There is a Go online button on the journeys screen. It is the only thing that starts location. While a chauffeur is online, the app sends their location to the office, including when the app is closed or the phone is locked. The office sees their live position on a map, and the route driven since they went online. While a chauffeur is offline, the app sends nothing and nothing is recorded: not a position, not a trail, nothing at all. Being signed in is not enough; a chauffeur who leaves the app signed in all week and stays offline cannot be located.
Go offline stops it straight away. Closing the app does not stop it; Go offline does, and a chauffeur does not have to sign out. The office cannot put a chauffeur back online; that is the chauffeur’s button and the database refuses anybody else who tries. While online, iOS shows its own location arrow at the top of the screen, and a blue pill when Tarlow is not on screen. If a chauffeur allows location only while using the app, nothing is sent while Tarlow is closed, but the office may not see them arrive and the app may not let them mark Arrived.
Why we collect it
So that when a job comes in we can offer it to whoever is actually nearest; so that we can tell a customer waiting for their car how far away it really is; and so that, if somebody disputes a waiting charge, there is a record of when the chauffeur arrived. From an hour before a pickup until the journey ends the position is more precise, so the app can tell the chauffeur really is at the pickup before they mark Arrived. The rest of the time it is rougher, about a street.
Lawful basis: our legitimate interests (Article 6(1)(f)), not consent. The button the chauffeur taps says “I’ve read this”, not “I agree”, because it acknowledges a notice and does not ask for permission we would then have to let them withdraw. They can object, as described below.
Who sees it
The office sees the live position and the route driven since going online, on a map. The customer on a job sees the chauffeur’s first name, the car, its registration and where it is, on their trip screen and tracking link, from 30 minutes before the pickup until the journey ends, and only for that job; never the route history. Other chauffeurs see none of it. It is kept in our database in London, behind the chauffeur’s login, and is not sent to anyone else unless the council, the police or an insurer asks for it and is entitled to it.
How long we keep it
Thirty days, and then it is deleted automatically. For those thirty days the office can look back over the routes driven while the chauffeur was online. The only thing kept longer is the part of a particular day that a specific dispute is about, and only while that dispute is live. While offline there is nothing to keep, because nothing was collected.
What we will not do with it
We will not use it to judge how a chauffeur works: not to score them, not to rank them against each other, not to decide what they are paid. We will not count their hours with it; how long a chauffeur chooses to be online is their business and nothing in our system adds it up. Nothing is being built on top of it, and if that ever changes chauffeurs will be told before it does, not after.
Other data in the driver app
The notification token, the messages on a job, the badge details and the job events are used to run the work: to deliver offers, to let the chauffeur and the customer or office talk about a journey, and to meet our licence conditions. The app contains no advertising, no tracking and no analytics or crash-reporting software from anyone else. Chauffeurs are removed from the app by the office rather than from within it.
What a chauffeur can do about it
- Ask to see it. We will give them their own location records in a form they can read, at no cost.
- Ask us to stop. They can object to us doing this at all. If they do, we have to stop unless we can show a serious reason why we cannot, and we have to look at it properly rather than assume the answer.
- Ask us to correct it, if it says they were somewhere they were not. Phone signals wander, especially in car parks and in town, and a single dot on a map is not proof of anything. We will not conclude anything from a trail without asking the chauffeur first.
- Complain: to us first, so we can fix it, at info@tarlow.co.uk, and if that does not work to the Information Commissioner’s Office at ico.org.uk or on 0303 123 1113. They do not need our permission and it will not be held against them.
In one line: online, we can see where a chauffeur is and the route driven, and we keep it for thirty days; offline, we cannot see them and nothing is recorded. They hold the switch.