Skip to content
All articles
Data, privacy and GDPR

DeepSeek writes down where data goes. A regulator wrote the exception.

DeepSeek’s privacy policy names the country where the data goes. Four European and Asian regulators then wrote down what that means, and one of them wrote down the way out.

BastionUpdated 5 min read

DeepSeek’s own privacy policy, last updated 10 February 2026, states: “To provide you with our services, we directly collect, process and store your Personal Data in People’s Republic of China.” The controller named in the policy is Hangzhou DeepSeek Artificial Intelligence Co., Ltd., with a registered address in China.

The European Union has no adequacy decision for China under Chapter V of the GDPR. A transfer still needs a legal basis, and the vendor has to accept that GDPR applies at all.

WhenWhoWhat it found
January 2025Wiz ResearchA DeepSeek database with chat history was reachable with no authentication
January 2025Garante, ItalyOrdered a limit on processing Italian users’ data; the companies said European law does not apply to them
April 2025PIPC, KoreaUser input went to Beijing Volcano Engine until 10 April 2025
June 2025Berlin data protection commissionerReported the app to Apple and Google; the violation named is GDPR Article 46(1)
July 2025NÚKIB, CzechiaA warning at threat level High that excludes open models deployed locally
The five findings, in date order. Each row names who made the finding

January 2025: chat history sat on an open port

Wiz found a ClickHouse database belonging to DeepSeek “hosted at oauth2callback.deepseek.com:9000 and dev.deepseek.com:9000”, reachable with no authentication. It held “chat history, backend data and sensitive information, including log streams, API Secrets, and operational details”, with “over a million lines of log streams”. Wiz disclosed it and DeepSeek “promptly secured the exposure”.

This is an operations failure, not a model failure. The plaintext conversations sat in a place a stranger could read, and no user of the service had any way to know.

January 2025: an EU regulator asked, and was told GDPR does not apply

Italy’s Garante ordered the limitation of processing of Italian users’ data by Hangzhou DeepSeek and Beijing DeepSeek. The two companies, in the Garante’s account, “declared that they do not operate in Italy and that European legislation does not apply to them”. The Garante called that reply “entirely unsatisfactory”.

GDPR Article 28 requires a written contract with a processor that accepts the regulation’s duties. A vendor that tells a supervisory authority the regulation does not bind it cannot be that processor.

April 2025: a regulator found that the prompts themselves left

South Korea’s Personal Information Protection Commission (PIPC) published the results of its status examination on 24 April 2025. It found that “DeepSeek transferred users’ personal data to servers located in China and the U.S.” and that “it failed to obtain separate consent from users regarding cross-border data transfer”.

Specifically, “DeepSeek transferred the details of device information, user networks, applications, and user input to Beijing Volcano Engine Technology Co., Ltd.” The commission recorded that “DeepSeek has blocked the transfer of user input since April 10, 2025”. The company described Volcano as a ByteDance subsidiary, while the commission found it to be an independent corporation.

A bank can put this finding in front of a supervisor: it is a public record, with a date and a named recipient, that the user input itself went to a third company. A claim about what an application could do is not the same thing.

June 2025: a European regulator named the article that applies

Berlin’s data protection commissioner, joined by Baden-Württemberg, Rhineland-Palatinate and Bremen, reported DeepSeek to Apple and Google as illegal content under Article 16 of the Digital Services Act.

The press release states: “The service transfers the personal data collected from users to Chinese data processors and stores it on servers in China.” The commissioner, Meike Kamp, said: “The transfer of user data by DeepSeek to China is unlawful.” The violation named is Article 46(1) of the GDPR.

Romania’s supervisory authority applies the same Chapter V. A champion inside a Romanian bank who is asked “under which article” now has one, from a European regulator, in writing.

July 2025: the Czech regulator excluded open models run locally

The Czech national cyber security agency, NÚKIB, issued a warning about DeepSeek products at threat level High. Its reasoning is about the company, not the mathematics: the risk arises “from the legal and political environment of the People’s Republic of China to which the company DeepSeek is fully subject”.

The warning does not apply to open-source DeepSeek large language models whose source code is publicly accessible and which are “deployed locally, without any capability to communicate with servers used by the company DeepSeek or its related entities”.

What this means for a regulated organisation

  • The Czech warning binds operators of critical information infrastructure, of essential services and of important information systems under the Act on Cybersecurity. A separate Czech government resolution bans the products on state-owned devices. Neither is a rule that binds a private Romanian bank. Do not quote them as law.
  • An open model is not the same thing as a vendor’s service. NÚKIB separates the two explicitly, and the separation is the network path.
  • Cisco tested DeepSeek R1 against fifty prompts from the HarmBench dataset and reported “a 100% attack success rate, meaning it failed to block a single harmful prompt”. That is a safety finding, not a privacy one, and it applies to the weights. Whoever runs an open model owns its guardrails.

With Bastion

What Bastion changes

Bastion is a private AI system delivered as one sealed box that runs inside your building. One monthly fee covers the hardware, the model, the hardened operating system and support, and nothing your team types leaves the building.

The Czech exception describes what Bastion is. The model runs inside the organisation’s own building on a box with no outbound connection, so there is no server to communicate with and no cross-border transfer to justify under Chapter V.

Bastion does not run DeepSeek, and none of this is an argument for it. The model is Qwen3.8-27B, open weights under the Apache 2.0 licence. Qwen is built by Alibaba Cloud, so it is Chinese in origin, and the same rule applies to it: the risk is the network path to a vendor, and a Bastion box has no such path. The box records the repository and the checksum of what it runs, so an auditor sees exactly what answered.

The guardrails are shared between the organisation and Bastion, which is why they are built into the box rather than promised in a policy.

The sentence to give a supervisor is that the processing happens at the organisation’s own address, not at a vendor’s. Three things prove it, and all three stay with the organisation: the exit plan, the annex to the rental contract, and the box’s own record of what it booted.

Questions this article answers

Is DeepSeek safe to run locally?
The Czech agency NÚKIB excluded open DeepSeek models run locally, with no link to DeepSeek’s servers, from its July 2025 warning. The risk it names is the network path to the vendor. Output safety is separate: whoever runs an open model owns its guardrails.
Where does DeepSeek store data?
In China. Its privacy policy, updated 10 February 2026, says it collects, processes and stores personal data in the People’s Republic of China.
Is DeepSeek banned in Europe?
The sources cited here show no EU-wide ban. Italy’s Garante limited the processing of Italian users’ data in January 2025, and Berlin reported the app to Apple and Google under the Digital Services Act in June 2025.

On the record

  1. 1
  2. 2
  3. 3
  4. 4

    Personal Information Protection Commission, Korea

    PIPC decision on DeepSeek, cross-border transfer of user data

    read 2026-09-22

  5. 5

    Berlin Commissioner for Data Protection and Freedom of Information

    Berlin DPA reports DeepSeek to Apple and Google as unlawful content

    read 2026-09-22

  6. 6
  7. 7
  8. 8

    Hugging Face

    Qwen, organisation page

    read 2026-11-17