Privacy

perch runs on your machine and is built to keep your work there. It has no analytics, no telemetry, and no crash reporting. It does not send usage data, identifiers, or the contents of your terminals to the app's author or to any third-party tracking service.

Last updated: July 2026

This page describes what perch itself does over the network. It does not cover the separate agent CLIs and shells you choose to run inside perch's panes (see Tools you run inside perch below).

What stays on your machine

These never leave your device by any action of perch:

Network connections perch makes

perch itself contacts exactly three endpoints, all first-party or public:

PurposeEndpointWhat is sentWhen
Update check + download github.com (this repo's Releases) Nothing personal — a normal request for the public release feed On the app's update checks
Claude usage display api.anthropic.com Uses the Claude sign-in that Claude Code already manages, to read your usage and limits Only when you're signed in to Claude
Cloud price estimates cloudbilling.googleapis.com Nothing personal — a request for Google Cloud's public price list When computing cost estimates

Tools you run inside perch

perch runs other programs for you. When you run an agent CLI or shell command in a pane (for example Claude Code, Codex, gcloud, or any other program), that tool does its own networking under your own accounts and credentials. perch launches it and displays its output; it does not intercept, reroute, or transmit that tool's data anywhere. What those tools send, and to whom, is governed by their privacy policies, not this one.

Changes

If perch's network behavior changes, this policy changes with it in the same release. If you find a discrepancy between this page and what the app actually does, please report it via SECURITY.md.