Bloom for Claude
Terms

Legal

Privacy Policy

Last updated July 28, 2026

Bloom for Claude asks Anthropic directly for your Claude Code usage limits. It contains no analytics or advertising and sends no usage data to 100k31d.

Who we are

Bloom for Claude (the “App”) is provided by 100k31d LLC (“100k31d”, “we”, “us”, or “our”). This policy explains how the App handles information when you use it.

Claude sign-in and Anthropic requests

If you are signed in to Claude Code, macOS stores its OAuth credential in Keychain. Bloom reads that existing credential locally and uses it only to request your current usage limits from Anthropic. Requests go directly from your Mac to Anthropic; they do not pass through a 100k31d server.

When Claude Code’s access token is close to expiring, Bloom may use its refresh token with Anthropic and update the same Claude Code Keychain record. Bloom never writes credentials to its preferences, logs, analytics, or developer systems.

Optional local fallback

You may optionally select your Claude configuration folder, normally ~/.claude, using the macOS folder picker. With that permission, Bloom adds a wrapper around Claude Code’s documented status-line command. It transiently receives the status-line payload, extracts only the Claude Code version and rate-limit fields, and does not retain the full payload.

Information stored on your Mac

Bloom stores the following information locally:

  • a sanitized cache of available rate-limit percentages, reset times, plan/capacity metadata, and the time of the last successful refresh;
  • if you enable the optional fallback, the Claude Code version, documented rate-limit fields, availability/freshness markers, and an integration record containing Bloom’s installed command and an exact backup of your previous statusLine setting, so Disconnect can restore it safely; and
  • App preferences such as flower appearance, window position, behavior, and a macOS security-scoped bookmark for the folder you selected.

A previous status-line setting is user-authored and may contain a command or local path. That backup remains in Bloom’s app-owned folder on your Mac and is not sent to us.

Information Bloom does not retain

Bloom does not retain prompts, responses, transcripts, tool output, other session content, source files, Claude credentials, OAuth tokens, or account identity. It does not open Claude conversation logs, project folders, or source files.

Data collection and sharing

We do not receive your Claude usage data. The App has no analytics, advertising, or tracking SDKs and does not sell or share personal information. Bloom’s network client contacts Anthropic only for Claude usage and OAuth token refresh. Links you choose in the App open in your default browser.

Apple may process download, purchase, diagnostic, or App Store data under its own privacy policy. Anthropic may process your use of Claude under its own terms and privacy policy. Those services are controlled by Apple and Anthropic, not by Bloom.

Your choices and deletion

You choose whether to grant optional folder access. Use “Disable Local Fallback” before uninstalling Bloom if you want it to restore the previous status-line setting automatically. Bloom never overwrites a newer third-party replacement it no longer owns.

Disabling the fallback deletes its snapshots, integration record, previous-setting backup, and saved folder bookmark. The sanitized usage cache and App preferences can be removed by deleting Bloom’s app data or sandbox container from macOS.

Children

The App is not directed to children under 13, and we do not knowingly collect personal information from children.

Changes to this policy

We may update this policy as the App changes. The current version and its effective date will always be available on this page.

Contact

Questions about privacy can be sent to go@100k31d.co.

Bloom for Claude
Product Terms 100k31d Contact

© 2026 100k31d LLC