Skip to content

Privacy & telemetry

Wyrm works on your machine. Your repositories, their history and your files are never uploaded anywhere. The app talks to the network when you ask it to (fetch, push, pull requests), to check for updates, to keep you signed in, and to look up whether a repository is private (see Account, trial & billing).

On first launch the welcome tour asks Help us fix bugs. Click Enable to send anonymous crash reports, or Skip to leave them off. Until you answer, nothing is sent. Skipping the rest of the tour doesn’t skip this question.

To change your answer later, open Settings… (⌘,) → General → Privacy & diagnostics and switch Send crash reports. It takes effect immediately. With it on, Send a test report checks that reports get through.

Some builds come without crash reporting at all. They say so in the same place: “This build doesn’t include crash reporting, so Wyrm sends no crash or performance data.”

Reports go to Sentry and contain:

  • crashes, panics and unhandled errors, with their stack traces;
  • the anonymous performance timings the app measures;
  • the app version, the operating system and its architecture, and your locale;
  • an anonymous device ID, a random value kept in your keychain.
  • your email address, name or account ID;
  • your IP address or your computer’s name;
  • repository paths, commit messages, bookmark names or file contents.

Paths into your home folder are cut down to <repo>/ plus the file name before anything leaves the app, and passwords or tokens inside URLs are replaced with <redacted>.

Help → Send Feedback / Report an Issue sends a message to us. Include a diagnostic report adds a short, redacted log excerpt plus app, OS and repository-layout facts (no names, paths, file contents or email). Click Preview what’s included to read exactly what will be sent, or use Copy report / Save report… to keep it yourself.

The setting lives in your jj user config. This turns crash reports off:

Terminal window
jj config set --user gg.ui.telemetry-enabled false

For how the website handles your data, see the privacy policy and the security page.