Privacy policy

The short version

Fleet has no account system, no telemetry, no analytics and no crash reporter. Your prompts, your transcripts, your repositories and your API costs are stored in files on your own Mac and are never sent to us. The only network request Fleet makes on its own behalf is an update check, and you can switch that off in Settings.

Fleet does drive other programs that talk to the network on your behalf: Claude Code, git, the GitHub CLI, and anything an agent runs at your request. Those are covered below, because they are the part of the picture that actually matters.

What Fleet stores, and where

Everything Fleet keeps lives in your macOS user data directory and in the git repositories you point it at. That includes:

• Your session records: titles, branches, worktree paths, statuses and costs.
• Session transcripts, which contain your prompts and the agent’s replies, written as files on disk.
• Your preferences: theme, default permission mode, notification level and so on.
• Your role files for squads, which are markdown you can open and edit outside Fleet at any time.
• A usage ledger: one row per completed turn, recording cost and token counts so the app can show you what you have spent.
• Git objects Fleet creates on your behalf, including worktrees, branches, and checkpoint commits kept on a Fleet-owned ref outside your branch history.

None of this is transmitted anywhere. Deleting a session deletes its record and its transcript. Deleting the app’s user data directory removes all of it.

The update check

If automatic updates are enabled, Fleet asks its release feed on launch whether a newer build exists. That request carries what any HTTPS request carries, including your IP address and the version being checked, and it is served by the hosting provider for the release files. Fleet does not attach an identifier to it, and it does not send anything about your sessions, repositories or usage. Turning the setting off stops the request entirely, and Fleet keeps working.

Programs Fleet runs on your behalf

Fleet is a front end for tools you already have installed and have already authenticated. It does not proxy any of them, and it holds no credentials of its own.

• Claude Code. Your prompts and the files an agent reads are sent to Anthropic by your own authenticated Claude Code installation, under your own agreement with Anthropic. Fleet neither sees nor stores your Anthropic credentials, and your usage is billed to your account, not ours.
• git and the GitHub CLI. Fetching a base branch, pushing a branch and opening a pull request use your existing git and gh configuration and credentials, and talk to whichever remote your repository points at.
• MCP servers you configure.An MCP server is a command Fleet will run, or a URL it will call. What it sends and where is that server’s business, not ours. This is why a server declared inside a repository arrives disabled and stays disabled until you approve it.
• Whatever the agent runs. An agent can run commands with your full filesystem privileges: installing packages, calling APIs, running your test suite. Those network requests are yours, and the permission modes are how you decide which of them happen without asking.

This website

This site is a static marketing and documentation site hosted by our hosting provider, which keeps standard server access logs including IP addresses. Fonts are self-hosted, so reading this page does not make a request to a font provider. We do not set advertising cookies and we do not embed third party trackers.

Downloads are served through a redirect so that we can count how many downloads a release got. That count is aggregate. It is not tied to any identifier, and nothing about it reaches the installed app.

Children

Fleet is a developer tool and is not directed at anyone under 16. We do not knowingly collect information from children.

Your rights

Data protection law gives you rights over personal data held about you, including access, correction and erasure. In Fleet’s case there is very little to exercise them against, because we hold no account and no usage records. For the server logs described above, write to the contact address and we will help.

Changes

If this policy changes in a way that affects what leaves your machine, the change will be called out in the changelog for the release it ships in, not just posted here quietly.

Contact

Questions about this policy go to [CONTACT EMAIL]. The data controller is [LEGAL ENTITY], [REGISTERED ADDRESS].