Fireworks and Notion AI: what should you check?
Your team uses Notion, and a security headline names Fireworks, a company you have never bought from. Ask whoever manages your Notion workspace whether an incident notice has arrived. If it has, follow its instructions. Start with that account-specific answer before deciding whether your team needs to change anything.
The app you recognise may use a supplier you do not
TLDR AI’s November 10 edition linked Fireworks’ updated security bulletin. Following that lead also brought us to Notion’s own advisory. The practical question is which service handled your information and who can confirm the impact.
Notion says affected data included AI chat transcripts used for its Insights feature. It has contacted affected customers and disabled Insights during the investigation. It says no other Notion features were affected and it has stopped using Fireworks.
For affected customers, Notion provides instructions to review the impacted data securely inside their workspace. It advises treating that data as exposed and replacing passwords or API keys pasted into Notion AI during the incident period.
If you have not heard from Notion, its current guidance says your workspace has not been identified as affected and no action is needed now. The investigation continues.
Discovery: TLDR AI, November 10Notion’s current incident advisory and instructions
Give the next step to the right person
Ask one person to confirm what applies to your account before the team starts changing tools. This table suggests who can help; it does not identify any account as affected.
| Your situation | Who to ask | The answer you need |
|---|---|---|
| Your team uses Notion AI | The person responsible for your Notion workspace | Has a notice arrived, and who will handle any instructions? |
| Your app connects directly to Fireworks | The person maintaining that connection | Which Fireworks account does the app use? What action does its notice require? |
| Another software product uses Fireworks | That product’s support team | Does its own advisory cover your account or feature? |
Notion’s account-specific response routeFireworks’ updated customer notice
The newer bulletin changes the scope
Fireworks’ November 9 update expanded its earlier disclosure to account and billing information. It also reported impacts to stored credentials, datasets and incomplete models for a limited set of accounts. The company says it does not store payment-card numbers and those were not affected.
Fireworks says it has not detected impact to its Inference, Training SDK or Nexus services. That is an investigation finding to date, not a guarantee about every product built on its infrastructure. Use your app provider’s notice for that product.
The update also says self-service dataset uploads and downloads for Batch Inference and dataset-based training are disabled during the investigation. If a planned job needs those transfers, confirm availability before promising a delivery date.
Check which information the service keeps
A promise not to keep prompts or replies covers specific data. It does not, by itself, establish whether an account was affected by this incident.
Fireworks’ documentation says it does not store prompts or generated answers for open models unless the user opts in, but does log service metadata, such as token counts. It separately documents conversation storage for its Response API: storage is on by default and can be disabled with store=False. Stored conversations can remain for up to 30 days.
For a custom app, ask its maintainer which API connection and storage setting it uses. The public notices do not establish that this setting caused the exposure; checking it helps you understand what your app stores.
Record who will finish the response
If a direct Fireworks notice identifies third-party passwords or API keys, its earlier bulletin says to replace or disable them with the provider that issued them, then update the applications using them. Deleting a stored copy alone does not make the password or key unusable.
For your internal record, keep the affected service, the person responsible, the required action and its completion date. Keep incident details inside the relevant account and approved internal channels.
If your account has no required action, name someone to watch for further notices. A wider redesign can wait until you understand what the notice requires.
Fireworks’ credential instructions for notified customersHow forvertz scopes AI connections and data requirements
Sources
Clarify one AI connection.
Tell forvertz which app and feature your team uses. We can discuss its place in your workflow using public documentation, without sharing private records or credentials.
Discuss your AI workflowUpdated