SynthCrewCookies and local storage.
Website sign-in uses Better Auth cookies to maintain authentication and protect the sign-in flow. Google or GitHub may also use cookies under their own policies when you choose to sign in.
Sign-in cookies in the current source
The table describes the configured application and its pinned Better Auth defaults, not an observed inventory of every cookie in your browser. Cookies are set when the relevant flow is used. These defaults use Secure, HttpOnly, SameSite=Lax, and path /; cross-subdomain cookies are not enabled.
| Cookie | Purpose and default lifetime |
|---|---|
__Secure-better-auth.state | Checks the sign-in request against its return from a provider. Maximum age: five minutes. |
__Secure-better-auth.session_token | Maintains the website session after sign-in. Normally seven days; the library can use a browser-session cookie for a do-not-remember session. |
__Secure-better-auth.dont_remember | Optional marker for a do-not-remember session, when that flow is used. No persistent maximum age is set. |
Session-cookie caching is not enabled by this database-backed configuration. Provider cookies and other browser storage have not been inventoried here; their behavior and settings can change. Clearing site data can sign you out.
The website source does not add an analytics service or advertising trackers. The desktop stores project work and conversations locally and protects its customer credential with the operating system’s secure store.
For the wider data flow, read privacy and data processing. For account and desktop controls, see connect a Client desktop.