🔍 Read the full analysis: AI Chat Transcript Exposure: Notion’s Fireworks Breach Explained on ThorstenMeyerAI.com
Get smart everyday buys delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
Notion says data accessed in the Fireworks AI breach included stored Notion AI chat transcripts used for its Insights feature. It says fewer than 1% of workspaces are affected and that exposed Notion API keys found in messages were revoked on November 11. The companies have not explained where or how long the data was retained, or whether other Fireworks customers were affected in the same way.
Notion says chat transcripts from its AI product were included in a dataset accessed during the Fireworks AI breach, and that on November 11 it revoked exposed Notion API keys found in affected user messages. The company estimates that fewer than 1% of Notion workspaces were affected; it has not said how many people or transcripts were involved.
According to Notion’s updated security advisory and help page, the transcripts came from data used for Insights, a feature that gives workspace administrators information about how teams use Notion AI. Notion says Fireworks provided a dataset on November 8 that included these stored requests and responses. The company says most transcripts in the affected workspaces were “unattributable”: they were not labeled with the person who wrote them or the workspace they came from, and did not include tool-call results.
That lack of labels does not mean the text was harmless. Notion defines a transcript as any input to or output from the model that was written in the chat. It advises affected customers to review the data because a prompt or response may contain sensitive information. On November 11, Notion said it revoked exposed Notion API keys found in affected user messages. The notice also tells affected users to review the material and rotate passwords, API keys or other credentials they pasted into Notion AI during the incident.
Notion says AI Meeting Notes—including audio, transcripts and summaries—were not affected unless someone used that material as input in a Notion AI chat transcript. It says no other Notion features were affected. The company’s stated estimate is fewer than 1% of workspaces; it says that if neither a user nor the workspace owner has received a notice, Notion has not identified that workspace as affected.
Notion’s Fireworks Breach Stored AI Chats Exposed
Notion says a dataset accessed in the Fireworks AI breach included stored Notion AI chat transcripts used for Insights. Affected organizations should review content and replace credentials shared in chats.
What Was in the Dataset
Notion says the transcripts came from stored requests and responses used for workspace-level Insights.
Chat inputs and outputs
Transcripts could include text written in chats, including sensitive details or credentials.
Often unlabeled
Most transcripts lacked author and workspace labels. That does not mean the text itself lacked identifying details.
Who and What Were Affected
Notion says affected customers should rely on direct notice about their workspace.
| Data or feature | Notion’s statement |
|---|---|
| Notion AI chat transcripts | Included in the accessed dataset |
| AI Meeting Notes | Not affected unless used as chat input |
| Other Notion features | Not affected |
What Organizations Should Do
For workspaces contacted by Notion, its guidance focuses on reviewing content and replacing exposed credentials.
Check transcripts for sensitive information; missing labels do not guarantee anonymity.
Replace passwords, API keys, or other credentials pasted into Notion AI during the incident.
Notion says a workspace without a user or owner notice has not been identified as affected.
Retention Questions Remain
Notion says Fireworks retained data from endpoints it used despite a contractual zero-retention commitment.
- Transcripts were used for Insights.
- Notion revoked exposed API keys found in affected messages.
- Notion is auditing critical vendors.
- Which system retained the data and for how long.
- How many people or transcripts were involved.
- Whether other Fireworks customers were similarly affected.
Why Stored AI Chats Matter
The disclosure matters because chat prompts can contain information users would not expect to be part of a vendor’s stored analysis dataset. A user might paste customer details, contract language or credentials into a chat. Notion says the exposed transcripts could include model inputs and outputs, and recommends a thorough review rather than assuming that unattributable data is safe.
The incident also highlights a distinction between zero data retention for live model requests and data kept to support product features. Notion says its zero-retention commitments for requests sent to model vendors do not cover stored data needed for functions such as chat history and Insights. That distinction may affect how organizations evaluate AI features, vendor contracts and what employees should be allowed to enter into workplace tools.
For affected organizations, the immediate practical concern is identifying sensitive content and replacing credentials that may have appeared in a transcript. Notion’s account does not establish that every exposed transcript contained sensitive material, or that anyone used the information. It does establish that customers should not treat the dataset as risk-free.
Products Worth Considering
Samsung Odyssey G9 QD-OLED 49 Dual QHD Curved Gaming Monitor
Logitech MX Master 4 Ergonomic Wireless Mouse with Haptic Feedback, Graphite
FlexiSpot E6 Electric Standing Desk, 55 × 28 in, Bamboo Top, White Frame
As an affiliate, we earn on qualifying purchases.
How Notion Used Fireworks
Notion says it used Fireworks for two purposes: classification jobs for Insights and as an inference provider for open-weight models in its product. The transcript dataset came from the Insights use, according to Notion. Its notice describes Insights as relying on stored Notion AI requests and responses to provide workspace-level analysis.
Notion’s published timeline says Fireworks notified it on November 2 that a small set of data had been accessed. Notion initially understood the material to be synthetic testing data. On November 3, it says it disconnected its systems from Fireworks, deleted data in the Fireworks system and halted training runs. Notion later updated its notice as the investigation developed. Fireworks’ own bulletin, cited in the source material, was last updated November 9.
Notion says Fireworks had made a contractual commitment to zero data retention for Notion’s use of its platform. The company then reported that its investigation found data had been retained from the Fireworks endpoints it used. Fireworks’ bulletin separately says it had not detected an impact to Inference, Training SDK and Nexus, which it describes as zero-retention by default, while listing datasets among data accessed for certain customers. The published information does not explain how those statements relate to Notion’s retained data.
““Unfortunately, during our investigation we learned that data was retained from the Fireworks endpoints that we used.””
— Notion
Questions About Retention Remain
The published notices do not identify which Fireworks system retained Notion’s data, why it was retained despite the contractual commitment, or how long it remained there. Notion has not provided a count of affected people or transcripts, beyond saying fewer than 1% of workspaces were affected. It is also unclear whether other Fireworks customers had similar data-retention issues.
The available information does not say whether attackers accessed every transcript in the dataset, what specific content was present, or whether any exposed information has been misused. Notion’s description that most transcripts were unattributable refers to missing labels, not necessarily to the absence of identifying details within the text itself. Fireworks’ public statement about services with zero retention by default does not resolve the unanswered question about the endpoint used for Notion’s Insights data.
Customer Reviews and Vendor Audit
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 completion date or published the findings of that audit. Further clarification from Notion or Fireworks about the retained system, retention period and affected customer scope would help organizations assess the incident.
Organizations that have been contacted by Notion should follow its guidance to review affected data and rotate credentials that may have been entered into Notion AI. Those steps address potential exposure; they do not establish that a credential or other information was accessed or misused. Customers who have not received notice should rely on direct communication from Notion for any change in their workspace’s status.
Key Questions
What Notion data was included in the Fireworks breach dataset?
Notion says the dataset included Notion AI chat transcripts used for its Insights feature. It defines transcripts as inputs to or outputs from the model written in the chat.
How many Notion workspaces were affected?
Notion says fewer than 1% of workspaces were affected. It has not disclosed a precise workspace count or the number of affected individuals and transcripts.
Were Notion AI Meeting Notes exposed?
Notion says AI Meeting Notes, including audio, transcripts and summaries, were not affected unless they were used as input in a Notion AI chat transcript.
What should affected users do?
Notion advises affected users to review the data and rotate passwords, API keys and other credentials they pasted into Notion AI during the incident. Notion also says it revoked exposed Notion API keys found in affected messages on November 11.
What remains unknown about the incident?
The companies have not specified which Fireworks system retained the data, how long it was kept, how many people or transcripts were involved, or whether other Fireworks customers experienced the same problem.
Source: ThorstenMeyerAI.com
