Skip to main content
Most of Fireworks never stores prompts or generations. A few features do store customer content, such as stored responses, batch jobs, and training. The Zero Data Retention policy blocks those features for everyone on the account by rejecting every request and job that would persist or log customer content.
Enterprise feature. The Zero Data Retention policy is available on Enterprise accounts. Contact your Fireworks representative if you need this enabled.
Only account Admins can change the Zero Data Retention policy. Other roles can view the current setting but cannot change it.
The policy applies account-wide: every user and API key on the account follows it. The policy doesn’t affect prompt caching, which holds KV caches only in memory, or the request metadata used to operate and bill the service. Fireworks may still retain data where required by law or to prevent abuse.

​
Settings

​
What it controls

Data sent to third parties, such as MCP servers you connect or the search providers and websites behind web search, is handled under their own policies.

​
Existing data

Turning on the policy doesn’t delete anything already stored on the account, such as stored responses, datasets, and uploaded models. You can delete any of it whenever you like.

​
Configure in the console

Account admins can set the Zero Data Retention policy in the Fireworks console at Settings → Governances → Zero Data Retention (open in console). Turn on Default Policy, or set Inference and Training individually, and save.

​
Configure with firectl

Enforce for Inference and Training:
Set Inference and Training individually:
Inspect the current setting:
Make Inference and Training follow Default Policy again:
Turn the policy off:

​
Configure with the API

Use Update Policy Settings with updateMask=zero_data_retention and an API key that belongs to an account Admin. Each request replaces the whole Zero Data Retention section, so always send defaultEnforced. A scope you leave out follows Default Policy. Enforce for Inference and Training:
Set Inference and Training individually:
To turn the policy off, send {"zeroDataRetention": {"defaultEnforced": false}}. Get Policy Settings returns the current setting. An absent zeroDataRetention means the policy is off.