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

3. Information Collected Automatically

4. Camera, Photos and Notifications

You can set a profile picture, either by taking a photo or by choosing an existing one.

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:

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 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:

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:

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

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.