Know what is on your site before a plaintiff’s firm does.Free website scanScan Your Site
Log in Sign up Book a demo
Solutions / ePrivacy
EPRIVACY DIRECTIVE · THE COOKIE LAW

Data privacy and confidentiality in electronic communications.

GDPR gets the headlines, but it’s the ePrivacy Directive, the “cookie law”, that requires prior consent before you store or read anything on a user’s device. It’s enforced by national DPAs and it’s where most banner fines actually come from. We make your consent layer meet it.

Prior-consent bannersPer-country nuanceePrivacy Regulation watch

Where the banner fines really come from.

Prior
Consent required

Non-essential cookies and trackers may only fire after the user agrees.

27
Transpositions

Each member state implements the Directive, so the details vary by country.

€60M
CNIL precedent

France has issued nine-figure cookie fines under its ePrivacy transposition.

Reg.
Replacement pending

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.

S

Tracker discovery

A live scan of every cookie, pixel and SDK so nothing fires before consent without you knowing.

C

Prior-consent banner

Trackers blocked until the user agrees, with reject-all as easy as accept-all.

P

Per-country tuning

CNIL, Garante and other DPAs differ on scroll, walls and consent lifetime. We apply the local rule.

N

Cookie notice

A live cookie table in your privacy notice, populated straight from the scanner.

R

Consent receipts

Timestamped proof of what each user agreed to, ready for a DPA inquiry.

A

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
Rollout · typical EU site
  • 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.

Without a program
  • 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
With Captain Compliance
  • 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?+
They work together but are distinct. The ePrivacy Directive requires consent to store or read anything on a device, regardless of whether it’s personal data. GDPR governs the personal data you then process and defines what valid consent looks like. Cookie banners live primarily under ePrivacy.
Which cookies actually need consent?+
Anything not strictly necessary to deliver the service the user asked for, analytics, advertising, personalisation, social embeds. Strictly necessary cookies (e.g. a session or load balancer) are exempt. Our scanner classifies each one for you.
Why do the rules feel different in France vs Germany?+
Because each country transposes the Directive into its own law and its DPA issues its own guidance, on consent walls, scroll-as-consent, and how long consent lasts. We apply the local rule based on the visitor’s country.
What about the ePrivacy Regulation?+
It’s been in the works for years and would replace the Directive with one directly-applicable EU regulation. It isn’t in force yet. We track it and will migrate your configuration when it lands.

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