DPO Radio

Cookie / ePrivacy AI Insight

Overview Image

Why Cookie / ePrivacy Insight Matters

Cookie classification — necessary, analytics, marketing, social — is a compliance task that maps directly to consent banner copy and consent collection mechanics. Misclassifying a marketing cookie as necessary is the kind of finding regulators surface during ePrivacy enforcement actions, because "necessary" is precisely the category that carries no consent requirement. Banner copy that diverges from the actual cookie purpose is the kind of finding that surfaces during compliance audits.

The cookie / ePrivacy AI insight workflow runs from a completed privacy scan of one of your web properties. It takes the cookies that scan recorded and the third-party hosts it saw, classifies each one by purpose, cites the relevant ePrivacy national overlay, and proposes banner copy that aligns with the classification. The DPO reviews the draft and accepts or rejects it, and that decision is recorded with the frameworks cited.

How It Works

Trigger From a Completed Privacy Scan

The workflow is launched from the result of a completed privacy scan — there is no separate cookie register to curate first. Each cookie the scan recorded and each third-party host it saw is classified independently.

Per-Cookie Classification

Four categories: necessary, analytics, marketing, social. The classification draws on cookie name, domain, and third-party context — a recognised social-platform host classifies as social, for example. Each entry also carries a severity derived from its category: necessary is low, analytics medium, social high, and a marketing tracker critical.

National Overlay Citation

Each classification cites the ePrivacy national overlay applicable to the operating jurisdiction. The overlay defines what consent mechanism is required per category.

Banner Copy Suggestion

For each classified entry the workflow proposes banner copy that matches the category. The DPO reviews and accepts or revises.

Withdrawal Mechanism Wording

The workflow proposes withdrawal mechanism wording per category — explicit opt-out for marketing, granular opt-out per purpose, withdrawal mechanism visibility requirements.

Three Audit Events Per Run

Each run emits three audit events: the workflow started, the draft produced, and the operator's accept or reject decision. The decision event carries the scan it came from and the draft identifier, so a reviewer can walk any classification back to the scan that recorded the cookie.

The Difference

Graphic Image

Without Cookie / ePrivacy Insight

Graphic Image

With Forseti Cookie / ePrivacy Insight

IconCookie classification is bespoke per entry with risk of inconsistent categorisation.
IconPer-cookie classification cites the national overlay.
IconBanner copy is reconstructed for each compliance refresh.
IconBanner copy suggestions align with the classification.
IconWithdrawal mechanism wording drifts from the actual cookie purpose.
IconWithdrawal mechanism wording matches the category requirement.

Built for Auditable AI

Build For Image

Classifications cite the national overlay. Banner copy is proposed, never auto-deployed.

Build For Image

Accepting a draft does not change your consent configuration. The platform records the decision and keeps the classification and the proposed copy as a reviewed working record; putting the wording live in a banner or a consent purpose is a separate action your team takes on the consent screens.

Build For Image

The audit trail walks each cookie classification from the scan that recorded it, through the draft the workflow produced, to the operator's accept-or-reject decision.

Regulatory Framework Support

FrameworkHow Cookie / ePrivacy Insight Supports It
EU ePrivacy national overlaysClassifies cookies and proposes banner copy against the operating jurisdiction's ePrivacy implementation.
EU GDPRCites GDPR consent and lawful-basis requirements for marketing and social cookies.
Overview Image

Related Forseti Work

Start cookie insight from a completed scan. Use the processing and notice reviews to check what the privacy records say about the wider activity. See Privacy Workflows.

Background Image

See Cookie / ePrivacy Insight in Action

Ready to see a completed privacy scan's cookies and trackers classified with banner copy suggestions in five minutes? Request a personalised demo.

Demo Image
Ronni K. Gothard Christiansen

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io+84 909 500 760

Next Steps

Icon Image

Start a Compliance Pilot

Run cookie / ePrivacy insight monthly against a fresh privacy scan of your web properties for one quarter.

Icon Image

Discuss Your Compliance Needs

Talk to our team about how the workflow fits your consent management platform integration.

Frequently Asked Questions About Cookie / ePrivacy Insight

Four: necessary, analytics, marketing, and social. The categories map to the ePrivacy national overlay requirements for consent collection — "necessary" being the one that carries no consent requirement.

No. Banner copy is proposed and nothing is deployed. Accepting a draft records the decision against the scan; it does not write to your consent purposes or policies. Applying the wording is a separate, deliberate action your team takes on the consent screens.

The ePrivacy national overlay applied per cookie matches the affected jurisdiction. Organisations operating across multiple jurisdictions run the workflow per-jurisdiction.

No. The insight run is started by a person, from the result of a completed privacy scan — there is no scheduler for it. Teams that want a monthly cadence run a fresh scan of the property and start the insight from that result, which also keeps every classification tied to the scan that observed the cookies.

Yes. Each run sends requests to the AI provider your organisation has configured, and your provider bills your organisation for them directly. A run is never refused because a Forseti allowance ran out, and the Usage page reports what each feature consumed.