Cookies, plainly.
What gets stored in your browser, what it does, and what never gets set. Each section starts with the short version.
The short version
The public pre-launch site sets no cookies. None — not analytics, not preferences, not tracking. That's also why there is no cookie banner: a banner asks consent for something, and there is nothing here to consent to.
What the site stores today
In short — zero on the public site.
The landing page and these legal pages run without setting or reading a single cookie, and the fonts we load set none either. Two sessions exist: the one our staff get when signing in to the content admin, and the one you get when you sign in to your own account. If you have not signed in, your browser holds neither.
When accounts arrive
In short — a session cookie so you stay signed in — that’s its whole job.
Sign-in needs a session cookie; that's the mechanism. It identifies your session to us and to nobody else, and it carries nothing beyond that. Interface preferences stay in your browser's own storage on your device — they aren't sent anywhere.
Analytics
In short — if it ever ships, it’s privacy-respecting and listed here first.
There is no analytics on the site today. If we add any, it will be the privacy-respecting kind — aggregate counts, no cross-site identity — and it will be described here before it runs. Third-party advertising cookies don't ship at all; the privacy policy already rules them out.
Your choices
In short — your browser already has the controls.
Every browser can inspect, block or clear cookies — nothing we set fights that. The only tradeoff arrives with accounts: clear the session cookie and you're signed out. That's the whole consequence.
Changes
If what gets stored changes, this page changes first — material changes get an email and at least 15 days' notice, the same rhythm as the terms.
Contact
Questions: legal@unispawn.io. We read it.