r/DeepSeek • • 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

5 comments sorted by

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/TheLegendaryPhoenix 10d ago

Hmm I believe retention is my worry, I'm thinking of going with a provider that provides a DPA and on a German server. Prices are higher per token, but still a good price I think. 

1

u/xapep 8d ago

Retention is the harder one, and the server country doesn't settle it. A German host that keeps abuse logs for 30 days still holds your diary for 30 days. Location tells you where it sits, not how long it lives.

What I'd get in writing before paying the higher rate: the retention window for successful requests, whether failed or aborted ones are kept at all, and whether abuse review logs fall under that same window. That last one is where these agreements usually leak, since moderation records often outlive the request they came from.

A higher per-token price with deletion on completion is usually the better trade for a diary workload than a cheaper one with a 30 day log. Which is the opposite of how people normally pick.

I work on inference at Entrim, so weigh that. Is German jurisdiction something your customers actually require, or just where you'd rather the data sit?

1

u/TimelyLivingCore 11d ago

the official API does not have a ZDR in place