Privacy policy

The short version

Fleet for Mac 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 it makes on its own behalf is an update check, and you can switch that off in Settings. None of that changes, and none of it is affected by anything below.

Fleet workspaces is a separate, opt in hosted service, currently invite only. It runs the same application on a machine we provide, so it has to have an account: we hold your GitHub identity, a record of which repositories you gave it access to, what its machine did, and what it cost. We do not hold your prompts, your transcripts or your code. What we hold, and for how long, is the table further down.

Fleet also drives 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.

Fleet for Mac: what it stores, and where

Everything the Mac app 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: 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 model credentials of its own, on your Mac or in a workspace.

• 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. In a workspace, that credential lives on your own volume and is not visible to us.
• 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. In a workspace they use a short-lived GitHub App token instead, described below.
• 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.

Fleet workspaces: what we hold

Signing in creates an account. This is the complete list of what that account consists of, and it is short on purpose: the control plane is designed so that the interesting data never reaches it.

• Your GitHub identity. Your numeric GitHub user id, your login, your display name and avatar URL, when your GitHub account was created, and whether you have two factor authentication enabled. The last two are a signup signal: an account created this morning with no two factor is the shape most abuse arrives in.
• Your sign-in sessions. A hash of each session cookie, when it was issued, when it expires, and whether it was rotated or revoked. Never the cookie itself.
• Which repositories you gave us access to. The GitHub App installation id, the account it is installed on, and the id and full name of each repository in it. Not their contents.
• Your workspace. Its state, its region, the Fly app, machine and volume identifiers, when it last reported in, whether a session was busy, and a hash of the token its machine authenticates with.
• An activity log. One row per thing that happened to your workspace: created, started, stopped, why it stopped, what failed. You can read all of it on your own workspace page, which is the point of it existing.
• Metered usage. Per hour: seconds the machine ran, gigabyte hours of volume, and gigabytes sent out. Quantities only. The money is calculated from them when it is shown.

What we deliberately do not hold

None of the following is ever written to the control plane, in any table, under any name: your prompts, your transcripts, an agent’s replies, the contents or diffs of your repositories, your Claude credential, or a raw session cookie or workspace token. Hashes only, where a secret has to be recognised.

Two more, worth naming because they would be convenient: we do not store the GitHub user access token from signing in (it is used twice, to read your profile and your installation list, and then discarded), and we never put the GitHub App private key on a workspace machine. A workspace receives minted tokens, scoped to the repositories you added and valid for at most an hour, and never the key that mints them.

Your workspace volume, honestly

Your workspace has a storage volume, and that is where your checkouts, your transcripts and your Claude login live. It is encrypted at rest by our infrastructure provider. We do not read it: there is no code in this service that opens it, and nothing on it is copied anywhere.

What we will not claim is that we couldnot. An operator with administrative access to our Fly organisation could attach a machine to that volume and read what is on it, in the same way any hosting provider’s administrator can. That access is limited to the people who run this service, it is not used, and the design keeps everything sensitive on the volume rather than in the database precisely so that reading it would take a deliberate act rather than a query. If that distinction matters to your work, Fleet for Mac exists and holds nothing at all.

Sub-processors

Three providers process data on our behalf for the hosted service. Each one is here because it is the thing it does, not as a list of everyone we pay.

• Vercel. Hosts this website and the control plane. It handles every request to this site and to your dashboard, and keeps standard server logs including IP addresses.
• Neon. The Postgres database holding the account records listed above, and nothing else.
• Fly.io. Runs your workspace machine and stores its volume. Your code and your transcripts are there while a workspace exists.

Anthropic and GitHub are not sub-processors here: you deal with both under your own agreements, and Fleet drives your credentials rather than holding them.

How long we keep it

A dormant workspace costs us money whether you use it or not, so we may reclaim the volume of an account that has not signed in for a long time. We will write to you first, with a date, and you will have time to get your work off it.

This website

This site is a marketing and documentation site hosted by Vercel, 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.

The only cookies this site sets are on your dashboard, if you sign in: one short-lived cookie during sign in, and one session cookie afterwards. Both are scoped to the dashboard host alone and neither is used to track anything.

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. If you have never signed in to a workspace there is very little to exercise them against, because the Mac app holds no account and reports no usage. If you have, write to the contact address: we can send you everything the table above lists for your account, correct it, or delete the account and its workspace outright. Deleting is not reversible and we keep no backup copy of a destroyed volume.

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. The same goes for anything new the hosted service starts holding.

Contact

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