The key insight: the risk lives in the API, not the model weights. Use a Chinese hosted API and your data falls under Chinese jurisdiction. Self-host the open weights on your own infrastructure and that risk essentially disappears. The cheapest option is also the most complex to deploy safely.
Risk 1 — Data sovereignty (the critical one)
DeepSeek stores data in China, subject to Chinese cybersecurity and national-security laws that can compel sharing with the government — its own privacy policy notes data is stored in China and processed under applicable laws. This has triggered formal action worldwide:
| Jurisdiction | Action |
|---|---|
| Italy | First to ban DeepSeek, citing GDPR violations |
| Netherlands | Warned users |
| Ireland, Belgium | Opened formal investigations |
| Australia | Banned on government devices |
| South Korea | Found data transferred without consent |
| Taiwan | Blocked access |
| US (NASA, Navy, Congress) | Staff warned against use |
Risk 2 — Content censorship built in
Users report DeepSeek censors or refuses content critical of the Chinese government. On politically sensitive topics (Taiwan, Tiananmen, Xinjiang, Tibet) outputs may be incomplete or refused. For most business tasks this is irrelevant — for research, journalism, policy or geopolitics work, it absolutely is not.
Risk 3 — and the mitigation nobody mentions
Because the weights are open, self-hosting changes everything. Running the model on your own infrastructure:
- Eliminates data transit through Chinese jurisdiction
- Removes dependency on Chinese-controlled infrastructure
- Gives you full control over audit logs, model versioning and data residency
For HIPAA, GDPR and financial-services compliance, self-hosting is the path that makes Chinese models viable. The trade-off is complexity and infrastructure cost — see self-host vs API.
The decision
| Your situation | Verdict |
|---|---|
| Non-sensitive, internal, low-stakes | Hosted API is usually acceptable |
| Regulated / personal / confidential data | Self-host only, or avoid |
| Politically sensitive content work | Avoid — censorship affects output |
| Want the savings, have infrastructure | Self-host open weights |
Check where every model's data goes in the data sovereignty comparison, and run the privacy checklist before signing up to anything.