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

Email Marketing

Brevo (E-Mail-Versand) : Datenschutz, & EU Alternatives

Brevo (E-Mail-Versand) is EU/EEA-based: no third-country transfer at the primary vendor. Still check the subprocessor list.

🇪🇺EUEU-Anbieter

Last checked:

Is Brevo (E-Mail-Versand) GDPR compliant?

Brevo (E-Mail-Versand) 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
Brevo (FR)
Owner
Brevo (Sendinblue)🇫🇷

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.

Data Categories

What data does Brevo (E-Mail-Versand) process?

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

  • Email addresses of all recipients
  • Transactional and marketing email content
  • Tracking data (opens, clicks, bounces)
  • For DKIM/SPF: full send flow of your domain

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:

  • All recipients of your newsletters and transactional emails
  • Newsletter subscribers
  • Existing customers receiving confirmation and service emails

Concrete Impact

What does this mean in practice?

All newsletter recipients and all transactional emails (confirmations, invoices) go through a US provider. For government or enterprise customers this is often a disqualifying factor.

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.

Migration Plan

How to migrate away from Brevo (E-Mail-Versand)

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

  1. 1

    Generate new API credentials and DKIM keys

  2. 2

    DNS: update SPF, DKIM, DMARC to new sender

  3. 3

    Port templates (HTML + plain text)

  4. 4

    Import list export from the old system

  5. 5

    Soft cutover: 10% traffic, then 50%, then 100%

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

Brevo (E-Mail-Versand) & Privacy: FAQ

Is Brevo (E-Mail-Versand) GDPR-compliant?

Brevo (E-Mail-Versand) 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 Brevo (E-Mail-Versand)?

The contracting party according to the DPA is Brevo (Sendinblue). The vendor profile above shows the exact ownership chain including subprocessors.

What EU alternatives are there to Brevo (E-Mail-Versand)?

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 Brevo (E-Mail-Versand) (E-Mail-Marketing). meetergo covers the core workflow and can fully replace Brevo (E-Mail-Versand) in many cases.

Where is Brevo (E-Mail-Versand) data stored?

According to provider information: Brevo (FR). 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 Brevo (E-Mail-Versand)?

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 Email Marketing

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