Notion published its advisory on 10 November and added on 11 November that it had revoked exposed Notion API keys identified during its investigation. Notion says fewer than 1% of workspaces were affected and that it contacted affected customers on 9 November. The dataset included Notion AI chat transcripts used by its usage analytics feature. The investigation is ongoing.
On 14 November, Sankei Shimbun said that a business partner had used Notion on a project for the newspaper. Notion Labs provides the service, and the unauthorised access occurred at its contractor, Fireworks AI. Sankei said some information about its own systems may have been exposed. After receiving the partner’s report, Sankei temporarily suspended Sankei iD on the evening of 13 November and restored it on the morning of 14 November after checking the system was safe. Its notice did not give the date of the unauthorised access. Whether information was disclosed externally remained under investigation, and the notice did not confirm any disclosure of personal data.
Sankei Shimbun notice of 14 November (PDF)
Notion provides affected customers with instructions for reviewing the relevant data securely in their workspace. Follow its advice to revoke and replace any credentials, including passwords and API keys, pasted into affected chats during the relevant period. Fireworks AI’s 9 November update describes its own investigation and customer notifications. Each advisory addresses the scope of its own service.
When reviewing an AI feature, document which data it sends to external suppliers, who receives it, how long it is retained and who handles incident notices. Agree what users may enter in chats and who can revoke and replace credentials if they are exposed.
Notion — Fireworks AI incident
Fireworks AI — 9 November incident update
Sources initially checked on 13 November 2026 (Japan time).