docs: Separate provider ZDR from analytics and product storage

src/content/docs/agents/getting-started/faqs.mdx

@@ -21,7 +21,9 @@ Agent Mode has replaced the previous AI chat panel. Agent Mode is more powerful
 
 ### Is my data used for model training?
 
-Warp reserves the right to use data collected to train models and improve Warp. Warp has Zero Data Retention with all its model providers (e.g. Anthropic, OpenAI, xAI, etc.). Learn more about telemetry on our [Privacy page](/support-and-community/privacy-and-security/privacy/).
+Warp may use collected data to train and improve models that support its AI features, as described in the [Privacy Notice](https://www.warp.dev/legal/privacy-policy). Turning off the **Help improve Warp** toggle stops analytics and eligible content collection for service improvement, subject to organization-enforced settings.
+
+When a request falls under Warp's [provider ZDR agreements](/support-and-community/privacy-and-security/privacy/#zero-data-retention-zdr), the AI provider cannot use its prompts or responses for training. Some models require provider retention and are excluded from ZDR. See the [model exceptions](/agents/inference/model-choice/#models-requiring-provider-retention) and the [separate controls for Warp's analytics and storage](/support-and-community/privacy-and-security/privacy/#provider-retention-analytics-and-storage).
 
 ### What model are you using for Agent Mode?
 

src/content/docs/agents/index.mdx

@@ -70,7 +70,7 @@ To automate more of your team’s software development, use Warp Factories, the
 
 ## Privacy and security
 
-Warp is **SOC 2 compliant** and has **Zero Data Retention** policies with all contracted LLM providers. No customer AI data is retained, stored, or used for training.
+Warp is **SOC 2 compliant**. Provider ZDR governs what AI providers retain. Warp's [analytics and conversation-storage settings](/support-and-community/privacy-and-security/privacy/#provider-retention-analytics-and-storage) are separate controls. Review the [provider ZDR policy](/support-and-community/privacy-and-security/privacy/#zero-data-retention-zdr) and [models that require retention](/agents/inference/model-choice/#models-requiring-provider-retention) before choosing a model. For factory runs, start with [factory ZDR guidance](/factories/zero-data-retention/).
 
 You can disable Warp's AI features entirely in **Settings** > **Agents** > **Warp Agent**.
 

src/content/docs/agents/inference/bring-your-own-api-key.mdx

@@ -105,15 +105,11 @@ You can update or replace your keys anytime by opening **Settings** and searchin
 
 ### Zero Data Retention (ZDR) and BYOK
 
-Warp is **SOC 2 compliant** and has **Zero Data Retention (ZDR)** policies with all of its contracted LLM providers. No customer AI data is retained, stored, or used for training by the model providers.
+Warp has a [SOC 2 Type 2 attestation](https://www.warp.dev/legal/security). Its [provider ZDR policy](/support-and-community/privacy-and-security/privacy/#zero-data-retention-zdr) applies to supported models accessed through Warp's provider accounts, but not to requests made through your own key.
 
-BYOK prompts and responses transit Warp's backend (see [How BYOK works](#how-byok-works)). Warp does not use this content for training; retention and analytics handling follow the same account-level privacy and telemetry settings that apply to Warp-billed traffic.
+Provider-side retention for BYOK depends on your provider account settings. Verify ZDR with your provider for the specific account, model, and configuration. Warp cannot enforce provider ZDR for BYOK.
 
-However, when you use your own API key:
-
-* Data retention policies on the **provider side** depend on your provider’s account settings.
-* Warp cannot enforce ZDR for requests sent through your API keys.
-* If your Anthropic, OpenAI, or Google account does not have ZDR enabled, your requests may be retained by the provider according to their terms.
+BYOK prompts and responses [pass through Warp's backend](#how-byok-works). Warp applies your account's privacy settings to this content, including any settings enforced by your organization. **Help improve Warp** controls collection for analytics and improvement. **Store AI conversations in the cloud** controls [cloud storage of your personal Terminal conversations](/agents/local-agents/cloud-conversations/). Neither setting changes your provider's retention rules. See the [analytics and storage controls](/support-and-community/privacy-and-security/privacy/#provider-retention-analytics-and-storage) for details.
 
 ### BYOK on Business and Enterprise plans
 

src/content/docs/agents/inference/custom-inference-endpoint.mdx

@@ -83,17 +83,9 @@ Other features use their own inference configuration and are unaffected by a per
 
 ## Zero Data Retention (ZDR)
 
-Warp is **SOC 2 compliant** and has **Zero Data Retention (ZDR)** agreements with all of its contracted LLM providers.
+Warp cannot enforce provider ZDR for your endpoint. You'll need to verify retention with the endpoint provider and any upstream model providers for your specific account, model, and configuration. Those providers' terms apply to these requests.
 
-Custom inference endpoint prompts and responses transit Warp's backend (see [How it works](#how-it-works)). Warp does not use this content for training; retention and analytics handling follow the same account-level privacy and telemetry settings that apply to Warp-billed traffic.
-
-When you use a custom inference endpoint:
-
-* Data retention on the **provider side** is determined by your endpoint provider and any upstream model providers they route to.
-* Warp **cannot enforce ZDR** for requests sent through a custom inference endpoint.
-* If your endpoint provider does not have ZDR with the underlying model provider, your requests may be retained according to their terms.
-
-Review your endpoint provider's data handling and retention policies before routing sensitive prompts through a custom inference endpoint.
+Prompts and responses still [transit Warp's backend](#how-it-works). Review [Warp's separate analytics and storage controls](/support-and-community/privacy-and-security/privacy/#provider-retention-analytics-and-storage). These controls don't change your provider's terms.
 
 ## Centrally managed configuration
 

src/content/docs/agents/inference/model-choice.mdx

@@ -73,7 +73,7 @@ Suffixes select effort level. `xhigh-fast` enables fast mode, and `thinking` ena
 Claude Haiku 5.5 has no fixed default `model_id`; choose one of its effort-specific IDs.
 
 :::caution
-Anthropic requires data retention for Claude Fable 5, Claude Fable 5.1, and Claude Fable 5.2 for safety, abuse monitoring, and compliance reasons, so these models are **not available under Zero Data Retention (ZDR)**. This requirement is specific to the Claude Fable models and doesn't change the ZDR behavior of any other supported model. For Enterprise teams, these models are off by default and a workspace admin must enable them — see the [Admin Panel](/enterprise/team-management/admin-panel/#models-settings) and the [Security overview](/enterprise/security-and-compliance/security-overview/#zero-data-retention-zdr).
+Some Anthropic models require data retention regardless of your **Help improve Warp** setting. Check [models requiring provider retention](#models-requiring-provider-retention) before selecting a model.
 :::
 
 #### Google
@@ -155,23 +155,31 @@ You can configure the base model for each [Agent Profile](/agents/capabilities/a
 
 Edit your default profile or any other profile directly in **Settings** > **Agents** > **Profiles**.
 
+### Reviewing inference and privacy in Terminal
+
+Before sending sensitive content through Warp Terminal:
+
+1. In the Warp app's prompt input, click the model name and choose a model outside the [exception list](#models-requiring-provider-retention).
+2. In **Settings** > **Agents** > **Profiles**, review the active profile's base model. For a [custom router](/agents/inference/custom-routers/), review every target and its default.
+3. In **Settings** > **Agents** > **Warp Agent**, review personal keys, endpoints, and subscriptions, plus any [team configuration](/enterprise/enterprise-features/team-managed-keys-and-endpoints/). Search Settings for `API keys` to find personal keys. For customer-managed inference, verify provider ZDR; review [BYOK fallback](/agents/inference/bring-your-own-api-key/#failover-and-fallback-behavior) if enabled.
+4. In **Settings** > **Privacy**, review **Help improve Warp**, **Send crash reports**, and **Store AI conversations in the cloud** separately. See [analytics and storage controls](/support-and-community/privacy-and-security/privacy/#provider-retention-analytics-and-storage).
+
+Confirm the model displayed before your next prompt. For factories, use [factory ZDR guidance](/factories/zero-data-retention/) instead.
+
 ### Zero data retention policies
 
-Warp integrates with multiple large language model (LLM) providers to power its AI-driven features.
+Warp has provider Zero Data Retention (ZDR) agreements for supported Warp-managed models on all plans. See [Privacy and data control](/support-and-community/privacy-and-security/privacy/#zero-data-retention-zdr) for the policy.
 
-**These providers include, but are not limited to:**
+Current Auto selections and fallback chains for other models don't introduce the exceptions below. For separate model settings and coverage limits in factories, use [factory ZDR guidance](/factories/zero-data-retention/).
 
-* OpenAI
-* Anthropic
-* Google
-* xAI
-* Fireworks AI
+#### Models requiring provider retention
 
-Warp has executed **Zero Data Retention (ZDR)** agreements with these providers. This means that, by default across all plans:
+Anthropic requires data retention for safety, abuse monitoring, and compliance. This requirement applies to the following models at every effort level:
 
-* LLM providers commit not to train their models on any customer-generated data processed through Warp’s services.
-* LLM providers commit to delete inputs and outputs after generating the relevant output, within a fixed time period.
+* Claude Fable 5
+* Claude Fable 5.1
+* Claude Fable 5.2
 
-Warp enforces these commitments through both technical measures and contractual safeguards with the LLM providers.
+These models aren't covered by provider ZDR even when **Help improve Warp** is off. For Enterprise teams, they are disabled by default and a workspace admin must enable them in the [Admin Panel](/enterprise/team-management/admin-panel/#models-settings).
 
-Zero data retention is available for supported models. Model availability may vary where providers require data retention for safety, abuse monitoring, or compliance reasons.
+If you use your own provider account, [verify retention with your provider](/support-and-community/privacy-and-security/privacy/#zero-data-retention-zdr). Choosing a model outside this list doesn't mean your account has ZDR.

src/content/docs/agents/local-agents/cloud-conversations.mdx

@@ -20,15 +20,15 @@ Warp can sync your [agent conversations](/agents/local-agents/interacting-with-a
 
 ## Enabling cloud conversations
 
-Cloud conversation sync is controlled by a setting in Warp:
+To control whether your personal Warp Terminal conversations sync to the cloud:
 
-1. Open **Settings** > **Privacy**
-2. Enable **Store AI conversations in the cloud**
+1. In the Warp app, open **Settings** > **Privacy**.
+2. Toggle **Store AI conversations in the cloud** on or off.
 
-When enabled, your Agent conversations automatically sync to the cloud as you interact with the Agent. When disabled, conversations are stored locally on your machine only.
+When **Store AI conversations in the cloud** is on, your personal Terminal conversations sync as you interact with the agent. When it's off, those conversations are stored only on your device. The **Help improve Warp** toggle controls collection for analytics and improvement, not conversation sync. See [analytics and storage controls](/support-and-community/privacy-and-security/privacy/#provider-retention-analytics-and-storage).
 
 :::caution
-If cloud conversations are disabled, conversation data is lost when you log out and cannot be shared with others. Cloud agent conversations are always stored in the cloud regardless of this setting.
+If personal cloud conversation sync is disabled, local conversation data is lost when you log out and cannot be shared with others. Factory and other cloud agent runs still store their transcripts, attachments, and artifacts independently of this setting.
 :::
 
 ## How it works
@@ -93,7 +93,7 @@ Cloud-synced conversations store snapshots of conversation data. For real-time c
 
 ## Cloud agent conversations
 
-[Cloud agents](/platform/) run in the cloud, and their conversations are automatically stored regardless of your local cloud conversations setting.
+Conversations from [cloud agents](/platform/), including factory agents, are stored even if you turn off personal conversation sync or analytics. By default, run data is stored by Warp. Enterprise admins can instead configure [self-hosted agent data storage](/factories/self-hosting/data-storage/). Provider ZDR does not prevent storage of these conversations.
 
 ### Accessing cloud agent conversations
 
@@ -110,13 +110,12 @@ This is useful when a cloud agent completes a task and you want to review what i
 
 ### Enterprise controls
 
-Enterprise administrators can disable cloud conversation storage for their organization through the [Admin Panel](/knowledge-and-collaboration/admin-panel/).
+Enterprise administrators can disable cloud sync for personal Warp Terminal conversations through the [Admin Panel](/enterprise/team-management/admin-panel/#privacy-settings).
 
-When cloud conversation storage is disabled by your organization:
+When your organization disables this setting:
 
-* Conversations are stored locally only and not synced to the cloud
-* You cannot share conversations or access them across devices
-* Cloud agent conversations are still accessible through the Warp dashboard
+* Your personal Terminal conversations remain on your device and cannot be shared or accessed across devices.
+* Cloud agent conversations remain accessible through the Warp dashboard.
 
 ### Storage limits