IPCRIME reporting published November 18, 2026. SmartHR’s first disclosure: November 17.
SmartHR says some conversations its officers and employees had with Notion AI may have been exposed following unauthorized access at Notion supplier Fireworks AI. The company’s November 17 notice identifies potentially affected material as some employee-entered text and AI responses from October 6 through October 24, 2026.
What is known
SmartHR says it received a report from Notion about possible external exposure and is investigating the contents and scope. It has reported the matter to Japan’s Personal Information Protection Commission. The notice does not disclose an affected-person total or establish that SmartHR’s customer HR database was accessed.
The company asks customers to be alert to messages impersonating SmartHR or Notion. It says it will not request passwords or other authentication information by email or telephone.
The wider supplier incident
In its separate security advisory, published November 12 with a November 13 update, Notion says the broader Fireworks incident affected fewer than 1% of workspaces. That figure applies to Notion’s overall investigation, not to a percentage of SmartHR employees or customers.
Notion tells affected customers to review the data supplied through their workspace and treat the relevant conversations as exposed. Where passwords or API credentials were entered during the incident period, its guidance is to replace those specific secrets. Notion also says it disabled exposed Notion API keys and informed third-party issuers about other discovered keys.
Why the distinction matters
IPCRIME’s assessment is that AI conversations deserve the same data-handling review as documents. A conversation can contain sensitive text even when a company has not granted an AI service access to its entire business database. An investigation therefore needs to establish what was submitted, who could see it, and which systems any included credentials could reach.
For affected organizations, keep the conversation review narrow and access-controlled. Record confirmed findings separately from potential exposure, assign an owner to each required credential change, and follow the supplier’s verified notification route. A broad breach headline alone cannot determine which accounts need action.
Sources
SmartHR’s November 17 notice; Notion’s Fireworks AI advisory. Both source notices were reviewed in Japanese.
Featured image: conceptual IPCRIME artwork, not a photograph or screenshot of this incident or product.
