Skip to main content

Buyer guide

Warp Security & Data Checklist

The settings to agree on before Warp touches company code: zero data retention, telemetry defaults, secret redaction, SSO, BYOLLM, agent permissions, and self-hosted execution.

Reading time
3 min read
Sources
15 cited
In this piece
Warp+30 Positive

Before engineers connect company code, settle where inference goes, what Warp collects, and how secrets are masked. Then set sign-in controls and define what the agent can run. Each check names the plan that carries the control.

When you need this

  • Security has to approve a terminal that sends commands and output to model providers.
  • Engineers installed Warp on their own and you need one enforced configuration.
  • You are deciding between Business and Enterprise and need to know which controls each carries.

Security review checklist

  1. Zero data retention scope

    Which requests are covered, and which are not?

    SetWarp's agreements with Anthropic, OpenAI, Google, xAI, and Fireworks AI cover Warp-provided inference on every plan. Requests through your own keys, a connected subscription, or a custom endpoint follow that provider's terms. Some models have provider retention requirements that exclude them from zero data retention. On Enterprise, those models stay off until an admin enables them.

  2. Telemetry and data collection

    Is collection on or off by default for your plan?

    SetOn Business and Enterprise, data collection is off by default and admins enforce it for the team. On Build and Max teams it is on by default, and each user can turn off Help improve Warp in Settings. Warp publishes every telemetry event and shows live requests in its network log.

  3. Secret Redaction

    Are credentials masked before a request leaves the machine?

    SetSecret Redaction is off by default. Turn it on with Warp's recommended patterns plus your own, and on Enterprise enforce it from the Admin Panel so no one can switch it off.

  4. Identity

    How do people sign in and lose access?

    SetSAML SSO from Business, set up with Warp through WorkOS, with Okta, Microsoft Entra ID, Google Workspace, OneLogin, or any SAML or OIDC provider. Admins can require SSO. Provisioning is just-in-time with domain auto-join, and removing a user in the identity provider blocks new sign-ins without ending existing sessions.

  5. Agent permissions

    What can the agent run without asking?

    SetAdmin-enforced autonomy, command denylists, and model policies are Enterprise features. On lower plans each engineer sets their own profile. Keep the denylist bypass for auto-approve turned off.

  6. Model routing and hosting

    Where do model calls and cloud runs execute?

    SetEnterprise BYOLLM routes eligible requests through Claude on AWS Bedrock or Gemini and Claude on Google Vertex AI, with no stored keys. Vertex does not serve cloud agents yet. Warp-hosted cloud agents run in ephemeral Docker containers on Google Cloud. Self-hosted execution keeps clones and secrets on your machines, and transcripts and inference still route through Warp's backend.

  7. The client itself

    Can your security team read the code?

    SetThe client is open source under AGPL v3 at github.com/warpdotdev/warp, published on April 27, 2026. Warp holds a SOC 2 Type II attestation, with the report available through its Trust Center.

Questions to settle before rollout

  1. Warp's legal security page offers zero data retention on Enterprise, while its pricing and docs apply it to every plan. Which does the contract state?
  2. Which models outside zero data retention are enabled for our team, and who approved them?
  3. How long are shared sessions kept? Warp's documentation says about one week, with no way to delete one sooner short of deleting the account.
  4. Does a security incident on a self-hosted run expose transcripts held by Warp?

Red flags

  • A Build or Max team handling regulated code with data collection left on by default.
  • Personal API keys in use where the company has no agreement with that provider.
  • Secret Redaction off on machines that hold production credentials.
  • Deprovisioning relied on to end sessions immediately.

Products in this piece

Sources

Official documentation
15
  1. Warp docs: Security overviewOfficial documentationdocs.warp.dev
  2. Warp docs: Privacy and data controlOfficial documentationdocs.warp.dev
  3. Warp docs: Warp network logOfficial documentationdocs.warp.dev
  4. Warp docs: Secret RedactionOfficial documentationdocs.warp.dev
  5. Warp docs: Single Sign-On (SSO)Official documentationdocs.warp.dev
  6. Warp docs: Admin Panel for teamsOfficial documentationdocs.warp.dev
  7. Warp docs: Bring Your Own LLMOfficial documentationdocs.warp.dev
  8. Warp docs: Team-managed LLM API keys and endpointsOfficial documentationdocs.warp.dev
  9. Warp docs: Architecture and deploymentOfficial documentationdocs.warp.dev
  10. Warp docs: Security and networking for self-hosted agentsOfficial documentationdocs.warp.dev
  11. Warp docs: Agent Session SharingOfficial documentationdocs.warp.dev
  12. Warp: PricingOfficial documentationwarp.dev
  13. Warp: SecurityOfficial documentationwarp.dev
  14. Warp on GitHub: warpdotdev/warpOfficial documentationgithub.com
  15. Warp docs: Changelog 2026Official documentationdocs.warp.dev

Keep reading

  1. Buyer guideWarp Agent Working Playbook: From Rules to a Reviewed DiffSix team settings for the Warp Agent, including what auto-approve runs by default and how many codebases each plan indexes.
  2. Buyer guideWarp Team Rollout Checklist: Plans, Spend Limits, and What to MeasurePick Build, Max, Business, or Enterprise by the controls you need. Set spend caps and BYOK terms, then judge the pilot on merged work and cost.
  3. Buyer guideWarp Cloud Agents & Factories: Triggers, Harnesses, and Who ApprovesWhich work starts from Slack, Linear, GitHub, or a schedule, which agent runs it, where it executes, and who reviews the pull requests that come back.
Read the research