Skip to content
Snagglee

Cookie Disclosure

Updated 15 September 2026

The Short Version

Snagglee does not set any cookies of its own, does not use tracking pixels, and does not run advertising scripts of any kind. The only thing stored in your browser is a single, small preference remembering that you have seen the cookie notice, and even that is entirely optional to keep — clearing it just brings the notice back on your next visit.

What This Site Stores In Your Browser

When you choose "Fine by me" or "Not for me" on the notice at the bottom of the screen, the site writes one entry to your browser's local storage so it does not ask again on your next visit. This is, technically, local storage rather than a cookie, but it is listed in the table below for full transparency. It never leaves your device, is never sent to our server, and is never read by us.

Cloudflare's Cookie-Free Analytics

Cloudflare, the content-delivery network that serves this site, may run a cookie-free analytics process (Cloudflare Web Analytics) that measures aggregate figures like page-load speed and approximate visitor volume without placing any cookie on your device or tracking you individually across other sites. It is listed below alongside our own local-storage entry for completeness, even though, technically, it involves no cookie at all.

The Table Below

The table lists everything this site is aware of that touches your browser or your request, cookie or not, so there is nothing left unstated.

Managing or Clearing This

Because nothing here is a traditional cookie, your browser's cookie settings will not show anything to manage. To reset the notice preference, clear your browser's local storage or site data for snagglee.com — the notice will simply reappear on your next visit. Standard browser cookie controls remain available to you for any site, ours included, even where nothing is currently set.

Changes to This Page

If what this site stores ever changes — for instance, if a future feature needed a real cookie — this page and its table would be updated to match before that change goes live, not after.