AI and security
AI models hosted in Europe: what that tells you
This article was created with AI.
A guide by sicherAI. We offer an AI service for Heilpraktiker practices. How we write these guides
In short
“Hosted in Europe” means that an AI service uses servers somewhere in Europe; it does not say whether that covers storage, the model’s processing or both, or who can access the data. Under the General Data Protection Regulation (GDPR), the dividing line is the European Economic Area (EEA), not Europe: Switzerland and the United Kingdom are third countries with adequacy decisions. According to the European Data Protection Board, access by a company in a third country, for example for support, counts as a transfer even when the servers are in the EEA. No location replaces a data processing agreement or a legal basis for the processing.
Contents
What does “hosted in Europe” tell you?
“Hosted in Europe” tells you that an AI service uses servers somewhere in Europe – but not which part of the service runs there or who can access the data.
Three locations are worth keeping apart:
- Storage: where chats, files and logs are kept.
- Processing: where the model computes its answers, a step called inference.
- The provider: where the contracting company and its sub-processors – the companies it uses to deliver the service – are based.
The phrase is not a legal test: the General Data Protection Regulation (GDPR) asks whether data is transferred to a third country, not whether it stays in Europe.
This guide is written for Heilpraktiker in Germany. A Heilpraktiker is a non-medical practitioner who holds a permit under the Heilpraktikergesetz, the German law on non-medical practitioners, to practise medicine without a medical licence. The GDPR is an EU regulation that applies directly in Germany.
Fictional example: A Heilpraktiker in Munich reads that an AI writing tool keeps all data in Germany. When she asks, she learns that chats stay in Frankfurt, but requests may be processed elsewhere in Europe and, at peak times, in the United States.
Is data stored where the model runs?
Data can be stored in one place and processed by the model in another.
Both steps involve personal data if a request concerns an identifiable client (Article 4(1) GDPR).
Data residency means that a provider stores customer data in a region the customer selects.
Data residency for storage does not always cover processing. A provider can offer storage in one region and still process requests outside it, so ask about each step separately.
A region named “Europe” can be wider than the European Economic Area (EEA), for example if it includes Switzerland, a third country with an adequacy decision.
Logs kept for abuse monitoring are a further location to ask about, because they can contain prompts and responses.
When does a transfer to a third country take place?
A transfer takes place when personal data is sent to, or made available to, a separate organisation in a third country – a country outside the European Economic Area (EEA).
The EEA consists of 30 countries: the 27 EU member states plus Iceland, Liechtenstein and Norway. The GDPR applies in these three through the EEA Agreement. Chapter V of the GDPR allows transfers only under the conditions in Articles 44 to 49.
The GDPR does not define “transfer”. The European Data Protection Board (EDPB), an EU body that brings together the national data protection authorities, uses three conditions that must all be met (Guidelines 05/2021, page 7):
- The sender is subject to the GDPR for the processing.
- It sends the data to another organisation acting as controller or processor, or otherwise makes it available.
- That recipient is in a third country, whether or not it is itself subject to the GDPR.
A practice is the controller: it decides why and how personal data is processed (Article 4(7) GDPR). A provider that processes the data on its behalf is a processor (Article 4(8)).
Important: According to the EDPB, remote access from a third country is a transfer if the three conditions are met. This applies “even if it takes place only by means of displaying personal data on a screen” (page 8).
Which countries count as third countries?
Every country outside the European Economic Area (EEA) is a third country, but the conditions for a transfer depend on whether the European Commission has adopted an adequacy decision for it.
Such a decision states that the country ensures an adequate level of protection (Article 45 GDPR).
| Where the recipient is | What Chapter V requires | Examples |
|---|---|---|
| Within the EEA | No third-country transfer | A provider in Ireland with servers in Norway |
| Third country with an adequacy decision | Transfer without specific authorisation (Article 45) | Switzerland; the United Kingdom; in the United States, only organisations on the Data Privacy Framework List |
| Any other recipient in a third country | Appropriate safeguards under Article 46, such as standard data protection clauses adopted by the Commission, with enforceable rights and effective legal remedies; in specific situations, an exception under Article 49 | A US company that is not on the Data Privacy Framework List |
For Article 46 safeguards, the European Data Protection Board states that it must be assessed whether protection is essentially equivalent to that in the EEA, or whether supplementary measures are needed (Guidelines 05/2021, page 6).
The decisions in the table, as of 6 November 2026:
- United Kingdom: Implementing Decision (EU) 2021/1772, renewed in December 2025. It expires on 27 December 2031 unless extended (Implementing Decision (EU) 2025/2574, Article 2).
- Switzerland: Decision 2000/518/EC of 26 July 2000, which remains in force under Article 45(9) GDPR.
- United States: Implementing Decision (EU) 2023/1795 of 10 July 2023; the US Department of Commerce maintains the Data Privacy Framework List.
What changes if the provider sits outside the EEA?
If a provider in a third country accesses data stored in the European Economic Area (EEA), that access is a transfer – even though the servers are in the EEA.
The European Data Protection Board (EDPB) gives the example of a company in a third country that, as processor for companies in the European Union, accesses such data for support purposes (Guidelines 05/2021, Example 11).
The position differs for a provider established in the European Union whose parent company is in a third country. If all processing takes place in the European Union and no one outside has access, the parent company included, using it is not a transfer (Example 12).
If the law of a third country also applies to such a provider, authorities there may request data from it, and handing data over would be a transfer. The EDPB says a controller, such as a practice, should assess this before engaging the provider (Article 28 GDPR).
What should you ask an AI provider about locations?
Ask the provider for written answers that name a country, not a continent, for each location.
- Which company is our contracting party, and where is it registered?
- In which countries are chats, files and logs stored, and for how long?
- In which countries does the model process requests, and can that change?
- Can anyone in a third country access the data?
- Which basis under Chapter V of the GDPR covers each transfer outside the European Economic Area (EEA)?
- Are chats kept in logs for abuse monitoring, in which country, for how long, and who can review them?
A practice can check one tool in four steps:
- Find the provider’s data processing agreement and its list of sub-processors, or ask for them.
- Note each company on the list with its task and country, mark countries outside the EEA and note the basis the provider names.
- Enter each transfer to a third country in the practice’s record of processing activities (Article 30(1)(e) GDPR). As of 6 November 2026, practices processing data concerning health must keep this record whatever their size (Article 30(5)); a pending amendment (procedure 2025/0130(COD)) may change this.
- Repeat the check whenever the provider announces a new sub-processor (Article 28(2) GDPR).
As of 6 November 2026: the list of sub-processors of Mistral AI, a company based in Paris, has 25 entries. Of these, 13 name only places in the EEA, 8 also or only the United States and 3 “Worldwide”; one names no place. Ask the provider which entries apply to your product.
We are based in Switzerland, a third country with an adequacy decision.
What does the server location not decide?
Even if an AI service stores and processes all data within the European Economic Area (EEA), the rest of the GDPR applies in full. According to the European Data Protection Board (Guidelines 05/2021, page 3), the controller – here, the practice – “remains fully accountable for its processing activities, regardless of where they take place”.
The location says nothing about how long the provider keeps chats and logs, or whether it uses them to train models. Nor does it replace a contract under Article 28(3) GDPR with a provider that processes personal data on the practice’s behalf. A legal basis under Article 6 is needed as well and, for data concerning health, an exception under Article 9(2).
Frequently asked questions
Are servers in Germany or elsewhere in Europe enough for the GDPR?
Not on their own: whatever the location, a practice still needs a contract under Article 28 GDPR with every provider that processes personal data on its behalf, a legal basis for the processing and appropriate security measures (Article 32). For the transfer rules in Chapter V of the GDPR, servers in Germany count the same as servers in Ireland or any other country in the European Economic Area (EEA). Servers elsewhere in Europe can be in a third country, such as Switzerland or the United Kingdom.
Do Switzerland and the United Kingdom count as third countries?
Yes: both lie in Europe but outside the EEA, so the GDPR treats them as third countries. Each has an adequacy decision from the European Commission, which means, in the words of the Commission’s page on adequacy decisions, that transfers there are “assimilated to intra-EU transmissions of data”. Adequacy decisions are not permanent: the Commission monitors them and can amend, suspend or repeal them (Article 45 GDPR).
What does the EU-US Data Privacy Framework cover?
It is the arrangement on which the European Commission based its adequacy decision for the United States of 10 July 2023, Implementing Decision (EU) 2023/1795. The decision covers only organisations on the Data Privacy Framework List. When you look a provider up on the list, use the name of the company that receives the data; it can differ from the name of the AI tool. A transfer to a US company that is not on the list needs another basis, such as standard data protection clauses under Article 46 GDPR.
Do clients have to be told about transfers to a third country?
When a practice collects personal data from a client, Article 13(1)(f) GDPR requires it to state, where applicable, that it intends to transfer personal data to a third country and whether an adequacy decision exists. For transfers based on safeguards under Article 46, the information must refer to those safeguards and explain how to obtain a copy or where they are available.
How can I find out where ChatGPT or another chatbot stores data?
Read the documents for the exact product and plan you use: the privacy notice, any data processing agreement and the list of sub-processors. Options can differ between products and plans of the same provider. If the documents name only a continent, ask the provider for the countries.
Sources
- Publications Office of the European Union (EUR-Lex): Regulation (EU) 2016/679 (General Data Protection Regulation), in particular Articles 4, 6, 9, 13, 28, 30, 32, 44 to 49, 68 and 99 (eur-lex.europa.eu), accessed
- European Data Protection Board: Guidelines 05/2021 on the Interplay between the application of Article 3 and the provisions on international transfers as per Chapter V of the GDPR, version 2.0 (www.edpb.europa.eu), accessed
- European Commission: Adequacy decisions (commission.europa.eu), accessed
- Publications Office of the European Union (EUR-Lex): Commission Implementing Decision (EU) 2023/1795 of 10 July 2023 on the adequate level of protection of personal data under the EU-US Data Privacy Framework (OJ L 231, 20.9.2023, p. 118) (eur-lex.europa.eu), accessed
- Publications Office of the European Union (EUR-Lex): Commission Implementing Decision (EU) 2021/1772 of 28 June 2021 on the adequate protection of personal data by the United Kingdom (OJ L 360, 11.10.2021, p. 1) (eur-lex.europa.eu), accessed
- Publications Office of the European Union (EUR-Lex): Commission Implementing Decision (EU) 2025/2574 of 19 December 2025 amending Implementing Decision (EU) 2021/1772 on the adequate protection of personal data by the United Kingdom (OJ L, 2025/2574, 23.12.2025) (eur-lex.europa.eu), accessed
- Publications Office of the European Union (EUR-Lex): Commission Decision 2000/518/EC of 26 July 2000 on the adequate protection of personal data provided in Switzerland (OJ L 215, 25.8.2000, p. 1) (eur-lex.europa.eu), accessed
- Publications Office of the European Union (EUR-Lex): Decision of the EEA Joint Committee No 154/2018 of 6 July 2018 (incorporation of the GDPR into the EEA Agreement) (OJ L 183, 19.7.2018, p. 23) (eur-lex.europa.eu), accessed
- Federal Ministry of Justice and Consumer Protection and Federal Office of Justice (gesetze-im-internet.de): Gesetz über die berufsmäßige Ausübung der Heilkunde ohne Bestallung (Heilpraktikergesetz), § 1 (www.gesetze-im-internet.de), accessed
- European Free Trade Association (EFTA), copy: Internet Archive: EEA & Relations with the EU (archived copy of 2 November 2026) (web.archive.org), accessed
- European Union: EU countries (european-union.europa.eu), accessed
- OpenAI: Data controls in the OpenAI platform (developers.openai.com), accessed
- Mistral AI: Mistral AI Trust Center (trust.mistral.ai), accessed
- Mistral AI: Privacy Policy (legal.mistral.ai), accessed
- BayernPortal (Free State of Bavaria): Heilpraktiker license; application (www.bayernportal.de), accessed
- European Parliament, Legislative Observatory: Procedure file 2025/0130(COD): Omnibus IV (small mid-cap enterprises) (oeil.europarl.europa.eu), accessed
ChatGPT is a trademark of OpenAI.
About this guide
- Publisher
- sicherAI (see imprint)
- Our interest
- We offer an AI service for Heilpraktiker practices and use models from several makers, including some named in our guides. The guide contains no rankings. Statements about other providers rest on the sources listed.
- How it was made
- This article was created with AI.
- Sources as of
- Legal position as of
- Limits
- This guide provides general information. It is not legal advice for your individual case.
- Report an error
- Contact us using the details in our imprint.