Cookie policy

Cookies and similar storage

Cookies are small values stored by your browser and sent to the relevant website. Local storage keeps preferences on your device without sending them on every request. 3C uses both where needed for authentication and interface preferences.

Essential authentication

Supabase authentication uses project-specific cookies, typically with names beginning sb- and containing auth-token. They maintain and refresh your signed-in session and can be split into multiple cookies. They are set when authentication requires them; their expiry is controlled by the authentication service and session lifecycle.

Blocking or removing authentication cookies can sign you out or prevent protected workspace pages from working. We do not classify these as optional analytics.

Interface preferences

The theme preference is stored locally by the theme system so the interface can remember your light or dark mode choice. The workspace sidebar uses the sidebar_state cookie to remember whether it is open; its configured lifetime is seven days.

Your cookie choice is stored under 3c-cookie-choice-v1 in local storage. Local storage does not have an automatic expiry; it remains until you change the preference or clear browser storage. If browser storage is blocked, a choice can last only for the current page session.

Optional Google Analytics

When Google Analytics is configured, it is loaded only after you select Allow analytics. Until then, no Google Analytics script or analytics events are sent by this integration. Essential only leaves optional analytics off.

Google Analytics may create _ga and _ga_* cookies to distinguish browsers and sessions. Google documents a default two-year expiry for these cookies; actual expiry can depend on its settings and browser restrictions. Usage data can include pages viewed, interactions, browser/device information, and network information processed by Google.

Our integration uses manual public-page views, omits query strings and fragments from reported page locations, uses generic context for private workspace events, and disables Google signals and ad-personalization signals. It sends fixed interaction labels rather than your form responses. The Google Analytics property must also have enhanced measurement disabled to avoid automatic collection outside these controls.

Change your choice

Open Cookie settings below or in the public footer to allow or decline optional analytics. On withdrawal, the integration stops sending events, removes accessible Google Analytics cookies for this site, and reloads the page if the script was already initialized. Withdrawal also takes effect in other open tabs through browser storage updates.

Your choice applies to this browser, not automatically to every device you use. Clearing browser storage removes the saved choice. You can also use your browser’s settings to review, block, or delete cookies. Blocking essential storage can affect sign-in and preferences.

External websites and policy changes

Links to investor websites, founder resources, and other 3rdLoop products open services with their own cookie practices. This policy describes 3C. We may update it when the integration or storage behavior changes; the date on this page identifies the current version.