Hackers accessed chat transcripts from some Notion AI users, TechCrunch reported on November 12, 2026. They got in through Fireworks AI, an outside vendor that ran AI jobs for Notion.
Notion says the incident touched fewer than 1% of its workspaces. The company cut its systems off from Fireworks on November 3.
Many freelancers and solo founders run their whole business inside Notion. They keep client notes, proposals, and project plans there, and they often paste that material into Notion AI. This breach shows how a vendor you never chose can still put your data at risk.
What The Breach Actually Exposed
According to TechCrunch, the attacker first broke into Fireworks’ cloud provider and then reached a Fireworks development system. Fireworks says the attackers took billing details and some customer datasets. TechCrunch calls this the company’s second breach in two months, after an October incident.
Notion’s incident notice ties the exposure to Insights, an admin feature that tracks how members use AI. Fireworks ran classification jobs for that feature. The exposed data covers anything a user typed into Notion AI chat and anything the model wrote back.
Notion says AI Meeting Notes data stayed safe unless someone pasted it into a chat. The company also says Fireworks kept data despite a contract that promised zero data retention. Notion has since deleted the data in Fireworks’ system and paused Insights.
Notion made other cuts as well. It stopped using Fireworks to serve open-weight models. It also halted training runs that used data from its early access program to test smaller task models.
Why This Matters For Self-Employed Notion Users
Solo workers rarely have an IT team to track vendor risk. Yet a client contract or an API key pasted into an AI chat could now sit in a stolen dataset. Fireworks believes attackers want to resell access to AI tokens, so stolen credentials have real value.
The breach also raises client obligations. Many freelance contracts include confidentiality clauses. If you pasted client material into Notion AI, you may owe that client a heads-up.
What Self-Employed Notion Users Should Do Next
If you own a workspace, open the incident review panel from the help menu in a desktop browser. Notion lets owners download a list of affected members.
Workspaces with a verified domain can also export the specific affected content. Check that file against your client list.
Next, rotate any password, API key, or token you ever pasted into Notion AI. Do this even if Notion has not contacted you. Then review which AI features in your other tools send data to outside model providers.
Members of a shared workspace see only their own affected content in the review tool. Owners can disable that access if they prefer to handle follow-up themselves.
Notion says it has already contacted affected customers. If you haven’t heard from Notion, the company hasn’t linked your workspace to the incident yet.
What To Watch Next
Notion says its investigation remains open and it will reach out directly if it finds more affected workspaces. The company is also auditing its key vendors for compliance with zero data retention. Watch Notion’s security bulletins for the results.
The bigger risk sits with AI infrastructure firms that most users never see. Recent attacks on self-hosted AI servers show that criminals now target the systems behind AI tools. Ask each software vendor which subprocessors handle your AI chats before you paste in client data.
Photo by Markus Winkler: Pexels
