Notion, the collaborative workspace platform, revealed a data exposure affecting its AI-powered features following a breach at Fireworks AI, the infrastructure provider handling some of Notion's AI operations. The incident came to light after Fireworks AI disclosed that attackers gained access to its development systems through a third-party cloud provider on October 23, compromising resource metadata, billing data, model weights, and customer datasets.
This marks the second security incident at Fireworks AI in as many months. An earlier breach in early October saw attackers access environment variables holding API keys and authentication tokens for a subset of accounts. Notion received notification from Fireworks on November 2 regarding an exposed dataset, which initially appeared to contain only synthetic test information.

Notion moved quickly to contain the situation, disconnecting from Fireworks' infrastructure, purging stored data, and stopping model training operations by November 3. However, Fireworks confirmed on November 8 that actual customer information, including data from Notion users, had been accessed during the breach.
The workspace platform uses Fireworks AI to power certain open-source language models within Notion AI and to process conversation logs for Insights, a feature providing workspace administrators with analytics on AI tool usage across their teams. The compromised transcripts originated specifically from the Insights dataset, which Notion has now deactivated.
Upon analysis of the dataset Fireworks AI gave us on November 8, we discovered that it included Notion AI chat transcripts used for the Insights feature, which for the vast majority of impacted workspaces were unattributable.
Notion
Notion clarified that "unattributable" means the conversations lacked identifying information about who authored them or which workspace they belonged to, and the transcripts excluded results from tool integrations. The company emphasized that Fireworks AI had contractual obligations requiring complete data deletion for Notion information.
The incident affects less than 1% of Notion's user base. Workspace administrators in impacted accounts can examine affected data through the Security incident review section in Notion's web application and generate shareable links allowing team members to retrieve their own chat records. Notion recommends that affected users change any passwords, API credentials, or other sensitive information that may have been entered into conversations during the exposure window.
Users and workspace owners who have not received direct notification from Notion can assume their accounts were not part of the affected group and do not need to take immediate action. The company has published a frequently asked questions resource providing additional details about the incident.