Cookie Policy

Cookies are small text files a website stores on your device. Browser storage (such as localStorage) works in a similar way, and this policy covers it too. We use essential cookies to keep you signed in and remember your settings. Everything else — analytics, session recordings and advertising measurement — stays off until you allow it, and you can allow each of the three separately.

These are required for the site to work and are always on:

• Session cookie ("drivingtest") — keeps you securely signed in to your account.
• Language cookie ("locale") — remembers your chosen interface language.
• Consent cookie ("cookie_consent") — remembers which of the three choices below you allowed. It also carries a random code that identifies nothing except the record we keep of that answer. Kept for 6 months, after which we ask again.
• Browser storage — keeps your place in a long practice session and your answers in a mock exam, so that reloading the page does not lose them (practice progress is cleared when you finish the session; exam answers stay until that exam is finished), and remembers for the current tab that you closed a promotional pop-up. Your browser also keeps a copy of the site's static files so pages load faster.

None of these follow you around the web.

Two short codes ("dt_fp", "dt_dc") are calculated in your browser from your device's settings — such as screen size, time zone, number of processor cores and graphics card — and kept for 12 months. We use them only to protect the Service: to apply the one-free-trial-per-person rule, to spot repeat or bulk sign-ups, and to keep a block on a banned account effective. They are never used for advertising, analytics or profiling, are never shared with anyone, and are not used to track you across other websites.

Because they exist to keep the Service secure and fair rather than to display the page you asked for, they are set without asking: we rely on the security ground in the ePrivacy Regulations (S.I. 336/2011, Regulation 5(5)) together with our legitimate interest in preventing abuse (GDPR Article 6(1)(f)). If you want to object to this use, write to [email protected].

The cookie banner — and this page, under "Your cookie choice" — offers three separate choices. Each is off until you turn it on.

• Analytics (Google Analytics) — how the site is used: the pages you visit and what you do on them, your device and browser type, your approximate region (estimated from your IP address) and, while you are signed in, your account ID — an internal code, not your name or email address — so that visits from your different devices can be linked to your account. The Google tag sets "_ga" and "_ga_*", and our tagging server (Google software running on our own server, which forwards the data to Google) sets "FPID"; all three identify your browser and last up to 2 years. "FPLC", a 20-hour form of the same ID, is set as well.
• Session recordings (Microsoft Clarity) — what our pages show you and how you use them: clicks, taps, scrolling, mouse movement and the page content around them, replayed as recordings and summarised as heatmaps, so we can find confusing or broken parts. What you type into form fields, numbers and email addresses are hidden; other text on the page, such as your name, is recorded. Clarity estimates your region from your IP address. It sets "_clck" (a Clarity ID for this site, 1 year) and "_clsk" (joins your page views into one recording, 1 day), and Microsoft sets its own cookies on its domains (clarity.ms, bing.com), such as "MUID" and "SRM_B" (about 13 months), "MR" (7 days), "ANONCHK" (10 minutes) and "SM" (until you close the browser), which it uses for advertising, site analytics and operational purposes.
• Advertising (Google Ads) — which of our ads bring sign-ups and purchases. Our tagging server sets "FPAU" (90 days) and, if you arrive from one of our Google ads, keeps the ad click ID in "FPGCLAW" or a similar "FPGCL…" cookie (90 days). When you sign up, start a free trial, start a checkout or buy a plan, that event is reported to Google Ads — for a purchase, with the plan's price. A purchase is reported by our server after payment, using a copy of your Google cookies taken when you started the checkout; we delete that copy once the purchase has been reported, or after 30 days at the latest. This choice also covers our own visit-source cookie, "dt_attr": for 90 days it remembers how you first arrived — the campaign details ("utm_" parameters) and ad click ID ("gclid" or "fbclid") in the link, the referring website and the first page you opened. If you create an account while it is stored, we save that with your account to see which campaigns bring sign-ups and purchases; it stays with us, and turning advertising off later does not remove what was already saved with your account.

Google Analytics and Google Ads data is processed by Google (Google Ireland Ltd), Clarity data by Microsoft (Microsoft Ireland Operations Ltd). Because "Session recordings" and "Advertising" also allow advertising use of that data, Google and Microsoft may use it for their own purposes, including personalised advertising, under their own policies: policies.google.com/technologies/partner-sites and privacy.microsoft.com/privacystatement.

Whatever you choose — and before you choose — the Google tag loads and sends Google limited information without cookies: the page you view, the site that referred you, your browser and device type, your IP address (used to estimate your region) and actions such as signing up, starting a free trial, starting a checkout or finishing a mock exam with its score. Sign-up, free-trial and checkout events may reach Google Ads this way too, with no cookie and nothing stored on your device, and Google may use such signals to estimate statistics. If you have not allowed analytics, a purchase is still reported to Google Analytics with its plan, price and our payment reference — the same reference your browser's own checkout signal carries — but with no account ID and no browser identifier. Microsoft Clarity does not load at all unless you allow session recordings. The site works exactly the same either way.

Whatever you choose, small notes in your browser storage ("dt_su_…", "dt_li" and, for the current tab, "dt_auth_method") make sure a sign-up or sign-in is reported once rather than twice, and with the method you used. They hold your account ID, that method and a time; the site reads them to decide whether to report the event, and "dt_su_…" stays until you clear your browser storage.

If you sign in with Google or Apple, pay for Pro, or use the email sign-up and sign-in forms, our sign-in, payment and security providers (Google, Apple, Stripe, Revolut and Cloudflare) may set their own cookies on their pages or in their embedded checks to complete that process securely. Those cookies are governed by the providers' own privacy and cookie policies, and are set whatever you chose here — they are part of signing in or paying, not of measurement. The cookies Microsoft sets through Clarity are described above. Videos on our pages are embedded from YouTube (Google) in its privacy-enhanced mode; the YouTube player loads only when you press play, and from then on YouTube may set its own cookies or use your browser's storage under Google's privacy policy.

You can change your choice at any time with the switches under "Your cookie choice" at the bottom of this page. The page reloads and the new choice applies at once. Turning a choice off also deletes the cookies it set: ours and Google's on this site, and Clarity's "_clck" and "_clsk". Microsoft's own cookies live on clarity.ms and bing.com and can only be removed in your browser.

You can also delete or block cookies in your browser settings at any time. If you remove our essential cookies you will be signed out and your language will reset to automatic detection, but you can still use the site. If you delete the consent cookie, the banner asks again on your next visit; in any case we ask again every 6 months. A page you already have open keeps the choice it was loaded with until it reloads — other tabs of this site reload themselves as soon as you change your choice.

We may update this Cookie Policy if our use of cookies changes. The date below shows when it was last updated. If a change affects what you agreed to, we ask you again rather than rely on the old answer.