Cookie policy

One cookie: the session cookie Supabase Auth sets to keep you signed in between page loads. It's strictly necessary for the Service to function — without it, you'd have to sign in again on every page. Because it's strictly necessary, it doesn't legally require opt-in consent under GDPR/ePrivacy the way analytics or advertising cookies would.

We also use Vercel Analytics for aggregate traffic numbers (which pages get visited, roughly how many people). It's cookieless — it doesn't set anything in your browser or track you individually across visits, so it doesn't trigger the same consent requirement as cookie-based analytics tools.

No advertising cookies, no third-party tracking pixels, no cookie-based analytics. The consent banner you may see on this site reflects the cookie side of that — it's a notice, not an opt-in request, because there's no optional cookie to opt into yet.

Switching from Vercel Analytics to something cookie-based (or adding one alongside it — Plausible, PostHog, Google Analytics), update this page with what it collects. Cookie-based analytics tools generally require consent before they fire in the EU/UK — the banner component in this codebase (components/CookieBanner.tsx) is built to be extended for that, not just decoration.

Most browsers let you block or delete cookies in their settings. Blocking the session cookie will sign you out and prevent staying signed in — that's the tradeoff of it being strictly necessary rather than optional.