Sovereignty Scan
Scan
Sovereignty Scan/Vendors/Didomi
Risk indicator, not a GDPR compliance verdict. Point-in-time assessment based on public web stack signals.Methodology & LimitationsCorrect listing / submit response
Didomi-Logo

Tag Management & CDPs

Didomi : Datenschutz, & EU Alternatives

Didomi is EU/EEA-based: no third-country transfer at the primary vendor. Still check the subprocessor list.

🇪🇺EUEU-Anbieter

Last checked:

Is Didomi GDPR compliant?

Didomi is EU/EEA-based: no third-country transfer at the primary vendor. Still check the subprocessor list.

Vendor Profile

Who is the contractual partner?

Jurisdiction
EU
Hosting
AWS EU (Paris)
Owner
Didomi SAS🇫🇷

Sovereignty Level: Level 3 of 4

EU-Anbieter mit US-Subprozessoren. Vertragspartner ist EU, aber ein einzelner US-Subprozessor reichert das Setup wieder mit Drittland-Risiko an.

  1. Level0
  2. Level1
  3. Level2
  4. Level3
  5. Level4

The five levels, from US-SaaS (Level 0) to fully sovereign (Level 4), we explain in detail here.

Contract & Subprocessor Chain

  1. 1.Didomi SAS (FR, Paris)
  2. 2.AWS EU Paris (Subprozessor)

Even if the main provider is based in the EU, a US subprocessor in this chain can trigger a third-country transfer. This is the core pitfall of .

Data Categories

What data does Didomi process?

In typical use, the following data categories arise. Which ones are relevant for you depends on your setup and scope of use.

  • Controls which other tracking tools are loaded
  • Reads from cookies, dataLayer and URL parameters
  • Indirectly: all data of subsequently loaded tools

Data Subjects

Who is affected by the processing?

Under Art. 30 GDPR, you must document the categories of data subjects per processing activity. In typical use, these include:

  • Persons whose data is processed in the application.

Concrete Impact

What does this mean in practice?

The consequences depend on the specific data type. For personal data, GDPR Art. 28 (DPA), Art. 30 (records) and Art. 44 ff. (third-country transfer) apply.

Note: This is a risk description, not a specific incident. Whether access occurred in your case depends on many factors. What can be documented: the risk must be named in your TIA and mitigated with additional measures.

meetergo Recommendation

EU-native CMP, Konfiguration aktuell halten

Didomi ist ein europäischer Consent-Manager mit solider DSGVO-Abdeckung. Stellen Sie sicher, dass alle eingesetzten Drittdienste in der Consent-Konfiguration erfasst sind.

CMP-Konfiguration prüfenCheck your own domain

Migration Plan

How to migrate away from Didomi

The following steps are the typical path for this tool category. Order and time required depend on your specific setup.

  1. 1

    Export container from the existing system

  2. 2

    Recreate triggers and variables in the EU alternative

  3. 3

    Debug all tags in test mode before going live

We help with migration planning at no cost: 30 minutes with a data protection specialist to prioritise and define a migration sprint. Book appointment

Frequently Asked Questions

Didomi & Privacy: FAQ

Is Didomi GDPR-compliant?

Didomi is an EU/EEA-based provider and generally well-suited for GDPR-compliant setups. The usual obligations still apply: DPA, check the subprocessor list, document technical and organisational measures.

Who is the contractual partner for Didomi?

The contract chain includes: Didomi SAS (FR, Paris) · AWS EU Paris (Subprozessor). The legal parent entity is decisive for data protection. Even if an EU subsidiary signs the DPA, a US subprocessor in the chain can trigger third-country transfer obligations.

What EU alternatives are there to Didomi?

There are several GDPR-compliant EU alternatives. They are listed under "EU Alternatives" on this page. The selection is tailored to the feature set of Didomi (Consent Management Platform). meetergo covers the core workflow and can fully replace Didomi in many cases.

Where is Didomi data stored?

According to provider information: AWS EU (Paris). Note: even an EU data centre does not protect against the CLOUD Act when the parent company is in the US. This is the core finding of the Schrems II decision.

How much effort is involved in switching away from Didomi?

Migration effort depends on your specific setup: typically between a few business days (booking, forms) and several weeks (CRM, hosting). The roadmap below shows the typical order.

Related Vendors

More tools in Tag Management & CDPs

Next Step

Which tools are running on your website?

60 seconds, no login: the Sovereignty Scan shows all detected vendors with jurisdiction, risk, and matching EU alternatives.

To the ScanMethodology

Note

Hinweis

Risiko-Indikator, keine Rechtsberatung.

Der Sovereignty Scan wertet öffentlich erreichbare Signale aus (HTML der Startseite und Rechtsseiten, DNS-, MX-, SPF- und ASN-Daten) und vergleicht sie mit unserer Datenbank von ca. 3.000 Anbietern. Die Zuordnung von Tool zu Eigentümer und Jurisdiktion basiert auf öffentlichen Quellen (Impressum, Datenschutzerklärung, Wappalyzer, RIPE/ARIN-Registrierungen) und ist als Erstindikation zum Stichtag der Auswertung gedacht, nicht als rechtsverbindliche Bewertung.

Die Note A–E ist ein Risiko-Indikator, kein DSGVO-Konformitätsurteil. Für eine konkrete DSGVO-Bewertung, insbesondere für Auftragsverarbeitungsverträge (AVV/DPA), Standardvertragsklauseln (SCC) und Transfer Impact Assessments (TIA), wenden Sie sich bitte an Ihren Datenschutzbeauftragten oder eine externe Rechtsberatung. meetergo trifft keine Aussage darüber, ob ein konkreter Anbieter in einem konkreten Anwendungsfall DSGVO-konform eingesetzt werden kann.

Korrektur & Stellungnahme: Wenn Sie Domain-Inhaber, Datenschutzbeauftragter oder Pressestelle der bewerteten Domain sind und die hier gezeigten Signale nicht Ihrer aktuellen Tool-Konfiguration entsprechen, nehmen wir Korrekturen auf und passen die Anzeige nach Prüfung umgehend an.

Methodik & GrenzenListing korrigieren / Stellungnahme einreichen