# What does local-first mean for Perch?

Canonical: https://perched.fyi/glossary/local-first/
Updated: 2026-10-23

For Perch, local-first describes where its app data and interactions live: on your Mac. The app has no account or server and makes no network requests.

## Name the data and its lifetime

Perch saves status and notes locally. Pending answer requests stay in memory and are discarded once answered. Commands, prompts, diffs and transcripts are not saved as Perch session history.

The phrase local-first is useful here because it points to concrete behavior. The privacy policy is the source for the full description of what is read, stored and discarded.


## Keep other services separate

Your coding agent may still connect to its provider. Perch’s local design does not turn that service into offline software or change its privacy policy.

The website also has separate handling for launch-list signups, hosting, analytics and future payments. A claim about the Mac app should not be read as a claim about every linked service.


[Read the privacy policy](https://perched.fyi/privacy/)

## Related reading
- [What Perch stores and which permissions it needs](https://perched.fyi/guides/privacy-and-permissions/)
- [Why an agent status monitor does not need your transcripts](https://perched.fyi/blog/status-without-transcripts/)