Legal
Cookie Policy
We use the minimum set of cookies needed to run Outercite securely. This page explains which ones, why, and how to turn them off.
Last updated:
2. How Outercite uses them
We use cookies only where they are genuinely necessary to operate the Services securely or to support features you've asked for. We do not currently deploy third-party advertising cookies or cross-site tracking pixels. If that changes, this policy will be updated and — where consent is required by law — we will ask for it before setting any such cookie.
3. Categories of cookies we use
3.1 Strictly necessary
These cookies are required for the Services to function. You cannot disable them without breaking core features. They include:
- Clerk authentication (
__session,__client, and related) — keeps you signed in and protects your session against hijacking. Provided by our auth partner, Clerk. - CSRF protection — short-lived tokens that protect against cross-site request forgery on sensitive actions.
- Stripe payment session (
__stripe_mid,__stripe_sid) — set when you interact with our Stripe-hosted checkout or billing portal; required by Stripe for fraud prevention.
3.2 Functional
Used to remember preferences and reduce friction in the app:
- Theme preference (
outercite_theme) — stores light / dark / system choice. - Dashboard layout — remembers which widgets you've resized or dismissed.
- Recent workspace — for agency users, recalls which client workspace you were last viewing.
3.3 Analytics and performance
We currently do not use Google Analytics, Mixpanel, Segment, or similar third-party analytics. We may collect anonymous error and performance telemetry via our self-hosted observability stack (Sentry / GlitchTip) for debugging. Those errors are keyed on your session but do not store behavioural profiles.
If we introduce analytics in the future we will update this page, and — where consent is required by law — ask you first.
3.4 Advertising / targeting
None. Outercite does not set advertising or behavioural-targeting cookies.
4. Third-party cookies
When you interact with embedded third-party services — signing in via Clerk, paying via Stripe Checkout, connecting Google Search Console — those third parties may set their own cookies on their own domains. We don't control those cookies; please consult the relevant provider's cookie policy for details. All current third-party providers are listed in the Privacy Policy.
5. Managing cookies
Most browsers let you view, disable, or delete cookies. Instructions vary by browser — see:
Disabling strictly necessary cookies will prevent you from signing in to the Services. Disabling functional cookies will not prevent sign-in but may cause preferences to reset between sessions.
6. Changes to this policy
We may update this policy from time to time. Material changes will be flagged on the Privacy Policy, and — where consent is required — presented in a banner before new cookies are set. Questions: privacy@outercite.com.