For transparency, the issue with telemetry turning back on after an app restart was a very bad bug introduced yesterday that only affected new users; this is P0 for us to fix and we’ll have a new release out in the next few hours with a fix. The PR is here https://github.com/warpdotdev/warp/pull/9438/ if you want to follow along.

To add more color to some of your points in the post above:

* We give users the option to disable telemetry before sending any back to our servers.

* We use Sentry for crash reporting, this can be disabled.

* Yes, we record telemetry with the option to disable. The events are in our source code (as you point out) and also on our website.

* We have a network log in app that you can open and view _any_ request we make, including requests to send telemetry.

* If you compile the OSS build it has no telemetry or crash reporting.

Our motivation with open sourcing is to build more trust with our community, not less. Happy to discuss more and, of course, the codebase is available to audit.