Privacy Policy

What we collect

Nothing. BlackFlare has no account system, no sign-up, no user ID, and no server of ours to send anything to. We do not know that you installed it, and we cannot tell how you use it.

What stays on your Mac

BlackFlare works on files you already have. Everything below lives on your machine and is never transmitted anywhere.

• Claude Code's OAuth token — read from your macOS Keychain, read-only. BlackFlare never adds, updates, or deletes that Keychain item. It is held in memory for the app's lifetime, never written to disk, and never logged. Reading it is off by default and requires your explicit consent.
• Telegram bot tokens and Slack webhook URLs that you paste in — stored in your Keychain as BlackFlare's own items, and deleted from the Keychain when you remove the channel. They never go into preferences files or logs.
• A licence key, if you bought a direct licence — also stored as one of BlackFlare's own Keychain items.
• Your Claude and Codex config files —~/.claude/settings.json and~/.codex/config.toml. BlackFlare reads them to show current state and edits them when you pick a different default. See “How your files are treated” below.
• Session transcripts and rollout files —~/.claude/projects/*/*.jsonl and~/.codex/sessions/**/rollout-*.jsonl. BlackFlare watches these locally to know when a session is waiting or finished. Their contents are never uploaded, and never leave the process.
• Preferences and caches — your settings in UserDefaults, plus a model catalogue cache and a usage cache under~/Library/Application Support/BlackFlare/.
• Backups BlackFlare makes for you — the first time it edits a config file it copies the original to settings.json.bak or config.toml.bak.

Logs

BlackFlare writes no log files to disk. It logs through the macOS unified logging system, which redacts dynamic values by default; tokens, credentials, and the contents of your config files are never logged. Only the current run's log is viewable, in the optional Debug tab, and it is discarded when you quit. The diagnostic bundle the Debug tab exports is written only where you choose to save it, and is sent to us only if you attach it to a message yourself.

When BlackFlare talks to the network

Five destinations, all listed. Nothing else is ever contacted.

Codex usage numbers involve no network call at all — they are read from a snapshot Codex itself writes into its local rollout files.

When you forward a notification, what leaves your Mac is only what the notification says: the event type, the message, the session identifier, and the project folder name. It goes to your bot or your webhook — not to us. We have no access to it.

What we never do

• No accounts, no sign-in, no profile.
• No analytics, no telemetry, no crash reporting. The app bundles no SDK for any of these.
• No advertising identifiers, no tracking, no fingerprinting.
• No selling or sharing of data — we hold none to sell.
• No reading of your source code or your conversations for any purpose beyond detecting, on your machine, that a session is waiting or finished.

How your files are treated

BlackFlare edits config files you wrote by hand, so it holds itself to strict rules:

• Surgical — only the changed value's bytes are rewritten. Key order, comments, and formatting are preserved.
• Atomic — a temporary file is written and renamed over the original, so a partial file is impossible.
• Backed up — the first-ever edit copies the pristine original alongside it.
• Refuses malformed files — if a config does not parse, BlackFlare alerts you and writes nothing.
• Validated after writing — the result is re-parsed and checked before the rename commits.

BlackFlare is not sandboxed, which is what allows it to read your Keychain, edit those config files, and launch the claude CLI. That is also why it is not distributed through the Mac App Store: the sandbox the store requires would disable all of it.

Children

BlackFlare is a developer tool and is not directed at children. It collects no personal information from anyone, of any age.

Changes to this policy

If what the app does changes, this page changes in the same release, and the date at the top moves. Material changes will also be noted on the blog.

Contact

Questions about this policy, or anything else: get in touch.