Brevo
Email marketing · brevo.com · last read 2026-11-16
At a glance
- Is Brevo GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Brevo itself publishes, each answer linked to its source and the date we read it.
- Does Brevo have a data processing agreement (DPA)?
- Yes. Brevo publishes a data processing agreement at brevo.com. It describes how a new subprocessor is announced but states no notice period. It promises breach notification "without undue delay", with no number of hours. Source and date
- Which version of the Brevo DPA is current?
- On 2026-11-09, Brevo's DPA at brevo.com printed “Version : October 1st, 2025”. Source and date
- Is Brevo ISO 27001 certified?
- Brevo states ISO/IEC 27001 certification (2022 edition, as Brevo names it), and its own page links to the certificate. In Brevo's words: “ISO 27001:2022-certified Your data is protected by multi-factor authentication, IP address whitelisting, and more. Download certificate.” We read this on 2026-10-05. Source and date
- How does Brevo transfer personal data out of the EU?
- Brevo's agreement relies on the EU standard contractual clauses and the EU-U.S. Data Privacy Framework. Brevo, Inc. is on the official Data Privacy Framework List (status: Active). Source and date
- Does Brevo offer EU data residency?
- The EU is the default region for this vendor. Source and date
- Who are Brevo's subprocessors?
- Brevo lists 23 third-party subprocessors; 13 of them name at least one processing country outside the EEA. We last read the list on 2026-10-05. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | Brevo |
|---|---|
| HQ | FR |
| Parent company | EIFFEL 65 |
| Ultimate ownership | FR |
| EU contracting entity | Brevo GmbH |
| LEI | 96950003GL1WWL9QWK73 |
| US CLOUD Act reach | No US company in the ownership chain on record |
| Source | brevo.com · 2026-10-26 |
Legal entity from the vendor's own terms. LEI, registered country and parent company from the Global LEI Index (GLEIF); ownership is left empty where GLEIF names no parent. The CLOUD Act row is arithmetic over those countries, not an assessment of risk.
Brevo data residency
| Region | EU data location | Minimum plan | Source | Observed |
|---|---|---|---|---|
| EU | EU by default | — | help.brevo.com | 2026-10-05 |
EU: The document states that all hosting servers where Brevo processes and stores its databases are located within the European Union, so EU storage applies without customer choice.
The same question for every vendor: where SaaS vendors store EU data.
Brevo's subprocessor list names Google for hosting or infrastructure. Which SaaS vendors run on which cloud, and the sovereign offerings of each: sovereign clouds.
Subprocessor chain
23 third parties · 5 of the vendor's own group companies · 13 with a country outside the EEA · all read 2026-10-05
| Subprocessor | Country | Purpose |
|---|---|---|
| Adyen | — | PCI DSS-compliant third party payment provider to process payments |
| Anthropic | IE, US | AI provider |
| Chargebee | — | PCI DSS-compliant third party payment provider to process payments |
| Cloudflare | US, EU | Content Delivery Network & WAF |
| Convrrt | US | Creation of customised landing pages (optional) |
| Eldar IT | RS | Maintenance of the Salesforce Plugin |
| GoCardless | — | PCI DSS-compliant third party payment provider to process payments |
| Google Cloud Platform (GCP) | FR, BE | Hosting |
| Google Gemini | EU, US | AI provider |
| iBasis | LI, AT, DE | SMS routing except NorAm zone and France |
| Integry | US, EU | Integration with third-party software (optional) |
| Langfuse | EU | AI provider |
| Omni | US, EU | Dashboards |
| Open AI | EU, US | AI provider |
| OVH | FR | Hosting |
| PayPal | — | PCI DSS-compliant third party payment provider to process payments |
| Sinch | GB, EU, US | SMS routing to Portugal, India, Indonesia and the Bahamas |
| Stripe | — | PCI DSS-compliant third party payment provider to process payments |
| Telnyx | IE, US, EU | SMS routing |
| Twilio | — | third party phone number provider |
| Twilio SMS | US, EU | SMS routing to the NorAm zone |
| Vonage | US, EU | SMS routing |
| Zendesk | US, EU | Ticketing/support tool |
Brevo's own group companies listed as subprocessors (5)
| Company | Country | Purpose |
|---|---|---|
| Brevo CRM Solutions Limited | IN, FR, BE | Customer experience & Maintenance |
| Brevo GmbH | DE, FR, BE | Customer experience & Maintenance |
| Sendinblue Inc. | US, FR, BE | Customer experience & Maintenance |
| Sendinblue SAS (Brevo France) | FR, BE | Customer experience & Maintenance, acting as sub-processor if You have contracted with another Brevo entity |
| Yodel GmbH | AT, EU | Brevo Phone Customer experience & Maintenance |
The count outside the EEA is arithmetic over the country column, not a judgement about lawfulness. A transfer outside the EEA can be perfectly lawful; whether this one is depends on your use, not on the vendor.
Every subprocessor in the registry, and which vendors name it: subprocessors.
Processing terms
From the vendor's data processing agreement · read 2026-10-09 · brevo.com
| Term | What the agreement says |
|---|---|
| Transfer mechanism | EU-U.S. DPF |
| Transfer mechanism | SCC (module not stated) |
| Notice of new subprocessors | By email or through the customer's account on the Software, before authorizing the new subprocessor (no advance period stated) |
| If you object to one | If the objection is justified by a violation of EU Data Protection Law, customer may terminate the Terms within 30 days following the notification |
| Obligations passed to subprocessors | written terms with each Sub-Processor with data protection obligations no less protective than this DPA; vendor remains responsible for Sub-Processor compliance |
| Breach notification | without undue delay, by email on file or via account on the Site |
| Deletion when the service ends | On account termination for any reason, Customer Content is immediately and permanently deleted, unless the customer requests temporary availability for recovery |
| Getting your data back | Customer may export its Exportable Data during a Transitional Period of 30 calendar days after the two-month Notice Period, with the vendor providing export instructions or Documentation; extendable once, and an alternative period of up to seven months if 30 days is technically insufficient |
| Requests from data subjects | Reasonable assistance (on written request, at Customer's expense) with data subject requests; requests sent directly to the vendor are not answered by it, and the data subject is referred to the Customer as controller with the Customer's contact details |
| Audit | Audit documentation (copy of most recent third-party audits/certifications or comparable documentation) on written request, at reasonable intervals and customer's sole expense; no more than once per contract year; no on-site investigation unless mutually agreed in writing |
| Processing on your instructions | Processes Customer Data only on Customer's written, documented instructions; informs Customer if an instruction violates Data Protection Laws |
| Confidentiality of staff | Only authorized employees have access, on a need-to-know basis, and they undertake to respect the confidentiality of Personal Data |
| Security measures | endeavours to protect the integrity, confidentiality and administrative, material and technical security of Customer Content |
Terms as the agreement states them. Where it is silent on a term, there is no row; that is not a statement that the vendor does not offer it.
Which version applies
On 2026-11-09, the agreement printed: Version : October 1st, 2025
at brevo.com
Last updated 2025-10-01
This version is in our copies from 2026-10-09.
These terms side by side for every vendor: data processing agreements compared. What vendors give you for a transfer impact assessment: transfer impact assessments.
Assurance
Is Brevo ISO 27001 certified?
Brevo states ISO/IEC 27001 certification (2022 edition, as Brevo names it), and its own page links to the certificate. We read this on 2026-10-05.
- Certificate published “ISO 27001:2022-certified Your data is protected by multi-factor authentication, IP address whitelisting, and more. Download certificate”
Source: brevo.com, 2026-10-05
Of the 122 vendors in this registry whose own pages state ISO/IEC 27001, 16 link to the certificate, 43 say it is available on request, and 63 state it without saying how to get it. A certificate names the certification body, the scope and the expiry date: those are the three things to check.
| Scheme | Status | Scope | Source | Observed |
|---|---|---|---|---|
| CCPA | Claimed | implemeted practices that support CCPA | brevo.com | 2026-10-05 |
| GDPR | Claimed | implemeted practices that support GDPR | brevo.com | 2026-10-05 |
| ISO 27001:2022 · ISO27001 | Certificate published | — | brevo.com | 2026-10-05 |
| CASL | Claimed | implemeted practices that support CASL | brevo.com | 2026-10-05 |
Claimed means the vendor asserts the scheme on its own page and offers nothing further. Available on request means the report or certificate exists but sits behind a request, a login or an NDA. Neither is a certificate we have seen. That is a distinction an auditor makes, so we make it too.
SecNumCloud, C5, ENS and HDS for every vendor, with the pages for ISO standards, SOC 2 and TISAX: certifications compared.
Official registers
| Register | Offering, as the register names it | Status | Level | Valid until | Observed |
|---|---|---|---|---|---|
| Data Privacy Framework List (US) | EU-U.S. Data Privacy Framework · Brevo, Inc. | Active | non-HR data | 2027-02-26 | 2026-10-07 |
| Data Privacy Framework List (US) | Swiss-U.S. Data Privacy Framework · Brevo, Inc. | Active | non-HR data | 2027-02-26 | 2026-10-07 |
| Data Privacy Framework List (US) | UK Extension to the EU-U.S. DPF · Brevo, Inc. | Active | non-HR data | 2027-02-26 | 2026-10-07 |
| Global LEI Index (GLEIF) | SENDINBLUE · SENDINBLUE | ISSUED | FR | 2027-01-28 | 2026-10-08 |
- ACN qualified cloud (Italy): checked 2026-11-16, no entry under Brevo; Brevo GmbH; Sendinblue
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under Brevo; Brevo GmbH; Sendinblue
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Brevo; Brevo GmbH; Sendinblue
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under Brevo; Brevo GmbH; Sendinblue
- Data Privacy Framework List (US): checked 2026-11-16, 3 entries under Brevo; Brevo GmbH; Sendinblue
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under Brevo; Brevo GmbH; Sendinblue
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Brevo; Brevo GmbH; Sendinblue
- FedRAMP Marketplace (US): checked 2026-11-16, no entry under Brevo; Brevo GmbH; Sendinblue
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under Brevo; Brevo GmbH; Sendinblue
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under Brevo; Brevo GmbH; Sendinblue
What the authority publishes, not what the vendor claims. An entry covers the offering it names and nothing else: a FedRAMP authorisation for a government edition says nothing about the commercial service. No entry is not a finding about security - most vendors never apply - and an entry filed under a name not listed above would not have been found.
What an entry on the Data Privacy Framework List covers, and which vendors hold one: EU-US Data Privacy Framework.
Support window
| Product | Support period | State | SBOM | Source | Observed |
|---|---|---|---|---|---|
| Brevo (service) | — | Service only | unknown | brevo.com | 2026-10-11 |
Vulnerability reporting: no security.txt at the well-known path (read 2026-10-17)
How other vendors publish theirs: security.txt across the registry.
Documents
| Document | Disclosure | Transcription | HTTP | Observed |
|---|---|---|---|---|
| certifications | Public | full | 200 | 2026-10-05 |
| dpa | Public | full | 200 | 2026-10-09 |
| residency | Public | full | 200 | 2026-10-05 |
| subprocessors | Public | full | 200 | 2026-10-05 |
History
Nothing has moved since we started watching this vendor on 2026-10-05. Changes appear here only after a human has reviewed them.
Every reviewed change across the registry, newest first: vendor changes.