[ Reference ]
Data and privacy
What Kanbell contacts on the network and when, what it stores on your machine, and which agent folders it reads but never writes.
Kanbell has no account and no Kanbell server. It goes online for three reasons only: your license, updates, and the GitHub or GitLab board you chose. Everything else stays on your machine.
What Kanbell contacts, and when
- Polar (
api.polar.sh), for the license: when you activate or deactivate it, at launch (without blocking), and every 24 hours. It sends the key, the organization id, a machine label such as "Kanbell · macOS · xxxx", the app version and the architecture. The trial is fully local and uses no network. - GitHub Releases, for updates: 1 minute after launch, then every 6 hours, and when you click Check for Updates. macOS only.
- GitHub API: only if you connect GitHub and a project uses a GitHub board.
- GitLab API: only the servers you enter, over https only.
What Kanbell never sends
- No analytics.
- Crash reports stay on your machine.
- Remote images in Markdown are not loaded.
- The hook server and the CLI server listen only on
127.0.0.1. - External links open in your browser.
What stays on your machine
Kanbell keeps its data in the app data folder (~/Library/Application Support/Kanbell on Mac):
- config and profiles
- sessions (never the text of your prompts)
- layout
- personal notes
- pasted images
- logs
Your GitHub and GitLab tokens and your license are sealed with the system keychain. On Linux, Kanbell refuses GitHub and GitLab tokens if there is no real keyring.
What Kanbell reads but never writes
Kanbell reads agent transcripts under ~/.claude, ~/.codex and ~/.gemini. It never writes there. To track agents, it injects its hooks into each session instead of changing your agent config.
What Kanbell writes outside its folder
- Repo notes and files you edit in Kanbell.
- The project folder created when you choose Start from scratch with Claude.
- The trial marker.
Privacy Policy
The full text is in the Privacy Policy.
Updated