🔍 Read the full analysis: Notion’s Fireworks Breach Disclosure Puts AI Chat Privacy In Focus on ThorstenMeyerAI.com
Get business pricing on tech for your team
- 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 from Insights, and that Fireworks retained data despite a contractual zero-data-retention commitment. Notion says fewer than 1% of workspaces are affected; it has revoked exposed API keys and advises affected users to review data and rotate credentials.
Notion says chat transcripts from its AI product were included in a dataset accessed by attackers in the Fireworks AI breach, and that Fireworks retained data despite a contractual commitment to zero data retention. Notion says fewer than 1% of workspaces are affected and reported revoking exposed Notion API keys found in affected user messages on November 11.
Notion’s updated notice says the dataset Fireworks provided to the company on November 8 included Notion AI chat transcripts used for the Insights feature. Insights gives workspace administrators information about how their teams use AI. Notion says the transcripts were unattributable for the vast majority of affected workspaces: they were not labeled with the author or workspace, and did not include tool-call results. But the company cautions that a transcript can contain any input or output written in the chat, which may include sensitive details users typed.
Notion says the affected material came from the Insights analysis workflow, not from every use of Notion AI. It also says AI Meeting Notes—including audio, transcripts and summaries—were not affected unless their content was used as an input in a Notion AI chat transcript. Notion states that no other Notion features were affected. It recommends affected users review the data and rotate passwords, API keys or other credentials they entered in Notion AI during the incident.
On November 11, Notion said it had revoked exposed Notion API keys found in affected user messages. The company’s guidance is to treat affected data as exposed and review it through its Security incident review process. Notion says people whose workspace has not been identified as affected will not have received a notice, but the public advisory does not provide a count of the number of people involved.
Notion’s Fireworks breach disclosure puts AI chat privacy in focus
Notion says an accessed dataset included AI chat transcripts used for Insights, despite Fireworks’ contractual zero-data-retention commitment. The disclosure highlights what businesses should review when AI features process internal information.
What the dataset included
Notion says the material came from the Insights analysis workflow, not every use of Notion AI.
Insights chat transcripts
Transcript text could include anything users entered or received in an AI chat.
Mostly unattributable
Notion says most transcripts lacked author and workspace labels and contained no tool-call results.
Other features
AI Meeting Notes were excluded unless their content was used in an AI chat transcript. Notion says no other features were affected.
What affected users should do
Notion advises people with an affected-workspace notice to treat relevant data as exposed.
Use Notion’s Security incident review guidance to identify data that needs attention.
Change passwords, API keys or other credentials entered in Notion AI during the incident.
Administrators can use it to determine which users and data to review.
The retention gap
Notion says zero-data-retention commitments cover live requests used to generate responses, but not all stored data used for features such as Insights.
- Fireworks had a contractual zero-data-retention commitment.
- Notion says it sent stored requests and responses for Insights analysis.
- Which Fireworks system retained the data or for how long.
- How many people were involved, or whether every transcript was accessed.
How the notice developed
Notion’s understanding changed as it received and reviewed information from Fireworks.
Why the Retention Commitment Matters
The disclosure puts a practical limit on what customers may infer from a zero-data-retention promise. Notion explains that its ZDR commitments apply to live requests sent to third-party model vendors to generate responses. They do not cover all data stored to provide features such as chat history and Insights. For Insights, Notion says it sent stored requests and responses to Fireworks for analysis.
The company says Fireworks had given it a contractual commitment to zero data retention, but that its investigation found data had been retained from the Fireworks endpoints Notion used. That creates a gap between the stated commitment and what happened to the data. For organizations using AI features with internal information, the incident makes vendor data handling, feature-specific retention and credential exposure relevant questions for security reviews.
Notion says it is auditing critical vendors and data processors to check their data-minimization practices, including ZDR policies. That is a stated response, not evidence that the audit has been completed or that the cause of retention has been established.
Products Worth Considering
Apple Watch Series 12 GPS 42mm Smartwatch
LG UltraGear 27-inch QHD OLED Gaming Monitor, 240Hz, 0.03ms, G-SYNC Compatible, FreeSync Premium Pro, HDMI 2.1, DisplayPort 1.4, Black
Samsung 32 Odyssey G5 (G51F) QHD 180Hz Gaming Monitor
As an affiliate, we earn on qualifying purchases.
How Notion’s Notice Changed
Notion’s notice changed after Fireworks told it on November 2 that a small set of data had been accessed by malicious actors. Notion initially understood the material to be synthetic testing data. According to Notion’s published timeline, the company disconnected its systems from Fireworks on November 3, deleted data in the Fireworks system and stopped communications with the provider. It also halted training runs.
Notion says it received a dataset from Fireworks on November 8 and later determined it included the Insights-related chat transcripts. The company updated its advisory on November 10 and 11. The source material says Fireworks’ own bulletin remained marked as last updated November 9 and described accessed datasets for certain customers, while saying it had not detected an impact to Inference, Training SDK and Nexus, which it describes as zero-data-retention by default.
Those statements do not establish which Fireworks system retained Notion’s data or explain how that retention related to Fireworks’ description of its services. The available information leaves that point unresolved; the incident should not be described as affecting all Fireworks products or customers.
“Unfortunately, during our investigation we learned that data was retained from the Fireworks endpoints that we used.”
— Notion
Open Questions About Retained Data
The public notices do not identify which Fireworks system retained the data, how long it was kept, or how many people were affected. Notion gives the affected share as fewer than 1% of workspaces but does not publish an exact count. It is also unclear whether other Fireworks customers experienced similar retention or whether the issue involved a specific endpoint or configuration.
Notion’s description of its ZDR scope and Fireworks’ account of which products were not affected do not resolve how the retained dataset fits into Fireworks’ service architecture. The available source material does not establish whether attackers accessed every transcript in the dataset or which, if any, contained sensitive credentials. Notion’s advice to treat affected material as exposed is precautionary guidance, not a claim that every item was read or misused.
Vendor Audit and User Reviews
Notion says its vendor audit is underway, including reviews of inference providers and data processors’ data-minimization practices. The company has not provided a completion date or publicly identified any resulting changes. Further clarification from Notion or Fireworks about the system involved, retention period and scope would help customers assess their exposure.
Users who receive an affected-workspace notice should follow Notion’s Security incident review guidance, examine relevant chat content and rotate credentials they entered during the incident. Workspace administrators can use the notice to determine which users and data need review. Notion says it has not identified workspaces as affected when neither the workspace owner nor the user has heard from the company; that guidance does not replace any later notice or update.
Key Questions
What did the Fireworks breach expose from Notion?
Notion says a dataset accessed in the breach included Notion AI chat transcripts used for Insights. The company says the transcripts were unattributable for most affected workspaces, but their contents could include text entered into or returned by the AI.
How many Notion workspaces are affected?
Notion says fewer than 1% of workspaces are affected. It has not published an exact workspace or user count in the information provided.
Were AI Meeting Notes affected?
Notion says AI Meeting Notes, including audio, transcripts and summaries, were not affected unless their content was used as an input in a Notion AI chat transcript.
What should affected users do?
Notion advises affected users to treat the relevant data as exposed, review it using the Security incident review guidance, and rotate any passwords, API keys or other credentials they entered in Notion AI during the incident. Notion says it revoked exposed Notion API keys it found in affected messages on November 11.
What does Notion’s zero-retention disclosure mean?
Notion says its ZDR commitments cover live requests sent to model vendors, not every feature that stores information, such as chat history and Insights. It says Fireworks had made a contractual ZDR commitment but that its investigation found data retained from the endpoints Notion used.
Source: ThorstenMeyerAI.com
