37 points sdko 1 hour ago 11 comments

redrix 1 hour ago | parent

Nice to see this move by OR.

That being said, the best ZDR agreement is the one that your company has directly with the inference provider(s). Unfortunately:

- Not everyone is large enough (or has enough $$) for that. - Ultimately you’re in the same position of having to “trust” that they’re doing ZDR; even after auditing their security docs.

rkagerer 1 hour ago | parent

I'd say that's the second-best one. The most robust ZDR policy is running your own AI locally and enforcing the retention policy yourself.

az226 53 minutes ago | parent

This right here.

ZDR is a marketing ploy. It’s not real. Only naive people believe it’s real.

Havoc 1 hour ago | parent

Solid move.

Though frankly I would think anyone even slightly bothered about ZDR does not start their train of thought with "OK so we're going to put a middle man in"

solarkraft 55 minutes ago | parent

With this change, everything is good in the world and we can just take everyone’s word that they’re actually ZDR without any audits or technical enforcement again. Right?

veeragoni 53 minutes ago | parent

I would redact PII before it leaves your machine. works with Openrouter and bunch of other providers. apart from being a meeting assistant, note taking etc. https://heychap.net/

the_lucifer 50 minutes ago | parent

Is there any information on the three companies that violated ZDR? I could only find mention of one of those affected providers in the original article (that OR links in their post): Lark. Trying to figure out if I ended up routing to one of their "ZDR" endpoints.

I don't understand why these names are being coyly tiptoed around especially given the impact to workflows. Why isn't OR calling out the actual providers they off-boarded by name?

fedpost 23 minutes ago | parent

Given how trust based the LLM world has to be right now, there should be zero tolerance for anyone doing stupid shit like this

SwellJoe 16 minutes ago | parent

They state they notified customers who used any of the problem models via email (I got an email about it), which answers your question of whether you ended up routing to one of those endpoints. They apparently know who was routed to all those providers, so you don't have to guess.

That still leaves the desire of people to make informed decisions about what providers to use unresolved. If reputation is the only thing we have to go on when choosing a provider to send a bunch of sensitive data to, it'd be nice if the folks who actually know whether a provider is trustworthy would share that info.

But, since the email they sent identified the provider and the model (MiniMax, in my case) and the dates of use, it seems like it won't be secret for long what the other problem providers are. I'll assume the email to users of other providers will also include those details, so people can post about it even if OpenRouter is cagey about it in their blog post.

mbgerring 12 minutes ago | parent

You should assume that no inference provider is honoring any public commitment they have made about data retention. You should assume that 100% of what you share with an LLM over the wire is being recorded, saved, and used as training data. Any other stance is indefensible naïveté for anyone who has been around the tech industry for more than, let’s say, 5 years.