Cookie Policy

Cookies we set

None. This site sets no cookies. There are no accounts, so there is no session cookie; no analytics, so no measurement cookie; and no advertising, so no advertising cookie.

Browser storage we use

We use a small amount of localStorage, which is similar to a cookie but is never transmitted to a server:

This is a preference you set deliberately using the theme toggle. It holds the word light or dark and nothing else, contains no identifier, and cannot be used to recognise you.

Why there is no consent banner

Because there is currently nothing to consent to. A consent dialogue on a site that sets no tracking technology is theatre, and it trains people to dismiss consent dialogues without reading them — which makes the ones that matter less effective.

When we introduce advertising or analytics, a genuine consent mechanism appears at the same time. Not before, and not afterwards.

What changes with advertising

Advertising typically involves cookies and identifiers set by the ad provider rather than by us. Before any of it is enabled:

• This page will list each cookie with its provider, purpose and lifetime.
• A consent management platform will be in place where the law requires one, with non-essential storage off by default until you choose otherwise, and a way to withdraw consent as easily as you gave it.
• The privacy policy will be updated in the same release.

Until a consent platform is integrated, the site makes no advertising request at all. That is deliberate: the failure direction is that we lose revenue, not that you lose a choice.

Controlling storage

Every browser lets you clear or block site storage, and doing so here removes your saved theme preference and nothing else. No practice results are stored, because they never leave the page you took them on — see the privacy policy.

If you block storage entirely, the theme toggle still works for the current page; it simply will not remember your choice next time.

What this means in practice for you

You can use this entire site — every practice test, every explanation, every guide — without being tracked, without an account, and without making a single consent decision. Nothing here is gated behind accepting anything.

Browsing in a private window works identically, except that the theme resets each time. Blocking storage entirely works too, with the same single consequence. There is no degraded experience to discover, because nothing about the product depends on remembering you.

Why we treat this as a design constraint

Setting nothing was not an accident of an early launch. Practice attempts are scored in the browser rather than on a server precisely so there is no session to track, and the site works entirely without accounts so there is no identifier to store. Those choices cost us features — you cannot currently save your progress — and the benefit is that this document is short and verifiable.

You can check it. Open your browser’s developer tools, look at the storage panel for this site, and you will find one key holding one word. There is no analytics beacon to block and no advertising script to inspect, because neither exists.

What counts as strictly necessary here

The theme preference is arguably not even that — the site works perfectly without it, it simply forgets whether you wanted the dark palette. We keep it because a study site that flashes white at somebody working late is a worse experience, and because the alternative is asking for consent to remember a colour, which is not a meaningful choice to put in front of anybody.

If we are ever wrong about that, the fix is trivial: the toggle continues to work for the current session without storing anything at all.

How to verify any cookie policy, including this one

A cookie policy is one of the few legal documents on a website you can check yourself in under a minute, and very few readers ever do.

Open your browser’s developer tools and look at the application or storage panel. It lists every cookie and every storage key the site has set, with values. Compare that against what the policy declares. A site setting a dozen advertising and analytics cookies while its policy mentions two is telling you something useful about how carefully it treats everything else.

Also check the network panel for requests to domains that are not the site you are on. Those are the third parties, and each one is a party the policy should name.

We would rather you checked than took our word for it, which is the main reason this document is written to be falsifiable rather than comprehensive.

Third-party content

We embed no third-party content. No fonts loaded from another domain, no analytics, no video players, no social widgets, no comment system. Fonts are served from this origin, which is why there is no font-provider cookie to declare. That also means no third party can set storage through this site without us adding them deliberately and updating this page.

Related

Privacy policy · Advertising policy · Security and data