Everything we know about consent, written down.

StrongPrivacy resolves a visitor’s country (and, for California and Quebec, their region) onto one of ten legal regimes, then applies a consent model. These pages describe each regime and the exact behaviour that follows.

Ten practical guides for the work consent actually involves: finding what is loading, holding it until the visitor agrees, proving that you did, and migrating off whatever is there now.

Three installation paths cover the platforms documented here: a Shopify theme app extension, a WordPress plugin, and a shared script tag for supported custom sites. What differs is where the snippet goes and which platform services may load independently.

Consent work looks different depending on what you run. A storefront’s trackers arrive from apps, an agency’s problem is twenty clients rather than one site, and a publisher’s problem is an advertising supply chain. These pages describe the shape of each.

The classification catalogue behind a StrongPrivacy scan carries over 130 host rules and more than 40 cookie-name rules. These pages cover the ones that turn up most: what each vendor is, which hosts and cookies identify it, which consent category it belongs in, and how to hold it until the visitor agrees.

Reference pages for the cookie names that turn up most often in an audit: who sets them, what they hold, which consent category they belong in, and what to write in a declaration.

Twenty-nine terms that come up when you are configuring consent, reading a scan result or answering an auditor: each one explained, and each one connected to what the product actually does.