business 5 min read

Notion's ZDR Promise Broke — What It Means for AI SaaS Security

Notion admitted its zero-data-retention guarantee failed because a subcontractor, Fireworks.ai, was keeping data at an endpoint it shouldn't have been. The breach exposes a structural weakness across the AI SaaS supply chain.

  • SaaS
  • Data Privacy
  • AI & Security
  • Notion
  • Fireworks AI

Notion Told Its Customers Its Zero-Data Guarantee Was Empty

Notion Labs published a disclosure on November 12 that quietly undermined one of the most attractive promises in enterprise AI software. The company confirmed that even subscribers on its ZDR (zero data retention) plan may have had their Notion AI conversation history exposed — despite a contractual safeguard designed to prevent exactly that.

The breach traces back to an unauthorized access incident at Fireworks.ai, a US-based inference provider to which Notion outsources part of its AI processing workload. Notion’s “Insights” feature, which analyzes how teams use AI inside the platform, sends request-and-response pairs to Fireworks for aggregation. Notion and Fireworks agreed that these intermediaries would not retain any of the transmitted data — a minimal-presumption arrangement meant to close the very gap that consumers worry about when they type confidential strategy documents into a chatbot.

It did not hold.

During its investigation, Notion found that data was in fact being retained at the specific Fireworks endpoint it used — a deployment configuration distinct from Fireworks’ default service offering. When Notion discovered the mismatch, it severed all connections with Fireworks immediately. A broader audit of other third-party AI processors is now underway.

Fireworks responded separately on November 9, stating that its own default ZDR-enabled services appeared unaffected by the incident. It declined to explain the relationship between those defaults and the specific endpoint Notion relied on.

That silence matters more than it initially appears.

The Real Failure Wasn’t the Breach — It Was the Subcontractor Stack

A single vendor compromise would be alarming but conventional. What makes this case structurally interesting is what sits beneath Notion’s public-facing product. The company does not run every layer of its AI stack itself. It pipelines queries through external inference providers, and those providers in turn may operate on infrastructure managed by yet another party. ZDR promises travel downstream along that chain only as far as the weakest contractual enforcement can carry them.

Notion’s internal audit showed that its legal agreement with Fireworks — a commitment not to retain Insights data — existed on paper but not in practice at the endpoint level where the traffic actually landed. That means either the wrong deployment was selected, or a configuration drift went unchecked long enough for data to accumulate before anyone noticed. In either scenario, Notion’s customers received no warning until the company told them directly.

This is the pattern to watch across the industry. Vendors are accelerating feature rollouts faster than their security review cycles can keep pace. Every new integration — a vector database here, an inference provider there, a prompt-caching layer somewhere else — adds another node where a promise can break invisibly.

Who Lost Trust Here

Enterprise Notion customers were told explicitly that ZDR applied to their plans. They signed up expecting that whatever they typed into Notion AI would not persist beyond the immediate response. Anyone using Insights — and the feature appears to have been broadly deployed — assumed their prompts and replies were stripped to metadata-level aggregates. Instead, raw conversations appear to have survived on a server they never saw.

The fallout is uneven. Small teams and individual users who treated Notion as their personal operating system may find out later whether particular Notes contained competitive intelligence, financial projections, or HR-sensitive material. Larger organizations with compliance obligations will face harder questions from auditors, especially if regulated industries can connect the dots between the leaked data and obligations under frameworks like SOC 2, ISO 27001, or sector-specific rules.

Fireworks lost credibility even though it maintained its defaults were clean. The market judges a cloud vendor not just by what it claims under ideal conditions but by how transparently it explains deviations. Stopping short of clarifying which endpoint caused the mismatch — and why Notion’s contractually enforced rule didn’t apply there — leaves that question hanging.

Notion retains some trust precisely because it went public with the finding rather than waiting for a customer to discover it independently. The disclosure came within days of the underlying incident, which is near the fast end of the spectrum for software companies responding to supplier-compromise events.

What Happens Next in the Market

Expect three immediate shifts.

First, vendors will tighten contract language around sub-tier providers. An agreement with your direct supplier is no longer sufficient proof that your data won’t sit in someone else’s logs. Procurement teams should demand visibility into routing configurations and endpoint-level retention settings — not just a generic clause promising minimization.

Second, the term ZDR itself will come under scrutiny. As Notion’s case shows, two vendors can sign the same words while meaning different things. One may intend true ephemeral processing with automatic deletion at the network edge; another may store temporarily for debugging then delete after an undefined window. The industry needs clearer definitions, and buyers need testable guarantees, not marketing labels.

Third, customers using Insights-like analytics features should assume those features are not covered by their ZDR pledge unless the vendor states otherwise in writing. Notion already acknowledged that features requiring persistent data — outside Insights — were not ZDR-eligible by design. The less obvious boundary is whether the analytics themselves create an exception within a supposedly zero-retention environment. They do, as this incident proves.

The Uncomfortable Takeaway

Notion’s problem is not unique to its supply chain. It is the supply-chain problem. AI productivity tools are becoming federations of vendor agreements layered atop each other, each promising security properties that degrade at every handoff. ZDR sounds definitive. The reality is usually a set of operational decisions made miles away from the product team that sold it.

Fireworks had a default-safe configuration. Notion called a different endpoint. Nobody caught the difference before raw conversation data sat somewhere it was supposed to be deleted. That is not a conspiracy. It is a systems-integration failure — exactly the kind that compounds silently until a breach makes it visible.

For Notion’s enterprise customers, the message is simple: ask your vendor where your data actually lives when it passes through their partners. If the answer requires trusting a statement rather than auditing a configuration, you already know which side of the current case you’re on.