Factories > Infrastructure
Zero data retention (ZDR) for factory inference
Provider ZDR, improvement collection, and saved factory runs are separate. Review coverage and controls before sending sensitive work.
Provider Zero Data Retention (ZDR) covers whether the AI provider keeps your prompts and responses. For factory inference, coverage depends on the model and whose provider account serves the request, not where the agent runs commands. For example, self-hosting execution does not establish provider ZDR or move saved run data.
Warp’s provider ZDR policy applies to supported models on every plan when Warp supplies the provider account. This is called Warp-managed inference.
Choose inference covered by provider ZDR
Section titled “Choose inference covered by provider ZDR”- Warp-managed inference - Choose models outside the retention-required exception list. Apply that choice to each agent and any separate model settings or overrides, not only the foreman.
- Your provider account - For team-managed keys and endpoints, BYOLLM, or direct Claude Code or Codex calls, you’ll need to verify ZDR with the provider for your specific account, model, and configuration. Warp’s agreements don’t establish ZDR for those requests, even if you avoid the listed models. For an endpoint that uses other model providers, verify their retention policies too.
Current Auto selections, fallback chains for models outside the exception list, and automatic Computer Use selection avoid the listed exceptions, but routes can change. Coverage of every background AI request remains unconfirmed. If your policy requires ZDR for every request, ask Warp to confirm coverage for your configuration before sending sensitive work.
See inference options for factory runs for supported providers, credentials, and harnesses. Personal keys and endpoints stored on your device do not apply to factory runs.
Understand collection and storage
Section titled “Understand collection and storage”Provider ZDR doesn’t stop Warp from saving data needed to operate your factory:
- Improvement collection - The Help improve Warp toggle controls Warp’s analytics and eligible content collection for service improvement. It doesn’t change provider retention.
- Run history - Warp stores transcripts, prompt attachments, and uploaded artifacts so you can revisit runs, even with analytics off. Destroying a sandbox doesn’t delete these records.
- Personal Terminal sync - Store AI conversations in the cloud controls personal Terminal conversations, not factory run storage.
For team content collection, follow the browser procedure in the Admin Panel, including plan and workspace restrictions. Personal analytics and crash preferences are separate. See analytics and storage controls.
Enterprise admins can configure self-hosted storage separately for transcripts, prompt attachments, and artifacts. Categories without a self-hosted storage configuration remain with Warp.
Configure your factory
Section titled “Configure your factory”Self-serve teams can change models and overrides manually, but don’t have a team-wide model-blocking control. Business supports shared provider keys and endpoints. Enterprise adds model restrictions in the Admin Panel.
Choose the procedure for where your definition is managed. Both work in a browser without installing Warp Terminal and include checks for defaults, overrides, and new runs:
Related pages
Section titled “Related pages”- Privacy and data control - Review the shared provider policy and collection controls
- Agent model choice - Find models that require provider retention
- About factory infrastructure and security - Review hosting, inference, networking, and credential boundaries
- Self-hosted agent data storage - Configure where run data is stored