OpenRouter off-boards three providers over data policy failures

OpenRouter off-boards three providers over data policy failures

OpenRouter, the routing layer that sits between customers and a large ecosystem of AI models and inference providers, has published a post about data processing incidents at some of those providers. Earlier this week, it says, security researchers reported that certain inference providers had data compromised or otherwise showed evidence that their data policies were not being upheld. OpenRouter says it has worked closely with the researchers and with the providers to understand the findings and to encourage the providers to address them.

OpenRouter is explicit that the findings did not show any breach or unauthorized access of OpenRouter itself. The testing, it says, revealed new findings about specific inference providers.

The company lists three actions already taken. It off-boarded three providers from OpenRouter, based on the results of its investigations. It removed 125 endpoints from Zero Data Retention (ZDR) eligibility; those removals covered providers flagged by the researchers plus additional endpoints removed as a precaution. And it notified all potentially affected customers.

Three pieces of work are described as underway. OpenRouter is adapting the researchers' testing approach so it can run the same checks on an ongoing basis. It is conducting technical verification of network paths to identify instances where requests and responses may be being forwarded to third parties. And it is requiring appropriate assurances and validation before restoring ZDR eligibility to any endpoint removed in this review.

OpenRouter says it is grateful for the Dragos report. As it builds similar testing techniques into its own platform, it says it will keep raising the bar, and providers that want to be on OpenRouter will need to meet it.

The post also carries a live list of security announcements received from providers. Novita published "Privacy notice regarding MiniMax requests on Novita". Phala published "November preliminary incident report". Together published "Security event: prompt leakage for requests in June and July of 2026". OpenRouter adds that not all affected providers have posted publicly; it has notified affected users whether or not a public post exists, is encouraging all providers to write incident reports, and will keep the list updated.

Key facts

  • OpenRouter says security researchers reported earlier this week that certain inference providers had data compromised or showed evidence their data policies were not being upheld.
  • OpenRouter off-boarded three providers and removed 125 endpoints from Zero Data Retention (ZDR) eligibility, including some endpoints removed only as a precaution.
  • OpenRouter states that the findings did not show any breach or unauthorized access of OpenRouter itself, and says it notified all potentially affected customers.
  • Ongoing work: adapting the researchers' testing for continuous checks, verifying network paths where requests may be forwarded to third parties, and requiring validation before any ZDR eligibility is restored.
  • Providers' own announcements are linked: Novita (MiniMax requests), Phala (November preliminary incident report) and Together (prompt leakage in June and July of 2026).

Why it matters

Zero Data Retention is a promise that prompts and responses are not kept by the provider. This post says that promise was not being upheld at some providers reached through OpenRouter, enough for OpenRouter to drop three of them and pull 125 endpoints from ZDR eligibility. The provider announcements it links point to specific problems: MiniMax requests on Novita, and prompt leakage for requests in June and July of 2026 at Together. For anyone routing sensitive prompts through an aggregator, the story shows that a data policy label depends on the downstream provider actually following it.

Who it affects

Customers of OpenRouter who sent requests to the affected providers, and especially those who relied on ZDR eligibility, are the group most directly involved. OpenRouter says it notified all potentially affected customers, and notified affected users whether or not a provider posted publicly. Inference providers that want to stay on the platform are also affected: OpenRouter says they will need to meet a higher bar as it integrates similar testing techniques.

How to use it

If you route requests through OpenRouter, watch for the notice OpenRouter says it sent to potentially affected customers. The post carries a live list of provider security announcements (Novita, Phala, Together so far) that OpenRouter says it will keep updated, so it is the place to check for new write-ups. Endpoints removed in this review will not regain ZDR eligibility until OpenRouter has appropriate assurances and validation, so check which endpoints your ZDR-dependent traffic actually uses.

How solid is it

This is OpenRouter's own first-party post, so the actions and counts (three providers, 125 endpoints) come straight from the company and are not independently confirmed here. The post does not name the three off-boarded providers. It does not say which providers the 125 endpoints belong to, or how many were removed as a precaution versus flagged by researchers. It mentions only "the Dragos report" and does not name the researchers outright, and it gives no absolute date, only "earlier this week". It does not describe the mechanism of the compromise beyond the titles of the provider announcements.

Risks and caveats

OpenRouter says it is verifying network paths to find instances where requests and responses "may be being forwarded to third parties"; that is work in progress, and the post does not confirm that forwarding actually occurred. Not all affected providers have posted publicly, so the linked list may be incomplete. The post does not say how many customers were affected or what data was exposed, and it gives no timescale for the ongoing work or for restoring ZDR eligibility.

“These findings did not show any breach or unauthorized access of OpenRouter.”

— OpenRouter, "Data Processing Incidents on Inference Providers"