🔍 Read the full analysis: Why The Fireworks Breach Has Notion AI Users Asking About Privacy 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 breach included Notion AI chat transcripts used for its Insights feature. The company says fewer than 1% of workspaces are affected and that it revoked exposed API keys found in affected messages on November 11. The parties have not explained which Fireworks system retained the data or how long it was stored.
Notion’s updated security advisory says Fireworks provided the company with a dataset on November 8 that included Notion AI chat transcripts used for Insights, a feature that gives workspace administrators information about team AI usage. Notion says those transcripts were unattributable for the vast majority of affected workspaces: they were not labeled with the writer’s identity or workspace, and did not include tool-call results.
That does not mean the transcript content was necessarily harmless. Notion defines a transcript as input to or output from the model written to the chat. The company advises affected customers to review the data because prompts or responses may contain sensitive information. It says fewer than 1% of workspaces are affected; it has not identified a workspace as affected if neither its owner nor the workspace has received notice from Notion.
Notion said that on November 11 it revoked exposed Notion API keys found in affected user messages. It advises affected customers to treat the data as exposed, review it under its Security incident review guidance, and rotate passwords, API keys and other credentials pasted into Notion AI during the incident. The company says AI Meeting Notes were not affected unless their audio, transcripts or summaries were used as input in a Notion AI chat transcript, and that no other Notion features were affected.
Why the Fireworks Breach Has Notion AI Users Asking About Privacy
Notion says an accessed dataset included chat transcripts used for Insights. The content may have included sensitive information, even when transcripts were not tied to a person or workspace.
What the dataset contained
Notion says the affected data came from Insights, which analyzes team AI usage.
Chat input and output
Transcripts could include prompts or model responses, potentially containing confidential business details or credentials.
Usually unlabeled
For most affected workspaces, transcripts lacked the writer’s identity, workspace label, and tool-call results.
How the response unfolded
Notion describes disconnecting from Fireworks and reviewing the incident.
What affected customers should do
Notion advises notified workspace owners to treat the data as exposed.
- Review the relevant data using Notion’s Security incident review guidance.
- Check chats for sensitive information, including credentials.
- Rotate passwords, API keys, and other credentials pasted into Notion AI during the incident.
- If neither the owner nor workspace received notice, Notion says it has not identified that workspace as affected.
What remains unclear
The public notices leave key details about retention and scope unresolved.
- Fireworks had a contractual zero-retention commitment for Notion’s use.
- Notion says its investigation found data retained from the endpoints it used.
- Which Fireworks system retained the data, and for how long.
- How many people or transcripts were involved.
- Whether other Fireworks customers faced the same issue.
What the Exposure Means for Workspaces
The disclosure matters because AI chat prompts can contain confidential business information, even when a transcript is not linked to a named user or workspace. Notion’s advice to review affected data reflects that the content itself may include customer details, contract terms, credentials or other sensitive material.
It also puts a specific vendor assurance under scrutiny. Notion says Fireworks made a contractual commitment to zero data retention for Notion’s use of its platform, but Notion later learned that data was retained from the endpoints it used. The company has not said that every retained record was exposed; it says a dataset accessed by attackers included the transcripts.
For customers, the immediate practical issue is whether their workspace was notified and whether sensitive information was entered into the affected chats. For other organizations using third-party AI services, the incident illustrates that a retention commitment and the actual handling of data can diverge. The published information does not establish that other Fireworks customers experienced the same issue.
Products Worth Considering
Canon SELPHY CP1500 Compact Photo Printer Bundle with Ink and Paper Set, White
Logitech MX Master 4 for Mac Wireless Ergonomic Mouse, White Silver
Vari Ergo Electric Standing Desk, 54×26, Light Wood/White
As an affiliate, we earn on qualifying purchases.
How Notion Used Fireworks
Notion says it used Fireworks for two different purposes: classification jobs for Insights and as an inference provider for open-weight models in its product. The exposed data described in Notion’s notice came from the Insights side, where stored requests and responses from Notion AI use were analyzed.
Notion’s explanation distinguishes those stored records from live model requests. It says its zero-retention commitments for live requests to third-party model vendors apply to requests sent to generate Notion AI responses, but are not intended to cover features that require data to be retained, including chat history and Insights. Separately, Notion says Fireworks had promised zero retention for Notion’s use of its platform, then says its investigation found data had been retained from the Fireworks endpoints it used.
Notion’s timeline says Fireworks first told it on November 2 that a small set of data had been accessed by malicious actors. On November 3, Notion says it disconnected its systems from Fireworks, deleted data from the Fireworks system, stopped communications with the provider and halted training runs. Notion updated its advisory on November 10 and 11. Fireworks’ own update was still marked last updated November 9 in the source material.
““Unfortunately, during our investigation we learned that data was retained from the Fireworks endpoints that we used.””
— Notion, in its security advisory
Open Questions About Retention
The available notices do not identify which Fireworks system retained Notion’s data, why it was retained, or for how long. Notion has not stated how many individual people or transcripts were involved, beyond saying fewer than 1% of workspaces are affected.
There is also an unresolved difference in emphasis between the companies’ public descriptions. Notion says it found retention from the Fireworks endpoints it used. Fireworks says it has not detected an impact to Inference, Training SDK and Nexus, which it describes as zero-retention by default, while its update lists datasets among data accessed for certain customers. The published material does not reconcile these statements, so it is not clear which Fireworks system was involved or how the descriptions relate.
The notices do not establish whether other Fireworks customers were affected by the same retention issue. Nor do they specify the complete contents of the dataset beyond Notion AI transcripts used for Insights. These points remain unconfirmed in the source material.
Vendor Audit and Customer Reviews
Notion says it is auditing critical vendors, including inference providers and data processors, to check their data-minimization practices and zero-retention policies. The company has not provided a public completion date for that audit in the available notice.
Affected workspace owners should follow Notion’s incident-review instructions, examine the relevant data for sensitive content, and rotate credentials that may have been entered into Notion AI during the incident. Customers who have not received notice should not assume their workspace was affected; Notion says it has not identified such workspaces as affected.
Further clarity depends on updates from Notion and Fireworks about the retained data, the system involved, the retention period and the scope across customers. Until those details are published, the extent of the exposure beyond Notion’s stated workspace figure remains unknown.
Key Questions
What Notion AI data does Notion say was accessed?
Notion says the dataset accessed in the Fireworks breach included chat transcripts used for its Insights feature, which analyzes Notion AI usage. It defines transcripts as model inputs or outputs written to the chat.
How many Notion workspaces are affected?
Notion says fewer than 1% of workspaces are affected. The company has not provided a specific workspace count in the supplied notice.
Were AI Meeting Notes affected?
Notion says AI Meeting Notes, including audio, transcripts and summaries, were not affected unless that material was used as input in a Notion AI chat transcript. It says no other Notion features were affected.
What should an affected workspace do?
Notion advises affected customers to treat the data as exposed, review it under its Security incident review guidance, and rotate passwords, API keys and other credentials pasted into Notion AI during the incident. Notion says it revoked exposed Notion API keys found in affected messages on November 11.
Why are customers asking about zero data retention?
Notion says Fireworks had a contractual zero-retention commitment for its use of the platform, but Notion’s investigation found data had been retained from the endpoints it used. The companies have not publicly identified the system involved or explained how long the data was retained.
Source: ThorstenMeyerAI.com
