EmailBrevo and the GDPR: agreement, role and data location.
Brevo is a email tool. Most customers use it as a processor, it explains how to get its data processing agreement, and it usually keeps data in the European Union. Below: what to check and how to declare it.
Prefilled for you · Free to set up · No credit card
In short
- Category
- Usual role
- Usually a processor
- Data location
- Usually the European Union
- Agreement
- Obtained through the vendor
What does Brevo do with personal data?
Deliver transactional emails such as account notifications and password resets. That is how Privacyboard describes a typical use of Brevo, as a starting point you can edit.
The data usually involved: recipient email addresses, message content and delivery metadata.
Is Brevo a processor or a controller?
Most customers use Brevo as a processor: it handles personal data on their instructions, for the purposes they set. That is the common reading for email tools and it is what Privacyboard suggests.
As a processor, it needs a written agreement with you under Article 28, and you should know which subprocessors it uses. Confirm the role against your own agreement, because the way you use a tool can change it.
Where does Brevo store personal data?
Brevo usually keeps data in the European Union for every customer on its standard service, so there is normally nothing to choose. Privacyboard prefills this and you can change it if your setup differs.
How to find yours: Brevo’s documentation and data processing terms describe where data is hosted.
Even when the main location is in the EU, ask whether subprocessors or support access involve a transfer outside the EEA, and record it if so.
Does Brevo have a data processing agreement?
Checked on 1 November 2026. Vendors change their pages, so check the date.
Brevo does not publish the full text of its data processing agreement on a public page. The reference page explains how a customer gets or signs it, usually from inside the account. Article 28 of the GDPR still requires a written contract, so get it and keep a copy.
What we noted when we opened the page: The DPA is an appendix of the Terms of Use; the appendix text itself was not read.
A page that exists does not mean you are covered. Whether the agreement applies to you depends on your plan and on what you accepted, so record the decision yourself in your vendor list.
Open the Brevo reference pageHow to declare Brevo
- 1
In your privacy policy
Name Brevo as a recipient, say what it is used for (deliver transactional emails such as account notifications and password resets) and mention any transfer outside the EEA. Articles 13 and 14 ask you to tell people who receives their data.
- 2
In your vendor list
Add Brevo with its purpose, the data involved, its role, its region and a link to the agreement. Privacyboard prefills all of this, you confirm or correct it.
- 3
In your processing register
Link Brevo to the activities that use it, so each record shows its recipients. Article 30 asks the register to list the categories of recipients.
What to check before relying on Brevo
- Check the sending region and how message content and logs are retained.
- Avoid putting more personal data in messages than the message needs.
- Make sure bounce and complaint data is handled in line with your retention rules.
- Record the provider as a recipient of customer email addresses.
Questions, answered.
Is Brevo GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how Brevo is configured and used, on the agreement you have with it and on your own practices. What can be checked is documented here: it explains how to get a data processing agreement, the usual role and the data location. Read the agreement itself before relying on it.
Does Brevo have a DPA?
Brevo does not publish the full text of its data processing agreement on a public page. The reference page explains how a customer gets or signs it, usually from inside the account. Article 28 of the GDPR still requires a written contract, so get it and keep a copy. The reference page is https://www.brevo.com/legal/termsofuse/.
Is Brevo a data processor?
Usually, yes. Most customers use Brevo as a processor that acts on their instructions. Check your own agreement and how you use the tool, because the role can differ.
Where does Brevo store data?
Brevo usually keeps data in the European Union for every customer on its standard service, so there is normally nothing to choose. Privacyboard prefills this and you can change it if your setup differs. How to find yours: Brevo’s documentation and data processing terms describe where data is hosted.
Do I need to mention Brevo in my privacy policy?
Yes, if Brevo handles personal data for you. The GDPR asks you to tell people who receives their data (Articles 13 and 14). Name the vendor or its category, say what it is used for and mention any transfer outside the EEA.
How do I add Brevo to my vendor list?
In Privacyboard, pick Brevo from the catalog. The purpose, the data, the suggested role and a link to its agreement are prefilled, and you confirm each one. Creating a workspace is free.
Privacyboard is not affiliated with Brevo. Names and logos belong to their owners and are used only to identify the tool. This page summarises public documents as checked on 1 November 2026; it is guidance, not legal advice, and it does not certify any vendor.