[warp-agent-staging]

What this feature does

Customers could not find ZDR guidance in the Factories tab, and existing pages confused provider retention with Warp's analytics and saved conversations. This documentation update adds a dedicated factory ZDR page, moves the shared policy to Support, and provides browser-based configuration and verification steps. It explains which settings affect provider requests, improvement collection, and stored run data without promising new privacy controls.

Summary

Engineering and Security confirmation remains outstanding for the items below.

Pending local follow-up: The standalone factory ZDR extraction and incoming-link updates are implemented and validated locally on top of 151e55bc, but are not yet committed or pushed. The ownership map below describes that revised working tree.

• Separate provider ZDR, improvement collection, and product storage, with one canonical policy owner.
• Give factory customers browser procedures for both dashboard-managed and GitHub-backed definitions, including defaults, overrides, application checks, and non-sensitive tests.
• Give the factory ZDR page its own entry under Infrastructure, replacing the shortcut to the preceding infrastructure page. Update discovery links, preserve old anchors, and distinguish manual choices from team enforcement.

This is a documentation correction, not a new privacy feature. No new retention periods, deletion commitments, or enforcement guarantees are asserted.

Content design plan

Audience and job: Customers deciding whether and how to use a factory with sensitive work, including customers without Warp Terminal.

Problem and outcome: Conflicting answers and scattered instructions made customers assemble the policy themselves. Readers should be able to find the answer, identify whose provider account they use, configure the relevant settings, understand what remains stored, and distinguish preferences from enforceable restrictions.

Goals: Readers can identify applicable provider coverage, distinguish collection from saved run data, and reach the correct browser configuration procedure.

Purpose and value: Extract existing factory retention guidance into factories/zero-data-retention.mdx so Infrastructure contains distinct destinations for deployment and ZDR, rather than adjacent links to one page.

Content type, skill, and template: Conceptual decision guide using draft_conceptual and .agents/templates/conceptual.md. Procedures remain in Configuring factory agents.

High-impact scenarios: Covers Warp-managed inference, customer provider accounts, direct third-party harnesses, collection/storage, plan controls, and dashboard/GitHub setup routes. Excludes new retention guarantees, contract approval, repeated procedures, and deferred lower-tier browser eligibility.

Canonical information versus guidance and discovery

Privacy and data control in Support is the canonical home of the Warp-wide ZDR policy. The dedicated factory ZDR page applies that policy to factories. Infrastructure and security retains deployment and data-flow details, with a short link to the ZDR page. Overview and sidebar links are discovery routes, not policy owners.

Role	Page	Information owned or purpose
Canonical shared policy	Privacy and data control — Support	Owns the Warp-wide provider ZDR policy, the boundary for customer-owned provider accounts, and the distinction between retention, improvement collection, and product storage. Also owns collection preferences.
Canonical model reference	Agent model choice	Owns the model-exception list, including effort variants, and Terminal model/privacy checks. Other pages link to this list.
Factory-specific ZDR guidance	Zero data retention (ZDR) for factory inference	Applies the shared policy to factory inference choices, coverage limits, collection/storage, and setup routes. Does not define a separate provider policy or duplicate the exception list.
Factory infrastructure reference	About factory infrastructure and security	Owns execution, hosting, inference support, networking, storage-location configuration, and credential boundaries. Four old ZDR anchors remain as onward links to the new page.
Factory setup and verification procedures	Configuring factory agents	Owns browser steps for dashboard/GitHub definitions, defaults and overrides, application checks, and new-run tests. Factory dashboard supplies navigation; Definitions as code supplies syntax and inheritance.
Team-control reference and procedure	Admin Panel	Owns plan-specific model restrictions, organization-enforced privacy controls, and browser steps for team improvement collection. Does not define provider retention policy.
Inference-path references	BYOK, custom endpoints, and team-managed keys and endpoints	Own credential scope, routing, and provider-verification responsibilities for each path. Link to Support for the shared policy.
Conversation-sync reference	Cloud-synced conversations	Owns personal Terminal sync and sharing behavior, including its separation from factory/cloud-agent run storage.
Deployment and data-flow references	Architecture and deployment, Architecture reference, and Security and networking	Own deployment choices, execution/data boundaries, and worker/network requirements, not provider policy. Self-hosted agent data storage remains the storage-configuration reference.
Discovery only	Warp Factories overview and Factories sidebar	Link directly to the dedicated ZDR page. The Infrastructure group uses a normal page entry, not an anchor shortcut to the preceding page.
Enterprise summary and evidence routes	Security overview and Trust Center	Summarize enterprise security and link to reports and shared policy. Existing Security overview ZDR anchors point onward to Support.
Other summaries and discovery	Agents/Enterprise overviews, Agent FAQs, and Pricing FAQs	Give short answers and links to the relevant policy, reference, or procedure. Do not create additional policy owners.

Factory customer journey

1. Find the guidance: Open Zero data retention (ZDR) under Infrastructure in the Factories sidebar, or follow the link from the factory overview.
2. Understand the factory implications: Read the dedicated ZDR page for applicable choices and limits. Follow its links to Support for the shared policy and Model choice for exceptions.
3. Configure and test: Follow the dashboard-managed or GitHub-backed procedure in Configuring factory agents.
4. Review controls and storage: Use the Admin Panel for team enforcement and collection controls, and the linked storage references for where run data is saved.

Editorial boundary: Preserve local warnings, useful training/BYOK explanations, and storage consequences. Do not duplicate full policy text or imply that source review proves deployed behavior or contract coverage.

Customer starting point

After merge, share ZDR for factory inference for coverage limits and browser-based configuration steps. Existing infrastructure-page anchors remain usable.

Unverified claims

Each item below needs confirmation or a narrower documentation statement. The listed functions indicate the expertise needed, not assigned reviewers.

• Provider-account and contract coverage: Routing code does not establish executed-contract scope. Action — Security/Legal: confirm the agreements covering actual serving accounts and hosts for Auto, fallback, Computer Use, Scorers, and Self-improvement, plus the completeness of the model-exception list. Approve the exact public wording or narrow/remove unsupported assurances.
• Production procedures and Self-improvement controls: Dashboard steps were checked against source, not a production account. Action — Engineering/product tester: exercise dashboard-managed and GitHub-backed disposable factories, save or merge, refresh changed settings, and inspect new runs. Record actual apply/failure behavior. Confirm deployed Self-improvement model controls, including existing factories, before documenting a control path.
• Collection scope and browser team controls: Production collection, organization precedence, and Business/Enterprise browser behavior remain untested. Action — Engineering: confirm those behaviors on appropriate test accounts. Security: review the resulting privacy wording. Keep lower-tier personal browser questions in the deferred plans follow-up below.
• SOC 2 wording: A legal-page attestation statement does not establish approval for every existing "certified" or "compliant" claim. Action — Security/Legal: supply the approved claim and scope, with report revision/audit period where applicable, then correct or remove unsupported wording. This evidence check is separate from provider ZDR.
• Confirm that all current production team-managed inference requests use only these two fixed outbound IPs.

Fixed-IP action — Engineering: verify production inference egress for the two addresses in factories/infrastructure-and-security.mdx, "Networking for BYO inference endpoints." Confirm the claim and resolve its VERIFY marker, or correct/remove the fixed-IP instruction before merge.

Deferred follow-ups

• Automatic classification: Security should identify the receiving providers/accounts and confirm their retention/training terms in the pinned background-request follow-up. Keep the documented coverage limitation until resolved. This question is not evidence of a violation.
• Factory plans and personal browser opt-out: Per HYC, the plans documentation update should confirm lower-tier eligibility, team versus individual scope, and the personal browser route. Use TODO(factory-plans) in the Admin Panel source as the handoff. Do not equate Terminal Free with a factory plan or anticipate new pricing behavior.

Documentation risk

Risk: engineering-review-required
Rationale: Changes security, privacy, inference, storage, and configuration guidance; contract scope and production behavior still need confirmation.
Source files consulted: warp/app/src/settings_view/privacy_page.rs; warp-server/logic/ai/util.go, logic/ai/ambient_agents/sources/agent_config.go, logic/factoryfile/resolution/automation.go; warp-server/client/packages/factory/src/pages/FactoryCode/index.tsx, CodeBrowser.tsx, useEditingSession.ts; warp-server/client/src/components/admin/team/PrivacySettings.tsx, admin/SettingStatusFooter.tsx; standard billing/config/tiers policy inheritance
Requested engineering reviewers: none — prior source-owner resolution returned teams, not one certain human owner
Engineering review status: pending
Docs override: none

Validation and evidence

The local extraction passes typecheck, build, heading tests, metadata, and whitespace checks: 5,059 internal links, zero broken. The new page and original infrastructure page were reread in full and checked together. Focused style checks completed with warnings, not a clean pass.

Validation results, source evidence, and limitations

• Extraction checks (uncommitted): Typecheck reported zero errors and seven hints; five heading-variable tests passed; the build generated 420 pages; 3,608 TOC entries and homepage JSON-LD passed. The link check scanned 419 Markdown files and 5,059 links. Both conceptual-page compression checks passed.
• Rendered structure: Confirmed the dedicated page entry under Infrastructure, all four compatibility anchors on the original page, links between both pages, and both browser procedure routes. These checks verify structure and destinations, not visual layout.
• Holistic review: The approximately 471-word ZDR page follows coverage, collection/storage, and configuration choices without duplicating detailed procedures. The infrastructure page retains its deployment purpose with a shorter introduction, a brief retention handoff, and a corrected inference cross-reference. Coverage limitations and the separate Support policy owner remain intact.
• Style: Focused checks found three warnings on the new page (intentional Terminal wording and glossary-missing lead/control terms) and four on the infrastructure page. The earlier full-PR check at a688be1f reported 149 findings versus a same-file baseline of 144. No bulk auto-fixes.
• Earlier checks: UI-reference validation at 577dc772 reported zero issues across 19 pages using client snapshot 1e6c3ae465d6a925a9b97ae03877aaadd159b8f1 (October 23). It is not a current live-dashboard check. The configuration compression check passed below 1,500 words.
• Tooling limits: Trunk is unavailable. Build warnings include deprecated Markdown configuration, large chunks, missing/empty i18n data, and a /404 conflict. Python reports a LibreSSL warning. Dependencies were unchanged; installation was not rerun.
• Product/evidence limits: No new live-product or visual-browser tests were performed. External HTTP checks were not rerun. The original screenshots below predate all editorial revisions and do not verify the revised procedures.
• Source provenance: Factory management mode, save outcomes, privacy UI, and tier inheritance were checked at warp-server@384ff47087fff8efc5256973ba37500aa409263f; earlier override review used 97a0d5c5c4c5d32d3b5e33ab2a5b912a34ea1fc1. The initial draft consulted warp-server@a816b38fb616cd4caaee3efd43f55c521e69df33 and warp@0b2db6e0bf3fa3c19f4c1a94899eb67c634a6973. Source presence is not deployment or contract evidence.
• Training policy: The Privacy Notice, modified August 18, 2026, permits collected data to support model training, fine-tuning, and improvement. Account agreements may differ. No BYOK-specific training exemption was established.
• SOC 2 evidence: The Legal/Security page, retrieved November 12, states that Warp obtained a SOC 2 Type 2 attestation. An individual approver, report revision, and audit period were unavailable; the wording review above remains open.

Editorial review conversation.

Co-Authored-By: Oz oz-agent@warp.dev
Co-Authored-By: Warp agent@warp.dev

Computer-use screenshots (10)

Pricing FAQ scrolled to "How can I enable Zero Data Retention in Warp?" with answer beneath

Factory ZDR section showing defaults, coverage limits and procedure links

Dashboard-managed procedure with six numbered steps

GitHub-backed procedure with six numbered steps and start of Checking new runs

Common Checking new runs subsection

GitHub-backed procedure reached via link, with shared Checking new runs below

Pricing FAQ answer for enabling Zero Data Retention in Warp

Integrated training FAQ with both answer paragraphs visible

Training FAQ section, both paragraphs visible, header not obstructing

Integrated BYOK ZDR section with all three paragraphs visible

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Nov 14, 2026 4:11am UTC

[warp-agent-staging]

Overview

This draft separates provider ZDR, analytics, and product storage and adds Terminal and Factory review steps. Publication is waiting for Engineering/Security confirmation of provider coverage and exception completeness.

Verdict

Checks: build pass, tests pass, CI green, visual proof present

Found: 0 critical, 0 important, 0 suggestions, 0 nits; 1 question

Responding as Docs Factory (V2): Open session · View in factory