localhost6767
Short version: we never ask for your name, email, phone number, or password. We store a passkey public key, what you submit to the wheel, your spins and reports, and one session cookie. There are no ads, no trackers, and no selling of data.
| Data | Why | How long |
|---|---|---|
| Passkey credential: credential ID, public key, signature counter, device type, whether it is backed up | To sign you in. Your biometric or PIN never leaves your device; we receive only a public key and signed challenges. | Until you delete the passkey or your account |
| Random account ID and creation time | To link your passkeys, codes, spins, and reports together | Until you delete your account |
Session cookie localhost6767_session (random token, stored on our side as a hash) | To keep you signed in. Strictly necessary; HttpOnly; expires after 30 days or on sign-out | 30 days |
| Short-lived state cookie during a passkey ceremony | To bind the challenge to your browser | 5 minutes |
| Referral codes or links and the benefit note you submit. Entries are labelled with your account number, never a name. | To show them on the wheel to other users. The code or link is visible to whoever lands on it. | Until you delete it or we remove it |
| Your spins: app, slice landed on, which code you got, seeds used for the fairness proof. Without an account they are stored under the hashed browser token; they move to your account when you create a passkey from that browser. | To enforce one spin per app, to let you reopen your result, and to let you verify the spin was fair | Until you delete your account; guest spins until that browser token is cleared |
| Your "worked / didn't work" reports and your "misleading or offensive" reports | To show community counts on a code and to hide entries that several accounts report | Until you delete your account, the code is edited (worked / didn't work only), or the code is deleted |
| Which app you added to the dock, if any | To enforce one app per account. This row stays if you delete your account, since it is not personal data. | Indefinitely |
| A random browser token (kept in your browser's localStorage, stored on our side only as a hash) and a two-letter country code | To count roughly how many browsers are active in the last two minutes and show them by country in the "Active users" window. The country code is derived by our hosting provider from your IP address at request time; we store the code, never the IP, and it is not linked to your account. | 24 hours after last check-in |
| Server and access logs kept by our hosting provider (IP address, user agent, request path, timing) | Security, abuse prevention, debugging | Per the provider's retention, typically days to weeks |
No email address, name, phone number, password, biometric data, payment details, precise location (country only, see above), advertising identifiers, or cross-site tracking. We do not sell, rent, or share data for advertising.
We use one strictly necessary session cookie and one short-lived passkey state cookie. We do not use analytics or advertising cookies, so no cookie banner is shown. Your browser's localStorage holds a random token for the active-user count; clearing site data removes it.
Servers may be located outside your country. We do not use any other third-party service, and we never send your data to the apps whose codes are listed.
If you are in the EU, UK, or another place with data-protection rights, you may also have the right to object, restrict processing, port your data, or complain to a supervisory authority. Our legal basis for processing is performance of the service you asked for (sign-in, spins, submissions) and our legitimate interest in keeping the service secure and fair.
The site is not directed at children and we do not knowingly collect data from anyone under 18. If you believe a minor has created an account, email us and we will delete it.
Passkeys mean there is no password to leak. Referral codes and links are encrypted at rest (AES-256-GCM) with a key that lives only in the server environment, so a copy of the database alone does not reveal them; they are decrypted only to show a code to the person whose spin landed on it, or to its owner. Session tokens and browser tokens are stored only as keyed or SHA-256 hashes. Cookies are HttpOnly, SameSite, and Secure in production. Links are validated to be https on the app's official domain. No system is perfectly secure, so please report issues to the email above.
We will update the date at the top when this policy changes. Significant changes will also be mentioned in the About window on the site.