Privacy

Written from the database schema rather than from a template, so it describes what is actually stored. Last updated 30 August 2026.

The short version

You can play without giving us anything. No account, no email, no name. A cookie is set the first time you press PLAY so your scores can be yours; nothing else about you is recorded unless you choose to add it.

What we store

A handle, in a cookie

Pressing PLAY for the first time issues adrun_pid, a random identifier with no meaning outside this site. It lasts a year, and it is HttpOnly, so no script on the page can read it — including any script an advertiser might one day get onto it. It is how the server knows a returning player is the same player.

Runs and scores

For each run we keep the score, how long it lasted in ticks, when it happened, and the seed the world was built from. We also keep the verdict our anti-cheat gave it.

To verify a score, your browser sends the inputs you pressed and the server replays the run to see whether that score is really what those inputs produce. Those inputs are replayed in memory and then discarded. They are never written to the database.

A name, only if you claim one

If you claim a name or an X handle, we store it and a folded version used to stop two people claiming the same one. You are also shown a recovery code once; we store only a salted SHA-256 hash of it, exactly as a password would be handled, so a copy of our database cannot be used to take over your name.

An account, only if you sign in

Signing in with Google or X stores which provider you used, the identifier that provider gave us, and an email address if the provider supplied one. X frequently does not, and we do not require it. We never receive your password, and we ask for nothing beyond basic profile identity.

Your address, briefly and not on disk

Two things need to know requests are coming from the same place: rate limiting, and the “N online” counter. Both hold that in memory only.

The online counter never stores your address at all. It keeps a salted hash of it, with a salt generated fresh each time the server restarts, and forgets the entry two minutes after you go quiet. Nothing about it reaches disk, and after a restart the old hashes are meaningless even to us.

Advertiser clicks

Clicking a sponsor’s link adds one to a counter for that sponsor. There is no player identifier on it. We can tell an advertiser their listing got 40 clicks; we cannot tell them, and do not know, who clicked.

What we do not do

• No third-party analytics, no advertising trackers, no pixels.
• No profiles, no cross-site tracking, no fingerprinting.
• We never sell or share personal data. Advertisers get counts, never people.
• Advertiser logos are proxied through this site rather than loaded from their servers, so browsing the sponsor board does not tell them you were here.

How long we keep it

Scores and names persist while the leaderboard does — that is the point of a leaderboard. Runs that were issued but never submitted are swept automatically. Presence data lasts two minutes. Ask us to delete your data and we will remove your player record, your scores and any linked account.

Your rights

If you are in the UK or EU, the GDPR gives you the right to access, correct, export or delete what we hold, and to object to processing. The lawful basis for the handle cookie and for rate limiting is legitimate interest — running a leaderboard that cannot be trivially cheated. The lawful basis for a name or an account is your consent, given by choosing to add one.

To exercise any of this, or to ask anything at all, email privacy@adrun.lol.

Cookies

One: adrun_pid, described above. It is strictly necessary for the leaderboard to work, which is why there is no cookie banner asking you to accept advertising cookies — there are none to accept. Signing in adds session cookies from Auth.js for as long as you stay signed in.

Changes

If this changes materially we will update the date at the top. The site is small enough that we can tell you plainly rather than burying it.