Notion AI chat transcripts exposed in Fireworks AI breach

Notion reported that a breach at AI infrastructure provider Fireworks AI exposed Notion AI chat transcripts used for its Insights feature, affecting fewer than 1% of Notion workspaces, according to a Notion security advisory updated 10 November 2026. Fireworks notified Notion on 2 November that malicious actors had accessed a small dataset, which Notion initially determined held only synthetic testing data; on 6 November Fireworks warned that potential customer data may have been accessed, and on 8 November Fireworks confirmed the final impacted dataset. Notion disconnected from Fireworks by the morning of 3 November, deleted all data in the Fireworks system, revoked exposed Notion API keys on 11 November, reported exposed third-party API keys to their vendors on 12 November, and disabled the Insights feature while it investigates.

All security advisories https://www.notion.com/en-gb/security/advisories Updates 1. InvestigatingIn addition to previously notifying the impacted customers, on November 12 we reported exposed third-party API keys found in affected user messages to the vendors that issued them. 2. InvestigatingOn 11 November, we revoked exposed Notion API keys that were found in affected user messages during our investigation. Fireworks AI incident Investigating Updated version: 10 November 2026. This post informs you about the recent Fireworks AI incident and how it’s impacting <1% of Notion workspaces. For the latest on the Fireworks AI incident, please see their official updates here https://fireworks.ai/security/bulletins . We have contacted our customers who were affected by the Fireworks incident. If you haven’t heard from us, we haven’t identified your workspace as affected, and no action is needed right now. Our investigation is ongoing. If we determine that your workspace was impacted, we will contact you directly. What happened and how we addressed it : | Date | Update | |---|---| | 2 November | On the evening of 2 November, Fireworks notified Notion that a small set of data had been accessed by malicious actors. Upon investigation, it was determined that the dataset included Notion AI synthetic testing data, and did not include any Notion AI customer data. | | 3 November | As a precaution, by the morning of 3 November, Notion had disconnected its systems from Fireworks, deleted all data in the Fireworks system, and stopped all communication between its systems and Fireworks. | | 6 November | On 6 November, Fireworks notified Notion that malicious actors may have accessed potential customer data. Notion immediately began another internal investigation. | | 8 November | On 8 November, Fireworks confirmed the final impacted dataset. | | 9 November | On 9 November, Notion reached out to impacted customers. | Upon analysis of the dataset Fireworks AI gave us on 8 November, we discovered that it included Notion AI chat transcripts used for the Insights https://www.notion.com/help/notion-ai-settings-overview insights feature, which for the vast majority of impacted workspaces were unattributable. “Unattributable” means the chats weren’t labelled with who wrote them or which workspace they came from, and the transcripts did not contain tool call results. Beyond what’s in the chat transcript itself, there’s no information tying the chat back to workspaces, users or companies. No other Notion features were affected, and we continue to monitor this incident. What is Fireworks AI and how we used them: Fireworks is one of the most used global AI infrastructure platforms powering tens of thousands of customers and used by hundreds of thousands of developers. We used Fireworks for classification jobs to help customers understand their own AI usage through a feature in Notion called Insights, and we used them as a general inference provider to serve open-weight models inside our product. The Insights feature has been disabled as we investigate this incident, and we are no longer serving open-weight models through Fireworks. What we recommend for affected customers: Affected customers are able to retrieve and review the impacted data securely inside their workspace, with instructions sent via email. We also recommend that affected customers treat this data as if it were exposed. If those with affected workspaces have pasted sensitive information, passwords, API keys or other credentials into Notion AI during the timeframe of the incident, rotate them. We will update this page as we learn more. We take your privacy and the security of your data seriously. Even though this was not a breach of our systems, keeping your data safe is fundamental to using Notion for your life’s work. It is our mission to make sure this never happens again. We will raise the standard for how your data is protected. On 10 November, we updated this post for style and clarity in response to customer questions and feedback. No changes have been made to previously reported facts. View the previous version of this article https://www.notion.com/security/advisories/security-incident-involving-a-third-party-ai-vendor-nov9 . Originally published