Data privacy and confidentiality in electronic communications.
GDPR gets the headlines, but it’s the ePrivacy Directive, the “cookie law”, that generally requires prior consent before you store or read information on a user’s device, unless that storage or access is strictly necessary to provide a service the user requested. It’s enforced by national DPAs and it’s where most banner fines actually come from. We make your consent layer meet it.
Where the banner fines really come from.
Non-essential cookies and trackers may only fire after the user agrees.
Each member state implements the Directive, so the details vary by country.
France has issued nine-figure cookie fines under its ePrivacy transposition.
The long-delayed ePrivacy Regulation would supersede the Directive EU-wide.
A consent layer that meets the actual cookie law.
The ePrivacy Directive is about the moment a tracker fires. Our scanner finds them, our banner gates them, and our notice documents them, in sync.
Tracker discovery
A live scan of every cookie, pixel and SDK so nothing fires before consent without you knowing.
Prior-consent banner
Trackers blocked until the user agrees, with reject-all as easy as accept-all.
Per-country tuning
CNIL, Garante and other DPAs differ on scroll, walls and consent lifetime. We apply the local rule.
Cookie notice
A live cookie table in your privacy notice, populated straight from the scanner.
ePrivacy Regulation watch
When the Regulation finally replaces the Directive, your config migrates with it.
Scan, gate, document — in one loop.
The reason cookie compliance breaks is that the scan, the banner and the notice drift apart. We keep them on one loop: the scanner finds a new tracker, the banner gates it, and the notice updates, so what fires always matches what the user consented to.
Run a ePrivacy Audit- Day 1 — Free scan inventories every tracker on the site
- Day 2 — Prior-consent banner blocks non-essential tags
- Week 1 — Per-country rules applied to EU traffic
- Week 2 — Cookie notice auto-populated from the scan
- Ongoing — New trackers caught and gated as they appear
What changes when the consent layer is real.
- Trackers fire before any consent is given
- One banner ignores per-country differences
- Cookie table in the policy is months stale
- No record of what each visitor agreed to
- New tags slip onto the site unnoticed
- Non-essential tags blocked until opt-in
- CNIL / Garante nuances applied per country
- Cookie notice synced to the live scan
- Consent receipts stored for every visitor
- Scanner catches new trackers automatically
ePrivacy, answered plainly.
Isn’t this the same as GDPR?+
Which cookies actually need consent?+
Why do the rules feel different in France vs Germany?+
What about the ePrivacy Regulation?+
Find out what’s firing before consent.
Run a free cookie scan and see every tracker that loads before a user agrees, then gate them in one click.
Demo with a privacy professional See pricing