Enterprise > Security and compliance

Security overview

Review provider Zero Data Retention, analytics controls, product storage, and security boundaries across Warp.

Evaluate provider retention, Warp’s analytics collection, and product storage separately when choosing how to use Warp. These controls apply to different copies of your data; turning off analytics doesn’t disable storage needed for a product feature.

Transparency and control

Warp’s security philosophy centers on transparency and developer control:

Complete visibility - View exactly what telemetry is collected through our exhaustive telemetry table
Real-time monitoring - Use Warp’s Network Log to monitor all network requests in real time
Opt-out controls - Disable telemetry and crash reporting at any time while retaining full functionality
Team-level enforcement - Admins can configure telemetry and data collection policies for the entire organization
Open source client - Warp’s client code is published under AGPL v3 at warpdotdev/warp, so security teams can audit the codebase directly. See Contributing to Warp for the source repository and the security reporting process.

Provider retention, analytics, and storage

Zero Data Retention (ZDR)

Provider Zero Data Retention (ZDR) governs whether an inference provider retains prompts and responses. Warp has provider ZDR agreements for supported Warp-managed models across all plans. Covered providers don’t use those prompts and responses for model training. Some models require retention; Model choice lists every known model exception.

Warp-managed inference uses Warp’s provider account, not your own. Turning off Help improve Warp doesn’t make a retention-required model ZDR-covered.

For personal API keys, custom endpoints, team-managed inference, connected provider subscriptions, and BYOLLM, verify ZDR with your provider for the specific account, model, and configuration. Warp’s agreements don’t establish ZDR for customer-managed inference. Claude Code and Codex calls made directly to their providers also use your provider terms, not Warp’s.

Follow the Terminal procedure or factory ZDR guidance for configuration steps, plan controls, and coverage limits.

Warp analytics and improvement collection

Help improve Warp controls product analytics and eligible collection of AI interactions and console content for service improvement. Turning it off stops that analytics and improvement collection, subject to organization-enforced settings. Send crash reports is a separate control.

Neither setting changes a model provider’s retention requirements or turns off product storage. See Privacy and data control for the controls and collected event types.

Product storage

Product features store data independently of provider ZDR and analytics preferences:

Terminal conversations - Store AI conversations in the cloud controls cloud sync of your personal Terminal conversations. Turning it off doesn’t disable factory or other cloud agent run storage. See Cloud-synced conversations.
Factory run data - Transcripts, prompt attachments, and uploaded artifacts persist so you can inspect past runs. They use Warp-managed storage unless an Enterprise admin configures self-hosted agent data storage. Categories are mapped independently; unmapped categories remain with Warp.
Shared sessions and snapshots - Sharing a live session and saving a workspace snapshot have their own storage behavior. See shared-session retention and access and workspace snapshot controls.

Self-hosting factory execution changes where commands run, not whether inference is ZDR-covered or where run data is stored. Evaluate inference and storage separately.

Disabling telemetry

Follow Privacy and data control to change your collection preferences. If your organization manages a control, ask an admin to review the Admin Panel privacy settings.

Data handling and privacy

Where your data lives

Code and files - Stay on your machine unless you explicitly use features that transmit them (e.g., Codebase Context indexing, session sharing, Warp Drive team resources)
Codebase Context - During indexing, code is sent to Warp’s servers to generate embeddings; the raw code is not stored, only the resulting embeddings are retained
Agent requests - Provider retention depends on the model and inference configuration described above.
BYOLLM - Requests are proxied through Warp’s servers to your cloud infrastructure, where inference runs. See customer-managed inference for retention.
Team-managed API keys and endpoints - When an admin configures team-managed API keys and endpoints, the keys are encrypted and stored server-side, never synced to member devices, and never delivered to cloud agent environments. They’re decrypted only in memory when serving a request.
Self-hosted cloud agent execution - Repository checkouts and execution workspaces stay on your infrastructure. Prompts, transcripts, attachments, and uploaded artifacts can contain code context. Inference and run-data storage have separate boundaries.

Encryption

In transit - All data transmitted to Warp servers uses TLS 1.2 or higher
At rest - Warp encrypts all user data at rest using AES-256

Secret redaction

When Secret Redaction is enabled, Warp masks matching sensitive information before sending terminal or AI content to LLM providers. Admins can configure patterns for:

API keys and tokens
Passwords and secrets
SSH keys and certificates
Custom secret patterns (configurable via Admin Panel)

Telemetry payload redaction is a separate mechanism. It applies built-in patterns to telemetry and includes user and Enterprise patterns when they are configured.

See Secret Redaction documentation for details.

Data retention

Inference and product data - See provider retention and feature-specific storage above
Telemetry data - When collected, Warp retains telemetry data indefinitely for analytics and debugging
User accounts - Data deletion requests are processed securely within 30 days at no cost, following verified authentication and compliance with legal and contractual obligations

Compliance and certifications

SOC 2 Type II

Warp is SOC 2 Type II certified, demonstrating compliance with industry-standard security controls for:

Security - Infrastructure protection, access controls, and monitoring
Availability - System uptime and disaster recovery
Confidentiality - Data protection and privacy controls
Processing integrity - Accurate, complete, and authorized processing

SOC 2 reports are available to Enterprise customers upon request.

Infrastructure security

Warp-hosted infrastructure

When using Warp’s hosted infrastructure:

Cloud provider - Hosted on GCP with SOC 2 and ISO 27001 certified datacenters
Network isolation - Workloads run in isolated VPCs with strict network policies

Warp’s operational security practices — including access controls, monitoring, and vulnerability management — are validated through SOC 2 Type II certification. See Compliance and certifications for details.

Self-hosted deployments

Enterprise teams can self-host cloud agent execution to control where agents run and keep repositories on their own infrastructure.

Self-hosted deployments use a split architecture:

Execution plane (customer-hosted) - Repository clones, build artifacts, runtime secrets, and container filesystem state stay on your infrastructure
Control plane (Warp-hosted) - Warp coordinates runs and routes Warp Agent inference. Transcripts can contain code context and persist as product data independently of provider ZDR. Claude Code and Codex call their providers directly.

Two deployment modes are available:

Unmanaged - Use oz agent run to run agents in your existing orchestrator or CI environment. Supports Linux, macOS, and Windows with no Docker dependency.
Managed - Run the oz-agent-worker daemon to let Warp orchestrate agents in isolated Docker containers on your infrastructure.

Agent runs are fully tracked and steerable in both modes. No inbound network access is required.

Network egress requirements

Self-hosted agents require outbound access to Warp’s backend services and, for the managed architecture, Docker Hub and GitHub.

Access controls and authentication

Single Sign-On (SSO)

Warp supports SSO via Okta, Microsoft Entra ID, Google Workspace, OneLogin, and any SAML 2.0 or OpenID Connect (OIDC) compatible provider. Admins can require SSO for all team members and enforce MFA through your identity provider.

See Single Sign-On (SSO) for setup instructions, SCIM provisioning, account linking, and troubleshooting.

Team permissions

Warp uses role-based access control with three roles — Team Owner, Team Admin, and Member — to manage team access and Admin Panel privileges. See User roles and permissions for details.

Resource sharing in Warp Drive has granular controls for who can view, edit, and share.

Admin Panel governance

The Admin Panel gives security and IT teams centralized control over AI behavior, data handling, and sharing policies. Settings can be enforced (overriding individual user preferences organization-wide) or set to respect user setting (deferring to individual preferences).

Security-relevant controls include:

Privacy - Configure user-generated content (UGC) data collection, cloud conversation storage, and enterprise secret redaction
Sharing - Restrict or permit direct link sharing and “anyone with link” sharing permissions
AI - Configure AI autonomy settings and general agent behavior for the team
Models - Control which LLM models are available to team members, including BYOLLM routing through AWS Bedrock and Gemini Enterprise (Vertex AI)
Platform - Configure cloud agent access and settings

Security features for developers

Bring Your Own LLM (BYOLLM)

Route agent inference through your own cloud infrastructure for complete control:

Data locality - Interactive agent inference runs in your AWS account or Google Cloud project
Cloud-native IAM - Authenticate using your user’s existing identity and access management process
No key storage - Warp never stores your cloud credentials or API keys
Billing control - Inference costs billed directly to your cloud account

See Bring Your Own LLM for configuration details.

Docker Sandboxes

Isolate agent execution in containerized environments:

Process isolation - Agents run in separate Docker containers, isolated from your host system
Resource limits - Configure CPU, memory, and disk quotas per sandbox
Network controls - Restrict outbound network access from sandboxes
Ephemeral environments - Sandboxes are destroyed after use; saved snapshots and run data have separate storage behavior

Agent permissions

Configure what agents can access and execute:

Tool restrictions - Enable/disable terminal use, code editing, web search, and file system access
Repository scoping - Limit agents to specific repositories or directories
Execution approvals - Require manual approval for sensitive commands
Visibility - When cloud conversation storage is enabled, agent actions are logged with full context for review

Incident response and support

Security issue reporting

If you discover a security vulnerability in Warp:

Email security@warp.dev.
Include detailed steps to reproduce.
Do not publicly disclose until Warp has addressed the issue.

Warp follows responsible disclosure practices and works with reporters to coordinate disclosure timelines.

Enterprise support

Enterprise customers receive priority security support:

Dedicated channels - Private Slack/Teams channels for security questions
Security advisories - Proactive notifications of security updates
Incident assistance - Support during security incidents or breach investigations
Compliance assistance - Help with compliance questionnaires and audits

Warp privacy policy
Warp Trust Center — security documentation and compliance reports. See also Trust Center for details on requesting SOC 2 reports, subprocessors, and vendor security assessments.
Warp subprocessors list
Privacy documentation - Privacy guide with complete telemetry table
Contact - privacy@warp.dev for privacy questions, security@warp.dev for security issues