Consent, with a clear way forward.
Control what loads.Keep evidence of recorded choices.
Consent management, script control, evidence records, and privacy scans. One policy behind Shopify, WordPress, and custom sites.
How StrongPrivacy works
01 · Discover
See what your site loads.
Inspect cookies, scripts, storage, and requests in a real browser. Bring unknown services into view.
Explore verification scans02 · Control
Let each choice set the boundary.
Publish consent categories and hold optional services until the visitor gives the matching permission.
Explore consent controls03 · Verify
Keep the choice and its context.
Connect each recorded decision to its policy version, then compare what loads before and after consent.
Explore privacy evidence
The evidence chain
Every decision leaves a trace your team can follow.
The scanner, policy, runtime, visitor choice, and evidence record use the same property and configuration model. A change at one stage stays visible at the next.
Site connected
The runtime identifies the property and platform.
Policy published
A versioned regional configuration becomes active.
Scripts controlled
Declared and managed optional services wait for the mapped category.
Choice recorded
The visitor decision is tied to that policy version.
Evidence stored
The decision keeps its source, region, and timestamp.
Behavior verified
A sampled browser scan records what loaded on the pages and states tested.
One operating model
Privacy work, joined from end to end.
Replace disconnected plugins, scan exports, and audit notes with one traceable workflow for each site.
- 01
Consent management
Publish regional policies with clear categories, version history, and a preference center visitors can reopen.
- 02
Script control
Hold declared scripts and supported adapters until the matching visitor choice exists; separately installed and server-side services still need their own controls.
- 03
Evidence records
Keep pseudonymous decisions connected to site, region, source, time, and configuration version.
- 04
Privacy scans
Compare cookies, storage, requests, scripts, and frames across consent states in a real browser.
Evidence records
Evidence you can hand to someone who asks.
Exports keep each recorded decision connected to the active property and policy version without storing direct identifiers such as a name or email.
| Recorded | Pseudonymous key | Region | Decision | Policy | Source |
|---|---|---|---|---|---|
| 10:23:47 | v_4f92…ad1 | EU | Necessary + functional | v18 | Banner |
| 10:20:11 | v_c71a…920 | US-CA | Necessary only | v18 | Preference center |
| 10:16:03 | v_1db3…7e2 | GB | All categories | v17 | Banner |
Decision to enforcement
What the visitor chooses changes what the site may load.
Necessary services remain available. Optional services wait for a matching decision, and the resulting state stays visible.
EU storefront policy
Try it: switch a category and watch what loads
The page loads
- LoadedCheckoutNecessary
- HeldGA4Analytics
- HeldHotjarAnalytics
- HeldMeta PixelMarketing
- HeldTikTok PixelMarketing
- HeldDynamic YieldPersonalisation
5 of 6 services held until the visitor allows them.policy v12 · EU
Installation
Install where your site already lives.
Every adapter delivers the same configuration, choices, script controls, and evidence model.
Pricing
Priced per site, not per visitor.
Every plan uses the same product. Capacity, scan cadence, and evidence retention grow with your site portfolio.
Drag to see the plan that fits. The product is the same on every plan.
3sites
Every plan includes
- Consent banner
- Script control
- Consent records
- Privacy scans
Your plan
Growth
PopularA product and marketing team
$59 / month
- Up to 5 properties
- 40 scans a month, 20 pages each
- Daily scheduled scans
- 24 months of evidence
Just checking one site? Start on Free
Compare every planCommon questions
Questions people ask before they install.
Does StrongPrivacy guarantee legal compliance?
No. It provides controls, records, and verification your team can use to implement its policy. Requirements still depend on your business, visitors, and deployment.
What happens when a scan finds an unknown service?
The finding stays visible for review. Your team can identify its purpose, assign a category, update the policy, and verify the site again.
Can visitors change their decision later?
Yes. The preference center can be reopened, and the new decision is recorded against the active configuration.
Do all three platform integrations behave the same way?
They use the same published policy and evidence model, but installation and platform handoffs differ. Shopify synchronises through Customer Privacy, WordPress can interoperate with its Consent API, and custom sites depend on the scripts and embeds you declare or gate.
Start with one site