Cookies and preferences

Essential and requested storage

Supabase authentication cookies keep you signed in and support multi-factor authentication. The browser stores your theme, product settings and dismissed onboarding/active-path identifiers in local storage so your choices survive a refresh. These stores do not contain provider credentials or saved chat text. Authentication storage lifetime follows your Supabase session; preferences remain until cleared in your browser.

Optional analytics

Plausible is prepared but disabled by default. When explicitly enabled in production, it makes no requests until you choose Accept analytics. Reject non-essential is equally available. No advertising or remarketing tags are installed. Analytics does not send chat content, conversation titles, user identifiers or credentials.

After consent, campaign attribution uses only validated utm_source, utm_medium and utm_campaign labels. Other query parameters, fragments and private conversation identifiers are excluded. Attribution is stored for the current tab session and removed when you reject analytics.

Change your choice

When analytics is enabled, use Cookie preferences at the bottom of any page to accept or reject it again. Rejection stops future analytics requests and clears stored campaign attribution; it cannot retract events already received by Plausible. Your choice is saved in local storage under ramea-analytics-consent-v1 until changed or cleared. If analytics is disabled, no consent banner or analytics requests are needed.