What the app sends to us
Update check. The app regularly asks api.openchamber.dev whether a newer version
exists. The request carries the app version, the operating system, the processor architecture, the kind of app
(desktop, VS Code, web or mobile) and a random installation ID created on your device.
We use the installation ID only to count unique installations. It is not linked to a name, an email address, an account or anything else that identifies a person. The server stores a keyed hash of the ID, never the ID itself, together with the details above and the dates of the first and latest check.
To stop sending the ID, turn off "Send anonymous usage reports" in Settings, General, Privacy. The update check keeps working without it.
Features that send data only when you turn them on
- Private Relay connects your phone to your computer through
relay.openchamber.dev. Traffic is end-to-end encrypted between your devices, and the relay passes it on without being able to read it. - Push notifications in the mobile app go through
api.openchamber.devto Apple. The readable part is a fixed title, such as "Agent response is ready", and the session name. Anything more is encrypted so that only your phone can read it. - Linear sign-in passes a short-lived authorization code through
api.openchamber.dev. Your Linear tokens stay on your computer. - AI providers, GitHub, GitLab, Cloudflare and ngrok tunnels connect directly from your computer to those services. Their own privacy policies apply.
What the app downloads
The app downloads the public model list from models.dev and new versions from GitHub Releases. These
downloads carry nothing about you.
Website
openchamber.dev and the docs use Google Analytics to count visits. Google's privacy policy applies to that data.
Questions
Write to [email protected] or open an issue on GitHub.
Last updated October 22, 2026.