Back to resources

Legal register

Cookies and Similar Technologies

Englishcookies

AUVY · Legal registerEnglishcookies

Version: 1.1 · Last updated: 2026-08-03

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

We distinguish between storage that is strictly necessary to provide the requested service, preference and consent storage, and optional analytics. Strictly necessary authentication, security, routing, and load-balancing storage is used to perform the contract and protect the service. Optional analytics loads only after the applicable consent choice or workspace configuration permits it.

Authentication and sessions

AUVY authentication uses Better Auth. Depending on domain and deployment security settings, Better Auth sets an HTTP-only session cookie (for example a better-auth.session_token cookie or its secure-prefixed equivalent) and may use short-lived state, nonce, or callback cookies during sign-in. These values authenticate the browser, protect login flows, and expire or rotate according to the active session configuration.

Product clients may also use the key auvy-session-token in browser localStorage or sessionStorage for an authenticated product session where that client flow requires it. localStorage persists until sign-out, rotation, expiry handling, or deletion of site data; sessionStorage is limited to the browser tab/session. These stores are not advertising trackers.

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 AUVY

In AUVY workspaces, the optional PostHog path activates only when enabled and configured. It may use pseudonymous event identifiers and browser storage needed for analytics or feature flags. Events remain subject to the Product Privacy Notice and applicable consent controls.

Change or withdraw preferences

Visitors can revoke previously granted optional consent through the available consent surface or browser controls. Deleting authentication cookies or auvy-session-token storage signs the browser out or ends the affected session. Workspace administrators may disable optional analytics configuration independently.