Consent model

The app provides necessary, preferences, analytics, and marketing categories. Necessary storage is always active. Analytics and marketing must only run after explicit consent. Users can change choices from the cookie banner manage dialog or by clearing the consent record.

Necessary storage

Authentication and session tokens required to keep you signed in.
cookie-consent-v2: stores consent choices and timestamp.
Service-worker and cache metadata required for app delivery.
Operational identifiers such as request IDs used for reliability and security where strictly necessary.

Cookie / storage key	Purpose	Retention
auth-token	Login and session maintenance	Session
cookie-consent-v2	Consent choices and timestamp	12 months
cf_funnel_session_id	Anonymous session identifier for landing-page conversion attribution	Session / 90 days
service-worker	Cache metadata and offline app delivery	Browser-controlled
request-id	Operational reliability and security tracing	Session

Preferences

Theme and language settings.
Dashboard layout and product preferences.
Optional UI state such as tours or dismissed banners.

Cookie / storage key	Purpose	Retention
theme	UI theme (light/dark) preference	12 months
language	Display language preference	12 months
dashboard-preferences	Layout and product UI settings	12 months
ui-state	Optional tours or dismissed banners	12 months

Analytics & observability

Product analytics (PostHog, EU hosting at eu.i.posthog.com) measures the acquisition funnel — landing view, signup, first strategy, checkout, subscription — so we can see where people get stuck. It loads only after you accept analytics consent, with autocapture and session recording disabled. Events carry a pseudonymous device identifier, your Flyzle user ID after sign-in, the page path and UTM/referrer values — no email, no prompts, no generated content.
Performance and error monitoring may collect page load timings, JavaScript errors, resource timings, interaction events with masked inputs, and trace metadata — only after you accept analytics consent.
Application error monitoring (Sentry) captures technical diagnostics with default PII disabled and request cookies and authorization headers stripped.
Browser real-user monitoring (Datadog RUM) is currently inactive in the shipped app; if it is re-enabled it will run under the same analytics consent gate.
Server-side attribution stores an anonymous session identifier used to attribute landing-page conversions to traffic sources. It does not contain IP addresses or other personal identifiers and is retained for up to 90 days.

Cookie / storage key	Purpose	Retention
ph_<project>_posthog	PostHog product analytics: pseudonymous device ID, funnel events, UTM/referrer, page path (set only after analytics consent)	12 months
cf_funnel_session_id	First-party anonymous session ID for landing-page conversion attribution	90 days

Withdrawing analytics consent stops collection immediately and clears the PostHog identifiers. Further details about Sentry and PostHog processing are available in the Privacy Policy and in the subprocessor list .

Marketing

As of the last update of this policy, Flyzle does not use Google Analytics, Meta Pixel, TikTok Pixel, LinkedIn Insight Tag, Reddit Pixel, Hotjar or Microsoft Clarity, and runs no advertising or cross-site tracking cookies. PostHog is used for product analytics only (analytics category, EU hosting) and is not used for ad targeting or data sales. If this changes, we will update this policy and obtain any required consent before activation.

Change choices

Use the cookie banner Manage choices option, or clear the cookie-consent-v2 local storage key to be asked again.