Where your email list really is — seven privacy policies side by side
The common assumption is that email tools are American and the list goes across the Atlantic. We read seven services’ own privacy policies on 3 September 2026 and again on 3 November 2026: four of seven state that they store the list data in the EU, and one does not say at all.
When choosing an email tool, data location is either not considered at all or assumed settled in the wrong direction. The most common assumption is that the industry’s tools are American. We went through seven services’ own privacy policies on 3 September 2026 — not directories or other comparison sites’ tables — and the result is different: four of seven state that they store the list data in the EU. The fifth, GetResponse, is an EU company but does not say where the lists are kept.
Seven tools by data location
In the EU according to their own documents: Brevo, Systeme.io, MailerLite and EmailOctopus. Outside the EU: Mailchimp, and ActiveCampaign by default (an EU region can be chosen). Not stated: GetResponse. A transfer outside the EU is lawful, but it needs a transfer basis and a line in your own privacy notice.
Seven services with sources
Every row was read from the provider’s own document, and the source is linked on the same row. Company home country and data location are different things: EmailOctopus is a British company whose lists are in Ireland, and GetResponse an EU company that does not name its data centre.
| Tool | Data in the EU | Contracting party | US sub-processors | Source | Read |
|---|---|---|---|---|---|
| Systeme.io | Yes | ITACWT Limited, Ireland | not stated | Privacy policy | 3 September 2026 |
| EmailOctopus | Yes | Three Hearts Digital Ltd, United Kingdom | not stated | Privacy policy | 3 September 2026 |
| Brevo | Yes | Sendinblue SAS (Brevo), France | Yes | Security page, Sub-processors (terms appendix) | 3 November 2026 |
| MailerLite | Yes | MailerLite Limited, Ireland | No | Privacy policy, Data processing agreement | 25 September 2026 |
| ActiveCampaign | Partly | ActiveCampaign, LLC, United States | Yes | Privacy policy, Data center policy (MRDC) | 25 September 2026 |
| GetResponse | not stated | GetResponse S.A., Poland | not stated | Privacy policy, Data processing agreement | 3 November 2026 |
| Mailchimp | No | Intuit / The Rocket Science Group LLC, United States | Yes | Data processing addendum, Sub-processors | 25 September 2026 |
← scroll →
Read from the provider’s own privacy notice, data processing agreement or sub-processor list, not from a marketing page. “Not stated” means the document does not say — not that the answer is no. Re-read at least every 180 days.
The company’s home country is not the same thing as the data location
This is the most important row in the table and the one most comparisons skip. Two questions are different questions:
- Who do you contract with? That decides which country’s company is the processor of the personal data and which country’s authorities it answers to.
- Where are the servers? That decides whether the data physically moves outside the EU.
In our comparison these differ at two services. EmailOctopus is operated by London-based Three Hearts Digital Ltd, which since Brexit is a non-EU company — but the lists are in AWS’s Irish data centre inside the EEA. MailerLite has a dedicated Irish contracting party for EEA customers, MailerLite Limited, and a separate US company for other customers. So ask both questions, not just one.
What you have to record in your own policy
An email tool is a processor of personal data, and it is recorded in your own privacy policy. If the tool transfers data outside the EU, there is more to record — and the obligation comes straight from the regulation.
Article 13(1)(f) of the GDPR obliges you to tell the data subject three things: that you intend to transfer data to a third country, whether the Commission has adopted an adequacy decision for it, and, if the transfer rests on Article 46 safeguards, a reference to them and to where a copy is available. The original wording requires information on the transfer and “the existence or absence of an adequacy decision by the Commission”.
In practice this is a few lines. The difference between an EU provider and a non-EU one is therefore not that one is prohibited — it is that one requires an entry from you that has to be correct and up to date. The regulation’s general principle points the same way: under Article 44 any transfer to a third country “shall take place only if … the conditions laid down in this Chapter are complied with”, and the level of protection guaranteed by the regulation must not be undermined. Read 14 September 2026.
Those transferring to the United States: what the adequacy decision covers
At two of the tools we compare the data goes to the United States. For them the decisive question is whether the Commission’s adequacy decision covers that specific company — and the answer is not “yes, because the United States”.
Commission Implementing Decision (EU) 2023/1795 was adopted on 10 July 2023, and its Article 1 limits adequacy precisely: the level of protection is adequate for transfers “to organisations in the United States that are included in the ‘Data Privacy Framework List’, maintained and made publicly available by the U.S. Department of Commerce”. Adequacy therefore does not apply to the United States as a country but to the individual organisations that have joined the list.
The list is public at dataprivacyframework.gov. We do not publish individual services’ list status on this page, and the reason is methodological: the status can change in a day, and our 90-day cycle does not guarantee it is current. Check it yourself and use the company’s official name — the service may be listed under its parent company, in which case a search by product name finds nothing. If the company is not on the list, the transfer needs an Article 46 safeguard under the GDPR — in practice the Commission’s standard clauses and the assessment made to support them. Why that is so and what the standard clauses require: Schrems II and moving an email list.
When this matters in practice
Data location is not equally important to everyone, and that is worth saying plainly. Three situations where it decides:
- You answer customers’ data protection questions. A business customer’s procurement questionnaire asks for processors and transfers. Data stored in the EU is a one-line answer; non-EU data requires a transfer basis and its documentation.
- You process sensitive data or public sector data. Then your own organisation or your customer has usually set the policy in advance.
- You want to keep the documentation short. In a one-person business this is the weightiest reason: every entry you do not have to make is an entry you do not have to keep up to date.
If none of these applies to you, data location is one criterion among others — and not a reason to pay for a pricier tool. Prices at the same list size side by side: price calculator.
What this page does not tell you
Three limits, so the reader knows what has been measured here and what has not.
- We have not audited anyone. Everything above was read from the services’ own privacy policies. A policy is the company’s own statement, not third-party verification.
- We do not cover sub-processors. Every service has its own processors, and their chain may reach elsewhere than the main data location. The services’ policies list them, and if your requirement is strict, the chain has to be gone through.
- We do not give legal advice. We say what the sources say and where to find them. Applying them to your own situation is your job or your lawyer’s.
The method in full and what we do not assess: how we compare. Consent, demonstrating it and the processing agreement: email marketing and GDPR.