Privacy policy
Last updated 5 October 2026
1. Who we are
LicencePath (“we”, “us”) provides an app that helps you prepare for the UK driving licence - the DVSA theory test, hazard perception and the practical test. We are the data controller for the personal data described here. We are not affiliated with the DVSA or DVLA.
2. What data we collect
- Account data: your email address and authentication details (handled by our auth provider).
- Profile & onboarding: your name, country, licence category, target test date, provisional status, transmission preference, study pace and language.
- Learning data: your practice attempts, mock results, hazard-perception timings, readiness scores, flashcard progress, driving-practice logs and trip recordings you choose to make.
- Driving licence number: if you add your provisional or full licence number (for example when you apply for or exchange a licence), we store the full number in your profile. We use it only to show it on your test booking checklist and to fill the “Copy my details” button you use on GOV.UK. In the app, only you can see it. We never send it to the AI coach or to analytics.
- Booking & monitoring data: if you use cancellation monitoring you may give us your DVSA booking reference, the last 3 characters of your driving licence and your current test date. We use these only to check GOV.UK for earlier dates on your behalf.
- Location: a base postcode or approximate location you provide, used to find nearby test centres and instructors.
- Instructor data (instructors only): your ADI/PDI number, vehicle, rates, availability, service area and CPD records.
- Coaching messages: questions you ask the AI coach (processed to generate a reply; chat history is held in your browser session and not stored on our servers). If you turn voice on, the reply text is sent to our voice provider to be read aloud. If you speak your question, your browser’s own speech service turns it into text.
- Records your instructor keeps: if your driving instructor or school keeps lesson records about you on LicencePath, they decide what is kept. See the pupil privacy notice.
- Website enquiries: if you contact an instructor through their LicencePath website, your message and contact details go to that instructor. The website assistant uses our AI provider to reply.
- Payment data: if you subscribe, our payment processor handles your card details - we never see or store your full card number.
- Technical data: basic device and usage information needed to run the service securely.
3. Why we use it, and our legal basis
- To provide the service (performance of a contract): run your account, save your progress and show your readiness.
- To personalise your learning (legitimate interests): adapt practice to your weak areas and power the AI coach and the “what next” recommendations.
- To take payment (performance of a contract) where you subscribe.
- To keep the service secure and improve it (legitimate interests).
4. Who we share it with
We use trusted service providers who act on our instructions. They are listed, with what each one does, in the next section. Analytics providers are used only if you accept analytics cookies, and analytics events never include your name, email, licence details or anything you type. Your coaching questions are sent to the AI provider only to produce your answer. We never send your licence number to the AI provider. We do not sell your personal data.
5. Where your data is stored
Our main database is hosted in London, United Kingdom (Supabase). To run LicencePath we use service providers, some of which process personal data in the European Economic Area or the United States. When personal data leaves the UK we protect it by one of the following:
- sending it to a country the UK recognises as adequate (including the EEA)
- sending it to a US organisation certified under the UK Extension to the EU-US Data Privacy Framework (the “UK-US data bridge”)
- using the UK International Data Transfer Addendum to the EU Standard Contractual Clauses (“UK Addendum to the EU SCCs”), with a transfer risk assessment
| Provider | What it does | Where | Safeguard |
|---|---|---|---|
| Supabase | Our main database, sign-in and file storage | London, UK. Support staff may access it from outside the UK. | Hosted in the UK. UK Addendum to the EU SCCs for support access. |
| Vercel | Hosting and running the app | App functions in London. Global delivery network and US support. | UK-US data bridge and the UK Addendum to the EU SCCs |
| Anthropic | AI coach replies, and the assistant on instructor websites | United States | UK Addendum to the EU SCCs |
| Resend | Sending emails | United States | UK-US data bridge |
| Stripe | Taking payments | United States and EEA | UK-US data bridge and the UK Addendum to the EU SCCs |
| Sentry | Finding and fixing errors (limited technical data) | United States or EEA, depending on our account settings | UK-US data bridge, or UK adequacy for the EEA |
| ElevenLabs | Reading coach replies aloud, if you turn voice on | United States | UK-US data bridge |
| Mapbox | Showing maps | United States, with a global delivery network | UK-US data bridge |
| postcodes.io (Ideal Postcodes, UK) | Turning a postcode you type into a location. We send the postcode only. | UK company. Hosting location not published. | No name or account details are sent |
| YouTube (Google) | Playing training and test route videos | United States | UK-US data bridge |
| PostHog | Product analytics, only if you accept analytics cookies | EEA (Frankfurt) | UK adequacy for the EEA |
| Google Analytics | Site analytics, only if you accept analytics cookies | United States | UK-US data bridge |
| GitHub | Holding encrypted nightly copies of our database for up to 30 days | United States | UK-US data bridge. Copies are encrypted before upload. |
You can ask us for a copy of the relevant safeguards.
6. How long we keep it
We keep your data while your account is active. If you ask us to delete your account, we close it immediately, sign you out on every device, stop any subscription and remove your personal data within 28 days, except where we must keep limited records to meet legal obligations, for example, payment records, and consent records which we may retain for up to 7 years. If pupils paid you through Stripe, we keep only your Stripe account reference until any money still owed has been settled, normally no more than 120 days after closure (longer only if money is still in your Stripe account, until it is paid out); Stripe keeps its own records under its own privacy policy. If you work with a driving school, the school keeps its own records of your lessons and pupils because it is responsible for them. Encrypted backups of our database are kept for up to 30 days, so deleted data can stay in a backup for up to 30 days until it is overwritten. We do not restore a backup except to recover from an incident.
7. Your rights
Under UK GDPR you can ask us to:
- access a copy of your data;
- correct inaccurate data;
- delete your data (“right to erasure”);
- restrict or object to certain processing;
- receive your data in a portable format.
You can delete your account at any time from Settings, or email us to exercise any of these rights. You can also complain to the Information Commissioner’s Office (ICO).
8. Cookies and local storage
We use essential storage to keep you signed in and to remember your preferences (such as theme and study settings). We ask for your choice on analytics cookies via the banner shown on your first visit. Nothing is sent to analytics providers unless you accept. You can change your choice any time by clearing the preference in your browser.
9. Children
The service is intended for users old enough to begin UK driving-licence preparation. It is not aimed at younger children.
10. Changes and contact
We may update this policy; we’ll change the date below when we do. For any privacy question or request, contact us through the app. Always verify official driving rules and fees on GOV.UK.