Search the evidence

Find the signal.

Search titles, impact clusters, countries, organizations and the full text of every analysis.

6 stories found

A folded yellow canary rises from an open archive drawer, trailing a coral ribbon.
PrivacyGlobal+1 clusters01

The prompt leak that five decoys helped expose

Five of the credentials an outsider tried were decoys. They belonged to a Dragos security experiment, not to five customers whose accounts had been emptied. Even so, something had happened that a customer reading an AI service’s settings could not have seen: somebody outside the service had obtained stored examples of what people had sent it. In its November 21 notice, Together AI says the samples came from a subset of June and July requests to three models on its serverless service. The company says it had permission to keep samples for testing. A coding agent exposed a credential; the company detected the exposure, but not before an unauthorized party used it to download the collection. Permission to test the software was not permission for that party to read the samples. The useful distinction is between the customer conversation and the copy engineers keep to check their work. A team can secure the first and still mishandle the second. Together says it has changed how development credentials are scoped and made zero retention the default for new accounts. Customers with existing accounts should check their own settings rather than assume the new default applies. The company was still reviewing what the samples contained. Neither it nor the independent canary experiment supplies a count of people whose personal information was exposed.

3 min
Three folded paper routes converge at a switch beneath jade tunnels.
PrivacyGlobal+1 clusters02

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.

3 min
Painted letters moving through a transparent conduit between rooms, representing a conversation crossing a vendor boundary.
PrivacyGlobal+1 clusters03

Your AI chat has a supply chain. So does its leak.

The name on an AI app is not necessarily the only company handling a conversation. Notion's incident notice makes that invisible supply chain unusually tangible. Notion says a Fireworks AI incident affected chat transcripts used for its Insights feature in fewer than 1% of workspaces. Its updated account records disconnection on November 3, deletion of its data at Fireworks on November 4, and notification of affected customers on November 9. A November 13 update says exposed third-party API keys found in messages were reported to their issuers the previous day. Notion had already revoked exposed keys of its own. Most affected transcripts lacked author or workspace labels, according to Notion. That does not mean the words inside a conversation could not identify someone. A password, company name or access token can be sensitive without a separate identity field attached. There is an important boundary. Fireworks says its investigation has not detected impact to its default zero-data-retention Inference, Training SDK and Nexus services. The companies' disclosures do not establish that every AI chat, or every such retention arrangement, is compromised. For affected users, Notion recommends reviewing the supplied incident information and rotating credentials placed in the exposed conversations. For buyers more broadly, the question is architectural: which features send data to which vendors, why is it retained, and how quickly can downstream exposure be contained? Removing an integration can stop new traffic. It does not automatically neutralize a credential already copied elsewhere. Privacy promises need a map of those dependencies, not just a reassuring app interface.

3 min
A luminous AI model is stopped outside a transparent corporate data vault as retention alarms seal sensitive code and security files inside.
PrivacyUnited States+3 clusters04

Companies begin walling off sensitive work from frontier AI models

Large technology and government-services companies are reportedly limiting frontier AI models over concerns about intellectual property and data handling. Reuters, citing The Information, says Palantir pressed Anthropic for an irrevocable zero-data-retention guarantee before offering its models through Palantir’s software. Nvidia reportedly restricts Anthropic models to less sensitive tasks and uses its own systems for internal work, while Booz Allen reportedly barred employees from using Anthropic’s commercial model for proprietary cybersecurity activity. The report says Anthropic faced customer resistance after a policy change allowed thirty-day retention of usage logs to investigate complex attacks, and that OpenAI faced scrutiny over a claim that user data may have helped solve a mathematics problem. Neither that claim nor the reported company restrictions were independently confirmed by the named firms in Reuters’ account; the companies did not immediately respond to requests for comment. Both laboratories say they do not train on business customer data by default unless customers opt in, though anonymized metadata may still be collected. The consequence is larger than one vendor dispute. For sensitive organizations, model quality is inseparable from data architecture, retention, legal guarantees, isolation, and auditability. If a frontier model cannot cross the trust boundary, enterprises may fragment deployment across private environments, smaller models, and vendor-specific systems, trading some capability for control.

7 min
A declassified dossier collage shows source code entering an anonymous black server while the provider name and data destination are covered by redaction bars.
PrivacyGlobal+4 clusters05

Anonymous coding model sends enterprise code to a provider users cannot identify

SiliconANGLE reports that a frontier-class coding model called Ox Alpha appeared on OpenRouter and OpenCode with free or near-unlimited access while no company admitted to building it. The model offers a context window above one million tokens and is marketed for sustained software-engineering work. Early attention focused on a ten-task benchmark result above 80 percent, but a later full-set run placed it roughly level with an established competitor and no public leaderboard had confirmed the score. Infrastructure fingerprinting matched six of nine probes with GLM-5.3, yet the researcher explicitly warned that shared infrastructure does not prove model identity. The unresolved issue is data custody. OpenRouter’s listing says the provider retains prompts and completions, while OpenCode advertises zero retention from an unnamed provider. With coding tools reportedly sending billions of tokens through the model, users cannot verify the operator, jurisdiction, retention promise, or incident contact behind the route. A free model is not free if the price is untraceable code exposure.

5 min
A qualified applicant enters a transparent hiring scanner while a sealed black scoring box rejects her and duplicate candidate silhouettes wait behind it.
Work & marketsUnited States+4 clusters06

AI hiring black boxes move discrimination from suspicion to litigation

The Guardian reports a growing set of lawsuits challenging AI used in hiring, layoffs, and other employment decisions. One class action alleges that Eightfold AI assembled an undisclosed dossier from résumés, profiles, and other data, then scored applicants without giving them access to the result or a practical way to challenge it. Eightfold denies the claims. Separate cases involving Meta and IBM include allegations about leave and age; the companies have denied or disputed the allegations reported. The broader impact does not depend on any one lawsuit succeeding. An automated score can determine who receives human attention while the applicant never learns that the score exists. When the same vendor or foundation model operates across employers, one hidden judgment may follow a worker from application to application. Hiring AI needs advance notice, data access, correction rights, independent bias testing, and a meaningful human appeal before efficiency becomes algorithmic blacklisting.

6 min