Cookie policy
Last updated November 2, 2026
TrailCircuit doesn't use advertising or analytics cookies, and nothing on the site tracks you across other websites. That's why there's no cookie banner. This page lists what the site, and the services it relies on, store in your browser, and why. "Cookies" here also covers similar browser storage such as local storage and IndexedDB.
What's stored
| What | Set by | Purpose | How long |
|---|---|---|---|
Sign-in token (IndexedDB, firebaseLocalStorageDb) | Firebase (Google), only when you sign in | Keeps you signed in so you can comment and post. Strictly necessary for that feature. | Until you sign out or clear your browser data |
Park finder search (local storage, tc:search) | TrailCircuit | Remembers your last starting place, distance and filters. It never leaves your device. | Until you clear your browser data |
| Spam check (Turnstile) | Cloudflare, on the contact page only | Tells people from bots before a message is sent. Strictly necessary for the form. | For the visit |
Security cookies, such as __cf_bm | Cloudflare, only if it detects unusual traffic | Protects the site from bots and attacks. Strictly necessary. | Up to 30 minutes |
The sign-in popup for Google is run by Google on its own site, under Google's cookie policy.
Your choices
Everything above is either needed for a feature you chose to use or kept only on your device, so the site doesn't ask for consent. You can still block or delete it in your browser's settings. If you do, the site keeps working for reading. You'll be signed out, and the park finder will forget your last search.
Changes
If we ever add analytics or advertising cookies, we'll update this page first and ask for your consent where the law requires it.
More about how we handle information is in the privacy policy. Questions? Use the contact form.