Cookie consent you can prove.
PXL Consent shows a banner where rejecting is as easy as accepting and holds trackers back until the visitor chooses. Each choice goes into a signed consent log, so anyone can check that it was not changed.
What regulators check
Datatilsynet and other European authorities look for the same things: a real choice, nothing stored before the choice is made, and records that hold up. PXL Consent is designed around these checks.
Reject next to accept
"Only necessary" has the same weight and position as "Accept all". Nothing is pre-ticked. A banner that hides or downplays the reject button, or fails WCAG contrast, cannot be published.
Nothing before consent
Known analytics, advertising and embed services are held back automatically, and your own tags wait once you mark them with a category. Videos and maps show a placeholder until allowed.
A log a third party can verify
Every choice is signed with the site's own Ed25519 key and chained to the one before. Once a day, an independent authority time-stamps the head of the chain.
Cookie scans
A real browser visits your pages before and after consent and lists what each page stores. The scan results keep the cookie declaration up to date.
Install in one line
Put the script first in <head>. It serves the banner you published, in the visitor's language, from a CDN.
<script src="https://cdn.consent.pxl.as/c/YOUR-SITE-ID.js" data-cfasync="false"></script>Hold back your own tags by changing their type:
<script type="text/plain" data-ccs-category="statistics"
src="https://example.com/analytics.js"></script>On WordPress, install the plugin instead. It also works on its own, with no account.
Features
- Opt-in or opt-out (with Global Privacy Control) chosen from the visitor's country, or a simple notice
- Google Consent Mode v2 signals
- 14 languages, including all the Nordic ones, English, German and French
- Runs in a shadow root, so site CSS cannot break it
- Consent lookup by ID for data subject requests, and CSV export
- Scheduled scans, and monitoring that opens an incident when it finds a problem
- Banner templates you can roll out to many sites
- Agency accounts with separate client organisations
- Passkeys and two-factor sign-in
Scheduled scans, monitoring, templates, API keys and agency accounts depend on the plan. See pricing.
For agencies
An agency manages all its clients' sites from one account. Each client is a separate organisation with its own consent log and people, and your team can work in all of them. When you roll out a banner template to fifty sites, you see which ones failed the checks.