Legal
Cookie & Tracking Notice
The cookies, local storage, and privacy-focused analytics Ennea AI uses, plus how consent will work for optional trackers.
Last updated: 2026-07-22
Version: cookies-2026-07-22
Legal review pending: This wording is an operational baseline. HeyData must supply or approve the final legal wording before production reliance.
Current Cookie Posture
Ennea uses an EU/UK-first consent posture. Strictly necessary cookies and storage are used to provide the service. Functional preference storage is used for language and app settings. Non-essential marketing or advertising trackers must not load unless the user has opted in.
Vercel Analytics and Speed Insights are treated as optional analytics. They do not load until the user has opted in through the consent banner, and the preferences flow remains available for later withdrawal.
Cookie Inventory
authToken and JWT-related authentication storage: strictly necessary, used to keep users signed in and secure authenticated API requests.
i18next and i18nextLng: functional preference storage, used to remember the selected language.
app-settings: functional preference storage, used to remember app settings such as theme, layout, and display density.
Vercel Web Analytics and Speed Insights: privacy-focused website analytics and performance measurement. These are disclosed as analytics tooling and should remain configured without advertising identifiers or cross-site tracking.
Firebase Analytics: treated as inactive unless explicitly wired into product code. If activated, it must be gated behind analytics consent.
Optional Tracking Rules
Google Analytics, Firebase Analytics, Meta Pixel, LinkedIn Insight Tag, retargeting scripts, heatmaps, and similar non-essential tools must not load before consent.
When optional trackers are enabled, users must receive equal-weight Accept all and Reject all choices, category controls, an easy withdrawal path, and Global Privacy Control handling where applicable.