1. Current use
No optional analytics, advertising or session-replay technology is integrated in the current application source. A cookie-consent popup is therefore not shown. This does not rule out operational logging or cookies configured outside the application by hosting or authentication services; the live deployment must be checked separately.
2. Essential session cookies
Cloud sign-in uses Supabase authentication cookies to maintain and refresh your session and complete sign-in. Names can include a project-specific prefix and multiple chunks. Server-managed session cookies are configured as HttpOnly, SameSite=Lax and Secure in production. Exact lifetimes depend on authentication configuration, not a retention period specified by this page.
Blocking these cookies can prevent sign-in or authenticated features. The public marketing pages do not require an account. Google or GitHub may use their own cookies when you choose their sign-in service; their policies apply to those interactions.
3. Workspace and functional storage
Browser local storage can retain local workspace conversations, active conversation selection, preferences, projects, saved memories and study cards. Attachment payloads use IndexedDB. Current records use the avenyq prefix; older aurenq and astra records may remain readable for migration. These are storage technologies rather than advertising cookies.
Signed-in workspaces synchronise through cloud storage. Choosing to import local data does not remove the original browser copy. Functional settings and local workspace records may persist until deleted or browser site data is cleared; no fixed expiry is implemented for these records.
4. Analytics and marketing
The current source contains no Google Analytics, Vercel Analytics, Microsoft Clarity, Meta Pixel, PostHog, Mixpanel, Plausible or Hotjar integration. There are no optional cookie categories to accept or reject in this version.
If optional trackers are added later, this notice and the implementation must be updated first. Where consent is required, optional tracking must remain off until accepted, with equally accessible rejection and preference changes. A future consent system must also handle withdrawal, not just display a banner.
5. Your controls
Use your browser settings to block or remove cookies and site storage. Export important local work before clearing site data; clearing it can permanently remove the local workspace. Clearing browser data does not erase a cloud account, provider records or other-device copies. Use in-app data controls or contact privacy for those requests.
You can also manage microphone permissions in your browser. Permission to use the microphone is separate from cookie consent.