Privacy Policy

Who we are

Fleet Command is an independent developer tool. It has two parts: an iPhone & Apple Watch app, and an open-source plugin for Claude Code and Codex you install on your own computer. The plugin reads your local agent hook events and forwards a metadata summary to the Fleet Command backend, which the app reads back to draw your fleet.

What we collect

When a session is active, the plugin sends only:

• ›Session activity — a verb describing what the agent is doing (e.g. thinking, running a tool, waiting, idle) and a timestamp.
• ›Activity detail — a short descriptor (max 120 characters) of what the current tool is touching: a file's basename (e.g. forwarder.mjs), a program and subcommand name (e.g. git push), or the hostname of a fetched URL (e.g. api.github.com). Never a full path, never file contents, never the full command line.
• ›Project folder name — the basename only (e.g. my-app), never the full path, never your username.
• ›Usage stats — token counts, context percentage, model name, and approximate cost, bucketed by 5-hour and weekly windows.
• ›A session identifier and sub-agent count — opaque IDs used to group ships; not linked to your identity.
• ›A random pairing token — created when you link a machine, used to authorize sync. No email or password.
• ›A notification token — only if you allow notifications: an Apple Push Notification (APNs) device token, so we can buzz your phone when a ship needs you. You can revoke it any time in iOS Settings.

If you turn on Remote Approvals (off by default), the plugin additionally sends a summary of the specific command awaiting approval — up to the first 400 characters of the real command (e.g. git push --force…) — so you can review and approve or deny it from your phone. This is sent only for the gated action, only while approvals are enabled, and only to your own paired device.

If your agent uses the ask-human tool (a question it can send to your phone mid-task), the question text your own agent writes — up to 4 KB — is relayed to your paired device, and the reply you type (also up to 4 KB) is relayed back to the session. Both exist only to complete that one exchange.

What we never collect

• ✕ Your source code or file contents.
• ✕ Your prompts or the conversation with your AI agent. (The opt-in approval summaries and ask-human questions described above are the only prose that ever transits.)
• ✕ Full file paths, your home directory, or your username.
• ✕ Your name, email, contacts, location, or any advertising identifiers.
• ✕ API keys, tokens, or credentials from your environment.

How it's used & stored

The metadata is used solely to render your fleet in the app and to relay approval decisions and replies back to your machine. It is stored on the Fleet Command backend (hosted on Cloudflare), associated with your anonymous pairing token — not with you personally. We do not sell data, and we do not use it for advertising. Pairing tokens are held securely in the iOS Keychain on your device.

Retention is short and automatic:

• ›Pending approval requests (including the command summary) expire after 5 minutes if undecided, and are removed once decided.
• ›Ask-human questions and your replies expire after 30 minutes, or as soon as the exchange completes.
• ›Pairing codes expire after 10 minutes.
• ›Live session metadata is kept only to render your current fleet; stale sessions are dropped automatically and each account holds at most a bounded number of recent sessions.
• ›Insights aggregates — daily counts (tool names, token totals, activity tallies; no prose) — are kept for 90 days, then deleted.

Website analytics

This marketing website (fleet-command-agents.com) uses Google Analytics to count page views and clicks on the download and install links, which may set cookies in your browser. That is the extent of it — the iPhone & Apple Watch app and the plugin contain no analytics, no trackers, and no advertising SDKs, and nothing from your coding sessions is ever sent to Google.

Your control & deletion

You can stop all data sync at any time by uninstalling the plugin (claude plugin uninstall fleet-commander) or removing the fleet in the app. Remote Approvals are off unless you explicitly enable them with /fleet-approvals on. To request deletion of any data tied to your pairing token, contact us at the address below.

Children

Fleet Command is a developer tool not directed at children under 13, and we do not knowingly collect data from them.

Changes

If this policy changes, we'll update the date above and post the new version at this URL.