POUNCE// PRIVACY

What Pounce stores in your browser, what gets sent to a server, and what doesn't · play the game → · read me

Short version

Pounce is a browser game. It saves your settings and progress locally on your device using localStorage (a more modern alternative to cookies, but functionally similar). The only time anything leaves your browser is when you submit a high score to the global leaderboard — and even then it's just a name and a number. The site doesn't use tracking cookies, third-party analytics, or advertising.

What is stored locally on your device

Each setting and bit of progress is stored under a named key in your browser's localStorage. Nothing here is shared with a server unless explicitly noted in the next section. If you clear your browser's site data, all of these are deleted.

Key	What it holds	Why
`pounce_cat`	Which of the four cats you picked (black, tabby, calico, orange)	So your choice persists between sessions
`pounce_music`	Music on / off (a single character: `1` or `0`)	Remember your audio preference
`pounce_sfx`	Sound effects on / off	Same — remember your audio preference
`pounce_music_vol`	Music volume (a number between 0 and 1)	Remember the slider position
`pounce_sfx_vol`	Sound-effects volume	Same — slider position
`pounce_level`	The level you last played	So returning visits resume on the right level
`pounce_progress`	Which levels you've unlocked + your best score per level	So you can continue past the first level on a return visit
`pounce_leaderboard_v1`	A cached copy of the global top-3 scores	So the leaderboard strip paints instantly without waiting for the network
`pounce_lb_last_name`	The last 5-character name you typed when submitting a high score	So repeat submissions are one tap shorter

That's the complete list. There are no tracking cookies, no fingerprinting cookies, no third-party cookies, and no third-party JavaScript that reads your storage.

What's sent to a server

Two things, both via Supabase over HTTPS, and only at specific moments:

Top-3 leaderboard fetch. When the page loads, and again right after a successful score submit, the game asks Supabase for the current top-three names + scores. No identifying information is sent in the request beyond the anonymous Supabase publishable key, which is meant to be public.
Score submit. If your final score qualifies for the top three and you choose to enter a name, two values are sent: the 5-character name you typed, and your numeric score. Nothing else — no IP capture by the application, no browser fingerprint, no email.

You can decline the score submit by simply not typing a name and closing the prompt. Your score still saves locally; it just doesn't appear on the global board.

What's not stored or collected

No login, account, or email is required to play.
No analytics tracker is loaded.
No advertising network is loaded.
No social-media tracking pixels are loaded.
The game does not read or write any other browser data (cookies, IndexedDB, etc.) — only the localStorage keys listed above.
The game has no access to your device's location, camera, microphone, contacts, or files.

How to delete your data

To wipe Pounce's stored data:

Easy: in your browser, clear site data for pounce.mike-lee.me. In Chrome that's Settings → Privacy → Cookies and other site data → See all site data → search for pounce → delete.
Per-key: open DevTools → Application → Local Storage and remove the keys above individually.
Global leaderboard entry: if you submitted a score and want it removed from the global board, email the address below with the name you used and the rough date — I'll delete it manually.

Children

Pounce is suitable for all ages. It does not collect personal information, so there is nothing to delete or share specific to children under 13. The score-submit prompt accepts a 5-character name, which we recommend not be the player's full real name.

Contact

This site is run by Mike Lee. For privacy questions, leaderboard removals, or anything else, contact me through that LinkedIn page or via mike-lee.me.

Changes

If this policy changes — for example if I add an analytics library, or any new localStorage key — the change will be visible in the page's git history, and a note will be added near the top of this page summarising what changed and when.

Last updated: 2026-04-26