What this browser keeps

Household profiles, policies, intents, quotes, shortlists, waitlists, support inbox, theme, welcome dismiss, cookie-banner dismiss, and other demo keys live under names like parity_app_v1 and companion keys. Nothing is uploaded to a Parity server in this build. See /privacy for the full inventory.

Parity does not set third-party advertising or analytics cookies in v1. Any first-party cookies would only come from the hosting stack or Next.js itself (for example session/routing needs on a future origin deploy) — not from ad networks. Preference dismissals use localStorage, not tracking cookies.

An optional service worker may register to precache a small offline shell (/offline, icons, manifest). It does not sync policies, quotes, health data, or waitlists. Unregister it in DevTools → Application if you prefer; clearing site data removes it with the rest of the demo.

No Google Ads / Meta pixels, no fingerprinting SDKs, no sold advertising IDs. In-product “analytics” and NPS live in localStorage for founder demo storytelling only.

A lightweight marketing-layout banner (Wave 155) offers Essential only or Accept all, stores preference in parity_consent_v1 (legacy dismiss key still honored), and links to /privacy, /cookies, and /app/privacy. It is a transparency stub — not a full CMP — because v1 has no third-party ad cookies to consent to. Revisit this page anytime from the footer.

Use /app/privacy (export household JSON + delete all parity_* keys with confirm), Settings → export / reset, clear site data in the browser, or reset consent preference after clearing storage. Theme and welcome keys are separate companion preferences; wiping site data clears all of them.