ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
TopicDisconfirmAI EditorialUpdated 2026-11-20 16:38

Fireworks AI Data Retention

6 steps1 pieces5 Sources

Fireworks AI, a US-based specialized intelligence platform, has clarified its data retention policies following a security breach that exposed Notion AI chat transcripts. The incident highlighted the distinction between two standard API designs: customer-managed retention (upload-use-delete) for batch jobs and ephemeral processing (send-compute-return) for real-time inference. CEO Lin Qiao stated on November 14, 2026, that Fireworks prioritizes ephemeral processing where workflows allow, as it eliminates human errors like forgotten datasets. However, the breach occurred in storage systems outside the default Zero Data Retention (ZDR) scope, specifically affecting batch inference and stored responses. While Fireworks offers an enterprise-wide ZDR policy to reject requests requiring persistence, this setting is off by default. The disagreement centers on whether contractual promises of non-retention cover all service modes or only specific endpoints, with Notion noting that data used for its Insights feature was retained despite expectations. Readers should monitor whether enterprise customers actively enable account-wide ZDR restrictions and how deletion processes for batch task data are verified.

How it got here

  1. 2026-10-23

    October 23, 2026: A third-party cloud provider hosting Fireworks R&D machines experienced a security incident.

    venturebeat.com ↗
  2. 2026-10-24

    October 24, 2026: Unauthorized parties accessed Fireworks development machines, leading to additional customer data impact.

    venturebeat.com ↗
Sign in / Sign up
ReadingResearchRadarInvestment framework
  • 2026-11-08

    November 8, 2026: Fireworks confirmed a new dataset to Notion, which included Notion AI chat transcripts used for the Insights feature.

    venturebeat.com ↗
  • 2026-11-09

    November 9, 2026: Fireworks issued a security update stating no impact to Inference, Training SDK, and Nexus, which are ZDR by default.

    venturebeat.com ↗
  • 2026-11-11

    November 11, 2026: VentureBeat reported that attackers breached Fireworks AI storage where Notion AI chats sat outside zero data retention.

    venturebeat.com ↗
  • 2026-11-14

    November 14, 2026: Fireworks CEO Lin Qiao posted on X clarifying the two standard API designs for data lifecycle management.

    x.com ↗
  • What is still unsettled

    • Which specific Fireworks feature stored Notion’s transcripts, given that neither company has explicitly identified it?
    • Will enterprise customers actively enable the account-wide Zero Data Retention restriction to prevent future breaches of stored data?
    • How will the industry reconcile contractual promises of 'no retention' with the technical reality of batch processing requirements?

    Sources

    • venturebeat.comVentureBeat↗
    • x.comX (Lin Qiao)↗
    • marktechpost.comMarkTechPost↗
    • ababnews.comABAB News↗
    • docs.fireworks.aiFireworks Docs↗

    Coverage in this topic

    • Fireworks AI CEO Lin Qiao: Two Standard Modes for AI API Data Retention, Advocating Ephemeral Processing When Workflows Allow2026-11-18News

      Lin Qiao, co-founder and CEO of Fireworks AI, outlines two standard lifecycle designs for AI inference and training APIs: customer-managed upload-use-delete and ephemeral send-compute-return. She argues that the latter should be prioritized when workflows permit, as it eliminates human errors such as forgotten datasets or missed deletion calls.