No tracking pixels, no analytics provider, no social widgets. What follows is the complete list of what the site stores on your device — two cookies of our own, the local storage the games need, and the cookies Google sets on the pages that carry an ad. It is short enough to check line by line.
Cookies the site sets
up_session— set only after you sign in with Google. It holds a random token that keeps you signed in for up to 30 days. It isHttpOnly(page scripts cannot read it),SameSite=Lax, and the database stores only a hash of the token. Signing out deletes it.up_oauth_state— set for 10 minutes while a Google sign-in is in progress. It holds a random value that proves the callback belongs to the request you started, which is what stops a third party from logging you into an account that is not yours. It is deleted as soon as the sign-in finishes.
Browser storage (not cookies)
Some things are kept in localStorage rather than in cookies, because they never need to reach the server and they stay on your device:
- Progress — games played, clears, best scores and times, Intel reads, XP and awards for a visitor who is not signed in.
- Preferences — the language you picked, whether the bottom bar is open, which of its tabs you last used, and the last announcement you have seen.
- Sound — whether interface sounds are muted and at what volume.
Clearing site data in your browser deletes all of it. If you are signed in, your progress is also stored with your account and comes back the next time you sign in.
Advertising cookies
The home page, the game library and the Intel pages load an ad from Google AdSense. A game page never does — the ad script is not on those pages at all. Where an ad does load, Google may set its own cookies:
IDE— set on Google'sdoubleclick.netdomain. It identifies this browser to Google's ad system so the same ad is not repeated on every page and so a view can be counted.__gadsand__gpi— set onunplayable.xyzby Google. They record which ads this browser has already seen, which limits repetition and measures performance.test_cookie— a short-lived check that the browser accepts cookies at all.
These belong to Google, not to Unplayable, and they are absent from every page without an ad. What you can do: switch off personalised advertising in Google Ads Settings, decline the consent message that appears on your first ad page (EEA, UK and Switzerland), use the opt-outs listed at aboutads.info, or block third-party cookies in the browser. None of that affects the games.
Visit counting
The Info panel shows how many people have opened the site. That counting is done without cookies and without storing IP addresses:
- When a page loads, a small request records one visit.
- A visitor is identified by a one-way hash of (a secret + your IP address + your browser's user agent). The address itself is used to compute the hash and then discarded — it is never written anywhere.
- The hash cannot be reversed without the secret, and it is not linked to an account. Delete cookies, change networks, or use another browser and you count as a new visitor.
- Requests that look automated — crawlers, previews, scripts, and browsers that announce they are driven by automation — are not counted: nothing is stored for them.
Third parties
- Cloudflare serves the site and may set its own security cookies (for example when it challenges automated traffic) and keeps request logs under its own policy.
- Google Fonts serves the two typefaces the site uses. That is a request to Google, which sees your IP address; no cookie of ours is involved.
- Google Sign-In only happens if you press the sign-in button, and then Google's own cookies apply to that flow.
- Google AdSense serves the ads described above, and its cookies are listed in that section.
There is no analytics provider, no embedded video and no social widget. The only third-party script that can set a cookie is the advertising one, and it is limited to the pages that carry an ad.
Contact
Questions about cookies or storage: hello@unplayable.xyz.
See also: Privacy Policy · Terms of Use