GOVERNATLAS / PRODUCT DOSSIER

CookieYes CMP

CookieYes describes customizable consent banners, cookie auto-blocking, scheduled scanning and centralized consent logs. Hosted, plugin and application editions are separately listed; universal blocking, edition parity and legal compliance are not independently established.

Explore the product ↗Add to comparison ↗

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Evaluate the exact installation you will operate: a hosted script, a plugin or an application integration. Inventory the tags and routes that matter before judging the banner. The useful question is whether a visitor's choice changes actual browser behavior for those integrations and remains understandable after the site or tag configuration changes.

What this record does not establish

The preserved page describes banners, blocking, scanning and logs but lists different product editions. It does not establish that every script is supported or that a consent-mode signal means all network activity stops. Confirm scan cadence, integration support, log retention and export rights for the proposed plan. Do not treat marketing badges as independently verified certification.

1 current source · 1 published assertion
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗

A test worth running

In an authorized test site, capture a fresh visit with no action, reject optional purposes, accept one purpose and then withdraw it. Repeat on a route containing an embedded widget and after a tag-manager update. Compare network events, stored state and the consent log for each step. Include one deliberately unmanaged script so the pilot exposes a coverage gap rather than rewarding a clean banner alone.

GovernAtlas editorial proposal. We have not performed this test.

Evidence to bring back

A route-and-tag coverage manifest with captures for no choice, rejection, selective acceptance and withdrawal.
A configuration and consent-log record tied to the deployed edition, plus a documented unsupported-script finding and owner.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

vendor asserted

Source, dates & preserved provenance

CookieYes CMP — official product documentation ↗

Authority: vendor owned
Observed 2026-10-15 · Reviewed 2026-10-15 · current until 2026-11-14

Artifact SHA-256: 81d7c3bd88779d2b3e3c7ddeec2dc922964b1a2d632da7664fa057e01f13d8f8

The hash identifies the preserved capture. The live source may have changed.

Source register

CookieYes CMP — official product documentation ↗vendor owned · captured 2026-10-15

Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

Can an authorized browser test show what requests occur before consent, after rejection and after withdrawal?

Which exact release, deployment and service responsibilities are included in the proposed configuration?

What evidence records the actual outcome, unresolved exceptions and accountable owner?

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗