Cookie Policy

1. What we set, and when

If you are not signed in, Sooqban sets no cookies at all. You can read every public page without one.

When you sign in, one cookie is set:

• better-auth.session token. This is your session. It tells the server that the browser asking for a page is the one that signed in. It cannot be read by scripts, it is not sent with requests that come from other sites, and it lasts seven days or until you sign out.

2. The one other cookie, and the ten minutes it lives

If you set up two-step sign-in, a short-lived cookie holds that setup while you confirm it with a code. It lasts ten minutes and is deleted the moment the setup is proved. It is never used for anything else.

3. There is no consent banner, and this is why

A banner exists to ask about cookies that are not strictly necessary. Analytics, advertising, tracking across sites. Sooqban has none of those. The session cookie is what makes being signed in possible, which is the one category no banner asks about.

If that changes, and measurement is something this platform will eventually need, this policy becomes a new version, and you will be asked before anything non-essential is set. Asking afterwards is not asking.

4. What we do not do

No advertising cookies. No cross-site tracking. No third-party analytics script running on these pages. No cookie that builds a profile of what you look at.

Nothing on Sooqban is loaded from an advertising network, and the fonts come from our own servers rather than from anyone else. That is also why no font provider learns that you visited.

5. Controlling them yourself

Your browser can block or delete cookies, and you can sign out, which ends the session everywhere rather than only in this browser.

Blocking the session cookie means you cannot stay signed in, not as a punishment, but because being signed in is what that cookie is.

6. Changes

This policy carries a version and a date. If the set of cookies changes, so does this document, and the new version says what changed.