Posted by werrett 8 hours ago
> As a precaution, we recommend that you treat this unattributable data as if it were exposed. If anyone on your team pasted sensitive information like passwords, API keys, or other credentials into Notion AI during this timeframe, we recommend rotating them right away.
Okay, so the actual impact is quite interesting: they did not notify you if they could not attribute the transcripts to you! You should really treat anything sensitive sent to Notion AI as compromised because they are not sure where these transcripts came from.
Coding agents in my experience alert you to this, which is good. I pasted what was temporary token I made into Claude, just to test something, and after it had done the task it said something like, "you gave me a live token to work with in the chat, I'd advise you to treat that as exposed and rotate it."
It would be a good standard for all chat interfaces to have those "alerts" built in.
Who is using Notion for a chat about the weather? It's chats about your content and data.
> Private: this provider does not train on prompts and does not retain prompt data.
So how come notion discovered that they actually stored the data?
> Upon analysis of the new data, we discovered that it included unattributable Notion AI chat transcripts
Is there any legal consequence for stating you are ZDR but then internally you don't give a shit about it? I'm guessing that'd be between OpenRouter and the provider, not between the provider and the one triggering the inference, would that be correct? Does OpenRouter validate anything at all in regards to the providers, or it's a free-for-all "do whatever you want" kind of deal for OpenRouter and the providers?
On the main fireworks breach page, they also say some customer weights of models and datasets to train them were leaked.
Ignoring whether or not there could be backdoors, security holes in the Trusted Execution Environment stuff are still being found on a regular cadence.
I'd guess it's good enough to avoid bulk surveillance (and therefore extraction of training data, which I guess is the attack that Notion was running when they screwed up and leaked the data), but that's about it.
Apple's stuff is a similar story. (And so are VM enclaves, which have been around longer.)
That is for now, I am sure there will be worse months ahead of us.
but good that they finally got around to posting something official ...
I asked the CISO if they can tell me if the data was accessed but they aren't answering and any communication is super slippy like "may have been accessed". I need to do some GDPR notations bc of them but I won't start running around just bc it "may have been" accessed
https://fireworks.ai/security/bulletins/october-2026-securit...
https://fireworks.ai/security/bulletins/october-2026-securit...
This is astonishing.
They’re saying “OTHER THAN THE ACTUAL CONTENTS OF YOUR CONVERSATION, NO INFORMATION WAS PRESENT”. That is not what unattributable really means and they’re trying to assert otherwise.
It’s trivial to identify the organisation or individuals involved in a conversation most of the time, but Notion are trying to make out that because the metadata wasn’t present, it’s no cause for concern.
That’s absolute bullshit and will give people a false sense of security. The contents of your conversation IS the critical information. Notion’s desktop app is very aggressive in prompting users to transcribe their calls and I imagine a large proportion do so by default. The potential for harm here is large.
I appreciate it’s Fireworks’ fault this happened, but Notion’s response destroys my confidence in them.
So we've all got all the data to make our own determination on the data being 'unattributable' or not.
/s