Privacy Policy

Effective 18 October 2026

AIMeter is a macOS menu-bar app that shows how much of your AI subscriptions you have used. It does not need an account. This page explains what AIMeter and its Chrome extension, AIMeter Cookie Bridge, do with your data.

Data that stays on your Mac

• Provider sign-ins and API keys are stored in the macOS Keychain on your Mac.
• Quota and usage history is stored in ~/.config/aimeter/. The shell helper and provider settings are in ~/.claude/aimeter/. Routing settings, provider configuration and analytics history are in ~/Library/Application Support/AIMeter/.
• The All tools and Usage pages read the usage logs that AI coding tools (Claude Code, Codex, opencode and others) write on your Mac, using a bundled copy of the open-source tokscale scanner. Those logs are read on your Mac and never leave it.

Data that leaves your Mac

• To the AI providers you connect. AIMeter uses your sign-in or API key to read your usage and quota from that provider. If you route Claude Code or Codex through AIMeter, your requests go from your Mac to the provider you chose.
• Usage stats (on by default). A daily ping, and error reports at most every 15 minutes. Each one includes a random install ID, the app and macOS version, your Mac’s model, chip and memory, and your Mac’s computer name, which may contain your name. Pings also include feature counts. They never include prompts, code, sign-ins or API keys. Turn usage stats off in Settings → General → Privacy.
• Feedback you choose to send. Your message, any contact details and screenshots you add are stored as an issue in a private GitHub repository. If usage stats are on, your install ID and device name are attached so a report can be matched to its diagnostics. You can opt out when sending.
• App updates and reference data. AIMeter checks GitHub for updates and AIMeter’s server for the minimum supported version. It can check providers’ public status pages, and downloads price tables for cost estimates once a week (turn that off in Settings → Usage).

AIMeter Cookie Bridge (Chrome extension)

The extension lets AIMeter read your usage from services you are already signed in to in Chrome, so you don’t have to sign in again inside the app.

• What it reads. The session cookies for claude.ai and opencode.ai, and the workspace ID in the address of opencode.ai pages you open. While platform.deepseek.com is open, the console sign-in token that site keeps in your browser. While platform.xiaomimimo.com is open, your plan usage from that page. It does not read Grok or any other site.
• Where it sends it. Only to the AIMeter app on the same Mac. From version 1.7.0 it uses Chrome’s native messaging, and a helper inside AIMeter checks that the receiving app is AIMeter, code-signed by its developer, before passing anything on. Earlier versions use a local connection on your Mac. What it reads is never sent to any server, and the extension contains no analytics. To read your Xiaomi MiMo usage it asks platform.xiaomimimo.com for it, the same request that page makes.
• What it stores in Chrome. For each service: connection status, the time of the last update, a hash of the last session sent so unchanged data is not sent again, and retry timing. It also stores your OpenCode workspace ID.
• How AIMeter uses it. Sessions are saved in the macOS Keychain and used only to read your usage from the same service.
• Removing it. Remove the extension from Chrome, and disconnect the provider in AIMeter to delete what AIMeter saved.

What we don’t do

We don’t sell your data, show ads, or share your data with third parties, other than the services that host it for us: GitHub for feedback and Cloudflare for usage stats. Your data is not used for anything other than showing your AI usage and improving AIMeter, and never for creditworthiness or lending decisions.

Deleting your data

• Delete AIMeter.app from /Applications.
• Remove ~/.config/aimeter/, ~/.claude/aimeter/ and ~/Library/Application Support/AIMeter/.
• Remove the source ~/.claude/aimeter/shell-init.sh line from your shell rc file.
• Search AIMeter in Keychain Access.app and delete the entries.
• Run defaults delete com.khairul.aimeter in Terminal to remove AIMeter’s preferences, including the install ID.
• Remove AIMeter Cookie Bridge from Chrome if you installed it.

Changes

If this policy changes, the new version is published on this page with a new effective date.

Contact

Use Send Feedback inside AIMeter.