Cookie Policy

Last updated: 31 October 2026

This policy explains how the Synapse web app uses cookies and similar technologies. It is short because the answer is simple: we use a small set of strictly necessary cookies to keep you signed in, and nothing else. There is no analytics, advertising or cross-site tracking on the hosted service.

Our approach

A cookie is a small file a site stores in your browser. Cookies can identify a returning browser, which is useful for sign-in and harmful when used for tracking. We only use them for the useful part.

The cookies listed below are strictly necessary to provide a service you asked for, so they are set when you sign in without a consent prompt. We do not use optional cookies, so there is no cookie banner and no preference to manage. If we ever add optional cookies, we will ask for your consent first and update this page.

Cookies we set

Authentication is handled by Supabase, and the cookies are set on synapse.app as first-party cookies. Their names include the Supabase project reference and begin with sb-.

Cookie
sb-<project-ref>-auth-token
Purpose
Stores your session and refresh token so you stay signed in. Large sessions may be split across numbered chunks such as .0 and .1.
Duration
Until you sign out, the refresh token expires, or you delete the cookie.
Cookie
sb-<project-ref>-auth-token-code-verifier
Purpose
Completes the PKCE sign-in flow used by email and Google authentication. It prevents an intercepted login link from being replayed.
Duration
A few minutes, until the sign-in round trip finishes.

Both cookies are strictly necessary. Blocking them disables sign-in; deleting them signs you out.

Local storage and similar technologies

The web app does not use localStorage, sessionStorage or IndexedDB for tracking. Sign-in state lives in the cookies above. The hosted service sets no advertising identifiers and no cross-site pixels. In the native apps, session tokens are kept in the operating system’s secure storage and are not browser cookies.

Third-party requests

Some features load from another company. These are requests, not our cookies, and the third party’s own policy applies to what it receives:

  • Google sign-in. If you choose “Continue with Google”, you are taken to Google’s authentication pages. Google may set cookies on its own domain during that flow; those are controlled by Google’s privacy policy.
  • DiceBear avatars. When a default initial avatar is displayed, your browser requests it from api.dicebear.com. The request includes a seed derived from the username and your IP address. DiceBear does not receive your password, email address or messages. Uploading your own avatar replaces the generated one.
  • Supabase API and storage. Your browser requests your project’s Supabase endpoints to read and write data and media. Those requests carry your session and may be logged by the provider for security and operations.

We do not embed social media widgets, advertising networks or third-party analytics scripts.

Managing cookies

You can view, block and delete cookies in your browser settings. Clearing cookies signs you out of Synapse and any other site you use in that browser. Blocking the sb- cookies prevents sign-in entirely, because the service has no other way to keep you authenticated.

Because we do not set optional cookies, there is nothing else to opt out of. If you use a native client, sign out from the app to revoke the session stored on that device.

Do Not Track and Global Privacy Control

We do not track you across websites, so there is no cross-site tracking to disable. We do not sell personal data or share it for behavioural advertising, which means there is no sale or sharing to opt out of through Global Privacy Control signals.

Changes to this policy

We update this page when the cookies or third-party requests change. The date at the top is revised and the change is recorded in the changelog. If we introduce optional cookies, we will ask for consent before setting them.

Contact

Questions about cookies or this policy: support@synapse.app. For a broader description of what we collect, see the Privacy Policy.

By using the hosted service you agree to this policy. If you would rather not receive any cookies, use a browser setting to block them — but you will not be able to sign in.