Cookie Policy

Version 3 — see the end of this document for what changed since Version 2.

1. What a cookie is

A cookie is a small text file placed on your device when you visit a website, used to make the site function, remember your preferences, or understand how it's used. We also use similar technologies where relevant (such as browser local storage for short-lived UI state); references to "cookies" below cover both.

2. The cookies we use

| Category | Purpose | Consent required? | |---|---|---| | Strictly necessary | Authentication session (keeps you signed in), CSRF-protection token (prevents cross-site request forgery on state-changing actions), and a short-lived cookie that remembers your cookie-consent choice itself | No — required for the Platform to function | | Functional | Remembers preferences such as light/dark theme | Yes | | Analytics | Privacy-respecting, first-party usage analytics (no cross-site tracking, no third-party ad networks) used in aggregate to understand which features are actually used | Yes |

We do not use third-party advertising cookies, and we do not permit cookie-based cross-site tracking of you across unrelated websites.

3. Managing your preferences

A consent banner is shown on your first visit for any visitor in a jurisdiction (such as the EEA or UK) where prior consent is legally required before setting non-essential cookies; elsewhere, functional and analytics cookies may be set by default subject to your ability to opt out. You can change your choice at any time from the cookie settings link in the site footer, or by clearing cookies in your browser. Strictly necessary cookies can't be disabled through this mechanism, since the Platform can't authenticate you or protect your session without them — if you block them at the browser level instead, core features (including staying signed in) will not work.

4. Third parties

Some strictly necessary functionality is provided by third parties who may set their own cookies as part of that functionality — for example, Stripe during a payment or billing-portal flow. Those cookies are governed by that third party's own privacy and cookie practices, not this Policy.

5. Changes to this Policy

We may update this Policy as the Platform evolves, including as we add or remove cookies. Check back periodically; material changes affecting consent-based cookies will re-trigger the consent banner where required.

What changed in Version 3: removed the AI-drafted/attorney-review notice that previously appeared at the end of this document.

What changed in Version 2: restructured the cookie list into a table with duration/consent detail, added an explicit statement on cross-site tracking and Do Not Track alignment with the Privacy Policy, and clarified when the consent banner is shown versus when cookies may be set by default.