Notion’s Fireworks breach: how to check if your AI chats leaked
Notion says fewer than 1% of workspaces had Notion AI chats exposed through Fireworks, which kept data it had promised not to. Here's where owners and members can see exactly what went out.
For most of the past few weeks, some Notion AI chats sat on servers belonging to a company that had promised not to keep them.
That is the plainest reading of Notion’s help-centre notice on the Fireworks AI incident. Fireworks, an inference provider Notion used, told Notion it had been breached. Notion’s own look then turned up something worse: data had been retained from the Fireworks endpoints Notion used, even though Fireworks had committed by contract to zero data retention. Notion says the incident touched “fewer than 1% of Notion workspaces.”
If that includes yours, there is a way to see exactly what went out. It takes a desktop browser and a few clicks.
What leaked, and from where
The exposed material is Notion AI chat transcripts: any input to or output from the model that was written to a chat, according to the notice. Notion sent those chats to Fireworks for two jobs. One was Insights, an admin feature that analyses how a workspace uses AI. The other was serving open-weight models. Notion also used data volunteered through its Learning and Early Access Program (LEAP) to experiment with training task-specific models on Fireworks.
AI Meeting Notes are not affected, Notion says, unless their contents were pasted into a Notion AI chat.
Notion says that as of Nov. 3 it had disconnected from Fireworks, deleted its data in the Fireworks system, stopped sending traffic there and halted all training runs. Insights is switched off. For most affected workspaces, Notion says it attached no metadata tying a transcript to a specific workspace, user or company. That lowers the odds of a chat being traced back to you. It doesn’t make the words inside any less sensitive.
The Fireworks timeline
Fireworks has disclosed more than one intrusion. The Record reported on Nov. 10 that Fireworks first discovered a breach on Oct. 6. BleepingComputer reported the same day that the early-October incident involved environment variables holding API keys and tokens for a limited number of accounts.
Then a second one. Fireworks said “a third-party cloud provider that hosted Fireworks R&D machines experienced a security incident on October 23,” per BleepingComputer, and that on Oct. 24 the intruder reached Fireworks development machines and ran a workload that “led to additional customer data impact.” The data listed includes resource metadata, billing details, invoices and payment history, and incomplete model weights and datasets for some customers. Fireworks says it doesn’t store payment card numbers.
How to check your workspace
Notion says it has contacted affected customers. If neither Notion nor your workspace owner has been in touch, your workspace hasn’t been identified as affected and there’s nothing to do for now. If you have heard from them, here is the path Notion’s notice gives:
1. Open Notion in a desktop browser, on the latest version. The review isn’t available on mobile.
2. In the workspace sidebar, click ?, then Security incident review.
3. Owners can download a CSV of affected members, or share a link so members can review their own data.
4. Owners with a verified domain can also download affected_content.csv and affected_content_annotated.csv, which show the content itself.
5. Members see only their own affected content, through the same page.
Owners can remove members’ access to their own affected content. Notion is clear that this deletes nothing and doesn’t change chat history.
Then read the files for one thing above all: secrets. Notion’s advice is to treat the data as exposed and, if anyone pasted passwords, API keys or other credentials into Notion AI during the affected period, rotate them right away. A search of the annotated CSV for strings like sk-, AKIA, ghp_ or password is a fast first pass. It won’t catch everything.
The fine print on “zero retention”
The most useful line in the notice is in its FAQ. Notion says its zero-data-retention commitment covers API requests to model vendors, but not features that store chat history or Insights data. In other words, the promise many enterprise buyers check for in a vendor review applied to one path through the system and not the others.
Notion says it is now auditing its critical vendors, including inference providers and data processors, to verify their retention and data-minimization practices. If your company signed off on Notion AI because of a zero-retention clause, ask which features that clause covers. Notion has now answered for itself: not all of them.
Researched and drafted with AI tools, fact-checked against primary sources and approved by a human editor before publishing. Prices and dates are as of publication. Our standards →
Sources- notion.com — Notion's help-centre notice
- therecord.media — The Record reported
- bleepingcomputer.com — BleepingComputer reported
Latest from prompt/power
- Nvidia beats its own forecast with US$115.8 billion, then guides margins lowerNov 18
- Apple, the NSA and Chase: what each says broke in a week of outagesNov 18
- ChatGPT for Healthcare now has agents that click through hospital software. The fine print is all AmericanNov 17
- ChatGPT Wallet lets an AI agent pay for you. Here’s who can use it, and why Canada and the U.K. waitNov 17
- Gemini 4 Argon’s API price doubles Dec. 1. Here’s what it costs in US$, CA$ and £Nov 17