Private beta for EU websitesGDPR + ePrivacy baseline

Cookie consent management,for EU-facing websites

One consent management platform to scan cookies and trackers, block optional technologies before consent and retain visitor choice records.

Built for EU-facing e-commerce and SaaS teams managing one or more websites. Google Consent Mode v2 supported. Access is reviewed during private beta.

Request beta access Test the consent experience

EU consent workspace

example-store.eu · last scan 8 min ago

technologies detected

blocked before consent

consent purposes

Consent readiness

6 / 7 checks

Prior blocking activeReject on first layerGranular purposesWithdrawal entry point

Latest consent event

Custom selection

Analytics allowed · Advertising denied

NecessaryAlways active

FunctionalDenied

AnalyticsGranted

AdvertisingDenied

Prior blocking

Consent records

Consent Mode v2

GDPR and ePrivacy baseline

Product

One control layer from discovery to consent evidence

The workflow connects the technical steps that often live in separate tools: finding trackers, controlling when they run, collecting a choice and recording what happened.

Prior consent and script control

Hold non-essential scripts, iframes and cookies until the visitor makes a choice.

Analytics, advertising and functional categories

Cookie and tracker inventory

Scan pages, identify third-party technologies and keep the inventory ready for review.

Manual and scheduled scans

Consent records

Record the selected categories, time and configuration context behind each decision.

Exportable evidence trail

Google Consent Mode v2

Send consent updates for analytics and advertising storage, user data and personalisation.

Default denied, updated after choice

Start with the cookie consent banner workflow to connect visitor choices to these controls, or compare all Consentory solutions for your website and team.

EU consent framework

Designed around a real choice, not a decorative banner

Built around the core consent principles reflected in GDPR, the ePrivacy framework and European regulator guidance.

Review the EU framework

No non-essential storage before consent

The default state remains denied for optional categories until a visitor actively opts in.

Reject is available on the first layer

Accept all, reject all and manage choices are presented together without a hidden refusal path.

Purpose-based, granular controls

Visitors can decide separately for analytics, functionality and advertising.

Consent can be changed later

The preference centre can be reopened so withdrawing consent is as practical as granting it.

Clear records for accountability

The service stores a pseudonymous visitor reference and the categories selected at that moment.

Country-level review stays visible

GDPR is EU-wide, while ePrivacy rules and regulator expectations still vary between Member States.

Consent management is one part of a wider privacy programme. Review the full compliance scope

Interactive preview

Test the decision path your visitors will see

Try the first layer and purpose controls. Optional categories start off, Reject all is immediately available and necessary storage remains clearly separated.

eu-demo.exampleLive preview

Your privacy choices

We use optional cookies to measure performance, improve features and personalise advertising. You can accept, reject or choose purposes. Strictly necessary cookies are always active.

Implementation

A reviewable path from scan to production

Consent management is operational work, not a one-off banner task. The workflow keeps discovery, configuration and verification connected.

Discover

Scan the domain, review cookies and third-party scripts, then assign each technology to a purpose.

Configure

Set the notice text, equal choice actions, purpose controls, branding and policy destination.

Deploy and verify

Install one script, confirm prior blocking and test consent updates in your tag and analytics stack.

Google Tag Managergtag.jsWordPressWebflowCustom HTML

Built for the operating owner

For the person accountable for consent across a growing web portfolio.

Consentory helps agencies and EU-facing e-commerce and SaaS teams review the technical consent setup across one or more websites. The operating team sets the policy; a developer installs and validates the technical layer.

Agencies and multi-site teams

A repeatable scan, configure and verify workflow for client portfolios.

Explore the agency workflow

EU-facing e-commerce

Check campaign tags and consent behaviour on representative storefront pages.

Explore the storefront workflow

EU-facing SaaS

Connect denied defaults, blocking, consent signals and records.

Explore the SaaS workflow

Illustrative private-beta scenario

A multilingual EU storefront replaces fragmented consent controls.

representative pages reviewed

cookies and trackers inventoried

purpose categories configured

The scenario models a mid-market retailer serving Germany, France and Poland. The team maps analytics, embedded media and advertising tools, publishes EN/DE/FR choices, verifies that optional scripts remain blocked before consent and exports a versioned consent record for review.

This is an illustrative workflow, not a customer endorsement or measured production result.

EU operating conditions

A CMP supports compliance. It does not replace governance.

The service is the technical consent layer. Your organisation remains responsible for the processing decisions behind it.

What the platform handles

Tracker and cookie discovery
Purpose-level visitor choices
Prior blocking rules for known technologies
Consent Mode v2 updates
Consent event records

What the controller must own

Legal bases and final notice wording
Vendor and sub-processor due diligence
Retention and deletion rules
International transfer safeguards
Member State and sector-specific review

What changes across the EU

National ePrivacy implementation
Regulator expectations and enforcement
Language and accessibility requirements
Rules for children and sensitive sectors
Ad-tech framework requirements

EU FAQ

The questions that should be answered before deployment

Straight answers on consent, analytics and responsibility. Final decisions should be validated for the countries and processing activities in scope.

Not necessarily. A consent layer is generally needed when a site stores or accesses information on a visitor's device for purposes that are not strictly necessary. The ePrivacy rules govern that device access, while GDPR applies where personal data is processed. The exact implementation should be checked against the law and regulator guidance in each target country.

Private beta

Prepare your consent layer for EU visitors.

Send us your domain and target countries. We will map the technical setup and identify the legal inputs your team still needs to supply.

Request beta access

No card required. Access is confirmed by the Consentory team.