Browser privacy
Cookie and storage notice
How the Engage AI public site uses essential cookies, browser storage and optional anonymous analytics.
- Version
- cookies-2026-08-03
- Effective date
- 3 August 2026
Read this document together with the related policies and any approved customer order form.
What cookies and browser storage do
Cookies are small values stored by a browser and sent with relevant requests. Local or session storage remains in the browser and is not automatically sent with every request. Engage AI uses these mechanisms only for the purposes described below.
Blocking essential storage may prevent secure signup, consent persistence or other requested features from working. Declining optional analytics does not block access to public content, signup or checkout.
Storage currently used
The public site uses the following first-party storage. Exact expiry may be shortened when a signup finishes, a session is revoked or a visitor clears browser data.
| Name | Category | Purpose | Typical duration |
|---|---|---|---|
| engage_public_consent | Essential preference | Stores whether this browser selected essential-only or optional analytics. | 180 days |
| engage_public_journey_v1 | Optional analytics — session storage | Random anonymous journey ID created only after analytics consent; excludes account and conversation identifiers. | Browser tab or session |
| __Host-engage_signup | Essential security | HttpOnly pending-signup session used after email verification. | Up to 2 hours |
| __Host-engage_signup_csrf | Essential security | Protects pending-signup changes against cross-site request forgery. | Up to 2 hours |
Essential storage
Essential storage supports security, fraud prevention, request routing, consent choice and secure signup state. It is not used for advertising and cannot be disabled through the Engage AI preference control where it is needed to provide a requested service.
Essential signup cookies use the __Host- prefix, Secure attributes and appropriate SameSite settings. The session credential is HttpOnly so browser scripts cannot read it.
Optional analytics
Optional analytics starts only after consent. It uses a random journey identifier and an allowlisted event schema to understand page and funnel use without intentionally including email, phone, company name, user ID, payment details, tokens, provider identifiers or private conversation content.
The current implementation dispatches consent-gated analytics events inside the browser and has no external analytics network sink. If an approved provider is added, this notice will be updated with the provider, purpose, location and retention before data is sent.
Connected and third-party services
A payment, messaging or other connected provider may set storage on its own domain or hosted component under its own notice. Engage AI does not control storage placed solely by a third-party domain, but provider use must be disclosed and approved before the related production feature is enabled.
Manage your choice
Use the preference control below to select essential-only or allow optional analytics for this browser. Choosing essential-only removes the optional journey identifier from session storage.
You can also delete cookies or block storage in browser settings. Those controls may affect other sites and may prevent secure Engage AI features from working.
Changes to this notice
We will update this notice before adding a new material storage purpose, analytics provider or advertising technology. Material changes will receive a new version and effective date, and renewed consent will be requested where required.