Cassette Cookie Notice
Last updated: TODO: publish date
Cassette's own pages set no cookies. They don't use advertising, third-party analytics or tracking across sites. To work, they store a few things in your browser's local storage. Each one is strictly necessary for something you asked for, so we don't need to ask for your consent to them, and we don't show a cookie banner. If we ever want to store anything that isn't strictly necessary, we'll ask you first.
We count visits with our own statistics, which store nothing in your browser. Our server recognises a visit for one day using a code it works out from your connection; the code changes every day and can't be traced back to you. See the Privacy Policy.
What Cassette stores in your browser
| What | Where | Why | How long |
|---|---|---|---|
| Your session: wallet address, sign-in token, @username and the email or account name you signed in with | Local storage | Keep you signed in | Until you sign out (the token expires after 7 days) |
| Wallet session and key | Local storage and IndexedDB, written by Polygon's wallet software | Let your browser use your wallet without passwords or pop-ups | Up to 180 days, or 10 days without use |
| Device key | IndexedDB | Tie play sessions to this browser, so copied session codes don't work elsewhere | Until you clear site data |
| Sign-in in progress | Session storage | Finish a Google or Apple sign-in when you return to the page | Until the tab closes |
| Claim in progress and publish draft | Local and session storage | Let a developer finish claiming a listing and publishing it | Until finished or the tab closes |
You can delete all of this by signing out and clearing site data for cassette.gg in your browser settings. You'll have to sign in again afterwards; what you own stays in your wallet.
Third parties
- Cloudflare, which delivers and protects Cassette, may set a security cookie (such as
__cf_bm) to tell people from bots. It is strictly necessary and expires within 30 minutes. - Google and Apple set their own cookies on their own pages if you sign in with them.
- Games. Games run from their developers' own hosting, shown inside Cassette. A game's own code and its host may set cookies or store data in your browser, for example to save your progress or offer offline play. The developer is responsible for what its game and host store; check its privacy notice, linked from the game page.
More
See our Privacy Policy for how we use data, or write to [email protected].