RetroSweep has no accounts and no sign-up. This page lists everything it stores and why. It’s short because there’s little to list.
What is stored
-
An anonymous cookie (
rs_daily_id), a random identifier with no personal information in it. It exists solely to enforce one recorded daily challenge attempt per UTC day, and the server reads it only for that. It is a first-party cookie set to SameSite=Lax and expires after one year. - An optional leaderboard entry. If you submit a score, the handle you type is stored alongside your time and difficulty. Leaving the field blank records the entry as anonymous. Entered handles are public on the leaderboard.
- Your history, in this browser only. Local storage keeps your daily results (for the streak) and your best Classic times. It also keeps your game settings: the last board size and mode you played, your custom board, and the Dig/Flag mode on a phone. It remembers the name you last posted under and which tips and walkthroughs you’ve already seen or hidden. It notes the date you first played here, so the beginner tips stop after your first week. It also keeps your Safe Pick best and sound setting, your answers to the install and reminder offers, and which loss and win lines you’ve seen today, so they don’t repeat. None of it leaves your device unless you post a time.
- Game files for offline play. Once you have visited, the browser keeps a copy of the game's pages, scripts and images so RetroSweep loads and plays without a connection. It holds nothing about you.
- Daily reminders, only if you turn them on in the installed app. Your browser gives us a push address, a web link issued by its push service (Google, Apple, Mozilla or Microsoft), which we store with two dates: the last day you played a daily on that device, so that day's reminder is skipped, and the last day a reminder was sent, so you never get more than one a day. Reminders go out through that push service. Turning reminders off deletes the address straight away. If you block notifications instead, it’s deleted the next time a reminder can’t be delivered.
Leaderboard names
Names are checked automatically against a list of blocked words before they’re posted. If a name is refused, you get an error so you can pick another.
The same check runs whenever a leaderboard is shown. So if a word is added to the list later, earlier entries using it show as Name hidden, and the time stays on the board.
Analytics
RetroSweep loads Vercel Web Analytics, which reports aggregate usage such as page views. It is cookieless and sets no identifier on your device; it does not track you across sites and does not identify you. It also loads Vercel Speed Insights, which reports how fast pages load (page load timings with your device type and browser). It is cookieless in the same way.
With your consent, RetroSweep also loads Google Analytics 4. It sets first-party cookies (named _ga and similar) to count returning visits. It records aggregate, non-identifying behavior: page views and a few gameplay events.
Those events are: the first click on a board; starting, winning or losing a game (with its mode, board size and time); changing mode or board size; starting or finishing the daily challenge or Safe Pick; moving between modes using the game’s buttons and cards; opening the stats panel; sharing a result; hiding the homepage tips; and the install and reminder offers. No handle or personal information is attached to these events.
Consent is required first. Google Analytics runs under Google Consent Mode with everything denied by default. Its script isn’t even downloaded until you choose Accept on the cookie banner. Choose Decline and it never loads and no Google request is ever made. Your choice is remembered in your browser so the banner does not reappear.
You can change your mind at any time:
What is not stored
No advertising cookies and no cross-site tracking. Analytics cookies are set only if you accept them, and no personal identifying information is stored beyond the optional leaderboard handle. RetroSweep does not sell or share this data with third parties.
Why the cookie exists
It is functional, not analytical. The one-attempt-per-day rule needs a way to tell one browser from another without an account, and the anonymous identifier is that. Clearing your cookies removes it; a new one is set the next time you open the daily challenge.