Cookie Policy

Local Aura does not add a third-party consent-management platform. The current code uses necessary storage for language preference and authentication and can use optional PostHog analytics when configured. No advertising pixels, social-media scripts, or third-party iframes were found in the audited code.

These items support the service, security, or a requested choice. They are not blocked by the analytics control:

• Authentication and session: the installed @convex-dev/auth and Convex integration maintains state needed for sign-in and security. The application source does not set a custom cookie name; exact names and storage location are determined by the auth provider and live authentication flow. Verify them in production before finalizing this policy.
• local-aura-locale: a localStorage key that remembers the English or Portuguese language preference.
• local-aura-cookie-consent: a localStorage key that records an accept or reject decision for optional analytics.

When the PostHog configuration variable is present, Local Aura shows an equally prominent accept-or-reject choice. PostHog does not initialize until acceptance. After acceptance, the current PostHog configuration may use cookies and localStorage for identifiers and sessions; this application does not configure or invent custom names for those keys.

After acceptance, campaign parameters utm_source, utm_medium, and utm_campaign may be kept for the session as mt_utm_source, mt_utm_medium, and mt_utm_campaign for checkout attribution. If you reject, this code does not create that storage or PostHog identifiers.

Use the “Cookie preferences” button in the footer at any time. Rejecting optional analytics does not block sign-in, product features, or language preference.