Legal
Cookie Policy
Last updated: August 26, 2026 · Effective: August 26, 2026
1. Overview
This policy describes the cookies and browser storage used by the current Introd public website. A cookie is a small value stored by a website in your browser. Local and session storage serve similar browser-side purposes. This policy should be read with our Privacy Policy. Product or third-party integration screens may have additional storage described in the notice or agreement that applies to them.
2. Current browser storage
This list is based on the website implementation reviewed on August 26, 2026. Provider names, cookie names, and durations can change, so we avoid promising provider-controlled expiry periods. We will update this list when the implementation changes.
| Name | Provider | When used | Purpose | Duration |
|---|---|---|---|---|
| introd.analytics-consent | Introd | Set when you save a choice | Remembers whether optional analytics and support tools are allowed. | Up to one year; replaced when you change your choice |
| introd.marketing-attribution.v1 (session storage) | Introd | Public-site navigation | Keeps a pseudonymous ID and allow-listed first/last campaign, referrer, and landing-path fields so a voluntary form submission can retain its source. | Current browser tab session, unless browser behavior preserves that session |
| _ga and _ga_* | Google Analytics | Only after optional-cookie consent | Measures allow-listed page and conversion events; advertising signals are disabled. | Provider-controlled; can change with provider or browser settings |
| PostHog browser identifiers (names may vary) | PostHog | Only after optional-cookie consent | Measures allow-listed page, CTA, and form-lifecycle events. Autocapture and session recording are disabled. | Provider-controlled; can change with provider or browser settings |
| intercom-id-v8fbftfu | Intercom | Only after consent, where support chat is enabled | Identifies an anonymous browser so Messenger can associate support conversations. | Provider-controlled; Intercom documentation reviewed August 26, 2026 |
| intercom-session-v8fbftfu | Intercom | Only after consent, where support chat is enabled | Keeps a Messenger session and access to prior conversations. | One week by default in current Intercom documentation |
| intercom-device-id-v8fbftfu | Intercom | Only after consent, where support chat is enabled | Identifies a device that interacts with Messenger to help prevent abuse. | 270 days, refreshed with use, in current Intercom documentation |
3. Optional analytics and support
Google Analytics, PostHog, and Intercom do not load through the current public-site implementation unless optional-cookie consent is active. Analytics is configured for explicit page, CTA, and form-lifecycle events rather than page-element autocapture. PostHog session recording is disabled. Event sanitization excludes email addresses, names, messages, cookie values, and URL query strings. Google advertising storage, advertising-user data, advertising personalization, and Google Signals are denied.
Intercom is also subject to a route and runtime setting, so consenting does not mean the messenger appears on every page. Withdrawing consent causes the site to disable these tools and attempt to clear their first-party identifiers; browser or provider behavior can affect deletion. The public messenger is anonymous and distinct from support in the signed-in app; the product notice that applies there may describe additional behavior.
4. Form attribution
Campaign attribution is separate from optional analytics. During the current tab session, Introd keeps a random identifier plus allow-listed UTM values, the referring origin and path, and the landing path. Query strings and fragments are removed from stored paths, and attribution does not copy form names, email addresses, or messages. If you voluntarily submit an access, demo, contact, API waitlist, or newsletter form, that attribution is sent with the request and retained as part of its server-side record. If you do not submit, it remains browser-session data.
5. Your controls
- Use the cookie banner to allow or reject optional analytics and support tools.
- Use Cookie settings in the footer to change that choice later.
- Use browser controls to view, block, or delete cookies and browser storage.
- Enable Global Privacy Control or Do Not Track to keep optional analytics and support tools disabled in the current implementation.
Blocking all browser storage may prevent choices or in-progress attribution from being remembered, but email contact remains available.
6. Changes and contact
We may update this policy as the website or its providers change. The date above shows the latest review. For a question about current storage behavior, email privacy@getintrod.ai.