Privacy Policy

Last updated: September 15, 2026

CapMeter ("the app") is a macOS menu bar utility that displays your personal Claude.ai and Codex/ChatGPT usage statistics. This policy explains how the app handles your data.

Data We Do Not Collect

The app does not collect your personal data, and does not send any of your data to us or to any analytics, advertising, or tracking service. Specifically:

• No analytics or tracking
• No crash reporting sent externally
• No advertising identifiers
• No data about you sent to us — there is no backend that receives it
• No account credentials stored outside your device

The app sends nothing about you to us or to any analytics service. Three network behaviours are worth naming explicitly, because each one is either your own doing, Anthropic's, or OpenAI's:

• If you set up a webhook yourself, the app sends usage alerts to the address you provide — described under "Network Requests" below.
• Alerts posted to Slack or Discord carry the app's icon, which is hosted on capmeter.app — a static marketing site with no database and no account system. When those services render the message, their servers fetch that image; nothing about you is sent with it, and the app never contacts capmeter.app itself.
• When you add an account, the app opens Claude.ai's or OpenAI's own sign-in page (depending on which you choose) in a window inside the app. That page comes from Anthropic or OpenAI, not from us, and while it is open it may contact the services it normally uses — for example Google Sign-In, hCaptcha or Cloudflare. The app puts no code of its own into that page and reads nothing out of it. It does make one change to the flow, for either provider: if you sign in with Google, the app asks Google to show its account chooser, so that you can pick which account to add instead of being signed in silently as the one you are already using. Anything set along the way — a cookie for Claude, an OAuth token for Codex — is stored in the app's isolated session on your Mac. "No analytics or tracking" above means the app contains no such code of its own.

Data Stored Locally

The app stores the following data only on your device:

• Account information — For each Claude or Codex account you add, the app stores its session credentials, account name, and email address locally, so you can switch between accounts: a session cookie for Claude, an OAuth access and refresh token for Codex. These credentials are encrypted with the macOS Keychain before being written to disk, whenever Keychain encryption is available on your Mac, and the app's settings file is readable only by your user account. Browser sessions are kept isolated in the app's own sandboxed session.
• Usage history — A local log of your past usage, stored in the app's sandboxed container and used to draw the history charts. Each entry holds the date and time, the time your session resets, your session and weekly usage percentages, your plan name, the associated account email and provider, and — if you use Claude's extra usage or Codex's usage credits — the amount spent, which is what the spend-rate figure is calculated from. The app keeps the most recent 20,000 entries per account and discards older ones automatically; you can also clear the whole history yourself at any time from the history view.
• App preferences — Notification settings, refresh interval, display options, and any webhook addresses you configure. Stored locally via Electron's app data storage.
• Licence state — The date your trial started and whether the one-time purchase has been made, kept in two small local files. These contain no personal information.

Network Requests

For a Claude account, the app communicates with claude.ai on your behalf, using your own authenticated session, to retrieve your usage data. Requests are made to:

• claude.ai/api/organizations — to identify which organization your account belongs to
• claude.ai/api/organizations/…/usage — to retrieve your usage limits
• claude.ai/api/account — to retrieve your account name and plan

For a Codex account, the app communicates with auth.openai.com (to sign you in and refresh your access token) and chatgpt.com (to retrieve your usage limits and credit balance), using that account's own authenticated session.

If you add more than one account, the accounts you are not currently viewing are refreshed in the background roughly every four hours, using each one's own session and its provider's own endpoints, so their history stays complete.

The app never reads, stores, or transmits your Claude or ChatGPT conversations.

The app does not send your data to us or any analytics service. The only other network destination is optional and entirely under your control: if you configure one or more webhook addresses (Slack, Discord, or any HTTP endpoint) in the app's settings, the app sends an alert to each of them when you cross a usage threshold, when your session renews, and when you press the test button. Slack and Discord alerts contain your usage percentage, the account's email address, its plan name, and its reset time; alerts to a plain HTTP endpoint omit the email address. This feature is disabled by default, is sent only to the addresses you provide, and is only active if you set it up. You can remove them at any time in settings to stop it.

Purchases

CapMeter offers a single one-time in-app purchase. Payments are processed entirely by Apple; we never receive or store your payment details. The app only records locally whether the purchase has been made.

Your Control

You can remove all locally stored data at any time by deleting the app together with its data folder at ~/Library/Containers/com.gulizarsanverdi.capmeter/. Removing an account inside the app deletes it from your settings and clears its active session credential; deleting that folder is what clears any remaining Claude.ai cookies and Codex OAuth tokens. One item lives outside that folder: the key used to encrypt your session credentials is held in your macOS Keychain and can be removed there — it is a key, not data about you.

Changes to This Policy

If the app's behaviour changes in a way that affects this policy, the policy is updated here and the date at the top changes with it. Because the app stores everything on your Mac and sends nothing to us, changes will normally be clarifications rather than new data practices.

Who Is Responsible

CapMeter is published on the Mac App Store by Gülizar Şanverdi, who is responsible for this policy. Because the app keeps everything on your device and sends nothing to us, we do not hold a copy of your data. Questions about it go to the address below.

Contact

Questions? Contact: capmeterapp@gmail.com