Reference
Privacy & data
What Beetool stores, where, and what leaves your Mac.
What leaves your Mac
- Nothing to us. Beetool has no telemetry.
- Git hosts you add, for merge requests.
- AI providers, only when you run something with AI, through the account you connected — or nothing at all with a local model.
- What you point a tool at: the databases, hosts and URLs you connect to in Database, SSH, Beequest and Network, and the js-debug download for Node debugging.
Logs never contain tokens or source code.
Secrets
In the macOS Keychain (service "Beetool"): Git tokens, AI keys and tokens, SSH keys and passphrases, logins, env values, database passwords and the MCP token.
Where data lives
| What | Where |
|---|---|
| Settings, conversations, history, drafts | ~/Library/Application Support/beetool (Settings › Advanced › Reveal) |
| Logs and terminal recordings | ~/Library/Logs/Beetool |
| Caches (worktrees, extracted text) | Your user cache folder |
| Shared with your team, in the repository | .beetool/run.json, .beetool/knowledge/, .beetool/templates/ |
Language servers, the repo map and the code index run on your Mac. AI usage and the run ledger keep names and numbers only. The MCP server listens on 127.0.0.1 with a token.