1 min read
Add as a preferred source on Google

Fireworks CEO Says Batch Files Remain Until Customers Delete Them

An account-wide zero data retention setting can reject storage-dependent batch jobs and uploads, but it is off by default and does not delete existing files.

A disconnected drive rests beside a closed storage cabinet / TokenPost.ai
A disconnected drive rests beside a closed storage cabinet / TokenPost.ai

Fireworks CEO Lin Qiao said batch processing stores uploaded files until customers delete them, while some other services support zero data retention.

Batch files remain stored until customers delete them; Fireworks says it does not retain copies after deletion.

In a post responding to retention concerns, Fireworks CEO Lin Qiao described batch processing as a file-based workflow that differs from individual inference requests. Qiao said Chat Completions, Nexus and serverless training support zero data retention (ZDR). She also said OpenAI, AWS and Google use similar designs for batch interfaces.

Fireworks offers enterprise customers an account-wide ZDR setting, which is off by default. When enabled, it rejects batch jobs and file uploads that require storage, but does not automatically delete existing data.

Fireworks processed conversations for Notion’s Insights feature, which provides workspace analytics. Notion said the exposed conversations came from fewer than 1% of workspaces and that Fireworks had contractually agreed not to retain the data.

Simon Yoon

Reporter

Simon Yoon reports on blockchain technology for TokenPost. Send corrections or tips to info@tokenpost.com.

Loading…