Skip to content

Cookies

Compasyn sets two kinds of cookie: one to keep you signed in, and one opaque per-visit identifier so a founder is not told the same person visited five times.

Last updated 22 September 2026

The complete list

  • Session cookie(s) — set by Supabase, our authentication provider, only when you sign in. Named with the prefix sb- and suffix -auth-token, sometimes split across more than one cookie if the session is large. httpOnly, Secure in production, SameSite=Lax. Without it you cannot stay signed in.
  • Analytics session identifier — compasyn.visit, an opaque, random, per-visit value that expires after two hours. httpOnly, so no script on the page can read it. Used to avoid double-counting a visit and to spot automated bursts.

What Compasyn does not set

No advertising cookies. No third-party analytics. No tracking pixels. No cross-site identifiers. Nothing follows you off Compasyn.

Consent

There is no consent banner yet. Both cookies exist only to run the service you asked for: keeping you signed in, and counting a visit once. Under India’s Digital Personal Data Protection Act, 2023 the analytics identifier is personal data processed for the purposes set out on the privacy page, and you can ask us to stop or erase it there. Whether it needs a consent banner under EU rules — given it is httpOnly, per-visit and used only for counting — is an open question we have not resolved, and we would rather write that here than show a banner that implies more certainty than we have.

Blocking cookies in your browser leaves search, matching and every product page working. Only signing in stops working.