whats-best.ai
Search Sign in

Data Protection

Cookiebot

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Cybot A/S · www.cookiebot.com

Report an error on this page Is this your product? →

Link to this page

Cookiebot: AI-assisted analysis on whats-best.ai Cookiebot: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Cookiebot at a glance

Vendor
Cybot A/S
Headquarters
Not stated on the vendor’s pages as of 20 Oct 2026
Data hosting
Not stated on the vendor’s pages as of 20 Oct 2026
Free plan
Yes, per the vendor’s own page source, captured 20 Oct 2026
Panel verdict
The AI panel rates Cookiebot 1.5/5, the mean of 6 judges. Cookiebot, a consent management platform from Cybot A/S, a trademark of Usercentrics A/S registered in Denmark, scored strongest on framework coverage at 5-7 and integrations and automation at 4-6. how scores are made
As of
Vendor pages captured 20 Oct 2026; evaluated by the panel 21 Oct 2026. all sources

Cookiebot alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The External DPO

Weighted verdict

Carries thirty client mandates and bills by the hour they save. Optimizes for multi-client capability, reusable templates, a RoPA that drives the rest, and client-ready reports. Rejects single-tenant tools that treat the consultancy as thirty separate customers.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The External DPO

Panel median The External DPO This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The External DPO
Records & DPIA depth 0.5 of 5 0.5 of 5
Data subject rights & incidents 1 of 5 1 of 5
Privacy regime coverage 3 of 5 3 of 5
Audit readiness & evidence 2 of 5 2 of 5
Integrations & automation 3 of 5 2 of 5
European sovereignty 2 of 5 2 of 5
Pricing transparency 2.5 of 5 2.5 of 5

Records & DPIA depth

How this is scored

The DSMS core: records of processing (RoPA/VVT), data protection impact assessments, processor/DPA management and TOMs — how deeply the legal artifacts are modeled and connected.

0 — Document templates in a folder tree; the "register" is a Word file with version numbers in the filename.

3 — A structured RoPA with basic fields and a DPIA questionnaire, but processors, TOMs and legal bases live outside the system.

5 — RoPA and DPIA as linked modules with templates; processor management and TOM assignment exist but are shallow, and group reuse is copy-paste.

8 — A connected data model — processing activities linked to systems, processors, TOMs and legal bases — with DPIA triggers derived from the record, reusable group templates, and outputs a supervisory authority accepts.

10 — Privacy records as a system of record: the RoPA drives DPIAs, processor management and TOM coverage from one data model, multi-client/mandate capability included, and the documentation is audit-ready without manual assembly.

Report an error

The External DPO

This is a consent layer, not a records system: the captured pages evidence cookie scanning, consent banners and consent logging, and I found no public information on records of processing, DPIA modules, processor management or TOMs. As a consultancy tool this sits beside the register rather than driving it — no multi-client register capability is evidenced on any page I reviewed. 3 4 5

Report an error

Data subject rights & incidents

How this is scored

The operational half of the DSMS: data subject request handling with statutory clocks, breach register and authority notification, deletion concepts that actually delete.

0 — Requests arrive by email and live there; breaches are a phone call and a memo.

3 — A request log and a breach list exist, but deadlines are manual, intake is unstructured, and deletion rules are documentation rather than workflow.

5 — DSR workflows with the Art. 12 clock tracked, structured breach register with the 72-hour clock, deletion concepts assignable to records; automation is reminders.

8 — Intake channels for requests (portal/form), identity-check support, deadline automation with escalation, breach severity assessment and authority-report output, deletion rules tied to the RoPA with execution tracking.

10 — Rights and incidents as operations: end-to-end request handling an authority audit walks through, breach workflows that produce the Art. 33 notification, and deletion automation with evidence that the deletion happened.

Report an error

The External DPO

What is evidenced is visitor-facing rights automation — consent withdrawal at any time, Global Privacy Control signals and an automatic Do Not Sell link routed by visitor location. I found no public information on data subject request workflows with statutory clocks, identity checks, a breach register or authority notification; the 45-day response promise on these pages is the vendor's own policy toward its users, not a module I can run client mandates through. 3 4 6

Report an error

Privacy regime coverage

How this is scored

Which privacy regimes the product actually operationalizes — GDPR, BDSG, Swiss nDSG, UK GDPR, ePrivacy, EU AI Act privacy duties — and whether one record maps across them or each regime is a fresh island.

0 — One regime, hard-coded; anything else is "on the roadmap".

3 — GDPR plus one national law as separate checklists; the same processing activity is documented once per regime.

5 — The major regimes for its market with partial cross-mapping; newer duties (AI Act, ePrivacy changes) present as content packs of varying depth.

8 — Broad current coverage with one-record-many-regimes mapping and visible maintenance as regimes evolve.

10 — Regime coverage as a living product: multiple privacy regimes on one data basis, per-country variants, and documented update cadence when the law moves.

Report an error

The External DPO

Regime breadth is real for the consent layer: GDPR, ePrivacy, UK GDPR and PECR, CCPA, Virginia, Brazil's LGPD, IAB TCF v2.4 and both Google and Microsoft consent modes, with one implementation routing EU visitors to consent and Californians to opt-out. Support for the new Consent Mode v2 signals suggests the set is maintained as frameworks move. I found no public information on broader privacy-regime variants such as Swiss law or AI Act duties. 2 3 5 6 9

Report an error

Audit readiness & evidence

How this is scored

Whether the system produces defensible proof: revision-safe history, evidence collection, reports for auditors, authorities and management.

0 — Exports are screenshots; history is overwritten in place.

3 — PDF reports exist but evidence is attached ad hoc and changes leave no reliable trail.

5 — Versioned records, standard report generators for the core registers, evidence attachments per activity; assembling a full audit file still takes days.

8 — Revision-safe change history, audit-scoped evidence packs on demand, management and authority reports current at a click, auditor access roles.

10 — Audit readiness as a standing state: continuous documentation status per regime and scope, exportable proof packs an auditor accepts as-is, and a defensible answer to "show me the state on date X".

Report an error

The External DPO

Every consent decision is logged including changes over time, and scan reports and consent statistics are generated automatically — a defensible trail for the consent slice, with even 24-month retention advice for opt-out records on the pages. But "audit" on these pages means a website tracking audit; I found no public information on revision-safe record history, evidence packs, auditor access roles or authority-ready report output. 3 4 6 7

Report an error

Integrations & automation

How this is scored

Whether the platform feeds from the real IT estate — directory import, ticketing, API — and automates the recurring privacy work instead of re-typing it.

0 — A closed island: manual entry in, PDF out, no API.

3 — CSV/Excel import and export; no live connections, no API worth the name.

5 — Directory import (AD/Entra), a documented REST API for core objects, a handful of native connectors (ticketing or SSO); automation is reminders and recurrence.

8 — Real connector set (ticketing, HR or asset sources), webhooks, SSO/SCIM, workflow automation with delegation and escalation, useful AI assistance with human review.

10 — The platform behaves like infrastructure: API parity for the data model, event streams, bidirectional sync with the estate, and automation that measurably removes the recurring toil (reviews, attestations, evidence pulls) rather than renaming it.

Report an error

The External DPO

Native no-code plugins for Wix, Shopify and WordPress, Google Tag Manager templates and consent signals to Google, Microsoft and Amazon are genuine estate integration for a consent platform, with monthly automated scanning and prior blocking removing recurring manual work. I found no public information on a documented API for core objects, directory import, ticketing or HR connections, or single sign-on. 1 2 8 9

Report an error

European sovereignty

How this is scored

Where the compliance record of the whole company actually lives and under whose law — entity, hosting, subprocessors, DPA. A platform that maps your processing is itself your most concentrated processing.

0 — Non-EU entity, non-EU-default hosting, no public DPA or subprocessor list — for the system holding your RoPA.

3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad or undocumented.

5 — EU hosting is the default, DPA and subprocessor list published; the vendor or a critical subprocessor is still within non-European jurisdictional reach.

8 — EU entity, EU hosting with named data centers, published subprocessor list free of content-touching non-EU processors, DPA and TOMs public.

10 — Jurisdictionally clean end to end: European ownership, EU-only hosting and subprocessors, on-premises or sovereign-cloud options, and the whole chain documented publicly.

Report an error

The External DPO

The controller is a Danish-registered company and a data processing agreement is available, with third-country transfers resting on EU standard contractual clauses. But I found no public information on hosting locations or named data centers or on a published subprocessor list, and the group shares data across entities including a US-incorporated company. 1 2 3

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real invoice — per module, per entity, per year, with consulting unbundled — from public pages alone. Unpublished pricing is the B2B norm in this market, so this criterion describes rather than condemns; the benches weight it accordingly.

0 — No public prices at all; every configuration is a sales conversation.

3 — An entry price exists, but module add-ons, entity counts or bundled consulting make the real total incomputable.

5 — Most editions carry real numbers with billing period stated and software separated from services; at least one commonly needed module or scale step is unpriced.

8 — Every edition and module priced publicly with entity/user boundaries and setup fees stated; only genuine corporate-group contracts are custom.

10 — Complete price computability: modules, scale steps, service packages and renewal rules public, so the invoice for a 100-employee company and a 10-client consultancy is a two-minute exercise.

Report an error

The External DPO

Per-platform pricing is unusually public: Shopify plans at six and thirty US dollars per month, Wix Premium at seven euros per month, WordPress Premium from seven euros per month per domain, plus a 14-day trial and a free tier. The page-count scale steps and the tiers aimed at larger businesses and enterprises carry no public prices, so the real invoice for a bigger client is not computable from these pages alone. 1 7 8

Report an error

European sovereignty — proven facts

0 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency Not determined — uncited Report an error
Subprocessors Not determined — uncited Report an error

Questions about Cookiebot

Is Cookiebot European?

Not determined: the vendor’s pages as captured do not say where Cookiebot is based.

Where does Cookiebot store data?

Not stated on the vendor’s pages as of 20 Oct 2026.

Does Cookiebot have a free plan?

Yes. Cookiebot has a free plan, per the vendor’s page captured 20 Oct 2026.

What are the best alternatives to Cookiebot?

As of 21 Oct 2026, the panel rates preeco | datenschutz (4/5), Dastra (3/5) and caralegal (3/5) highest among the other 41 Data Protection products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is preeco | datenschutz (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Cookiebot alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Do you know more about Cookiebot? Tell us Report an error on this page

Sources (9)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page www.cookiebot.com Checked 20 Oct 2026 Details →
  2. 2 Legal notice — found from the homepage www.cookiebot.com Checked 20 Oct 2026 Details →
  3. 3 Privacy policy — found from the homepage www.cookiebot.com Checked 20 Oct 2026 Details →
  4. 4 Security / trust page — found from the homepage www.cookiebot.com Checked 20 Oct 2026 Details →
  5. 5 Privacy regime coverage — found from sitemap www.cookiebot.com Checked 20 Oct 2026 Details →
  6. 6 Privacy regime coverage — found from sitemap www.cookiebot.com Checked 20 Oct 2026 Details →
  7. 7 Audit readiness & evidence — found from sitemap www.cookiebot.com Checked 20 Oct 2026 Details →
  8. 8 Integrations & automation — found from sitemap www.cookiebot.com Checked 20 Oct 2026 Details →
  9. 9 Integrations & automation — found from sitemap www.cookiebot.com Checked 20 Oct 2026 Details →