No cookies, ever
The driven browser asserts document.cookie stays empty across pages, tiers and interactions — on your deployment, not a demo.
Verify privacy
Privacy, verified
at deploy time.
Privacy claims are cheap in brochures and expensive in court. So the claims are tested — by a real browser, against YOUR deployment, during onboarding. The report is addressed to your DevOps team, and it re-runs at every upgrade.
Prove, don't promise
The suite runs against your domain.
During the deploy session, our engineers drive the 6-spec browser privacy suite through your deployed collector — a real Chromium visiting real pages on your hardware, asserting what the platform promises. The report is delivered to your DevOps team as part of onboarding, and it is re-run at every upgrade we perform together. The same platform also carries 90 automated unit and live-HTTP tests; the six specs below are the browser-driven ones.
# 6-spec browser privacy suite · run against YOUR deployment # (sample output shown for illustration — yours is generated at onboarding) ✓ no cookies set ✓ zero storage accessors ✓ PII scrubbed end-to-end ✓ consent gate: zero pre-T2 beacons ✓ GPC silences the SDK ✓ DNT silences the SDK # report delivered to your DevOps · re-run at every upgrade
The six specs
What the browser is asked to prove.
Zero storage accessors
In the default tier, a proxy-sealed storage asserts zero reads and zero writes: no localStorage, no sessionStorage, no IndexedDB. Nothing to find because nothing is kept.
PII scrubbed end-to-end
Emails, card-length digits and API keys are scrubbed to placeholders before anything is stored — verified through the full path, from page to stored event.
Consent gate
Before consent (Tier 2), the suite asserts zero beacons leave the page. Collection starts only after opt-in — enforced server-side, checked by a browser.
GPC silence
With Global Privacy Control signaled, the SDK goes silent — zero beacons, zero storage. The signal is honored unconditionally, and the test proves it.
DNT silence
Do Not Track gets the same treatment: the SDK silences itself, and the suite watches the network to confirm nothing leaves the browser.
Beyond the browser
The math is verified live, too.
Two guarantees are checked on your running deployment during onboarding: rows below the k-anonymity floor (n ≥ 5) are suppressed on every dashboard, export and share snapshot — enforced as a post-filter, not a policy — and every administrative action lands in the audit log your team can read. Both are visible on the Privacy Posture page, on your hardware.
Don't trust it.
Watch it pass.
At onboarding, the privacy suite runs against your deployment and the report goes to your DevOps — evidence, not testimonials, from the day the stack goes live.