Most cookie policies are long because most sites have a lot to declare. This one is short for the opposite reason.
Cyclosa sets no analytics cookies, no advertising cookies and no third-party trackers. There is nothing here to opt out of, which is why you have not been shown a consent banner.
Every cookie below exists to keep you signed in or to stop someone signing in as you. Under the ePrivacy rules these are strictly necessary, and consent is not required for them. If that changes — if we ever add something measuring you — you will be asked first, and this page will say so before it happens.
Nothing is stored until you sign in. Browsing the marketing pages sets no cookies at all.
| COOKIE | WHAT IT DOES |
|---|---|
| authjs.session-token | Your signed-in session. Holds a signed token identifying your account — no password, and nothing readable by a script on the page. Expires when the session does. |
| authjs.csrf-token | Stops another site from submitting the sign-in form on your behalf. Set when a form is shown, checked when it is submitted. |
| authjs.callback-url | Remembers which page to return you to after sign-in, so you land where you started. |
| authjs.pkce.code_verifier | Only when you sign in with Google. Ties the response coming back from Google to the request that started it, then expires within minutes. |
| cyclosa_admin | Operator console only. A signed, eight-hour session for our own staff. A customer browser never receives this. |
Over HTTPS the first four carry a __Secure- or __Host- prefix, which tells your browser to refuse them over a plain connection. All of them are HttpOnly — no JavaScript on the page can read them — and all are restricted to this site.
The privacy policy lists the handful of services that do receive data — Polar for payments, Google if you choose to sign in with it — and exactly what reaches each of them.
Every browser lets you block or clear cookies for a site. Blocking ours does not degrade the marketing pages, which need none of them — but it makes signing in impossible, because a session that cannot be remembered is a session that ends on the next page load.
Open an account and see what the console does with the data it holds — which is only what you put in it.