DeepSeek GDPR Data Transfer Risk: What Teams Can Use

Image: Unsplash, used under the Unsplash License.

TL;DR: DeepSeek's own privacy policy says it collects, processes and stores personal data in the People's Republic of China, and China is not on the European Commission's adequacy list. The policy names no specific transfer mechanism such as Standard Contractual Clauses. Italy's Garante ordered DeepSeek to stop processing Italian users' data on January 30, 2025, two days after asking it for information, and Berlin's data protection commissioner reported the app to Apple and Google as illegal content on June 27, 2025. Self-hosting the open MIT-licensed weights on your own EU servers avoids the China transfer. Microsoft Foundry lists DeepSeek V4-Flash in its EU Data Zone, which is a third route.

Updated October 22, 2026. We re-checked every claim on this page against the primary sources again; all still hold, and we added the US federal order on DeepSeek that DHS published on October 20. An October 8 review had corrected the rest: Italy's order was in January 2025, not early 2026; we found no source for "investigations in 13 jurisdictions" or for Apple and Google rejecting the Berlin notice, so both are removed; Baidu does publish open ERNIE 4.5 weights on Hugging Face; and we could confirm DeepSeek V4 in an EU region only on Microsoft Foundry, not on AWS Bedrock or Google Vertex AI. DeepSeek also released V4.1-Flash on September 10, 2026.

The short answer by use case

Why hosted DeepSeek fails the GDPR transfer test

GDPR Chapter V allows a transfer of personal data outside the EU in three main ways.

1. An adequacy decision. The European Commission "has so far recognised" Andorra, Argentina, Brazil, Canada (commercial organisations), the Faroe Islands, Guernsey, Israel, the Isle of Man, Japan, Jersey, New Zealand, the Republic of Korea, Switzerland, the United Kingdom, the United States (for Data Privacy Framework participants), Uruguay, and the European Patent Organisation. China is not on the list.
2. Appropriate safeguards under Article 46. These include binding corporate rules under Article 47, standard data protection clauses adopted by the Commission, and an approved code of conduct "together with binding and enforceable commitments" of the importer.
3. Narrow derogations for specific situations, which do not fit routine business use of a chatbot.

DeepSeek's privacy policy, last updated February 10, 2026, says: "we directly collect, process and store your Personal Data in People's Republic of China." On transfers it says only: "Where required, we will use appropriate safeguards for transferring Personal Data outside of certain countries." It does not name Standard Contractual Clauses or any other Article 46 tool. The controller is Hangzhou DeepSeek Artificial Intelligence Co., Ltd., and the policy names Prighter Group as its privacy representative for the EU and the UK.

A named EU representative is not a transfer mechanism. Until DeepSeek can show you an Article 46 safeguard for your data, assume sending EU personal data to the hosted service is an unlawful transfer.

What regulators have done

Image: Pexels, used under the Pexels License.

In Italy, the Garante said the companies had told it they "do not operate in Italy" and that European law does not apply to them. In Berlin, commissioner Meike Kamp said DeepSeek could not show that German users' data is protected in China at a level equal to the EU, and that a fine could not be enforced against a company in a third country. The Berlin notice asks Apple and Google to review the app; we found no published decision by either company.

The open-weight route: self-host on your own EU servers

DeepSeek publishes model weights on Hugging Face under the MIT license. The V4 model card describes "a preview version" of two Mixture-of-Experts models: DeepSeek-V4-Pro with 1.6T parameters (49B activated) and DeepSeek-V4-Flash with 284B parameters (13B activated), "both supporting a context length of one million tokens."

Image: Pexels, used under the Pexels License.

If you run the weights on servers you control in the EU, prompts never reach DeepSeek, so there is no transfer to China. You are still the controller: you need a legal basis, security measures, retention rules, and a DPIA where the processing is high risk. Those are the same duties you have for any self-hosted software.

Size is the practical limit. Even V4-Flash has 284 billion parameters, so this is a data-center deployment, not a laptop one.

The same test applies to other Chinese labs. Alibaba's Qwen team and Baidu both publish open weights on Hugging Face (Baidu's include ERNIE 4.5 models). Self-hosting those weights in the EU avoids the transfer; using a hosted service run from China does not.

The cloud route: Microsoft Foundry's EU Data Zone

Microsoft announced DeepSeek V4 Flash and V4 Pro in Microsoft Foundry on April 30, 2026. For Data Zone deployments, Microsoft "processes prompts and responses anywhere within the specified data zone," and the European Union is one of the zones. On October 8, 2026, Microsoft's region table listed DeepSeek-V4-Flash under Data Zone Standard in the EU zone (France Central, Germany West Central, Italy North, Poland Central, Spain Central, Sweden Central, West Europe). DeepSeek-V4-Pro was listed only in the US data zone.

This route sends data to Microsoft under Microsoft's terms, not to DeepSeek. Your transfer analysis becomes the one you already do for Azure. We could not confirm DeepSeek V4 in an EU region on AWS Bedrock or Google Vertex AI, so we do not list them here. Check the model catalog for your region before you plan around either.

Model versions move fast. DeepSeek released V4.1-Flash on September 10, 2026 and retired the earlier V4 Flash models on its own API. Confirm the exact model and deployment type in your contract and DPIA.

Image: Pexels, used under the Pexels License.

What to do now

Find shadow use. Ask each team which AI tools they use, including phone apps. The hosted DeepSeek app and website are where EU personal data is most likely to leak.

Block hosted DeepSeek for EU personal data. Write it into your AI acceptable use policy by name, and include other China-hosted chat services.

If you want DeepSeek's models, pick one of two routes: self-host the open weights in the EU, or use an EU Data Zone deployment on a cloud provider you have already assessed. Record the route, the model version, and the region.

Add two questions to vendor due diligence: "Where is data stored and processed?" and "Which Article 46 mechanism covers EU data?" A vendor that cannot answer both fails. The AI vendor due diligence checklist has the full list.

US-only data: GDPR transfer rules do not apply, but your contracts, sector rules, and state privacy laws still do. Read the vendor's terms before you send customer data.

What practitioners say

A June 2025 r/gdpr thread, "What are DeepSeek's privacy practices?", got a short answer from one commenter: "I would immediately assume none and avoid their own hosted version provided via their website and app." That is the same line this page draws: the hosted service is the problem, not the model.

Our take

Based on DeepSeek's own policy and the regulator actions cited here, the problem with hosted DeepSeek is not the model. It is that the data goes to China under a policy that names no transfer safeguard. The open weights and the EU Data Zone route remove that problem, which is why "Can we use DeepSeek?" is the wrong question. Ask instead where the prompts are processed.

Frequently asked questions

Does DeepSeek store my prompts in China? DeepSeek's privacy policy says it directly collects, processes and stores personal data in the People's Republic of China. For EU personal data, treat anything sent to the hosted service as transferred to China.

Can I use hosted DeepSeek for data with no EU individuals in it? GDPR transfer rules apply to personal data. If no personal data of people in the EU is involved, they do not apply. Confidential business data is a separate question for your own risk policy.

Are the open weights the same model as the hosted service? DeepSeek publishes V4-Pro and V4-Flash weights on Hugging Face. Hosted versions on DeepSeek's API change over time (V4.1-Flash replaced V4 Flash on the API in September 2026), so confirm which version you are comparing.

How we checked this

On October 22, 2026 we re-read DeepSeek's privacy policy (still dated February 10, 2026), its API change log, and its V4 model card on Hugging Face; the Hugging Face listings of Qwen and Baidu (ERNIE 4.5); the European Commission adequacy page; GDPR Articles 46 and 49 on EUR-Lex; the Garante's January 28 and 30, 2025 releases; Australia's PSPF Direction 001-2025 page; the EDPB's February 12, 2025 release; Microsoft's Foundry announcement and region table (V4-Flash still the only DeepSeek model in the EU Data Zone); netzpolitik.org's June 27, 2025 report; the r/gdpr thread; and the DHS notice and order in Federal Register document 2026-21447. For the US order's effect on contractors, see our DeepSeek federal ban post.

Last reviewed: October 22, 2026.

Related Reading

• DeepSeek federal ban: what government contractors check now
• Treasury's first outbound investment fine: $200K against Amidi for a China AI deal
• ICO agentic AI call for evidence: what 10 AI developers changed
• Privacy-first AI APIs with no training on your data
• AI vendor due diligence checklist 2026
• AI data privacy for small teams
• Vetting AI tools: security and compliance checks
• Anthropic vs OpenAI: GDPR compliance comparison
• CNIL's Agentic AI Note: Three GDPR Risks Your Team Needs to Address
• China's Moonshot Accused of AI IP Theft. Treasury Threatens Sanctions.