
Why 125 lost privacy designations do not mean 125 breaches
A company can keep its own promise not to store a prompt and still have a problem: somebody else runs the model. OpenRouter sits between applications and the companies that answer their requests. On November 22 it said it had removed three providers and taken 125 endpoints off the list eligible for zero-data-retention routing. An endpoint is a route to a model, not a person, a company or a confirmed leak. Some routes came off as a precaution. That distinction matters to a developer choosing between a cheap route and one cleared for sensitive work. Yesterday’s choice may no longer qualify. Disabling a questionable route helps prevent another request from going the same way. It does not by itself tell a developer where last month’s requests went, whether they were retained, or which customers need a call. Novita’s own notice makes the problem concrete. It says some requests for MiniMax models went on to MiniMax’s service instead of being processed on Novita’s infrastructure. That is a different failure from the download Together described. It is not evidence that every forwarded prompt was read or saved. For a customer reviewing an incident, the most useful receipt would identify the actual processor at the time of the request and the retention rule that applied there. A current list of eligible providers answers a different question.





