Cookies and local storage

Published 14 August 2026. No lawyer has read this.

That is worth stating plainly rather than leaving you to assume otherwise. This document was prepared by the person who operates the site, not by a solicitor, and nobody with legal qualifications has checked it. It is published for information only and does not constitute legal advice.

The factual parts are not hedged, and they are the parts you can check. What this site stores, what it sends, and what changes when advertising is switched on are all described exactly as they are — and you can confirm most of it yourself in your browser's developer tools in about thirty seconds. Where something is genuinely undecided it is named below rather than filled in with something plausible.

Nothing in this particular document is unsettled — it describes what the site does, and that is a matter of fact rather than of drafting.

1. The honest headline

This site sets no cookies. Not one — not for analytics, not for preferences, not for advertising, and not the “essential” kind either. There is no banner asking you to accept anything because there is nothing to accept.

It does store things in your browser, and that is a different mechanism with different properties. The rest of this page is about the difference, and about exactly what is stored.

2. Local storage is not a cookie

They are often talked about as if they were the same thing. The distinction that actually matters to you is this: a cookie is attached to every request your browser makes to the site, and local storage never leaves your device. A cookie travels; local storage sits still.

That is why the lists you save here can be genuinely private in a way a cookie-based version could not be. It is also why they cannot follow you to your phone.

3. Everything this site stores

The list below is generated from the same registry the code reads, so it cannot fall out of step with what the site actually does — and a key with no description here stops the build rather than shipping undescribed.

Key	What it holds
`lw:theme`	Whether you chose light or dark. If you never chose, this is absent and the site follows your operating system.
`lw:lists`	The lists you explicitly saved and named, shared across the wheel, the team generator and the order shuffler — so a roster typed once does not have to be typed again.
`lw:random-order:state`	Whatever was in the order shuffler’s box when you last left it.
`lw:team-generator:state`	Whatever was in the team generator’s box when you last left it.
`lw:wheel:state`	Whatever was in the wheel’s box when you last left it.
`lw:dice:state`	The dice you had set up, and your roll history.
`lw:coin-flip:state`	Your running coin tally.
`lw:random-number:state`	The range and settings you last used for drawing numbers.

Two more things can appear, and neither is a surprise once explained. If a saved value ever fails to load — corrupted, or written by a newer version of the site — it is moved to a key beginning lw:quarantine: rather than deleted, so that a bad read can never destroy the only copy of something you care about. And when the site checks whether storage is available at all, it writes a temporary value and removes it immediately; nothing is left behind.

4. How to remove it

Clearing site data for this site in your browser removes every one of the keys above, immediately and completely. You do not need to ask anybody, and nothing needs to happen at our end, because there is no our end — it is all on your device.

Private or incognito windows discard it when the window closes, and some privacy settings block storage entirely. The tools still work in that case; the saving does not, and each page says so rather than failing quietly.

5. What would change if advertising were switched on

No advertising code is loaded at the time of writing, and that is checked on every build rather than promised — the build fails if any ad or analytics code appears in the published files.

If it is switched on later, Google and its partners would set their own cookies, and this section would list them by name and purpose in the same release. That ordering is deliberate: the disclosure and the change ship together or not at all. A cookie table written in advance would describe cookies that do not exist, and one written afterwards would be a page that was wrong for however long it took somebody to remember.

6. Changes

Anything that alters what is stored is recorded on the changelog with its date. See also the privacy page, which covers what the web server itself sees.