Skip to content

Cookie Policy

Sooqban sets no cookie until you start to sign in, and then only the ones signing in needs. This page names each of them, says what it does and how long it lasts, and explains why there is nothing to consent to yet.

Version
2026-10-1
In force since
8 Oct 2026

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.

Each cookie below exists only because signing in needs it. None of them can be read by scripts on the page, and none is sent with requests that come from other sites.

On the live site the first three carry __Secure- in front of their names, which tells your browser to send them only over an encrypted connection.

  • better-auth.session_token: your session. It tells the server that the browser asking for a page is the one that signed in. It lasts seven days, renewed as you use the site, never more than 30 days from signing in, and it ends when you sign out.
  • better-auth.two_factor: set when your password is right and two-step sign-in is on, to hold that first step while you enter your code. It lasts ten minutes and is deleted as soon as the code is accepted.
  • better-auth.state: set when you choose to sign in with Google, so that Google’s answer can be matched to the sign-in you started. It lasts five minutes and is deleted when Google answers.
  • sq_2fa_setup: set while you set up two-step sign-in, to hold the setup until 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.

2. Google’s own cookies

If you choose to sign in with Google, you are sent to Google’s own pages for a moment, and Google sets its own cookies there, under its own policy. They belong to Google’s site, not to ours, and Sooqban cannot read them.

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. Every cookie above is what makes signing 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. Signing out ends the session in this browser only; Other devices, on your account’s Security page, ends it everywhere else, and changing your password does the same.

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.

Earlier versions

Every version anyone has agreed to stays readable, exactly as it was.

Contact

Write to us about anything in this document:

Sooqban
THE FIRST PROJECT S.P.C
Commercial registration 1582509
Ghala
privacy@sooqban.com