ToolNavs Find Useful AI Tools
Submit Sign in
Back to AI information
Notion Admits AI Chat Logs Leaked via Vendor Breach: Under 1% of Workspaces Affected

Notion Admits AI Chat Logs Leaked via Vendor Breach: Under 1% of Workspaces Affected

AI information • Admin • • 22 views

Notion published a security advisory on November 12 admitting that the October intrusion at Fireworks AI exposed Notion AI chat transcripts from under 1% of workspaces. The breach was not in Notion's own systems: the records were conversations Notion had sent to Fireworks for classification behind its Insights feature, including user inputs and model outputs. Fireworks had promised Notion zero data retention — these records should never have been stored.

From the October intrusion to the November advisory

  • October 23–24: attackers entered Fireworks' research machines through its cloud provider.
  • November 2: Fireworks reported a small dataset had been accessed, initially saying it held only synthetic test data.
  • November 3: Notion cut its connection to Fireworks, deleted data stored there, and halted training runs.
  • November 8: Fireworks confirmed the final dataset included Insights chat transcripts.
  • November 9: Notion contacted affected customers; on November 11 it revoked Notion API keys found in the leaked messages, and on November 12 it notified third-party key issuers.

The impact splits in two. For users, most affected records carry no author or workspace label and include no tool-call results; Notion's pages, databases and files were untouched, and audio from AI meeting notes was not involved either. But any workspace that received a notice and pasted passwords or API keys into Notion AI chats should rotate them now; workspaces that got no notice need take no action. The other layer is vendor governance: Notion has disabled Insights and stopped serving open-weight models through Fireworks. A 'zero retention' clause in a contract did not stop the data from being kept — a promise is not a technical guarantee.

Notion says it has contacted every affected customer, and workspace admins can review the outcome in the desktop app's security incident review. What matters next is Fireworks' investigation findings, and whether Notion resumes working with the vendor — until then, any product that sends user conversations to a third-party model provider has to answer where the data lives and for how long.

Recommended Tools

More