Privacy Policy
Last updated: June 29, 2026
Calyx is a macOS terminal application that runs locally. This page describes the data Calyx handles and the network traffic it generates.
User information collected
Section titled “User information collected”Calyx does not collect any user identifiers, usage logs, or crash reports. No analytics or telemetry is sent.
The developer has no way to observe your launch times, feature usage, or input.
Information stored locally
Section titled “Information stored locally”Calyx stores the following on your machine to restore state and run features. None of it is sent off your machine.
- Open tabs, splits, and per-tab working directories (for session restore)
- Terminal scrollback (in memory, within the session)
- AI agent integration configs (
~/.claude.jsonand the equivalents for other agents) - Browser server connection info (
~/.config/calyx/browser.json) - Background language server processes for the LSP proxy
- Browser tab storage (non-persistent — discarded when the tab closes)
Outbound network traffic
Section titled “Outbound network traffic”The only outbound traffic Calyx initiates is the following.
1. Auto-update (Sparkle)
Section titled “1. Auto-update (Sparkle)”The directly-downloaded build fetches the Appcast on launch to check for new versions.
- URL:
https://yuuichieguchi.github.io/Calyx/appcast.xml - Content: version info, release notes, and download URLs
- Downloads are verified against a public key signature before installation
2. Release asset download
Section titled “2. Release asset download”When you accept an update, Calyx downloads the new build from GitHub Releases. This happens only after you confirm in the update dialog.
3. Language server auto-install (optional)
Section titled “3. Language server auto-install (optional)”If you enable auto-install in Settings under LSP Proxy, Calyx downloads missing language servers via package managers. This feature is off by default.
4. Browser tab requests initiated by you
Section titled “4. Browser tab requests initiated by you”URLs you load in a browser tab generate normal browser traffic. Storage is non-persistent and is discarded when the tab closes.
Locally-running servers
Section titled “Locally-running servers”Calyx hosts several servers inside its own process.
They listen on the loopback interface (localhost) and are not exposed to the network.
- AI Agent IPC MCP server: used by AI agents on the same machine
- Browser automation server:
localhost:41840, used by thecalyx browserCLI
They do not accept connections from outside the machine, so no firewall-crossing traffic is generated.
Interactions with AI agents
Section titled “Interactions with AI agents”When you use AI agents (Claude Code, Codex CLI, OpenCode, Hermes) through Calyx, the prompts you type and the responses you receive flow through Calyx and appear in the terminal, but Calyx itself does not record or transmit them.
What each agent sends to its provider’s API is governed by that agent’s own privacy policy.
Diff review comments
Section titled “Diff review comments”Review comments you create from the sidebar Git view are sent only to the AI agent tab you select with Submit Review. They are not sent to GitHub or any other external service.
Differences by install type
Section titled “Differences by install type”- Homebrew install: Sparkle auto-update is disabled. Updates flow through
brew upgrade. The Appcast is not fetched. - Direct download: “Auto-update” and “Release asset download” above apply.
Changes to this policy
Section titled “Changes to this policy”This policy may be updated as features change. Updated versions take effect when published on this help site.
Contact
Section titled “Contact”Questions about privacy can be filed on GitHub Issues.
