A Contract Is Not A Control
Notion told customers last week that a company running part of its writing assistant had been breached, and that chat transcripts were in the stolen data. It affected under one percent of workspaces and Notion handled it about as well as anyone could. The part worth keeping is a detail in the middle of the advisory: that company had promised Notion in writing to keep nothing at all.
When software grows an assistant, most people see one new button. Behind it there is usually a second company you have never heard of, running the model it talks to. Last week one of those companies was breached. Notion, which makes note-taking software a great many small firms run on, published an advisory: a vendor behind part of its assistant had been compromised, and chat transcripts were in the stolen data. The scale is small and Notion's handling was good. Fewer than one percent of workspaces. Told within days. The affected material made available for customers to inspect. Our interest: we recommend these tools, we use them, and we are the people who switch them on in other companies. This is a risk we help put into your business. And the unhelpful part, plainly: we cannot audit your software vendor's model provider for you. Nobody can, from outside. The technical part — you can skip this box The sources are Notion's own security advisory, first published November 9, 2026 and updated since, and its help-centre notice titled "Notice about the Fireworks AI incident that may impact some Notion workspaces." We read both, plus the company's frequently-asked-questions section. Notion's words: "One of our vendors, Fireworks AI, notified us of a security incident impacting fewer than 1% of Notion workspaces," and "Even though this was not a breach of our systems, keeping your data safe is fundamental to using Notion for your life's work." The timeline, as Notion gives it: on the evening of November 2 the vendor told Notion a small dataset had been accessed by malicious actors, and that first dataset "included Notion AI synthetic testing data, and no Notion AI customer data was involved"; on November 6 the vendor said potential customer data may have been accessed; on November 8 it confirmed the dataset; on November 9 Notion contacted impacted customers. What was in it: "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," and, from the questions section, "Any input to or output from the model that was written to the chat is included in that chat transcript." On identification , Notion says "the chats weren't labeled with who wrote them or which workspace they came from" and that it "did not add any additional metadata that attributes the chat transcript back to your specific workspace, user, or company" — it calls the data unattributable, with that holding for "the vast majority of impacted workspaces," and we are quoting the qualifier because one write-up of this incident dropped it. The relationship, in Notion's words: "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." And the line this entry is built on: "Fireworks provided us with a contractual commitment to zero data retention for our use of its platform." Notion's advice to affected customers is to treat the data "as if it were exposed" and to rotate any credentials pasted into its assistant; customers who were not contacted are told "no action is needed right now," and "No other Notion features were affected." What we could not confirm: the vendor has published nothing about this incident on its own security-bulletin page, which carries only an October bulletin about a different and earlier event. Notion's notice points readers at that page for official updates, and when we looked there was no November entry. And one thing we deliberately did not chase: a headline elsewhere refers to a further breach at the same vendor involving a third-party cloud provider, and an aggregator site claims it touched several companies. We did not read those articles, Notion's advisory does not mention a cloud provider, and we are not repeating the claim. What that actually means The company whose logo is on your software is often not the company running the assistant inside it. There is a second firm, with its own staff, security and bad weeks. A chat transcript is a record. Whatever was typed into that box, and whatever came back, is written down by default. And a promise to keep nothing is a promise, not a mechanism. The vendor had committed in writing to retain no data. A dataset of transcripts existed anyway. The part that is actually good news This is a small incident, handled properly, which makes it a cheap way to learn something. Nobody has to do anything urgent because of it. And the lesson costs nothing to apply. The questions below are asked once per tool rather than maintained. The caveat, which is a check rather than a fear We are not telling you contracts are worthless or assistants dangerous. A commitment to keep nothing is worth having — it decides who is liable and it is a reason to prefer one supplier. It is simply not the same claim as the data not existing. So the check is what you put in rather than what you were promised: if something would be damaging to read aloud, it does not belong in a chat window. What to do in ten minutes Change anything that was pasted into an assistant. Passwords, keys, card numbers. This is the only step with a clock on it, and it is Notion's own advice. Ask each of your main tools one question: whose servers run the assistant? Most vendors publish a supplier list and will send it if you ask. Find out which assistants switched themselves on. Features arrive enabled more often than not, and the decision gets made by a release note nobody read. Tell your team the chat box is a filing cabinet, not a conversation. That sentence does more than any setting. If we look after your systems, send us the tools you use and we will tell you which ones publish a supplier list.