Privacy Policy

UK Routes: Driving Test · Last updated: 3 November 2026

UK Routes: Driving Test is published by BMKS. This policy explains exactly what the app handles and what it does not. It is written to be read, not to be skimmed past.

The short version. There is no account. We never ask for your name, email or phone number. Your location stays on your phone, with two exceptions: when you ask for test centres near you, your approximate position is sent to our server to sort the list; and if you leave the route during a drive, your current position is passed through our server to our map provider to work out a way back. We keep neither. There is no advertising SDK and no analytics SDK of our own. The Mapbox map component sends Mapbox anonymous usage and location data, which you can switch off (see Mapbox below).

Data we handle

What	Why	Where it goes
Precise location (GPS)	To show where you are on the route, give voice directions at the right moment, and track your progress along the route.	Stays on your device while you are on the route. If you ask for test centres near you, your approximate position is sent to our server to sort the list and is not stored. If you leave the route during a drive, your current position and direction of travel are sent through our server to Mapbox to calculate a route back (see below). Our server passes them on and does not store them.
Device identifier	A random value the app generates on first launch. It is what your purchase is attached to, since there is no account.	Sent to our server with purchases, route requests and route-back requests. It is not an advertising identifier, not your Apple ID or Google account, and not linked to your identity.
Purchase receipt	To check that a purchase is genuine, to work out when your access ends and, for subscriptions, to keep that date up to date when the subscription renews, is cancelled or is refunded.	On iPhone: sent to our server and to Apple for verification; Apple also notifies our server of renewals, cancellations and refunds. On Android: Google Play takes the payment, and RevenueCat (our purchase-validation provider) confirms the purchase with Google Play and tells our server, using the device identifier above. We store the transaction reference, the plan, whether it will renew and the expiry date.
Route requests	To serve the route data you asked for and to check your access is valid.	Our server receives the route identifier, your device identifier and standard request data such as your IP address.

Location, in detail

The app asks for location permission so it can place you on the route line. On iPhone, while a drive is running, the app requests background location so guidance keeps working when your screen is off or you switch apps — this is the same permission a navigation app needs. On Android the app keeps the screen on during a drive instead and does not use background location.

While you are on the route, your position is used on the device and then discarded. We do not upload your position, your speed, your drive history or a track of where you have been. Nobody at BMKS can see where you have driven.

Leaving the route. If you leave the route during a real drive (not a simulation), the app works out a way back to it. To do that it sends your current position, your direction of travel and a few points on the test route nearby to our server, which passes them to Mapbox, and Mapbox returns driving directions. The directions for that route back are spoken by turning their text (street names and turns) into audio through Mapbox, also via our server. Our server checks that your device may use the route back and counts how many of these requests it made each day, so the service cannot be misused; it does not store your position or the directions. Mapbox receives these requests from our server, not from your phone, so it does not receive your device identifier. If there is no internet connection, nothing is sent and the app tells you the route back could not be calculated.

Test centres near you. When you choose a test centre, you can sort the list by distance. The app then sends your approximate position to our server, which returns the nearest centres. The position is used for that one request and is not stored or linked to your device identifier.

You can revoke the location permission at any time in your phone's settings; the map still works, but positioning, voice guidance and the route back will not.

Data we do not collect

Name, email address, phone number or postal address.
Contacts, photos, calendar, microphone or health data.
Advertising identifiers. The app does no tracking across apps or websites, and shows no ads.
Analytics events of our own. No Firebase, no Google Analytics, no crash-reporting SDK. The only usage data that leaves the app is the Mapbox map component's telemetry, described under Mapbox.
Card numbers or billing details. Those go to Apple or Google; we never see them.

Third parties

Apple

In-app purchases run through the App Store. Apple handles payment and gives us a signed receipt to verify. See Apple's Privacy Policy.

Google Play

On Android, in-app purchases run through Google Play, which handles payment. See Google's Privacy Policy.

RevenueCat

On Android, RevenueCat, Inc. checks purchases with Google Play on our behalf and tells our server when a subscription starts, renews, is cancelled or is refunded. It receives the app's random device identifier and the purchase details from Google Play — not your name, email or location — and processes them only to provide this service to us. See RevenueCat's Privacy Policy.

Mapbox

The maps in the app are provided by Mapbox. To draw the map the app has to fetch the portion of the map you are looking at, which means Mapbox receives the approximate area shown on your screen along with standard request data. When you leave the route during a drive, Mapbox also receives, through our server, your current position and direction of travel to calculate a route back, and the text of the directions for that route to turn into speech (see Leaving the route above). It does not receive your progress along the test route or a history of where you have driven from us.

Like every app that uses the Mapbox map, the map component itself also sends Mapbox anonymous usage and location data (Mapbox telemetry), which Mapbox uses to improve its maps and services. It uses Mapbox's own anonymous identifier, not our device identifier, and we never see it. You can switch it off at any time: tap the ⓘ button in the corner of the map and turn off Mapbox telemetry. See Mapbox's Privacy Policy.

Our hosting provider

The app's routes and this website are delivered through Cloudflare, Inc., which acts as our hosting and content delivery provider. In doing so it processes standard request data, including your IP address, to deliver the response and to protect the service from abuse. It does not use that data for its own purposes.

Retention

Purchase records — device identifier, plan, transaction reference, start and expiry dates and, for subscriptions, whether they will renew — are kept while your access is valid and afterwards as an accounting record of the sale. The server also records each device identifier with the dates it was first and last seen and the app version, so we can find your installation when you contact support; nothing else about the device is kept. For the route back, the server keeps a daily count of requests for each device identifier — how many, never where — to enforce fair-use limits and to see how much the feature is used. Server request logs are short-lived and are used for operating and securing the service.

Your rights

Under UK GDPR you can ask for access to, correction of, or deletion of personal data we hold, and you can object to or restrict our processing of it. Because there is no account, the only handle we have is your device identifier and your store transaction. Include the Apple order number, or the Google Play order number (it starts with GPA.), in your request so we can find the record.

Write to [email protected]. We respond within 30 days. Deleting a purchase record ends the access it grants, and Apple and Google do not refund on that basis. If you are unhappy with our response you may complain to the Information Commissioner's Office at ico.org.uk.

Children

The app is aimed at learner drivers and is not directed at children under 13. We do not knowingly collect personal data from them.

Changes

If this policy changes, the date at the top of this page is updated. Changes that affect what we collect are described in the app's release notes in the App Store and Google Play, and on this page, before they take effect.

Contact

BMKS · [email protected]