Privacy Policy
Drivingo AI Ltd (“Drivingo”) is committed to protecting your privacy.
Effective Date: 2 November 2026
1. Introduction and Scope
This Privacy Policy explains how we collect, use, share, retain and delete your information when you use the Drivingo mobile application (the “App”) and our website https://drivingo.co.uk (the “Website”). Together we call these the “Services”.
The Services are owned and operated by Drivingo AI Ltd, a company registered in England and Wales, which is the data controller for the personal data described here. We process personal data in accordance with the UK GDPR and the Data Protection Act 2018. For any privacy question, or to exercise any of the rights in section 12, contact us at support@drivingo.co.uk.
2. Information You Give Us
- Account details — your name and email address. If you sign in with Google or with Apple, we receive the account identifier and the email address those services release to us. If you use Apple’s private relay address, that relay address is what we hold.
- Your driving test date, where you choose to enter it, so the App can pace your study plan.
- A profile picture, if you add one (see section 4).
- Messages you send to the AI coach, and anything you tell it about yourself that it saves in order to be useful later — for example how you are finding a topic, or what you are worried about before your test (see section 5).
- Your study activity — quiz and mock test answers, scores, topic progress and streaks.
- App preferences — such as theme, language, and which question bank you are studying.
- Feedback you send us — if you are signed in and have an active subscription, you can choose to write to us from the feedback form in the App, up to three notes per account. Each note holds the email address you enter (filled in from your account, which you can change; we do not verify it) and your message, up to 1,000 characters; you can leave that address empty if you do not want a reply. We store it with your account identifier, the App version, your platform, the question bank you have selected, your subscription plan and the time you sent it. We use it to read what you think of Drivingo and to reply to you. Notes are stored in our Firebase database (section 7) and are deleted when you delete your account (section 11). We also email each note to our own support inbox, which is where we read it, using Resend as our email provider (section 7); your address is set as the reply address, or, if you left it empty, no reply address is set. That email carries your message, the details above and a short summary of your account taken from our records — the email address and sign-in method on your account, your name, your subscription status and when it expires, how many AI coach sessions you have left, when your account was created, the question bank you have selected and your account identifier. It never contains your answers, your scores or progress, anything from your AI coach conversations, analytics or device identifiers, your payment records or your IP address. Section 10 explains how long that copy is kept. The “How is Drivingo doing?” thumbs up or thumbs down is not stored with your note; it is recorded only as a usage event (section 3).
- Messages you send us through “Contact us” — in the App, Profile → Help & contact answers common questions and then offers a “Contact us” form. Anyone can use it, whether or not you are signed in and whether or not you subscribe. Your email address is required, because it is the only way we can answer you, and your message can be up to 1,000 characters. We store it with your account identifier, the App version and build, your platform and operating system version, the question bank you have selected, your subscription plan, and whether the email to our support inbox went out. You can send up to three messages in any seven days, counted against both your account and your email address. We use it to answer you and for nothing else. The message is emailed to our own support inbox through Resend (section 7), with your address as the reply address so that we can reply by hand, and that email carries the same short account summary described above, with the same exclusions. If you are not signed in there is no account to summarise, so it says only that you are not signed in. Section 10 explains how long these are kept, and section 11 what deleting your account removes.
3. Information Collected Automatically
- Usage and interaction events — which screens you open, questions answered, quizzes started and completed, and similar in-app actions, together with the device and app information that accompanies them (device model, operating system version, app version, language, approximate region) and your IP address.
- Crash and error diagnostics — when the App fails, we collect the error, the device context around it and a technical trace, so we can fix it.
- Quality and anti-fraud signals: from version 2.0.2 of the App, the first time it opens on a device it sends our server, once, your platform (Android or iOS) and the App version. On Android it also sends, when Google Play has them, two times from the Google Play Install Referrer (section 8): when the store link was tapped and when the install began. On iOS it sends no times and no extra identifier. Our server stores this once, in a record held against your Drivingo account identifier (section 6), together with whether the App’s genuine-copy check (section 15) passed on that request, whether the request came from a data centre rather than an ordinary home or mobile connection, and, on Android, the number of seconds between the tap and the start of the install rather than the two times themselves. To tell whether a request came from a data centre we compare its IP address with the address lists that cloud hosting providers publish; the address itself is not stored, logged or kept in any form. From these our server marks whether the install looks automated or fraudulent. We also use the usage events above to count installs that were opened once and never used again. We use all of this only to tell genuine installs from fake ones in our paid advertising, so that we do not pay for, or count, installs that are not real people. The result stays on our server: nothing is sent back to your device, nothing in the App changes, it is not used to make decisions about you, and it has no legal or similarly significant effect on you. The record is kept in our Firebase database (section 7) for as long as your account exists, and is deleted with it (sections 10 and 11).
- Server request logs: when the App contacts our servers, for example to run an AI coach lesson, save your progress or send us a message, Google Cloud, which hosts those servers (section 7), records the request: your IP address, the time, which of our services was called, whether it succeeded and how long it took, and the user agent (the App and device software that made the request). Our own log lines for the same request may include your Drivingo account identifier, so while the logs are kept an IP address can be matched to an account. We use these logs only to keep the Services working and secure and to investigate faults and abuse. The install check described above is the one exception: its requests are left out of these logs, so its IP address is not logged. Section 10 says how long the logs are kept.
- Subscription and purchase state — whether you have an active subscription, how many AI coach sessions you have left (including any you bought as a one-off top-up), and the purchase history our payment processor reports to us. Our subscription processor also holds a record for every install, whether or not you ever subscribe (see sections 6 and 7).
- Website analytics — see section 9.
4. Camera, Photos and Notifications
You can set a profile picture, either by taking a photo or by choosing an existing one.
- Camera: the App asks for camera permission only at the moment you tap “Take Photo”, and only for that purpose. You can decline, and the rest of the App works normally.
- Photo library: we use your device’s own system photo picker, which hands the App only the single image you select. The App never receives access to your photo library, and does not ask for it.
- Microphone: the App never requests microphone access and cannot record audio.
The picture you choose is stored as your profile picture and is deleted when your account is deleted (section 11).
Daily study reminders. The App can send you one study reminder a day. It is off until you turn it on, and three separate things must all be true before we hold anything for it: you switch Daily study reminder on in the App, you are signed in to a Drivingo account, and you allow notifications when your device asks. The notification permission prompt appears when you tap that switch, never at launch, and if you decline it the rest of the App works normally. If you have not turned the reminder on, none of what follows applies to you.
When all three are true, we store against your account:
- A notification registration token — a device identifier created by Firebase Cloud Messaging, Google’s notification delivery service. It is what allows a message to reach that particular device, and it is stored per device, so a phone that has never had reminders turned on has no token held for it. It is not an advertising identifier and it tells us nothing about you beyond where to deliver a reminder.
- Your device’s timezone — the timezone name your device is set to, such as “Europe/London”, kept beside the token so a reminder arrives at the hour you picked in your own time rather than ours. It is a setting we read from your device, not a position: the App does not read your location for this, and we do not use the timezone to work out where you are.
What they are used for, and nothing else. Our server sends one templated reminder a day, through Firebase Cloud Messaging, at the hour you chose, on days you have not studied. That is the only message these details are used for — no marketing, no other notifications. Google receives the token as our service provider, in order to deliver that message; it is not used for advertising and it is never shared with advertisers or data brokers. This is not tracking, and section 8 applies to it in full.
Turning it off, and removing it. Switching the reminder off in the App stops the reminders. Signing out removes that device’s token from your account, so a phone you hand on cannot keep receiving reminders meant for you. Deleting your account removes the token and the timezone along with everything else (section 11).
5. The AI Coach and Third-Party Model Providers
Drivingo’s coach is powered by large language models operated by third parties, including OpenAI and Anthropic, and we may add or change providers as the technology moves. This means:
- The messages you send to the coach are transmitted to those providers in order to generate a reply. This is not anonymous aggregate data — it is the text you wrote.
- To keep the coach useful across sessions, we also send it relevant context we hold about you: your study progress and the notes it has saved about how you are getting on. Those notes can be personal, because you decide what to tell it.
- We keep engineering records of these exchanges — including the full context sent to the model — so we can debug wrong or unsafe answers and measure quality. These records are held in Langfuse, hosted in the EU.
The coach can be wrong. Nothing it says is legal advice or an official DVSA position — always check anything that matters against the Highway Code or GOV.UK.
6. Subscriptions, Purchases and Payments
Subscriptions, and the one-off packs of extra AI coach sessions you can also buy in the App, are sold and charged by Apple (App Store) and Google (Google Play). We never see or handle your card details. We use RevenueCat as our subscription processor: it receives your purchase and renewal events from the stores and tells us whether your subscription is active and which purchases you have made, so the App can unlock what you have paid for. We keep the number of AI coach sessions you have left with your account. RevenueCat and the stores hold the record of your purchases as payment processors in their own right — see section 11 for what this means when you delete your account.
Who this covers: everyone who installs the App, not only subscribers. RevenueCat is set up the first time the App starts — before you sign in, before you see a price and whether or not you ever subscribe — so a RevenueCat record exists for you from that first launch. If you never subscribe, that record is still there; it simply never gains a purchase. RevenueCat holds that record against your Drivingo account identifier — the same identifier our own systems use for your account, and not your name or email address. Before you sign in, that is the identifier of the anonymous account the App creates for you at first launch; when you do sign in, the same record carries over rather than being replaced. It carries your app analytics identifier, your subscription state, and, on iOS, your app-tracking setting, the campaign attribution token described in section 8, and your device’s identifier for vendor. That last one is an identifier Apple gives to apps from the same developer: it is the same across Drivingo’s apps on one device, it identifies you to nobody else, and it is not your advertising identifier. It is set on iOS only, at first launch and again when the App keys the record to your account, and it is what lets RevenueCat match a subscription back to the install it came from. On Android, the record instead carries the campaign the install came from — its source and, where the link had them, the campaign name and search keyword — read from the Google Play Install Referrer described in section 8. It is set up at first launch rather than at the point of purchase because Apple’s attribution token expires about 24 hours after an install, so waiting for a purchase would lose the campaign that a subscription came from.
7. Who We Share Information With
We do not sell your personal data. We share it only with the service providers that make the Services work, with legal authorities where we are legally required to, and as part of a business transfer such as a merger or acquisition. Our providers are:
- Google (Firebase, Google Cloud and Google Analytics) — sign-in, database, file storage, the servers the App talks to and their request logs (section 3), and product analytics. Our analytics events are also exported to Google BigQuery, where we retain them at event level rather than only as aggregate reports. We also use these events to measure our Google Ads campaigns — which of them lead to people signing up, using the AI coach and making a purchase — and Google Ads uses that to decide where our ads are shown. Your name and email address are not part of these events. If you turn on the daily study reminder, Firebase Cloud Messaging also delivers that reminder to your device and receives the registration token described in section 4; it does so as our service provider, and that token reaches no advertising platform.
- Sentry (EU region) — crash and error reporting. Sentry receives your Drivingo account identifier — the same identifier described in section 6, and not your name or email address — alongside the crash and error diagnostics described in section 3, so that when you contact us about a problem we can find the error reports belonging to your account. Nothing else about you is attached to a report: no name, no email address and no advertising identifier, and before you sign in the identifier is the one belonging to the anonymous account the App creates at first launch or, for a crash in the first moments after install, a random identifier for that installation. Sentry also derives an approximate, city-level location from the IP address a report is sent from; that happens on Sentry’s own servers once the report arrives, not in the App.
- Langfuse (EU region) — AI coach quality and debugging records, as described in section 5.
- Expo — delivery of updates to the App. Each time the App starts it asks Expo’s servers whether an update is available, sending a random identifier for that installation of the App, the App and platform version, and your IP address. Expo does not receive your Drivingo account identifier, your name or your email address.
- Resend (EU region) — email delivery for our support inbox. When you send a feedback note or a message through “Contact us” (section 2), Resend delivers that one email from us to us, and receives what the email contains in order to deliver it. Resend is not used to send you anything: the App and the Website send you no email, and any reply you get comes by hand from our support inbox.
- RevenueCat, Apple and Google — subscription and payment processing. RevenueCat also receives the install attribution described in section 8, and holds a record for every install rather than only for subscribers (section 6).
- OpenAI, Anthropic and other model providers — the AI coach, as described in section 5.
- Microsoft Clarity — heatmaps and session recordings on the Website only, and only if you accept analytics cookies (section 9). Clarity is not used in the App.
Some of these providers are outside the UK. Where personal data is transferred internationally, we rely on UK adequacy regulations, or on Standard Contractual Clauses with the UK International Data Transfer Addendum, together with appropriate technical safeguards.
8. Advertising Identifiers and Tracking
The App does not track you across other companies’ apps or websites. Specifically:
- On iOS, the App never shows the “Ask App not to Track” prompt and never collects your advertising identifier (IDFA). There is nothing to opt out of, because the identifier is never requested or read.
- On Android, the App does not collect your Google advertising ID.
- To understand which campaigns bring people to Drivingo, we use the privacy-preserving attribution the platforms provide — Apple’s AdServices and SKAdNetwork on iOS, and the Google Play Install Referrer on Android. These tell us the campaign an install came from; they do not identify you to advertisers. On Android, when you sign in we also store that campaign — its source, and the campaign name and keyword where there are any — with your account, so we can see which campaigns bring people who keep studying. It is deleted with your account (section 11). From version 2.0.2 of the App, on Android, we also read from the Install Referrer when the store link was tapped and when the install began, and use them only for the install check in section 3. Nothing is read for it on iOS.
- We never put your email address or user ID into an advertising platform.
9. Cookies and the Website
The Website uses a consent banner. Analytics cookies — Google Analytics and Microsoft Clarity — load only after you accept them. If you decline, Google Analytics sends cookieless measurement signals only and Microsoft Clarity does not load at all. You can change your choice at any time with the “Cookie settings” link at the bottom of every page, which brings the banner back.
If you arrive from one of our Google or Microsoft ads, the Google Play links on the page you land on carry a reference to that ad to Google Play, so we can tell which ad led to an install; it is never passed to the App Store. If you arrive from one of our Meta ads (on Facebook or Instagram), or through one of our own tagged links — from our Instagram or TikTok, for example — the store links carry that ad’s or link’s channel name and campaign name to both Google Play and the App Store, so we can count which of our ads and posts lead to downloads. If you arrive from an AI assistant — ChatGPT, Perplexity, Gemini, Claude or Copilot — the store links carry that assistant’s name in the same way, so we can count how many downloads they lead to. We read only which assistant sent you, nothing else about your visit. These are names or numbers we set, not details about you, and our website analytics record the same channel and campaign when you tap a store link or the download page opens. We send nothing about you to Meta. On the page you land on, none of this stores anything on your device. If you accept cookies, we also keep it in your browser for the rest of your visit so links on other pages carry it too — it is deleted when you close the tab or decline.
10. How Long We Keep Your Information
If you stop using Drivingo, we delete the personal data held in your account after 24 months of inactivity. We chose 24 months because a DVSA theory test pass is valid for two years, so a learner returning after that long starts over in any case and their old history is of no further use to them. Deleting sooner would punish the many people who fail, retake months later, or come back to Drivingo a year on, and find their history gone.
Inactivity means exactly that: no sign-in, no automatic renewal of your sign-in, and no activity in the App for 24 months. This applies to accounts you have signed in to. Two kinds of account are not deleted this way. The first is an account with an active subscription: we check our own records and ask our subscription processor, and if either says your access is live — or cannot tell us — we keep the account. The second is the anonymous account the App creates before you sign in, which a separate clean-up covers: it is deleted after 30 days of inactivity. An anonymous account with a subscription purchase recorded against it is kept, even if that subscription has since ended.
When the 24 months do pass, we remove the account in exactly the same way as if you had deleted it yourself (section 11), with one exception: the answer history carried over from the previous version of Drivingo is kept until that older app is retired, because that app still uses it and it is stored under your email address rather than under your account. If you delete your account yourself, that history is deleted with it.
Some information is kept on different clocks, and is not part of your account history. The AI coach engineering records described in section 5 are deleted automatically and kept no longer than 30 days — they include the text of your lessons, so they are not held indefinitely. Crash diagnostics are kept only as long as we need them to investigate faults and abuse, and are then deleted. Server request logs (section 3) are deleted automatically after 30 days. Usage events (section 3) carry your account identifier and are kept as event-level history in Google BigQuery (section 7). We have not yet set an automatic deletion period for them; until we do, they stay until we remove them, and you can ask us to delete yours at any time (section 12). Records we are required to keep by law, such as transaction records for tax purposes, are kept for the period the law specifies.
Messages you send us — feedback notes and messages sent through “Contact us” (section 2) — reach us in two places, on two clocks. The copy stored in our database follows the account rules above and section 11. The copy in our support inbox, and any reply we sent you, stays there until you ask us to delete it (section 12) — a reply quotes your message, so the two go together. Deleting your account does not reach that copy: it is email we have already received (section 11).
If you used “Contact us” without signing in, there is no account to delete, and we have not set a period for the stored copy of that message; it stays in our database until we remove it. You can ask us to delete it at any time using the rights in section 12.
We may keep anonymised, aggregated statistics — for example how difficult a particular topic is across all learners — indefinitely. These contain nothing that identifies you and are not personal data. One of them is a daily count of installs by platform and by which install checks (section 3) they failed, which we add to when the clean-up of unused anonymous accounts deletes an install’s record.
11. Deleting Your Account
You can delete your Drivingo account at any time in the App, from Profile → Manage account → Delete account, or — if you no longer have the App — by emailing support@drivingo.co.uk from the address on your account.
What deletion removes. We delete the personal data held in your Drivingo account — in our database, our file storage and our sign-in system — including: your learning profile and study progress; your quiz and mock test results; the notes the AI coach has saved about you and the record of your conversations held in our own database; your app preferences; your subscription entitlement records held by us; your profile picture; the feedback messages you have sent from the App and the messages you have sent us through “Contact us” from that account (section 2); the notification registration tokens for your devices and the timezone stored with them (section 4); on Android, the record of which campaign your install came from (section 8); the record of the install checks made when the App was first opened (section 3); any answer history carried over from the previous version of Drivingo; and your sign-in account itself. Nothing on that list is archived in the background — where we say deleted, we mean deleted. What deletion does not reach is set out below.
You do not have to delete your account to remove a reminder token. Signing out removes that device’s notification registration token from your account, and switching the daily study reminder off stops the reminders (section 4).
What deletion does not remove, and why. Your purchase record is held by Apple or Google and by RevenueCat in their capacity as payment processors. We deliberately do not destroy it: it is the record that you paid, and erasing it would destroy your proof of purchase along with our accounting history. It is retained under those companies’ own policies and ours, separately from the account data we delete.
The RevenueCat record described in section 6 is not deleted either, and it exists whether or not you ever subscribed. It is held against your Drivingo account identifier rather than against your name or email address, and if you did subscribe it is the same record that holds your proof of purchase.
The AI coach’s engineering records are not deleted one by one. The quality and debugging records described in section 5 include the text of your lessons and carry your account identifier. Deleting your account does not reach into them individually; they expire instead on the 30-day clock in section 10, and are then gone.
Server request logs are not deleted one by one either. The logs described in section 3 can carry your account identifier and your IP address. Deleting your account does not reach into them individually; they expire instead on the 30-day clock in section 10, and are then gone.
Usage events and crash reports are not deleted with your account. Both carry your account identifier (sections 3 and 7). Usage events stay in Google Analytics and BigQuery, and crash reports in Sentry, on the clocks in section 10. You can ask us to delete them (section 12).
The copies in our support inbox are not removed either. When you send a feedback note or a “Contact us” message, it also reaches us as an email (section 2). Deleting your account removes what we store in our database, but not an email we have already received, and not a reply we have already sent you. They stay until you ask us to delete them (section 12). If you sent a message through “Contact us” while signed out, account deletion does not cover the stored copy of it either, because there is no account it belongs to — ask us and we will delete it (section 12).
Deleting your account does not cancel your subscription. Subscriptions are managed and cancelled through your App Store or Google Play account settings, not by us — please cancel there first, or you will continue to be billed.
12. Your Rights
Under UK data protection law you have the right to access your personal data, to have it corrected, to have it erased, to restrict or object to how we process it, and to receive a copy of it in a portable format. Where we rely on your consent, you can withdraw it at any time, which does not affect processing carried out before you withdrew it.
To exercise any of these rights, email support@drivingo.co.uk. If you are unhappy with how we have handled your data, you can complain to the UK Information Commissioner’s Office at ico.org.uk/make-a-complaint, though we would appreciate the chance to put it right first.
13. Legal Basis for Processing
- Contract — providing your account, your study progress, the AI coach and your subscription.
- Consent — analytics and session-recording cookies on the Website, and any marketing email you opt in to.
- Legitimate interests — keeping the Services working and secure, diagnosing crashes, understanding which campaigns bring people to Drivingo, detecting fraudulent and automated installs so that we do not pay for advertising that reached no real person (section 3), and understanding in aggregate how the product is used so we can improve it.
- Legal obligation — where the law requires us to keep or disclose information.
14. Children’s Privacy
The Services are not intended for anyone under 16, and we do not knowingly collect their data. If we learn that we have collected personal data from a child under 16, we will delete it. If you believe a child has given us their data, contact us at support@drivingo.co.uk.
15. Security
We use encrypted connections, access controls and managed cloud infrastructure to protect your data, and our access rules are written so that one user’s account can never reach another’s. To keep our servers from being used by anything other than the real App, the App proves it is a genuine copy using Apple’s App Attest and DeviceCheck on iOS and Google Play Integrity on Android; these check the App and the device, not you. No system is ever completely secure, but if a breach affects your rights we will notify you and the Information Commissioner’s Office as the law requires.
16. Changes to This Policy
We may update this policy as Drivingo changes. When we do, we update the effective date at the top of this page, and we will tell you in the App or by email before any change that materially affects your rights takes effect.