Your AI chat has a supply chain. So does its leak.
The name on an AI app is not necessarily the only company handling a conversation. Notion's incident notice makes that invisible supply chain unusually tangible. Notion says a Fireworks AI incident affected chat transcripts used for its Insights feature in fewer than 1% of workspaces. Its updated account records disconnection on November 3, deletion of its data at Fireworks on November 4, and notification of affected customers on November 9. A November 13 update says exposed third-party API keys found in messages were reported to their issuers the previous day. Notion had already revoked exposed keys of its own. Most affected transcripts lacked author or workspace labels, according to Notion. That does not mean the words inside a conversation could not identify someone. A password, company name or access token can be sensitive without a separate identity field attached. There is an important boundary. Fireworks says its investigation has not detected impact to its default zero-data-retention Inference, Training SDK and Nexus services. The companies' disclosures do not establish that every AI chat, or every such retention arrangement, is compromised. For affected users, Notion recommends reviewing the supplied incident information and rotating credentials placed in the exposed conversations. For buyers more broadly, the question is architectural: which features send data to which vendors, why is it retained, and how quickly can downstream exposure be contained? Removing an integration can stop new traffic. It does not automatically neutralize a credential already copied elsewhere. Privacy promises need a map of those dependencies, not just a reassuring app interface.
