1. What cookies are
A cookie is a small text file a site stores in your browser so it can recognise you on the next request — for example, to keep you signed in between pages. Similar technologies include local storage and pixels.
2. Cookies we set
| Name | Purpose | Type | Expires |
|---|---|---|---|
| sa_sid | Keeps you signed in and links your browser to your session on the server. Without it you would be signed out on every page. Also carries the CSRF token that protects forms from cross-site submission. | Strictly necessary | 14 days |
sa_sid is set with the HttpOnly, SameSite=Lax and —
over HTTPS — Secure flags, so it cannot be read by scripts or sent from another
site.
3. What we do not use
This build sets no advertising cookies, no cross-site tracking pixels and no third-party analytics cookies. We do not build advertising profiles and we do not share cookie data with ad networks. Because the only cookie we set is strictly necessary to deliver a service you asked for, no consent banner is required in most jurisdictions.
Web fonts are loaded from Google Fonts, which means your browser makes a request to that service; it receives your IP address as part of any web request but is not used here to set a cookie. If you would rather avoid that request entirely, the fonts can be self-hosted — ask us.
4. Controlling cookies
Every major browser lets you view, block and delete cookies from its privacy settings.
Blocking sa_sid will prevent you from signing in, since there would be no way
to maintain a session. Public pages — the state browser, search and the Ask page — work
without it.
We honour the Global Privacy Control signal where your browser sends one. As we do not sell or share personal data, there is nothing further to opt out of.
5. Changes
If we add a cookie, this page and the table above will be updated before it is set. See the Privacy Policy for how personal data is handled more generally.