🔍 Read the full analysis: How Notion’s AI Chats Were Affected By A Fireworks Security Breach on ThorstenMeyerAI.com
Get business pricing on office and shipping supplies
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Notion says a dataset accessed in the Fireworks AI security breach included stored Notion AI chat transcripts associated with its Insights feature. The company says fewer than 1% of workspaces are affected and that it revoked exposed Notion API keys found in affected messages on Nov. 11. Notion has not identified which Fireworks system retained the data or how long it was stored.
Notion’s updated advisory says the dataset Fireworks provided to the company on Nov. 8 included stored requests and responses from Notion AI use that were sent to Fireworks for Insights analysis. Notion says most transcripts in the affected workspaces could not be attributed to a particular person or workspace: they lacked those labels and did not contain tool-call results. That does not mean the text was necessarily harmless. The company defines a transcript as model input or output written to the chat, which may include sensitive information entered by a user.
Notion advises affected customers to treat the data as exposed and conduct a thorough review. It says users should rotate passwords, API keys and other credentials that they pasted into Notion AI during the incident. Notion also says it revoked exposed Notion API keys found in affected messages on Nov. 11. It has not described the number or type of keys involved.
The company says AI Meeting Notes, including audio, transcripts and summaries, were not affected unless that material was entered as input in a Notion AI chat transcript. Notion says no other Notion features were affected. It identifies Fireworks’ role in Insights classification jobs and as an inference provider for open-weight models, but says the exposed dataset came from the Insights side.
Notion AI Chats ExposedIn Fireworks Breach
Notion says data accessed in the Fireworks breach included stored chat transcripts used for Insights. Affected customers should treat the data as exposed and review chats for credentials.
What the dataset included
The exposed dataset came from Insights analysis, not ordinary live model requests.
AI chat transcripts
Stored requests and responses could contain sensitive text users entered into chats.
Tool-call results
Notion says the transcripts did not contain tool-call results.
Meeting Notes
Audio, transcripts and summaries were not affected unless entered into an AI chat.
What customers should do
Notion advises affected customers to review exposed content and act on any credentials found.
Check for passwords, API keys and other credentials pasted into Notion AI.
Change any credentials found in affected messages. Notion says it revoked exposed Notion API keys on Nov. 11.
Notion recommends a thorough incident review for customers who receive a notice.
What remains unclear
The public notices leave key details unresolved for customers and other Fireworks users.
- Which Fireworks system retained the data
- Why it was retained despite a contractual zero-retention commitment
- How long the data was stored
- Exact counts of affected workspaces, users or transcripts
- Number or type of exposed credentials
- Whether other Fireworks customers were affected
What the Chat Exposure Means
The disclosure matters because chat transcripts can contain whatever users type or paste into an AI conversation, including customer details, contract information or credentials. Notion’s statement that most affected transcripts were unattributable limits what the dataset directly revealed about their authors or workspaces, but it does not establish that the content itself was nonsensitive.
The incident also raises a practical question for companies relying on zero data retention promises from AI vendors. Notion says Fireworks had made a contractual zero-retention commitment for its use of the platform, yet its investigation found that data had been retained from the endpoints Notion used. The published accounts do not explain how that retention occurred, so the breach does not by itself establish that all zero-retention arrangements work the same way—or that other customers’ data was affected.
Popular right now
Vitamix 5200 Professional-Grade Blender
KitchenAid Classic Series 4.5-Quart Tilt-Head Stand Mixer, Onyx Black
eufy E25 Robot Vacuum and Mop
As an affiliate, we earn on qualifying purchases.
How Notion’s Fireworks Data Was Used
Notion says it used Fireworks for two purposes: processing Insights classification jobs, which help workspace administrators understand how teams use AI, and serving open-weight models within its product. The company says the accessed data was from Insights, where stored Notion AI requests and responses were analyzed, rather than from ordinary live inference requests.
Notion’s advisory distinguishes its zero-retention commitments for live requests to model vendors from features that rely on stored data, such as chat history and Insights. It says those stored-data use cases are not covered by the same commitment. Notion’s timeline says it disconnected its systems from Fireworks and deleted data in the Fireworks system on Nov. 3, after Fireworks notified it on Nov. 2 that a small set of data had been accessed. Notion says it initially understood that data to be synthetic testing data.
Fireworks’ own bulletin, last updated Nov. 9 according to the source material, says it had not detected an impact to Inference, Training SDK and Nexus, which it describes as zero-retention by default. Its bulletin also lists datasets among information accessed for certain customers. The two companies’ public statements do not identify the specific system that retained the Notion data.
““Unfortunately, during our investigation we learned that data was retained from the Fireworks endpoints that we used.””
— Notion, in its security advisory
What the Notices Do Not Explain
The public notices do not identify which Fireworks system retained the data, why it was retained despite the contractual commitment, or how long it remained there. They also do not give a count of affected users, transcripts or exposed credentials. Notion’s estimate—fewer than 1% of workspaces—does not provide a precise number or clarify how many people within those workspaces may have been affected.
It remains unclear whether the same retention issue affected other Fireworks customers. Notion’s description of the breach and Fireworks’ statements about services not showing an impact do not, on their own, settle how the two accounts fit together. The available information also does not establish whether attackers used any exposed credentials or whether the exposed chat content has been published or otherwise misused.
Vendor Review and Customer Checks
Notion says it is auditing critical vendors and data processors for compliance with data-minimization practices, including zero-retention policies. The company has not provided a completion date or detailed findings from that review. Customers who receive a notice from Notion should follow its incident-review guidance and check affected chat content for passwords, API keys and other credentials, rotating any that were included.
Further clarity depends on updates from Notion and Fireworks about the retained data, the systems involved and the scope of affected customers. Until those details are published, Notion’s stated workspace estimate and advice to treat affected data as exposed are the clearest available guidance.
Key Questions
What Notion data was accessed in the Fireworks breach?
Notion says the accessed dataset included Notion AI chat transcripts used for the Insights feature. It says the transcripts contained model input or output written to chats and did not include tool-call results.
How many Notion workspaces are affected?
Notion says fewer than 1% of workspaces are affected. It has not given a precise count of workspaces, users or transcripts.
Were Notion AI Meeting Notes affected?
Notion says AI Meeting Notes—including audio, transcripts and summaries—were not affected unless material from them was used as input in a Notion AI chat transcript. It says no other Notion features were affected.
What should affected users do?
Notion advises affected customers to treat the data as exposed and review it under its security incident guidance. Rotate any passwords, API keys or other credentials pasted into Notion AI during the incident; Notion says it revoked exposed Notion API keys it found in affected messages on Nov. 11.
Does the breach show that other Fireworks customers were affected?
That is not clear from the published notices. Notion and Fireworks have not specified whether the retention issue affected other customers or which Fireworks system held the Notion data.
Source: ThorstenMeyerAI.com
