Privacy

Terminal sessions may contain sensitive information and Warp prioritizes sending minimal data over the network to maintain user privacy. Telemetry data never includes console input or output.

Our philosophy is complete transparency around any data leaving your machine. This means you can:
Note that this page does not contain our official privacy policy - for that please see this pdf that basically says the same thing in much less readable legal language.

Our Product

Our product is a fully-native, local app that runs fine with no internet connection whatsoever (although you will lose some of our cooler features).  By default, we do not process any content from your terminal session on our servers. 

We do collect login email, crash-reports, and generic telemetry (things like whether a block has been created or whether a user has used our AI command search). This information helps us improve user experience and monitor the health of our application.  You can choose to opt-out of telemetry if you wish.

Our Business Model

The app is 100% free for any and all individuals. Our business plan is to create collaborative and cloud-based features that businesses will be willing to pay for. Please check out our pricing page to learn more.

Please note that our business model is not about collecting and monetizing any of your personal data.

Open Source

Our plan is to eventually open-source the Rust client code and related projects, like our UI framework. The server portion of Warp will remain closed-source for now.

However, we have open-sourced some of Warp’s extension points, like themes and workflows. We would love it if you checked out the Github repos and contributed to our growing community!

We’ve committed to open-sourcing all Warp code (client and server), should the company ever cease operations.

Specifics

By default, none of your command input or output is ever sent to our servers. 

Unless you specifically choose to use a cloud feature like Block Sharing and AI Search, you can feel completely comfortable that no data is being uploaded in the background (except for generic telemetry events and crash reports).

Login

At this time, Warp continues to require login.  The primary reason is that login allows us to build cloud-oriented features that make the terminal have a concept of “your stuff” and “your team’s stuff” – for example Block Sharing.  This is the same reason other collaborative apps like Figma and Github require login – identity is the basis of building cloud-native apps.

That said, we understand the desire to try Warp before logging in and are exploring product experiences that will allow users to preview Warp before signup.

Telemetry

We send telemetry events by default and associate them with the logged-in user. You can see a full list of telemetry events here. You can also monitor all communications from the Warp client to the external servers with our native Network Log Console.

Telemetry makes it much easier to reach out for feedback if something goes wrong. Terminal input and output are never included in telemetry payloads. We track things like whether the user has created a new block, looked through our welcome tips, or used our AI Command Search feature. Information like this helps us improve our product and correctly prioritize engineering work.