[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fUyqQeI-N0rng4_ht5hVDPycWHmUlwRUHpZdx4QWTaNk":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":17,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":43,"controls":50},"6b326a15-d4cd-4db2-a57d-591adebbd5ff","third-party-ai-providers-exposed-private-chats-by-ignoring-data-retention-policies","ab8e0cce-fc07-4cab-80d5-def1e3745bd1","Third-Party AI Providers Exposed Private Chats by Ignoring Data Retention Policies","OpenRouter's reliance on third-party AI hosting providers created a supply chain trust failure: some providers either suffered their own compromise or deliberately disregarded Zero Data Retention (ZDR) commitments, logging and forwarding user prompts they were contractually obligated to discard. Critically, researchers found that prompts were copied even before the model processed them, meaning data left the user's control at the infrastructure layer regardless of model-level rejections. This incident illustrates that data protection guarantees are only as strong as the weakest third-party link in the service chain. Users who sent sensitive information — including credentials or API keys — through affected endpoints may now face credential theft or data exposure risks.","**Immediate actions:**\n- Revoke and rotate all API keys and passwords sent through affected OpenRouter endpoints as identified in vendor notifications.\n- Audit logs of requests made through affected providers to determine the scope of potentially exposed data.\n\n**Long-term improvements:**\n- Establish contractual audit rights and periodic technical verification (e.g., canary tokens, honeypot prompts) to confirm third-party data retention compliance.\n- Require third-party AI providers to undergo independent security assessments before being granted Zero Data Retention eligibility.\n- Implement a formal third-party risk management program with ongoing monitoring and clear offboarding procedures when providers are found non-compliant.\n\n**Detection measures:**\n- Deploy automated testing that sends tagged synthetic prompts through providers and monitors for unexpected reappearance or exfiltration.\n- Establish a continuous vendor risk scoring system that flags anomalies in provider behavior or security posture for rapid response.",[12,13,14,15,16],"NIS2 Article 21(2)(d)","ISO\u002FIEC 27001:2022 A.5.19: Information security in supplier relationships","ISO\u002FIEC 27001:2022 A.5.20: Addressing information security within supplier agreements","NIST SP 800-53 SR-6: Supplier Assessments and Reviews","CIS Control 15: Service Provider Management (v8)",{"NIS2 Article 21(2)(d)":18,"CIS Control 15: Service Provider Management (v8)":19,"NIST SP 800-53 SR-6: Supplier Assessments and Reviews":20,"ISO\u002FIEC 27001:2022 A.5.19: Information security in supplier relationships":21,"ISO\u002FIEC 27001:2022 A.5.20: Addressing information security within supplier agreements":22},"This point requires organizations to implement security measures addressing supply chain risks, which would have mandated formal vetting and ongoing assurance of third-party AI hosting providers before granting them access to user data.","This control requires organizations to establish and maintain a process to evaluate and monitor third-party service providers, which would have uncovered the providers' failure to comply with data retention policies before a breach occurred.","This control requires periodic assessments of suppliers to verify they are meeting security requirements, which would have detected providers retaining or forwarding data in violation of their ZDR commitments.","This control requires that information security requirements be agreed with suppliers and that compliance be monitored, which would have included verifying that providers honored Zero Data Retention commitments.","This control requires contractual clauses obligating suppliers to meet security and data handling requirements, including auditable evidence that retention policies are followed.","published","2026-11-22T04:20:21.399231+00:00","2026-11-22T04:20:21.381+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fcybersecuritynews.com\u002Fopenrouter-ai-chat-leaks\u002F","openrouter-users-private-ai-chats-may-have-been-exposed-via-compromised-third-pa-17e522","OpenRouter Users’ Private AI Chats May Have Been Exposed Via Compromised Third-Party Providers",[31,37],{"id":32,"name":33,"slug":34,"description":35,"color":36},"c8b843a5-d5a7-41d1-8d3b-cabded09d2ef","Data Protection","data-protection","Unencrypted data, missing DLP, poor classification","#3b82f6",{"id":38,"name":39,"slug":40,"description":41,"color":42},"f0c2a0af-58aa-4128-87c9-6acd30f2dc48","Supply Chain","supply-chain","Third-party risk, compromised dependencies","#8b5cf6",[44],{"id":45,"date":46,"edition":47,"title":48,"audio_url":49},"43288d5f-06ee-493d-a621-ec9347fca688","2026-11-22","morning","ThreatNoir Weekend Brief — November 22","https:\u002F\u002Fcdn.threatnoir.com\u002Fpodcasts\u002F2026-11-22\u002Fthreatnoir-morning-brief-2026-11-22.mp3",[51,55,59],{"slug":52,"name":53,"problem":54},"data-loss-prevention","Data loss prevention (DLP)","Sensitive data cannot quietly leave by email, upload, USB stick or AI tool.",{"slug":56,"name":57,"problem":58},"encryption-key-management","Encryption and key management","Stolen data stays unreadable, and the keys stay under your control.",{"slug":60,"name":61,"problem":62},"third-party-risk-management","Third-party risk management (TPRM)","You know which suppliers could hurt you, and you hear quickly when one of them is breached."]