Notion has disclosed that Notion AI chats in fewer than 1% of its workspaces may have been exposed after a breach at Fireworks AI, an outside vendor Notion sent chat transcripts to for processing. The surprise: Fireworks had contractually committed to zero data retention, yet Notion found the data had in fact been kept. What to do today: open the Security incident review menu in your company workspace from a desktop browser, and if anyone on your team pasted a password or API key into a Notion AI chat, change it now, as Notion itself recommends. Back in August we wrote about an AI model with no known owner, and this incident completes the picture: even a well-known vendor can pass your data to a party you do not know.
What happened, by date
The story started at Fireworks AI, a company that runs AI models for other businesses, and then reached Notion's customers. This timeline comes from the two companies' official statements:
- October 6, 2026: Fireworks detected unauthorized use of internal credentials and began containment. The attacker reached environment variables holding API keys and tokens for a limited number of customers.
- October 9: Fireworks published its first security bulletin, saying at the time it had found no evidence of access to training data or chat transcripts.
- October 23 and 24: Attackers compromised a third-party cloud provider hosting Fireworks' research and development machines, and used it the next day to run an unauthorized workload on Fireworks systems.
- November 3: Notion disconnected from Fireworks, deleted its data there, halted all training runs, and disabled its Insights feature.
- November 9: Fireworks updated its bulletin: exposed data includes resource metadata, billing information such as addresses, invoice history and balances, and for some customers datasets and parts of incomplete model weights.
According to The Register, citing Bloomberg, Fireworks is also working with other customers, including Cursor and Harvey, to assess the impact on them. Notion is not the only one affected, but it has been the clearest in its disclosure so far.
What exactly was exposed from Notion
According to Notion's official page, the exposed data is Notion AI chat transcripts: what the user typed and what the assistant replied, in the chats that were sent to Fireworks. Notion used Fireworks for three things: classifying chats for its Insights feature, serving open-weight models, and experiments in training task-specific models on data from its early access program.
AI Meeting Notes audio, transcripts and summaries were not affected, unless someone copied them into a Notion AI chat. Notion says most exposed transcripts carry no metadata linking them to a workspace, user or company. That is less reassuring than it sounds: if an employee typed a client name, a contract number or a quoted price into the chat, the text itself reveals who it belongs to.
The key lesson: zero data retention is a promise on paper
The most serious line in Notion's disclosure is that Fireworks had contractually committed to retaining no data from Notion's use, and yet the data turned out to be stored in the systems Notion used. Your company signed with Notion, Notion signed with Fireworks, and Fireworks rented machines from a third cloud provider, which is where the breach happened. Three links in the chain, and you chose only one of them.
The same applies to every AI feature inside software you use: your accounting system, your customer service tool, your notes app. The smart feature often sends your text to a model provider whose name never appears on your invoice. Fireworks links the attack to a group that sells stolen access to AI models, a practice called LLMJacking, and BleepingComputer reports that the cloud bills it has caused reached as much as $1 million in some cases.
5 steps for your company this week
- Check the workspace now: the workspace owner opens ? in the sidebar, then Security incident review, from a desktop browser on the latest version, since the data does not show on mobile. If you have not heard from Notion, Notion says no action is needed right now.
- Download the list of affected members: the owner can download a CSV with affected members' names, emails and row counts, and with a verified domain can download the affected content itself for review.
- Change every secret pasted into chats: passwords, API keys and tokens anyone pasted into Notion AI during the period should be treated as exposed and rotated with whoever issued them, not just deleted from Notion.
- Write one clear rule: no passwords, no ID numbers, no card data and no complete customer files in any AI assistant, however big the name of the company behind it.
- Ask your vendors one specific question: for every piece of software with an AI feature, ask in writing for the list of providers your data passes through, where it is processed, and how the vendor verifies their zero-retention commitment. Notion says it is now doing exactly this with its own vendors.
The Origami view
Notion handled this transparently: it disclosed, gave owners a tool to see what was exposed, and cut off the vendor within days. But the incident proves that data leaving your company for an AI tool travels through a chain you cannot see. When we build an internal assistant for a client, we start with one question: which data actually needs to leave? Then we name the model provider in the contract, strip names and sensitive numbers before the text goes out, and keep a log of every request inside the company's own system. If you want a review of the AI tools your team uses, or a tool that keeps your data with you, contact us or see our services.
Sources
- Notion — Notice about the Fireworks AI incident: the under 1% figure, the exposed data, the zero-retention commitment, the November 3 actions, and the owner steps.
- Fireworks AI — October 2026 security incident: events of October 6 to 10, 2026.
- Fireworks AI — Security incident update: the cloud provider breach of October 23 and 24, the data categories exposed, and the November 9 update.
- BleepingComputer — Fireworks AI discloses new breach after cloud provider hack, November 10, 2026.
- The Register — coverage of the incident and its impact on Notion and other customers.
Frequently asked questions
Was my company's data exposed in the Notion incident?
Notion says the incident affected fewer than 1% of workspaces and that it has contacted those affected. Open ? then Security incident review from a desktop browser to see whether your workspace has affected content. If you have not heard from Notion, it says no action is needed now.
What data was exposed in the Notion AI incident?
Notion AI chat transcripts, meaning what users typed and what the assistant replied, in chats that were sent to Fireworks AI. Meeting notes were not affected unless they were copied into a chat.
Should I change passwords after the Notion AI leak?
Yes, if anyone on your team pasted a password, API key or token into a Notion AI chat. Notion recommends treating them as exposed and rotating them right away with whoever issued them.
Is an AI vendor's zero data retention promise enough to protect my company?
Not on its own. Fireworks was contractually committed to retaining no Notion data, and Notion still found the data stored. Ask every vendor for its list of sub-providers, and keep secrets and sensitive customer data out of any AI assistant.







