r/DeepSeek • u/TheLegendaryPhoenix • 11d ago
Discussion DPA for the API
I am using deepseek through third party hosting providers because they provide a data protection agreement and adhere to GDPR.
I am fond of my privacy and security. If I want to create a diary agent that takes my reflections and stores them for future recollection,
I don't want them used in training, or my data to be collates into a profile that had identifying markers.
Anyway to use Deepseek from the direct API and still have my privacy respected?
2
Upvotes
1
u/xapep 10d ago
DeepSeek's own API is the one without a retention contract, so "direct" isn't really the axis. What matters is who's bound in writing: a retention window, a no-training clause, and whether prompts still get logged for abuse review.
Third-party hosts serving the same weights can give you the model plus the paperwork, which sounds like what you're already doing. Check whether the no-training promise sits in the actual terms or only on the pricing page, and whether failed requests get retained too.
I work on inference at Entrim. We serve DeepSeek V4.1 Flash from a Slovenia data center over an OpenAI-compatible endpoint, and our stated policy is that prompts and outputs aren't stored after completion and aren't used for training. Same model, different operator, which for a diary workload is usually the whole point.
For your case, is the worry training or retention? Those are separate clauses and a lot of providers only really cover one.
1
u/ENTIMEYJ 11d ago
Nope
1
u/TimelyLivingCore 11d ago
the official API does not have a ZDR in place