Cookie Policy

1. The consent manager owns the choice

FairMind does not render or store a separate cookie-banner preference. An external consent management platform presents the choice, records it under its own controls, and passes the current analytics decision to this website. The website keeps that decision in memory only long enough to apply it to the analytics SDK.

2. Analytics is off before opt-in

PostHog analytics does not initialize unless the external consent manager explicitly passes an analytics opt-in. The integration also requires a FairMind-specific PostHog project token and regional ingestion host. Missing configuration, a denied choice, Global Privacy Control, or supported Do Not Track signals keep analytics inactive.

3. Storage used after opt-in

After opt-in, PostHog may use first-party cookies and browser local storage to maintain an anonymous visitor identifier, session state, attribution, and the SDK's capture preference. PostHog storage keys commonly begin with ph_ and include the FairMind project identifier. Exact names may vary with SDK versions and project configuration.

FairMind does not identify marketing-site visitors to PostHog and does not send form values, names, email addresses, messages, request bodies, response bodies, headers, or console logs. Form controls are excluded from interaction autocapture, and session replay masks every input plus the full form surface.

4. What analytics may measure

• Page views, page exits, referring source, campaign attribution, and anonymous sessions.
• Navigation, calls to action, section visibility, scroll depth, and named product interactions.
• Form start, validation block, and submit events without field names or field contents.
• Core Web Vitals, network timing, unhandled browser errors, heatmaps, dead clicks, and rage clicks.
• Video or audio play, pause, progress, and completion without media contents being uploaded.
• Consent-gated session replay with the masking rules described above.

5. Withdrawal

When the consent manager passes a denial or withdrawal, FairMind removes its analytics event listeners, stops session recording, opts the PostHog SDK out of capture, and resets the active anonymous analytics state. The external consent manager remains responsible for presenting and retaining the preference record.

6. Consent-manager integration contract

The preferred handoff iswindow.fairmindConsent.setConsent({ analytics, source, policyVersion }). A consent manager may instead dispatch fairmind:cmp-consent with the same fields in the event detail. The analytics field must be a boolean. Neither interface receives form data or a visitor identity.