A third-party AI vendor incident has affected a limited set of Notion workspaces, according to Notion's November 13 security advisory. Notion says the data it received from Fireworks AI included chat transcripts used by its Insights feature and affected fewer than 1% of workspaces. It says most of those transcripts could not be tied to a person, workspace or company. The update is still under investigation, so the scope should be read as what the companies have reported so far.
This is a report about data handled by an outside inference provider, not a claim that every Notion AI conversation or Notion feature was exposed. Notion says no other Notion features were affected, and Fireworks describes additional information about its own incident that goes beyond the Notion dataset.
What Notion says was in the dataset
The affected records were chat transcripts from Notion AI's Insights feature, which helps customers understand their use of AI. Notion says the vast majority had no label identifying their author or workspace and did not include tool-call results. In the November 13 update, it says it revoked Notion API keys found in affected user messages on November 11, then reported exposed third-party API keys found there to the vendors that issued them on November 12.
Notion's timeline starts with a November 2 notice from Fireworks about a smaller dataset of synthetic test data. Notion disconnected its systems and deleted data from Fireworks the next morning. Fireworks later notified Notion that potential customer data could also have been accessed; it supplied a final affected dataset on November 8, and Notion says it contacted affected customers on November 9. The November 13 update adds the credential-remediation steps.
How Fireworks describes the wider incident
Fireworks' November 9 bulletin says a third-party cloud provider hosting its research and development machines had an incident on October 23. The following day, an unauthorized party used that access to reach Fireworks development machines and run an unauthorized workload. Fireworks says a limited set of its accounts also had impacts to account and billing information, stored secrets, datasets and incomplete model weights. It says payment card numbers were not stored by the service and were not impacted.
Those are Fireworks-wide categories, not a description of the Notion records. Notion's own notice describes the dataset relevant to its customers. Fireworks says it has not detected impact to its inference, Training SDK and Nexus services, which it says are zero data retention by default; its investigation remains ongoing. Keeping the two scopes separate matters when deciding what the public notices do and do not establish.
Notion security advisory: incident timeline, affected workspace count and response guidance
Fireworks AI security bulletin: incident path, data categories and investigation status
What should a workspace owner do?
Notion says it has contacted the customers it identified as affected. If a workspace has not heard from Notion, the company says it has not identified that workspace as affected and no action is needed at this time. If Notion has notified a workspace, its guidance is to retrieve and review the affected data through the secure in-workspace instructions it sent, treat the relevant content as exposed, and rotate passwords, API keys or other credentials pasted into Notion AI during the incident period. Notion says it will contact customers if its continuing investigation identifies more affected workspaces.
The incident also illustrates a practical boundary in AI products: a prompt may pass through a provider that is separate from the app a person uses. For builders, the provider, purpose, data types, retention and incident-notification path are useful questions to check before sending real user content to an external model service. These questions do not prove a service is unsafe; they make the data path visible.
The facts may change as Fireworks and Notion continue investigating. For now, Notion's specific notice is the source for workspace impact and recommended customer action; Fireworks' bulletin describes the provider's broader incident. Neither supports treating every Notion AI user or every Fireworks customer as affected.