Privacy Policy
Last updated: October 6, 2026
The short version
Kitbar runs on your Mac or your Windows PC. It has no account of its own, and no server of ours sits between you and your tools. It talks to the services you connect, directly, and to a few places of ours listed below. This page covers both apps; where they differ, it says so.
The tools you connect
Kitbar reads each tool with a key or a sign-in you give it. That key or token is sent only to the service it belongs to, over HTTPS, as often as you choose in Settings (every 30 seconds by default). Kitbar never sends it anywhere else, and we never see it.
- Vercel (api.vercel.com): your teams, projects and their deployments; a redeploy when you ask for one.
- Cloudflare (api.cloudflare.com): your accounts, Pages projects, Workers and their builds; a retry or a new build when you ask for one.
- GitHub (api.github.com): your repositories, their commits, workflow runs, commit statuses and deployments; a re-run when you ask for one. Your avatar comes from github.com.
- GitLab (gitlab.com): your groups, projects, pipelines and jobs; a retry when you ask for one.
- Stripe (api.stripe.com): your account's name and the latest charges, with the customer's name and email as Stripe holds them. Nothing can be changed from Kitbar.
- Polar (api.polar.sh): your organizations and the latest orders, with the customer's name and email as Polar holds them. Nothing can be changed from Kitbar.
- Claude, with an admin key (api.anthropic.com): your organization's cost and usage reports.
- Codex, with an admin key (api.openai.com): your organization's cost and usage reports.
A project's icon is fetched once per launch from the website the project is live on (the page's own icon), without any key. That is a request to your own site.
How a tool is connected
- A command-line tool that is already signed in. If the GitHub CLI (gh), the GitLab CLI (glab) or Wrangler is signed in on your computer, Kitbar can use that sign-in. It asks the tool for its current token with the tool's own command and keeps the token in memory only. It never signs the tool in or out, and never refreshes its token. On Windows, Kitbar can also use the Vercel CLI and the Stripe CLI. For Vercel, it reads the CLI's sign-in file without changing it, and runs "vercel whoami" so that the CLI refreshes itself. For Stripe, the CLI makes the request itself, so Kitbar never sees a Stripe key.
- Sign in with GitHub, GitLab, Polar or Cloudflare. Your browser opens the service's own sign-in page. The service sends a one-time code back to Kitbar on your computer, and Kitbar exchanges that code with the service directly (OAuth with PKCE). GitHub uses a device code instead, which you type on github.com. No secret of ours and no server of ours is involved. Kitbar keeps the tokens it receives and refreshes them with the service before they expire.
- A key you make. You make a key in the tool's own dashboard and paste it in. While the connect sheet is open, Kitbar also checks the clipboard for a key you have just copied. It reads only short text that matches that tool's key format, and skips anything a password manager marks as private. It keeps or logs nothing else, and stops checking when the sheet closes.
Keys and sign-ins are kept in the macOS keychain on a Mac, and in Windows Credential Manager on a PC.
Claude Code and Codex on your computer
Claude Code and Codex connect without a key. Kitbar never reads the sign-in either of them keeps. Instead:
- Kitbar sets its own small program as Claude Code's status line (in ~/.claude/settings.json, keeping a copy of the file as it was). It saves the limits Claude Code reports to a file in Kitbar's folder, and Kitbar reads that file. It still runs the status line you had before. Disconnecting puts the settings back. If you installed Kitbar from the Microsoft Store, disconnect before you uninstall: the Store does not let Kitbar run anything at uninstall.
- To keep the numbers up to date while you are not in a terminal, Kitbar runs Claude Code itself and has it answer one very short message, as often as you choose in Settings. That uses a little of your plan: about a thousand tokens of the smallest model, and twice an hour of your own model. Claude Code runs with no tools, in an empty folder of Kitbar's, without your own settings, and with your hooks, plugins and MCP servers switched off. Kitbar also asks it which account is signed in, to show on the card. On a Mac, Claude Code also runs in a sandbox that cannot read your Desktop, Documents or Downloads folders. On Windows there is no such sandbox.
- Codex is asked through its own app server, the way its editor extension asks it, for your limits and the account that is signed in.
Requests to us
- License activation and validation. To activate the license, and to check every few days that it is still valid, Kitbar sends your license key, the name of your computer and an anonymous device identifier to our payment provider, Polar. The identifier is a one-way hash of your Mac's hardware ID or of Windows' machine ID. Polar's answer includes an opaque customer number, which Kitbar keeps with the license.
- Update checks. The Mac app fetches a small file from kitbar.io to see whether a new version is available, and downloads the update from the same site. The Windows app downloaded from kitbar.io does the same from kitbar.io/app/win. The app's What's New window also reads its notes from kitbar.io.
- Usage statistics. See the next section.
- Feedback. If you choose to send feedback from the app, Kitbar sends your message, the app version, your operating system's version and the email address you typed (if any) to kitbar.io, which forwards them to us by email. Nothing is sent unless you press Send.
Usage statistics
To learn which parts of Kitbar are used and where it fails, Kitbar may send us usage statistics through Open Analytics. We switch this on from our side, one app version at a time, so your copy may not send anything yet. To check whether it is on, Kitbar reads a small file from kitbar.io about once a day.
- What may be sent: the screens of Kitbar you open and what you do in them (opening a card, connecting a tool, changing a setting), which kinds of tools are connected and how (for example, GitHub by sign-in), error codes, the app version, the operating system family, the language and the processor type. Only your own actions are counted; background checks send nothing.
- How it is linked: Kitbar keeps a random identifier for this installation. While "Include my license" is on, statistics are also linked to your license through the opaque customer number from Polar. They are never linked to your email or name.
- Never sent: your keys or tokens, the names of your accounts, teams or projects, repositories, commits, deployment URLs, customers, payment amounts, your Claude or Codex usage, file paths, or any text you type.
- Your IP address is not stored. Open Analytics works out the country from the connection and keeps only the country.
Settings > About > Privacy has two switches. Share usage statistics: turning it off stops statistics completely, deletes anything waiting to be sent, and asks the server to forget this installation's identifier. Include my license: turning it off leaves anonymous counts only, with no identifier and no link to your license.
What Kitbar keeps on your computer
- On a Mac: your keys, sign-ins and license in the keychain; your settings in the app's preferences; the limits Claude Code reports, and the small state files for statistics, in ~/Library/Application Support/Kitbar.
- On Windows: your keys, sign-ins and license in Credential Manager; your settings and the limits Claude Code reports in %APPDATA%\Kitbar (the Store version keeps the limits in its own package folder); the small state files for statistics in %LOCALAPPDATA%\Kitbar; an error log in %LOCALAPPDATA%\Kitbar\logs, at most 1 MB, with keys and tokens blanked out before anything is written.
The latest answers from each tool are kept in memory only, until you quit.
Microsoft Store
If you install Kitbar for Windows from the Microsoft Store, Microsoft handles the download and the updates under its own privacy statement. Kitbar then gets its updates from the Store, not from kitbar.io. Everything else on this page applies unchanged.
This website
kitbar.io uses Open Analytics for aggregate, privacy-friendly visit statistics.
Payments
Purchases are processed by Polar as merchant of record. Your payment details go to Polar, not to us. Their privacy policy is at polar.sh/legal/privacy.
Changes
If this policy changes, the new version is published on this page with a new date.
Contact
Questions? Write to [email protected].