Storage and Cookie Notice

Necessary SiteAirbag app storage

Supabase authentication storage (a project-specific sb-…-auth-token key and provider cookies where configured) maintains the signed-in session. siteairbag-theme in localStorage remembers light or dark appearance. siteairbag-ad-policy is a first-party cookie that records only which advertising-measurement rule applies to your region (blocked, opt_in or opt_out), never your country or location, so the site can apply that rule before any optional technology loads; it lasts for the browser session and is refreshed on each page. The siteairbag-analytics-consent and siteairbag-advertising-consent localStorage keys remember the privacy choices you make. If you use the Protection Scan, siteairbag-scan in localStorage keeps the scanned page's origin and path (never its query string), the platform found, the action you chose and any numbers you entered, for up to 14 days, so adding the website can continue where the scan left off; it never leaves your browser and is removed once the website is added or when you choose another website. siteairbag-sticky-bar-dismissed in localStorage remembers that you closed the “Check free” bar on an article, so it stays closed; it holds no identifier and never leaves your browser. These are necessary for the account, appearance, privacy choices or setup continuity requested by the user.

Customer-site runtime storage

The runtime uses sessionStorage key sa_session for a random per-tab identifier and sa_pending_navigation while an observed journey crosses pages, capped at ten minutes. Pending journey data contains action/profile identifiers, timestamps, progress position, and sanitized origin/pathname only; query strings and secret-like fragments are excluded. sa_setup_session, sa_setup_dock_state and sa_outcome_learning exist only during an authorized setup tab. Outcome learning stores the selected action fingerprint, visitor intent, timing, and an ordered list of normalized structural/page-change signals so recording can survive navigation. sa_airbag_test_session exists only in a tab the owner opened from Test My Airbag: it holds that signed test link and the action identifier until the link expires (20 minutes) or the owner ends the test, and while it exists observation is off in that tab. sa_config_… in localStorage caches a site's configuration for up to 24 hours so observation can fail open during an outage; rescue forms are disabled for cached fallback configuration. Runtime authorization remains in memory. These keys never contain keystrokes, original form values, HTML, request bodies, advertising IDs, or session replay.

Optional analytics

siteairbag-analytics-consent stores the explicit allow/decline decision and date. Only after an allow choice, PostHog may use a ph_…_posthog localStorage key for minimized product analytics within the SiteAirbag website and app. Autocapture and session recording are disabled. Public pages send a minimized page-view event and button-use events only after an allow choice (no query strings). Declining prevents the library request; withdrawal opts out of future capture and removes its local analytics key. PostHog is never loaded by the customer-site runtime.

Page-load counts without storage

Cloudflare, which hosts SiteAirbag, runs Cloudflare Web Analytics on public website pages to count page loads and measure web performance. It sets no cookie and uses no local or session storage on your device, and it does not depend on the analytics choice below. See the Privacy Notice for what it receives.

Optional advertising measurement (Meta)

Meta advertising measurement is optional and is not necessary to use SiteAirbag. Whether it can run depends on your region's rule and your own choice. In the EEA, the United Kingdom and other markets SiteAirbag does not serve, it never runs. In the United States it runs unless you opt out. In India and in every other region, including any region SiteAirbag cannot determine, it runs only after you allow it. A Global Privacy Control signal from your browser always keeps it off. It runs only on public SiteAirbag website pages, never on signed-in app pages, checkout confirmation or setup links, or customer websites.

When it runs, the Meta Pixel from Meta Platforms loads and may set the first-party cookies _fbp (a random browser identifier) and _fbc (an ad-click identifier, when you arrive from a Meta ad). Meta receives the page address, your IP address and browser information with each request. SiteAirbag reports page views, pricing viewed, plan page viewed, plan selected, Protection Scan completed (with nothing about the scanned page) and checkout started. They carry the plan name and, for checkout started, the billing interval (monthly or yearly), whether it is a free trial or a paid start, the trial length, and the plan's listed price for the first payment and its currency; never anything you type. SiteAirbag's code turns Meta's automatic event collection off.

When you start checkout, start a free trial or finish account setup while it runs, SiteAirbag's server sends Meta that event (checkout and free-trial events with the same plan and checkout details as above) with _fbp, _fbc, your browser's user agent, your IP address and country, and a SHA-256 hash of the email address you entered at checkout together with a pseudonymous buyer identifier derived from it. A hash is a fixed code computed from the address; SiteAirbag never sends the readable address, and Meta uses the hash to match the event with a Meta account that has the same address. To attribute a purchase, SiteAirbag stores those identifiers, the hashes, the IP address and the user agent with its own checkout record (never with Paddle) for up to eight days, and when Paddle confirms the first payment it sends Meta a Purchase with the plan, the billing interval, whether it followed a free trial, the amount charged excluding tax, and the currency. Only a Purchase carries an amount paid. A free trial's first payment comes when the trial ends; if it is taken more than eight days after checkout, those identifiers are already deleted and no Purchase is sent. Events waiting to be sent are retried for a limited time and their identifiers are deleted once sent or abandoned.

SiteAirbag never sends Meta your name, readable email address, phone number, password, account or workspace identifiers, anything else you type, or any customer-website or monitoring data. Opting out or declining stops the Pixel, removes _fbp and _fbc from this site and stops SiteAirbag collecting advertising identifiers from then on. When you opt out, SiteAirbag also deletes the advertising identifiers it stored for checkouts made from that browser or, if you are signed in, by your account, and cancels those events not yet sent, so no later free-trial or purchase event is sent for them; to do this, the opt-out request carries this browser's _fbp value, which is used for that lookup and not stored. Deleting your account does the same. If you opted out on a different browser from the one you used for checkout, email privacy@siteairbag.com and SiteAirbag will do this for your checkout email address. None of this recalls data Meta already received. Meta's own use and retention of this data are governed by Meta's Business Tools Terms, Data Processing Terms and policies.

Optional advertising measurement (Google, YouTube ads)

Google advertising measurement is optional and is not necessary to use SiteAirbag. It follows exactly the same regional rule and the same choice as Meta advertising measurement above: it never runs in the EEA, the United Kingdom or other markets SiteAirbag does not serve, runs in the United States unless you opt out, and runs in India and every other region, including any region SiteAirbag cannot determine, only after you allow it. A Global Privacy Control signal from your browser always keeps it off. It runs only on the same public SiteAirbag website pages, never on signed-in app pages, checkout confirmation or setup links, or customer websites. It is for measurement only: SiteAirbag does not use it to build advertising audiences from visitors and tells Google not to use it for ad personalisation.

When it runs, Google's tag loads from googletagmanager.com and may set first-party cookies whose names begin _gcl_. Google receives the page address, the address you came from, your IP address and browser information with each request. SiteAirbag reports page views and, when you start checkout, a checkout-started signal that carries only a hashed identifier of that checkout request. If you arrived from a Google ad, the address carries an ad-click identifier (gclid, gbraid or wbraid); while this measurement is allowed, SiteAirbag keeps it in your browser's local storage (siteairbag-ad-click) for up to seven days so a later checkout can be matched to the click.

When you start a free trial or make a payment while it runs, SiteAirbag's server stores that click identifier, if you have one, and a SHA-256 hash of the email address you entered at checkout (computed the way Google asks, which treats some Gmail addresses with and without dots as one) with its own checkout record (never with Paddle) for up to eight days. When Paddle confirms the trial's start or a payment, SiteAirbag sends Google that event through Google's API with the click identifier, the hash, the time and a hashed transaction identifier, and for a purchase the amount charged excluding tax and the currency. Only a purchase carries an amount paid. Google can use the hash to match the event with a Google account that has the same address. Events waiting to be sent are retried for a limited time and their identifiers are deleted once sent or abandoned.

SiteAirbag's server never sends Google your name, readable email address, phone number, password, IP address, account or workspace identifiers, anything else you type, or any customer-website or monitoring data. Opting out or declining stops the tag, removes the Google cookies the tag set and the stored click identifier from this site, reloads the page if the tag was running, and stops SiteAirbag collecting advertising identifiers from then on. When you opt out, SiteAirbag also deletes the click identifier and hashes it stored for checkouts that carry your stored click identifier or, if you are signed in, by your account, and cancels those events not yet sent, so no later free-trial or purchase event is sent for them; to do this, the opt-out request carries your stored click identifier, which is used for that lookup and not stored. Deleting your account does the same. If you opted out on a different browser from the one you used for checkout, email privacy@siteairbag.com and SiteAirbag will do this for your checkout email address. None of this recalls data Google already received. Google's own use and retention of this data are governed by Google's advertising terms and policies.

Controls

Use Privacy choices (at the top of this notice, in the site footer and in Settings) to allow or refuse optional analytics and to allow or opt out of advertising measurement at any time. When you save a change to these choices, SiteAirbag also records it on its servers as a short log entry: which option (analytics or advertising measurement), your answer and the previous one, the advertising rule for your region (never your country), whether your browser sent a Global Privacy Control signal, the date and time, and the version of these notices in force. It is linked to your account only if you are signed in, and it holds no IP address, browser identifier or location. It is kept for three years so SiteAirbag can show what choice was made, then deleted. Browser controls can also clear storage, but removing necessary authentication or setup storage may sign you out or restart setup. Contact privacy@siteairbag.com with questions.