Cookies
Three of them, and only one is optional
You can read the whole calendar without accepting anything. Nothing optional is set until you say yes, and saying no leaves the site working exactly as it does now.
Signing in
When you sign in, Supabase sets a cookie that keeps you signed in. Without it you would be signed out on every page, so there is no option to refuse it — declining it and signing in are the same request. It goes away when you sign out.
Remembering your answer
When you answer the banner, we set one cookie to remember what you said, so we stop asking. It holds one word — whether you agreed — and nothing else. It lasts a year, and clearing it means we ask again rather than assume.
Analytics, if you agree
If you accept, Google Analytics sets cookies that let us count how many people read a page and which searches come up empty. That is genuinely what we use it for: an empty search is a race missing from the calendar, and it is the most useful signal the site produces. If you decline, Google Analytics is never loaded at all — not loaded and switched off, but never fetched.
We used to run Microsoft Clarity, which recorded sessions and built heatmaps. It has been removed, and it is not coming back behind a checkbox.
Changing your mind
Whenever you like, and without emailing anyone.
You haven't answered yet, so analytics are off.
The rest of what we hold, and how to ask for a copy or a deletion, is on the privacy page.