Cookie policy

Cardhigher uses no cookies. None of its own and none from third parties, technical, analytical or advertising. That is also why there is no banner asking for your permission.

Check it yourself

Open your browser’s developer tools, go to Storage or Application, and look at the cookie list for cardhigher.com. It is empty, before and after playing.

Why there is no cookie banner

A cookie notice exists to ask permission before storing or reading information on your device when that is not essential to the service you asked for. Cardhigher stores nothing when you arrive: if you come, look and leave, your browser is left exactly as it was.

What it does store — your settings, your best streaks, the games you marked — appears only when you do something that can only work by remembering it, stays on your own device and is sent nowhere. Putting up a banner to ask permission for that would be asking for nothing, and would teach people to accept without reading.

If Cardhigher ever added analytics, advertising or anything else that does need consent, it would not run without asking you first and without letting you refuse just as easily. That is not the case today, and this document would say otherwise if it were.

What is stored in your browser, then

Local storage, not cookies: the practical difference is that it never travels in a request to the server. The full list, with what each item is for and when it appears, is in the privacy policy.

It is wiped from Settings, with the button that deletes your data, or by clearing site data in your browser. It does not expire on its own: it lives until you delete it.

Third parties

Card images load from third-party servers, which receive your IP address because any server receives it when asked for a file. They do not set cookies in your browser when serving an image. They are all listed in the privacy policy.

The share buttons at the end of a run are links, not those networks’ scripts: they load nothing, set no cookies and contact nobody until you press one. That is exactly the case where most sites do drop third-party cookies without the visitor having done anything.

Date

Last updated and in force since: 23 September 2026. Earlier versions of this document are in the project repository’s history.