Privacy policy
QuotaPeek collects no data. It has no account, no analytics, no advertising and no tracking. Nothing about you or your usage is sent to us, because there is no server of ours to send it to.
What stays on your Mac
QuotaPeek works on your Mac. The only thing it shares is with your own iPhone, through your iCloud account (see "Your iPhone" below). It reads only the files you allow, when you connect a plan:
- Claude: reads the plan usage Claude Code reports, saved in
~/.claude/quotapeek/: the "Current session" and "Current week" lines of its/usagecommand (usage.txt), and the usage percentages, reset times, context share and cache state from its status line (claude.json). It also reads the record Claude Code writes in its logs (~/.claude/projects) when a plan limit is reached. To set this up, QuotaPeek installs a small helper,~/.claude/quotapeek/claude-statusline-bridge.sh, and in~/.claude/settings.jsonsets its status-line command and adds one Stop hook, keeping a backup. After each Claude Code reply the helper asks Claude Code for/usage, at most once a minute, and a few times a day which kind of plan you have (claude auth status), keeping only that one word, such as "max", inplan.txt. From version 1.1, for a Max plan it also reads one field of Claude Code's profile file (~/.claude.json, or the one in the folder of the profile it uses): the plan's rate-limit tier, and keeps only "max_5x" or "max_20x" intier.txt, so QuotaPeek can show Max 5x or Ultra. Nothing else from that file is kept. Also from version 1.1, in sessions of the Claude app, which signs in on its own and can be on another account, the helper keeps a 12-character code made from the account id the Claude app gives its sessions, never the id itself or your email, inaccount.txt. To follow the Claude app's account, the helper asks each Claude Code profile (your usual one, and any you've signed in to in a folder named~/.claude-and a name) which account it's on, withclaude auth status, and compares that with the email the Claude app gives its sessions, keeping neither; it then asks the profile on the app's account for/usage. It keeps only that profile's folder, inprofile.txt, and one word, "app" or "other", inusage-account.txt, so QuotaPeek can tell you when no profile is on the Claude app's account. Claude Code uses its own sign-in for all of this, and the helper never reads it. The helper asks only while QuotaPeek is running: QuotaPeek marks an empty file,~/.claude/quotapeek/.app-seenwhile it runs and removes it when it quits; if QuotaPeek stops some other way, the mark stops counting after an hour. Disconnect restores your settings. - Codex: reads only the rate-limit and token-count lines in Codex's session logs in
~/.codex/sessions, never your prompts or code. - Grok: reads only the usage lines in Grok Build's log,
~/.grok/logs/unified.jsonl, never your prompts or code. - Grok Bot (from version 1.1): in the folder you allow,
~/Library/Application Support/Grok Bot/sand-client-persistence, opens only the weekly usage file (the share used, the reset time and the plan's name). Your chats and sign-in data in the same folder are never opened.
QuotaPeek keeps your settings and the little it needs for alerts (such as which alerts it has already sent) in its own preferences on your Mac.
Audits
The audits run on your Mac and send nothing anywhere:
- Plan value: counts each reply's token numbers and model name in Claude Code's logs (
~/.claude/projects) and each session's token totals in Codex's logs. It never reads prompts, replies or code. The totals are kept for 30 days in QuotaPeek's own folder. Delete Audit Data removes them, and so does Delete Usage History in Settings. - Access: reads modes and counts from Claude Code's
settings.jsonand Codex's latest session log, such as the permission mode or how many hooks run. Never commands, paths or keys.
QuotaPeek also checks when Claude Code's logs last changed, to tell you when its numbers are out of date.
Week charts
With QuotaPeek Premium (from version 1.1), QuotaPeek draws each plan's week from the usage it reads: when, the share of the weekly limit used, and when it resets. It keeps these readings for five weeks in its own folder on your Mac, for weekly limits only. For Codex and Grok Build it also takes the same numbers from earlier lines of their logs. The free version keeps none. Delete Usage History in Settings › Privacy removes them.
Your iPhone
If you use QuotaPeek on iPhone (from version 1.1), your Mac shares what its widgets show through your own iCloud account's key-value storage: plan names, the shares used, reset times, API balances and, with Premium, each plan's week chart. With Premium it also shares, for the iPhone's Usage tab: each day's token counts per model from Claude Code's and Codex's logs, the tokens in each hour of the day, their value at API list prices, when each Claude Code and Codex session started and how long it ran, how each plan's past weeks ended, and when a limit ran out. Never prompts, code, or file and folder names. Only devices signed in to your iCloud account can read it; we can't. Apple stores it under its own privacy policy.
If you turn on reset reminders, the iPhone schedules local notifications from those shared reset times. They are prepared on the iPhone and are not sent through our server; we have no server.
The iPhone app can also read API balances itself, with no Mac: an OpenRouter, DeepSeek or xAI key you add there stays in that iPhone's Keychain and is sent only to its own provider (openrouter.ai, api.deepseek.com, management-api.x.ai), as on the Mac. Remove Key in the app deletes it.
It can also read what your Anthropic or OpenAI organization was billed for API use, with an organization admin key you create and add there. The key is sent only to api.anthropic.com (/v1/organizations/cost_report) or api.openai.com (/v1/organization/costs). An admin key can manage your whole organization; QuotaPeek only reads costs with it and never changes anything. It stays in that iPhone's Keychain and isn't restored to another device from a backup. You can give the key an expiry, and revoke it in the provider's console at any time.
API keys
If you add an API key for OpenRouter, DeepSeek or xAI, it is stored in your Mac's Keychain. QuotaPeek sends it only to that provider's official API, to read your balance:
openrouter.ai(/api/v1/keyand/api/v1/credits)api.deepseek.com(/user/balance)management-api.x.ai(your team's prepaid balance)
Those requests are covered by each provider's own privacy policy. Apart from the App Store, for the unlock, and iCloud, for your iPhone, QuotaPeek contacts no other host.
Purchases
The one-time unlock (or the supporter unlock) is bought through the App Store. Apple handles the payment; QuotaPeek only learns whether the unlock was bought, from your Mac's App Store receipt.
Notifications
Usage alerts are optional and are made on your Mac. Nothing is sent to produce them.
Removing your data
Disconnect a plan or remove a key in QuotaPeek's Settings. Delete Usage History in Settings › Privacy removes the audit totals and the week charts' readings, and the charts and usage figures on your iPhone at the next sync. Disconnect Claude before deleting the app, so your status line is put back. Deleting the app leaves its preferences in ~/Library/Containers/com.quotapeek.QuotaPeek; delete that folder to remove them. Keys you added stay in your Keychain until you delete them there.
Children
QuotaPeek collects no personal information from anyone, including children.
Changes
If this policy changes, the new version will be posted on this page with a new effective date.
Contact
Questions about privacy: open an issue.