LetsCollab

LetsCollab.bio

Cookie Policy

Effective date: May 12, 2026 · Last updated: May 12, 2026

This Cookie Policy explains how LetsCollab.bio ("LetsCollab", "we", "us") uses cookies and similar technologies — local storage, session storage, pixels, and the like — when you visit our website or use the Service. It supplements our Privacy Policy.

1. What Are Cookies

Cookies are small text files placed on your device by a website. They let the site remember things between page loads or visits — for example, that you are signed in, which privacy choices you have made, or which performance bucket your session falls into. "Similar technologies" — local storage, session storage, and IndexedDB — work like cookies but live in your browser's storage instead of being sent on every request.

2. Categories We Use

2.1 Strictly Necessary

Required to deliver the Service you asked for: signing in, holding your session, protecting against CSRF, remembering your privacy choices. These cannot be switched off in our interface because the site does not function without them.

  • Authentication (Supabase): keeps you signed in between requests. First-party HTTP cookies and local storage. Session-length to 7 days.
  • CSRF protection: a per-session token used to confirm a request originated from your browser. First-party. Session length.
  • Privacy consent: stores your analytics choice and Global Privacy Control state so we do not re-prompt. First-party local storage. Up to 12 months.
  • UI preferences: stores collapsed/expanded states, last-selected dashboard tab, and timezone. First-party local storage. Up to 12 months.

2.2 Functional

Improve usability but are not strictly required. We treat these as required while you remain signed in (e.g., auto-saving message drafts) and clear them on sign-out.

  • Draft autosave: stores in-progress message drafts locally so a refresh does not lose your work. First-party local storage. Cleared on send or sign-out.

2.3 Analytics (Optional)

Help us understand product usage and page performance. Off by default and only set if you accept them through the privacy banner. We never set them when Global Privacy Control (GPC) is enabled on your browser.

  • Aggregated feature-usage events keyed by anonymous session id. First-party. Up to 13 months.

2.4 Advertising

We do not use advertising cookies. We do not sell or share personal information for cross-context behavioral advertising. We do not set Google advertising cookies and we do not use Google user data for advertising.

3. Third-Party Cookies

Some pages may load resources from service providers that set their own cookies under their own privacy policies:

  • Supabase — authentication session storage.
  • Sentry — error reporting beacons; does not set advertising cookies and respects PII scrubbing rules we configure.
  • Google — if you sign in with Google or connect Google Calendar, Google sets cookies on its own domain during the OAuth handshake under Google's Privacy Policy.

4. Managing Cookies

  • In-app banner: open the privacy banner from the footer or wait for the next required prompt to change optional analytics.
  • Browser controls: every modern browser lets you block or delete cookies and clear local storage. Blocking strictly necessary cookies will break sign-in.
  • Global Privacy Control: if your browser sends the GPC header, we treat it as an opt-out of analytics and "sale/sharing" for California residents — no further action needed.
  • Do Not Track: there is no universal industry standard, so we treat GPC as the canonical signal and do not respond to DNT separately.

5. Changes

We may update this Cookie Policy when we add or remove tools that use cookies. We will revise the "Last updated" date above and, for material changes, prompt you to renew consent for optional analytics.

6. Contact

Cookie questions: feedback@getletscollab.com.