Cookies and Similar Technologies

Last updated: 2026-03-16

How AUVY uses cookies and local storage alongside the Product Privacy Notice.

Why we use cookies

We differentiate between cookies required for routing, authenticated sessions (sb-* session cookies), consent storage and optional telemetry that only loads after affirmative consent banners match the marketing site behaviour.

Consent cookie

When interacting with consent surfaces on www.auvy.ai landing experiences, selections may be stored locally (for example cookie name auvy-consent) for up to 12 months describing whether analytics telemetry is authorised.

Locale & UI preferences

Language cookies (e.g. auvy-locale) persist UI locales; similar keys keep dark/light mode synced per device without identifying end users uniquely.

Optional analytics inside Cortex

In Cortex workspaces, PostHog and similar tooling only activates when administrators configure the public ingestion key. Events respect workspace consent tooling and obey the Product Privacy Notice analytics disclosures.

Change or withdraw preferences

Visitors can revoke previously granted consent via browser controls (delete site data/cookies). Authenticated Cortex admins may rotate analytics keys independently.