Privacy Policy
We collect no telemetry by default.
Yep Anywhere runs entirely on your own machine. There are no accounts, no cloud services, and no databases. Your sessions and data stay local.
Network Requests
The application makes minimal network requests:
- Yep Anywhere update service — The app periodically checks
updates.yepanywhere.comfor version information, and opening Settings → About or using the manual update check triggers a fresh check. These requests include the running app version and an installation identifier so we can maintain relay compatibility, monitor rollout reliability, and support backwards compatibility. - Your AI provider — When you run sessions, requests go directly to your configured AI provider (Anthropic, OpenAI, etc.) using your own API keys.
Aside from update/version checks to updates.yepanywhere.com, app data is not sent to yepanywhere servers. We do not send session contents, prompts, or files to that service.
Local Data Storage
All data is stored locally on your machine:
- Session transcripts (managed by the Claude SDK in
~/.claude/projects/) - Server state including logs, uploads, and settings (in
~/.yep-anywhere/) - Push notification VAPID keys (generated locally, no third-party service)
- Optional password hash if you enable authentication
Public Relay (Future)
We're building an optional public relay service to enable secure remote access without requiring Tailscale or port forwarding. If you choose to use the public relay:
- Connection metadata (timestamps, bandwidth usage) will be logged to prevent abuse
- Message content is end-to-end encrypted — the relay cannot read your conversations
- This is entirely opt-in; local-only usage will always be available
- You can also self-host your own relay server
This Website
This website (yepanywhere.com) loads fonts from Google Fonts, which means Google receives requests when you view these pages. We don't use any other analytics or tracking services on the website.
Open Source
Yep Anywhere is 100% open source under the MIT license. You can inspect the code to verify these claims.
We publish to npm using trusted publishing with provenance attestation directly from GitHub Actions. Every published package links back to the exact source commit and CI workflow run, so you can verify that the code on npm matches the code on GitHub.
Last updated: January 2026