"Zero retention" was in the contract. The chats were kept anyway

Notion says a breach at Fireworks AI, a vendor that served some of Notion's AI features, exposed Notion AI chat transcripts for fewer than 1% of workspaces, although Fireworks had a contractual
Summary
Notion says a breach at Fireworks AI, a vendor that served some of Notion's AI features, exposed Notion AI chat transcripts for fewer than 1% of workspaces, although Fireworks had a contractual zero-data-retention commitment. For a CA office, the lesson is that a "zero retention" clause is a promise about some traffic, so ask which features and which sub-processors it does not cover before client data goes into an AI chat.
The situation
Most CA offices now use at least one tool with "AI" inside it: a notes app, a mail client, a document workspace. When we ask whether it is safe, the question is usually "does the vendor train on my data?" and the answer is usually a settings page saying no.
Notion's notice shows why that is the wrong question, or at least an incomplete one.
What happened, in Notion's words
According to Notion's help-centre notice:
- Fireworks AI, a vendor Notion used, reported an incident affecting "fewer than 1% of Notion workspaces".
- What was exposed is Notion AI chat transcripts, which Notion defines as "any input to or output from the model that was written to the chat".
- Notion had sent stored requests and responses to Fireworks for a feature called Insights (now disabled), and also used Fireworks to serve open-weight models.
- Fireworks had a contractual zero-data-retention commitment, but Notion says "data was retained from the Fireworks endpoints that we used".
- Notion's enterprise zero-retention terms did not cover Insights or chat history.
- Data from customers in a programme called LEAP had been used to experiment with training on Fireworks.
- As of 3 November, Notion had disconnected Fireworks, deleted the data there and stopped the traffic. Workspace owners can download lists of affected members and content, and Notion says to treat the data as exposed and rotate any credentials pasted into Notion AI.
The notice gives no date for the incident itself.
Why it matters to a CA office
Three things in that notice are worth a partner's attention.
The contract was not the control. A zero-retention clause existed. Data was retained anyway, at a company the customer never contracted with. A clause tells you what someone promised, not what their servers did.
Some features sat outside the promise. The enterprise terms did not cover "Insights" or chat history. Vendors add analytics, summaries and "insights" features all the time, and each one can move data along a route the main terms never mention.
The data was whatever people typed. Transcripts mean the questions, not just the files. In an accounts office that can be a client's name with a PAN, a bank login pasted "just to check", or a draft reply to a notice. If it went into the chat, it is now in the breach.
What to do
This is the list I am working through in my own office.
- For every tool with AI inside it, write down who serves the model (the sub-processor list) and which features the "no retention" or "no training" terms leave out.
- Ban passwords, OTPs, portal logins and client bank details from every AI chat. If one has been pasted, change it today.
- Treat chat history as stored client data, with the same retention and access rules as the client's folder.
- Read what a vendor's beta or "early access" programme allows before joining it. In Notion's case, that was the route to training experiments.
- Keep a named contact and a notification clause for each AI vendor, so that if this happens to you, you hear it from the vendor, not from a news site.
None of this needs a new tool. It needs one page per vendor and a rule everyone in the office knows.
Sources
- Notion, "Security incident involving a third-party AI vendor" — https://www.notion.com/help/security-incident-involving-a-third-party-ai-vendor
Share line (for WhatsApp / LinkedIn — Karan pastes it once the article is live)
Notion's AI vendor kept chat transcripts despite a zero-retention contract. Ask every AI tool in your office who serves the model and which features the promise leaves out. https://www.notion.com/help/security-incident-involving-a-third-party-ai-vendor