Cookie atlas

30 March 2026 · Applies to same-origin top10ukselection.co.uk surfaces only.

Micro files + storage silos remember compliance choreography (age clearance, puzzle clearance, banner vote). Optional analytics—if it ever lands—loads only after Allow all. Below: handles, jobs, clocks, brakes.

1. Cookie vs localStorage — cheat line

Cookies hitch on HTTP hops; localStorage camps in the tab until you evict it. Different APIs, one transparency bucket here.

2. Stacks

Strictly necessary

Top10ukselection_age, Top10ukselection_entry (cookies) echo Top10ukselection_age_ok, Top10ukselection_entry_ok, Top10ukselection_cookies (local). Combo fuels the age sheet, slider gate, and ribbon memory. Nuke them and every refresh reboots onboarding.

Optional / analytics-ready

Hypothetical pixels stay dark until Allow all. “Necessities only” keeps measurement hungry on static hosting wherever the stack permits.

3. TTL

Consent cookies aim for ~12-month max-age where browsers obey. Purge faster anytime via site-data panels in Chrome, Safari, Firefox, Edge.

4. Third rails

Google Fonts may chirp upstream—read Google’s own retention yarn. Casino tabs you spawn afterwards bake their own cookies; we can’t see or wipe those remotely.

5. Controls

Ribbon: Allow all vs Necessities only first. Global nuclear block still works if you accept janky chrome. GDPR levers sit in the Privacy charter.