Skip to content
Legal

Cookie Policy

How authentication, preferences, analytics, and support integrations may use browser storage.

Beta notice: this policy describes the current browser-storage behavior. Consent requirements and any additional production analytics must be reviewed for the jurisdictions where the service is offered.

Essential storage

The service uses essential cookies or equivalent browser storage for authentication sessions, security, request integrity, language, and theme preferences. These are required for signed-in and preference-driven functionality.

First-party SaaS Factory measurement

SaaS Factory uses a random identifier in sessionStorage to connect a small set of first-time beta milestones within one browser session, such as seeing the homepage and starting or completing signup. The identifier expires with the browser session and is not used for cross-session advertising or profiling. Server-side milestones after signup are associated with the account or generated product. The funnel does not store idea text, email addresses, IP addresses, or user agents and is retained for at most 90 days. Operators should still review whether local law requires consent for this first-party product measurement.

Optional analytics and support

The application can integrate Google Analytics, Umami, Plausible, Microsoft Clarity, and Crisp. Enable only the tools you intend to use. Where consent is required, do not load optional tools until the visitor grants the appropriate category.

Managing choices

Users can clear browser storage through their browser. Operators should add a visible consent-management control when optional tracking is enabled and document how consent can be changed or withdrawn.

Retention

Document the exact cookie names, purposes, providers, and lifetimes from the deployed environment. Provider dashboards and browser developer tools should be part of the pre-launch audit.