Privacy Policy
Last updated: 5 November 2026
1. Who We Are
Driving Test Expert Ltd ("we", "us", "our") operates the website drivingtestexpert.com and the Test Routes Expert mobile application for iPhone and Android, including its CarPlay and Android Auto screens. This policy explains how we collect, use, and protect your information. We are the controller of your personal data, except where section 5 says a service handles it as its own controller.
Driving Test Expert Ltd is a UK company, number 16943216. Registered office: The Old Post Office Mill Meece Marsh, Cotes Heath, Stafford, ST21 6QU.
2. Data We Collect
We collect the following categories of information.
On this website
- Usage data: Pages visited, device type, operating system, and browser type. On this website, Google Analytics collects this only if you allow analytics cookies (see Cookies).
- Sami pilot and waitlist data: Your email address, whether you are an instructor or student, whether you want to test Sami or join the release waitlist, your phone platform, and the consent you provide when submitting the form.
In the Test Routes Expert app
Some of this applies only to newer app versions: versions after 1.4.54. Section 5 says which services receive what.
- Your Support ID: the app makes a random ID the first time you open it. You don't need an account, a name or an email address. You can see it in Settings. It keeps your purchases and progress together and lets us find your records if you contact us. The app also makes a random device ID. Both are stored so they can survive reinstalling the app. Delete My Data removes them from your phone.
- Your test details: the test centre you choose and the date of your test, or roughly how far away it is. Newer app versions also keep the time of your test and your result, if you give them. We use these to show your routes and to time reminders.
- Location: when you navigate, the app uses your phone's precise location and sends it to Mapbox to plan the route from where you are. We don't keep your location history. If you draw or record your own route and save it, we keep that route's points with your Support ID.
- Messages to us: what you write in Help & feedback, with your Support ID and device ID, and the notes our AI assistant keeps while it helps you. The assistant answers first (see Anthropic in section 5).
- Routes you share: if you send a route in the app for review, we keep the name you give with it. We never show that name with your route. We keep it only so we can contact you in the app about your routes. Delete My Data deletes it from our database, except in the older app versions listed in section 7. If you also give a credit name, we show it with the route once it is published, and Delete My Data does not remove it: ask us.
- Purchases: if you buy, the App Store or Google Play takes the payment and RevenueCat records what you bought. We never see your card details. We also keep our own record of a purchase (the product, price and date) if it came from one of our adverts or counts towards an instructor partner's earnings.
- Advertising measurement: to tell which adverts and links lead to installs and purchases, the app uses Tenjin and, with your permission, your phone's advertising ID. On iPhone it reads the ID only if you allow tracking. On Android, newer app versions ask you first, and version 1.4.54 doesn't read the ID. See section 3.
- Crash reports: when the app crashes or hits an error, it sends a technical report to Sentry, with a log of what the app did just before. In version 1.4.54 that log can include the web addresses it called, which can contain your Support ID, the app's device ID or a postcode you searched for. Newer app versions take IDs and map coordinates out of those addresses and don't log postcode searches. There is no switch for crash reports: to object, email us.
- Push notifications: on Android, and on iPhone in newer app versions, the app registers with OneSignal when it opens, using the random device ID. OneSignal sends notifications only if you allow them.
- Usage analytics (newer app versions): what you do in the app, such as the centre you choose, the routes you open and the purchase steps you take, linked to your Support ID. We use it to see what to improve. It's on unless you turn it off: Settings → Data & Privacy → Usage analytics. See PostHog in section 5.
- Mock tests with the camera (newer app versions): the front camera checks your mirror and head movements on your phone. Those images are never recorded or sent anywhere. On Android, road-facing video (no sound) is recorded and kept on your phone. It leaves your phone only if you share a clip yourself, or switch on cloud analysis (see Modal in section 5). If you share a mock test result with your instructor, they see the result.
- Instructors and instructor partners: if you use the app as an instructor or join our Instructor Partner Programme: your name, your ADI number, an email address, your partner code, and the payments made by pupils who used your code (amounts and dates; we never tell you who they are). In version 1.4.54 the email address is required and is your login for the partner dashboard. Newer app versions ask for one only when we first owe you money, to arrange the payment.
Why we use your data, and our lawful basis
- To run the app and give you what you bought (your routes, navigation, restoring purchases and answering your messages): to perform our contract with you.
- To keep the app working and secure (crash reports, update checks and stopping misuse): our legitimate interest in a reliable, safe app. You can object by emailing us.
- To improve the app (navigation records and, in newer app versions, usage analytics): our legitimate interest in knowing what works. You can object at any time: the switch in Settings for usage analytics, or email us.
- To measure our adverts: your consent where we ask for it (cookies on this website, Apple's tracking prompt, and the question newer app versions ask on Android). Where the app doesn't ask (version 1.4.54 on Android, and what Tenjin records on iPhone if you don't allow tracking): our legitimate interest in knowing which adverts work. You can object by emailing us.
- To send notifications: your consent, through your phone's notification permission. Website analytics cookies and the Sami pilot and waitlist also rely on your consent.
- Cloud analysis of road video (newer app versions): your consent. It is off unless you switch it on.
- Records we have to keep, such as accounts, tax and payments to instructor partners: our legal obligations and our contract with the partner.
3. Advertising & Conversion Tracking
We run advertising campaigns through Google Ads. When you click one of our ads, Google may append a click identifier (GCLID) to the URL. We use this identifier to measure whether an ad click led to an app download. Specifically:
- The GCLID is captured from the URL and logged alongside a pseudonymous click record.
- Your IP address is hashed using SHA-256 before storage. We never store your raw IP address.
- Click records may be matched to anonymous app subscription events to calculate return on advertising spend. No personally identifiable information is shared with Google beyond what Google already holds from the original ad click.
- Click records are automatically deleted after 90 days.
If you allow marketing cookies, our website also uses the Meta pixel and the TikTok pixel to measure whether our adverts lead to app downloads. Google's tag measures both Google Analytics and our Google adverts, so it loads only if you allow analytics and marketing cookies. Without that consent these tags do not load.
If you arrive from one of our TikTok adverts, TikTok adds its own click identifier (ttclid) to the URL, which we handle in the same way as the GCLID above.
Most download buttons send you to the app store through Tenjin, our install-attribution provider. Tenjin records the click, including your IP address and device type, to tell us which link led to an install. It sets no cookies on your device. If you arrived from one of our Google or TikTok adverts, the link goes straight to the store with that advert's click identifier instead.
In the app
- On iPhone, the app asks whether you allow tracking. If you allow it, Tenjin and RevenueCat get Apple's advertising ID. If you say no, they don't, and Apple sends anonymous install reports instead. Tenjin still records the install and app opens, with your IP address and device details, and RevenueCat still gets the ID Apple gives our apps and your IP address.
- On Android, newer app versions ask once. Until you say yes, the app doesn't start Tenjin, doesn't read your advertising ID and doesn't save any advert details. You can change your answer in Settings → Data & Privacy → Advert measurement. If you turn it off later, new collection stops. What was already sent stays until you ask us to delete it (section 7).
- On Android, version 1.4.54 doesn't ask. Tenjin records the install and app opens, with your IP address and device details. This version doesn't read your advertising ID.
- On Android, Google Play tells the app which link or advert led to the install (the install referrer). The app saves the source, the campaign, a test centre and the advert's Google click identifier (GCLID), where there is one, on your RevenueCat customer record. In newer app versions it saves these only if you said yes. In all versions, if the link carried an instructor's code, the app claims it, so you get that instructor's offer.
- When you buy, RevenueCat tells Tenjin, but only if the app has your advertising ID. Tenjin passes installs and purchases to the advertising networks we use (such as Google, Meta and TikTok), so each can tell whether one of its adverts led to them. For an Android install from one of our Google adverts, we also report the purchase to Google Ads with that advert's GCLID. Google Play also reports purchases to our Google Ads account directly.
4. IP Address Hashing
When you visit our download page, we create a one-way SHA-256 hash of your IP address. This hash cannot be reversed to recover your original IP address. It is used solely to deduplicate click records and is deleted with the click record after 90 days.
5. Third-Party Services
These services receive data from this website or the Test Routes Expert app. Each entry says what the service is for, what it gets, where it is processed, how long it is kept and what you can do. Items marked newer app versions apply only to app versions after 1.4.54.
Some of these services are outside the UK. Each entry names the safeguard for that transfer: the UK-US data bridge (for US companies certified to it), or the EU standard contractual clauses, with the UK Addendum where the provider's terms include it. Email us for more detail or a copy (section 11).
Supabase
- What for
- Our database and servers, for the app and this website.
- What it receives
- From the app: your Support ID and the app's random device ID; your test centre and your test date (or how far away it is); the messages you send us in the app; routes you save, rate, report, request or send for review, including the points of any route you draw or record; when the app was last open; and records of when you start navigation (route, centre and phone type, with no GPS positions); instructor partner details; and a record of purchases that came from our Google adverts or count towards a partner's earnings. Newer app versions also keep your test time and result if you give them, paywall views, push notification taps, mock test results you share with your instructor and any mock test marks you dispute. From this website: ad click records, Sami pilot and waitlist sign-ups and creator applications.
- Where
- Frankfurt, Germany (EU). The company we contract with is in Singapore. Safeguard: the UK Addendum to the EU standard contractual clauses.
- How long
- See section 6. Daily backups are kept for 7 days.
- Your choices
- Delete My Data in the app, or ask us (section 7).
RevenueCat
- What for
- Handles purchases and subscriptions you buy through the App Store or Google Play.
- What it receives
- Your Support ID; what you bought, when, and whether your subscription is active; your phone's identifiers and IP address (on iPhone, the ID Apple gives our apps and, only if you allow tracking, the advertising ID; on Android, in newer app versions and only if you say yes to advert measurement, the Android ID and the advertising ID); the Tenjin install ID; an instructor's code if you used one; and, on Android, details of the store link that brought you to the app (the advert's click ID, the campaign and a test centre; in newer app versions, only if you say yes). We never receive your card details.
- Where
- United States. Safeguard: the UK Addendum to the EU standard contractual clauses.
- How long
- For as long as we use RevenueCat, unless you ask us to delete your record sooner.
- Your choices
- Ask us with your Support ID to delete your RevenueCat record (section 7). Advertising ID: see Tenjin.
Mapbox
- What for
- Maps, directions and turn-by-turn navigation, and drawing or recording your own routes.
- What it receives
- Your location while you navigate, to plan the route from where you are and re-plan it if you go off it; the map areas and routes you look at; the points of a route you draw or record (sent by our server) so it follows the roads; and your IP address and basic device details. Mapbox's software in the app also sends Mapbox usage and location data, without advertising IDs, which Mapbox uses to improve its maps, under its own privacy policy.
- Where
- United States. Safeguard: the UK-US data bridge, and the UK Addendum to the EU standard contractual clauses.
- How long
- As long as Mapbox needs it, under its own policy. Mapbox says it keeps IP addresses for 30 days (longer for investigations) and breaks the link between session IDs and location within 24 hours.
- Your choices
- You can refuse location access in your phone settings, but navigation needs it. Where the map shows Mapbox's ⓘ button, it includes a setting to stop the usage data. Mapbox still gets your location for navigation.
Tenjin
- What for
- Tells us which advert or link led to an app install, and whether our adverts lead to purchases.
- What it receives
- Your advertising ID (on iPhone, Apple's, only if you allow tracking; on Android, Google's, only in newer app versions and only if you say yes), your device model, operating system and IP address, when the app was installed and opened, the names of some app events (such as "paywall viewed" or "navigation started"), and purchase events with their value, which RevenueCat sends only when the app has your advertising ID. Tenjin passes install and purchase events to the advertising networks we use (such as Google, Meta and TikTok) so they can tell whether our adverts worked. On iPhone, Tenjin runs even if you don't allow tracking, without Apple's advertising ID, and Apple also sends it anonymous install reports (SKAdNetwork). On Android, version 1.4.54 runs Tenjin without asking, and without an advertising ID. Newer app versions don't start Tenjin on Android until you say yes, and then also let it read Meta's install referrer from the Facebook and Instagram apps.
- Where
- United States. Safeguard: the EU standard contractual clauses, in Tenjin’s terms.
- How long
- 30 days to 24 months, depending on the data and the contracts behind it, then deleted or anonymised.
- Your choices
- On Android, in newer app versions: Settings → Data & Privacy → Advert measurement. You can also delete your advertising ID in your phone's Settings → Google → Ads. On iPhone: Settings → Privacy & Security → Tracking. Ask us with your Support ID to delete what Tenjin holds (section 7).
Google
- What for
- On this website: Google Analytics and Google Ads measurement (only with your consent) and YouTube videos. In the app: Street View and Google Maps when you preview a route or look at a test centre; on Android, the Google Play install referrer (which link or advert led to the install) and delivery of push notifications; and measuring our Google adverts. The app includes Google Maps features and content. Their use is subject to the current Google Maps/Google Earth Additional Terms of Service and the Google Privacy Policy.
- What it receives
- For Street View and maps: the test centre and route you are looking at (not your own location), your IP address and device details. For Google Ads: install and purchase events from Tenjin, and, for Android installs that came from one of our Google adverts, purchases matched to that advert's click ID (GCLID). On iPhone, the app also checks your internet connection by contacting a Google server. Newer app versions also load Google Fonts and Google Maps on the paywall, and use Google's ML Kit to spot your face on your phone during camera mock tests. ML Kit sends Google technical data (device model, app version, an installation identifier and performance figures), never camera images.
- Where
- Google’s servers, including in the United States. Safeguard: the UK-US data bridge.
- How long
- Set by Google, which handles maps and Street View data as its own controller; see Google’s privacy policy.
- Your choices
- Cookie settings (section 8) for this website; the advertising ID settings under Tenjin for the app.
Google Privacy PolicyGoogle Maps/Google Earth Additional Terms
Meta
- What for
- Measuring our Facebook and Instagram adverts.
- What it receives
- On this website, the Meta pixel (only with your consent). In the app, install and purchase events from Tenjin, with your advertising ID where it is available.
- Where
- Meta’s servers, including in the United States. See Meta’s privacy policy for its safeguards.
- How long
- Set by Meta; see Meta’s privacy policy.
- Your choices
- Cookie settings for this website; the advertising ID settings under Tenjin for the app.
TikTok
- What for
- Measuring our TikTok adverts.
- What it receives
- On this website, the TikTok pixel (only with your consent). In the app, install and purchase events from Tenjin, with your advertising ID where it is available.
- Where
- TikTok’s servers, which may be outside the UK. See TikTok’s privacy policy for its safeguards.
- How long
- Set by TikTok; see TikTok’s privacy policy.
- Your choices
- Cookie settings for this website; the advertising ID settings under Tenjin for the app.
Sentry
- What for
- Crash and error reports, so we can find and fix problems.
- What it receives
- What went wrong (the error and where in the app's code it happened), the app version, your device model and operating system, a random identifier for the app installation, and a log of what the app did just before. In version 1.4.54 that log can include web addresses containing your Support ID, the app's device ID or a postcode you searched for. Newer app versions take those out first (see section 2).
- Where
- Reports are stored in the EU (Frankfurt, Germany). Some account information may be held in the United States. Safeguard: the UK-US data bridge.
- How long
- 30 days on our plan.
Codemagic (CodePush)
- What for
- Delivers small app updates without a new download from the App Store or Google Play.
- What it receives
- Each time the app checks for an update: the app version, the update it is running, a random install identifier (on iPhone, the ID Apple gives our apps) and your IP address; and whether an update downloaded and installed.
- Where
- Codemagic (Nevercode Ltd) is a UK company. It doesn’t publish where this data is stored. Its privacy policy says it uses standard contractual clauses for transfers out of the UK.
- How long
- Codemagic doesn’t publish a period for this data.
- Your choices
- None in the app: update checks keep the app working. You can ask us to request deletion (section 7).
OneSignal
- What for
- Sends push notifications, such as reminders before your test and replies from our team. On Android, and on iPhone in newer app versions.
- What it receives
- The app's random device ID, your push token and basic device details; labels for how far away your test is and how your practice is going; and the notifications we send you, which can include the first part of a reply to your support message. Notifications reach your phone through Google on Android and Apple on iPhone.
- Where
- OneSignal is a US company whose main data centres are in the EU. Safeguard: the UK-US data bridge.
- How long
- On our plan, people inactive for 18 months are deleted, and the messages we send are kept for about 30 days.
- Your choices
- Turn notifications off in your phone’s settings. Newer app versions also have a switch in Settings. Ask us with your Support ID to delete your record (section 7).
PostHognewer app versions
- What for
- Shows us how the app is used, so we can tell whether a change made it better or worse.
- What it receives
- These actions, linked to your Support ID (before the app has one, a random ID): opening the app, finishing onboarding, choosing a test centre (and which one), loading and opening routes, starting and finishing navigation (and how long it took), seeing the paywall, starting, finishing, cancelling or restoring a purchase (the plan, never the price) and opening support. With them: your device make and model, operating system, app version and screen size. PostHog discards your IP address, and does not get your location, advertising IDs, anything you type, screen recordings or payment details.
- Where
- EU (Frankfurt, Germany). Some of PostHog’s suppliers are outside the UK, including in the United States. Safeguard: the UK-US data bridge.
- How long
- Events for 1 year on our plan. Your analytics profile stays until it is deleted: ask us (section 7).
- Your choices
- Usage analytics is on unless you turn it off: Settings → Data & Privacy → Usage analytics. Turning it off stops new events straight away, and doesn't delete what was already sent. Delete My Data gives the app a new analytics ID. Ask us with your Support ID to delete past events.
Anthropic (Claude)
- What for
- An AI assistant that reads and answers the messages you send us in the app. It can check what you bought, restore your access and look into routes and test centres. A person on our team handles refunds, legal and safety matters.
- What it receives
- Your support conversation, your Support ID and what the assistant looks up to help you, such as whether your purchase is active and details of a route.
- Where
- United States and other countries. The assistant runs on a Claude subscription, so Anthropic Ireland, Limited handles this data as its own controller, under its consumer terms and privacy policies. We have no separate data processing agreement with Anthropic. Anthropic's privacy policy says it uses standard contractual clauses for transfers.
- How long
- Up to 30 days. We have turned off the setting that lets Anthropic use these chats to train its models. Anthropic can keep anything its safety systems flag for up to 2 years (safety scores for up to 7), or longer if the law requires. The assistant's own records stay in our database: see section 6.
- Your choices
- To have a person review something the assistant did, email us (section 7).
Slack
- What for
- Our team’s internal messaging.
- What it receives
- Alerts about route requests, route problem reports and routes sent for review (with the name you gave), support conversations a person on our team needs to look at, instructor partner events (name, code and amounts), creator programme events (section 12) and, in newer app versions, mock test marks you dispute, with your note.
- Where
- United States. Safeguard: the UK-US data bridge, through Salesforce, which owns Slack.
- How long
- Up to one year on our plan, then deleted.
- Your choices
- Ask us to delete messages about you (section 7).
GitHub
- What for
- Stores our code, and runs our process for fixing bugs in the app.
- What it receives
- If the assistant files a bug in the app from your message, the description of that bug, which can include your words. It doesn't include your Support ID.
- Where
- Including the United States. Safeguard: the UK-US data bridge.
- How long
- Until we delete it. Ask us if you want it removed (section 7).
OVHcloud and Cloudflare
- What for
- Servers that run our support assistant (OVHcloud) and some of our internal tools and alerts (Cloudflare).
- What it receives
- Support conversations while the assistant works on them (OVHcloud); routes sent for review and support alerts on their way to our team (Cloudflare); and, in version 1.4.54, an instructor partner's code when the app shows their QR code page (Cloudflare).
- Where
- OVHcloud: United Kingdom. Cloudflare runs worldwide, with related records in the United States and Europe. Safeguard for Cloudflare: the UK-US data bridge.
- How long
- OVHcloud: the assistant keeps no chat transcripts on the server. Technical logs, with no message text, are kept for up to 90 days. Cloudflare: worker logs for up to 7 days. Cloudflare doesn't publish a fixed period for its other traffic records.
Netlify, Zoho, MailerSend and Vercel
- What for
- Host this website (Netlify), our email (Zoho) and an internal dashboard of advert results (Vercel), and send Sami pilot emails (MailerSend).
- What it receives
- Your IP address and what you send through a form on this website (Netlify); emails you send us (Zoho); your email address if you join the Sami pilot (MailerSend); and records of purchases that came from our adverts (Vercel).
- Where
- Zoho: EU. The others may process data outside the UK; ask us for the safeguard.
- How long
- Emails: as long as we need them to deal with what you asked. Otherwise, set by each provider’s policy.
Netlify Privacy PolicyZoho Privacy PolicyMailerSend Privacy PolicyVercel Privacy Policy
Modalnewer app versions
- What for
- Analyses road video from a mock test, only if you switch on cloud analysis.
- What it receives
- Road-facing video from that mock test, uploaded on Wi-Fi to our storage and then analysed on Modal's computers to estimate things like following distance and lane position. The video has no sound, and the front camera is never recorded.
- Where
- United States. Safeguard: the UK Addendum to the EU standard contractual clauses.
- How long
- The video is deleted from our storage after analysis, normally within 24 hours (longer if a service is down). Modal's own systems keep function data for up to 7 days and logs for up to 30 days. The results stay with your mock test until they reach the limit in section 6 or you delete your data.
- Your choices
- Cloud analysis is off unless you switch it on before a mock test, and you can switch it off.
postcodes.io
- What for
- Finds test centres near a postcode you type.
- What it receives
- The postcode you type and your IP address.
- Where
- Run by a UK company (Ideal Postcodes), through Cloudflare. It doesn’t publish where it processes requests.
- How long
- postcodes.io doesn’t publish how long it keeps request logs.
- Your choices
- Search by centre name instead of postcode.
Content the app loads from other sites: route previews load a map code library from unpkg.com, and newer app versions load an onboarding map from OpenStreetMap. These services receive your IP address.
6. Data Retention
An automatic clean-up runs every week, so data can stay for about a week past these limits, or a little longer if a run doesn't finish.
- Ad click records (including hashed IP and GCLID) are deleted after 90 days.
- Records that a purchase came from one of our adverts lose the advert's click identifier 90 days after the purchase is recorded, and your RevenueCat ID after 6 years. The product, value and date stay for our accounts.
- Newer app versions: usage analytics events are kept for 1 year, and your analytics profile until you ask us to delete it (see PostHog in section 5). Totals we work out from analytics, which say nothing about you, may be kept indefinitely.
- Purchase and subscription records are held by RevenueCat (section 5). Instructor partner details, and the referral and payment records behind them, are kept while the partner relationship lasts, and afterwards for as long as accounts and tax rules require, normally 6 years.
- Sami pilot and waitlist details are kept while the pilot or launch communications remain relevant, or until you ask us to delete them. We use these details only to manage testing access and send the Sami updates you requested.
- Most app records are deleted 24 months after they were made or last updated, even if you still use the app: your test details, navigation records, paywall views, notification records, mock test results you shared, mock test marks you disputed, road analysis results, route problem reports, feedback and instructor sign-up details.
- Route ratings, route requests and confirmations that a route is still in use keep counting towards our route statistics. After 24 months we remove what links them to you, and any comment you wrote.
- Your support conversations and the AI assistant's records of them are deleted 24 months after your last message, unless a case is still open. Section 7 lists what stays.
- Records of access our support gave you are kept while that access could still need removing. Bug reports, feature ideas and route problem or correction records have no link to you, and have no fixed limit.
- Routes you create stay until you delete them or use Delete My Data.
- Newer app versions: your test time is deleted 21 days after your test. Road video sent for cloud analysis is deleted after analysis, normally within 24 hours.
- Deleted data can stay in our database backups for up to 7 days.
- Data held by the services in section 5 is kept for the periods shown there.
7. Your Rights (GDPR)
If you are in the UK or European Economic Area, you have the right to:
- Access the personal data we hold about you.
- Rectification of inaccurate personal data.
- Erasure of your personal data where there is no compelling reason to continue processing it.
- Restriction of processing in certain circumstances.
- Data portability to receive your data in a structured, machine-readable format.
- Object to processing based on legitimate interests.
- Withdraw consent at any time, where we rely on it. In the app, use the switches in Settings or your phone's permissions. For anything else, email us. This doesn't affect what we did before you withdrew it.
You don't need to give us your name or email address to use the app. Some features can't work without certain data: navigation needs your location, for example, and a purchase needs a record of what you bought.
To exercise any of these rights, contact us at the email address below. We will answer within one month.
Decisions made by our AI assistant
Our AI assistant can act on its own, without a person checking first. For example, it can restore a purchase, link your access across your devices, give you a short period of access as goodwill, or remove access it gave if the purchase behind it is refunded. It decides from your store purchase records and what you tell it. If you disagree with something it did, email us and a person will review it.
Deleting your app data
Your Support ID and Delete My Data are both in the app's Settings.
- Version 1.4.54, after its automatic update of 4 November 2026, and newer: Delete My Data deletes what our database holds about you (your test details, your messages to us and the AI assistant's records of them, private routes, route requests and reports, navigation records and any road video) and removes your link to routes you shared that are now public. It also clears the app's data from your phone and gives you a new Support ID. The update reaches your phone the next time you fully close and reopen the app. If our servers can't be reached, nothing is deleted and the app lets you try again.
- Older app versions: Delete My Data only clears your phone. To delete what we hold too, update the app first. Or copy your Support ID, send it to us in Help & feedback or email it to the address below, and then use Delete My Data.
- What Delete My Data keeps: any access our support gave you (your Support ID, the purchase it was copied from and the dates), so it can be removed if that purchase is refunded; instructor partner records, which we need for payments; bug reports, feature ideas and route problem or correction records from your messages, with their text as written but no link to you; for a decision handed to a person, such as money back, only what kind of decision it was; and purchase figures that no longer name you. Records under an older RevenueCat ID that we can't match to you stay until the limits in section 6. It doesn't cancel a subscription or refund anything.
- Copies it can't reach: messages already posted to our team's Slack, the text of a bug report on GitHub, and backups (section 6). Ask us to delete the Slack and GitHub copies.
- Other services: Delete My Data does not reach the other services in section 5. To delete what RevenueCat, Tenjin, OneSignal, PostHog, Mapbox or Codemagic hold, send us your Support ID and we will delete it or ask them to, within one month. Some can't pick out one person: Sentry reports and Mapbox's usage data use random identifiers, so we may not be able to find yours, and they then age out under the periods in section 5.
Complaints
You have the right to complain to us. Email the address below. We will acknowledge your complaint within 30 days, look into it and tell you the outcome. You can also complain to the Information Commission (the ICO) at ico.org.uk.
9. Children
Our services are not directed at children under 16. We do not knowingly collect personal information from children. If you believe a child has provided us with personal data, please contact us and we will delete it.
10. Changes to This Policy
We may update this policy from time to time. Material changes will be noted by updating the "Last updated" date at the top of this page.
11. Contact Us
For privacy-related enquiries, contact us at: support@drivingtestexpert.com, or write to Driving Test Expert Ltd, The Old Post Office Mill Meece Marsh, Cotes Heath, Stafford, ST21 6QU.
12. Creator partners
This section covers creators and driving instructors who apply to, or take part in, our Partner Programme. The rest of this policy applies too.
What we collect
- When you apply: your name, email address, channel link, main platform and audience size, your confirmation that you're 18 or over and, if you give them, the town or area you're based in, a phone number, your message and any product or partnership idea you share. Driving instructors give their name, email address, how many pupils they teach, their confirmation that they're 18 or over and, if they give them, their ADI number, area, phone number and message.
- Once you join: your creator code; your public creator profile (the display name, headline, channel link and platform shown on your invite page); a private dashboard link, of which we store only a scrambled (hashed) form; counts of visits to your invite link by device type, which never record who visited; and the purchases made by learners who used your code, with the commission each earned. We show you these as totals and never share learners' personal details with you.
- To pay you: the bank details we need to pay you, your VAT number if you're VAT-registered, and the statements and payouts we make. We ask for these by email when we first owe you money.
Why we use it, and our lawful basis
- To review your application and reply to you, and, if we approve you, to run your part in the programme: your code, invite page and dashboard, working out your commission and paying you. Lawful basis: steps you ask us to take before entering into an agreement with you, and then performing that agreement (the creator programme terms).
- To check for self-referral and other misuse of codes, and to keep the programme fair. Lawful basis: our legitimate interests.
- If you share a product or partnership idea, to contact you about it. Lawful basis: our legitimate interests. You can ask us to stop at any time.
- To keep financial records of commission and payouts. Lawful basis: our legal obligations.
Who sees it
Our team. Applications and programme records are stored in our database, hosted by Supabase, and our team is told about new applications and programme events in our internal Slack workspace. Your public profile and code appear on your invite page. We don't sell your details or share them with advertisers.
How long we keep it
- If we don't take your application forward, we delete it within 12 months of our reply.
- If you take part, we keep your details while you do and while commission is still due to you. We then switch off your code, invite page and dashboard link, and delete your contact and bank details, but keep commission, payout and invoice records for 6 years after the end of the financial year they relate to, as UK tax rules require.
Your rights
You have the rights set out in section 7: to access, correct or delete your data, to restrict or object to how we use it, and to receive it in a portable format. To use them, email support@drivingtestexpert.com. You can also complain to the Information Commissioner's Office at ico.org.uk.
