Cookies

There is no banner because there is nothing to consent to. Everything here is either how sign-in works or a preference you set yourself.Last updated 2026-08-17

Draft — not yet reviewed by counsel. Wording may change before it is relied on.

1. The cookies

Name	What it does	Set when	Lifetime	Sent to
`SSESS…`	Keeps you signed in. A random session id; the session itself lives on our server.	When you sign in	23 days idle, or until you sign out	Our server, over HTTPS only
`sot_theme`	Remembers whether you chose the light or dark scheme, so the page renders in it before any script runs.	When you pick a scheme	1 year	Our server (read only to render the right scheme)
`sot_rail`	Remembers whether the left rail is expanded or collapsed, so it does not flash on load.	When you toggle the rail	1 year	Our server (read only to render the rail state)

Cross-site request forgery protection uses a token fetched by the page and sent in a header; it is not a cookie. Cloudflare may set a short-lived challenge cookie (cf_clearance or similar) if it needs to tell a browser from a bot; that is Cloudflare’s, is strictly necessary for the site to be reachable, and is described in their policy.

2. Local storage

Two small keys in your browser’s local storage, never sent to us: which rail sections you folded, and whether you have already seen the one-time meetup safety notice. Clear your browser storage and they are gone.

3. What there is not

No analytics cookies. No analytics at all.
No advertising cookies. No advertising.
No third-party scripts that set cookies. GIF search is proxied through our server so the provider never sees your browser.
No cookie banner, because a banner for the three above would be theatre.

4. If that changes

If analytics or anything non-essential is ever added, this page will list it first, and where the law requires consent before it is set, consent will be asked for — with an equally easy no. Until then, the Privacy Notice is the whole story.