Cookie policy
We set one cookie. It keeps you signed in. That's the whole policy, but here it is properly.
Last updated 12 August 2026
01The banner, and what it actually controls
Your answer is remembered in your browser's local storage rather than in a cookie, which is why saying yes or no doesn't itself add one to the list below. You can change it here, whenever you like:
Checking your current choice…
02The cookie
| Name | Purpose | Lasts | Type |
|---|---|---|---|
| khan_session | Keeps you signed in. It holds an opaque, random token, not your identity, and nothing readable about you. | 30 days, or until you sign out | Strictly necessary. First-party. |
It's marked HTTP-only, so JavaScript can't read it; SameSite=Lax, so it isn't sent from other sites; and Secure in production, so it only travels over HTTPS.
03What we don’t use
No Google Analytics. No advertising or retargeting pixels. No social media trackers. No session recording or heatmaps. No fingerprinting. Nothing that follows you to another site, and nothing that builds a profile of you.
04Controlling it
Sign out and the cookie is cleared. You can also block or delete cookies in your browser settings, but since this one is what keeps you signed in, blocking it means you can't stay signed in. The public site works fine without it.
05If this changes
If we ever add something that sets a non-essential cookie, we'll update this page and ask for your consent first: properly, with a real choice, rather than a banner engineered to be accepted. Questions: hello@khanterminal.com.