LEGAL

Cookies & analytics

Last updated: 22 May 2026

We run a small, transparent analytics setup. The marketing site uses a cookieless analytics tool (Plausible) on every page. Google Analytics 4 is also loaded on every page but starts in Google Consent Mode v2 with analytics and ad storage set to denied — no analytics cookies are written and no identifying data is collected until you click Accept. The web app at /app uses essential cookies to keep you signed in. There is no advertising, no cross-site tracking, and no third-party retargeting.

Your choice

Change your mind any time. If your browser sends a Do Not Track signal we treat that as a decline automatically.

What we set

This is the full list of cookies and browser-storage keys the marketing site uses.

Name	Type	Party	Purpose	Loads when	Retention
`_ga`	Cookie	Third-party (Google)	Google Analytics 4 — distinguishes unique visitors so we can measure which marketing channels send recruits to FirePrep.	Only written after you click Accept. The GA4 script itself is loaded on every page but starts in Consent Mode v2 with analytics storage denied.	Up to 2 years (set by Google; reset on each visit).
`_ga_<CONTAINER-ID>`	Cookie	Third-party (Google)	Google Analytics 4 — session and engagement state for the GA4 property.	Only written after you click Accept. The GA4 script itself is loaded on every page but starts in Consent Mode v2 with analytics storage denied.	Up to 2 years (set by Google).
`fireprep-consent-v1`	localStorage	First-party (FirePrep)	Remembers your cookie choice (“accepted” or “declined”) so we don't ask again on every visit.	Set as soon as you make a choice — accept or decline.	Until you clear your browser storage or change your choice.
`fireprep-section-views-v1`	sessionStorage	First-party (FirePrep)	Avoids sending the same “section viewed” analytics event more than once per session.	Set when you scroll a tracked section into view.	Cleared when you close the tab.

Plausible Analytics itself does not set cookies or use cross-site identifiers, so it is not listed in the table above. The Google Analytics 4 script (gtag.js) is loaded on every page but configured with Google Consent Mode v2 defaults of denied for analytics and ad storage — Google receives only cookieless "consent mode" pings until you choose Accept.

App-side storage

Once you're signed in to /app, additional storage is used to keep your session active. These are essential for the app to function and aren't covered by the analytics banner:

Clerk session — Clerk-managed cookies and storage to keep you signed in across pages.
Stripe Checkout — Stripe sets short-lived cookies on its own checkout pages during the payment flow.
FirePrep app preferences — small first-party keys that remember UI state (e.g. last-seen notifications, onboarding step).

How to clear cookies

You can clear cookies and storage from your browser settings at any time. Doing so will sign you out of the app and reset your cookie choice on this site (we'll ask again on your next visit).

See also: Privacy policy · Terms of service