Privacy
Fleet works on your Mac. Almost everything it reads stays there, and what it sends, it tells you about here.
Last updated November 17, 2026
- Your setup stays on your Mac unless you sign in to sync. Then it travels and is stored encrypted, and our server keeps the key, so signing in on a new machine is all it takes to get it back.
- Your secrets stay in your vault. Fleet keeps their names, not their values, and sends one to another of your machines only when you ask, sealed.
- Fleet keeps no words from your providers' chat logs. From them it keeps names, times, models, project folders and token counts only. The chats you have inside Fleet stay on your Mac until you delete them.
- Fleet counts how it's used, never what's in your setup. Usage counts are numbers and fixed words, with no names, paths or prompts, and one switch turns them off.
- Crash reports are asked for each time, and pass through our server, which drops your IP address.
- The website counts visits without cookies. Which page, and which site linked to it, as counts with no IP address and no ID.
- No ads, and we never sell your data.
What stays on your Mac
Fleet reads the setup your AI providers load: skills, MCP servers, plugins, instructions files and provider settings, in folders such as ~/.claude and ~/.codex. It keeps its own copy in ~/.fleet as plain files you can open.
To show when you last used a skill or MCP server, and what your setup would cost at API prices, Fleet reads your providers' chat logs for the names of the tools and skills that ran, when, the model, the project folder and the token counts. It never keeps, shows or sends what you or your AI wrote there.
Ask Fleet, prompt automations and Clean up's provider save their chats in full in Fleet's own folder, so you can pick one up later. A screenshot or file you attach to an Ask Fleet message is copied there too. They are never synced, and a chat's files go when you delete the chat.
Secrets stay in the vault you pick: Keychain, 1Password or Bitwarden, which supplies a value when an MCP server starts. For 1Password and Bitwarden, Fleet asks their own programs (op and bws) for it and whether you're signed in, and they reach their own service.
Settings files you keep in Fleet (Git, SSH, your shell, your terminal) are copied into ~/.fleet/dotfiles. A file that holds a secret stays where it is and is never copied. A machine's activity on the Machines page (CPU, memory, disk, what's running) is read on your Mac.
Full Disk Access
Fleet asks for Full Disk Access only if you turn on Approve passwords with Touch ID, because macOS guards the file that sets how your Mac asks for its password. Fleet adds one line to that file and never opens your documents, mail, messages or photos. Switch it off in System Settings, Privacy & Security, Full Disk Access.
Your AI providers
When you use Ask Fleet, a prompt automation, the helper on a skill's page, or Clean up for what no rule fixes, Fleet runs your own provider (Claude Code, Codex, OpenCode, Pi or Grok) with your own login. The model you pick for Skill summaries also writes a skill's summaries, from the skill's files, and each Ask Fleet chat's title, from its first message. A screenshot or file you attach to an Ask Fleet message goes to that provider with it: an image as an image, and every file as the path of Fleet's copy, which the provider can read. What goes to that provider is covered by its own privacy terms, and Fleet sends it nowhere else.
Fleet also runs each provider's own program to read its version, whether you're signed in, its models, its plan limits, Grok's token counts for a chat, and the MCP servers it sees after a change (its mcp list, or Claude Code's mcp get for each MCP server the change touched, which may start or reach that MCP server to check it). The program may ask its own service for these, with your login.
What leaves your Mac
Everything Fleet itself sends off your Mac, or has another program send, is in these two tables. Your providers, your MCP servers and the automations you schedule reach the internet on their own.
Without an account
| What | Where to | When |
|---|---|---|
| Catalog searches. What you searched for, nothing about you or your setup. | getfleet.cloud, which reads skills.sh and the official MCP registry (registry. | As you browse the catalog |
| Skill update checks. The names of the skills.sh skills you added. | getfleet.cloud | Once a day |
| Model recommendations. The request only. | getfleet.cloud | At start and once a day |
| GitHub repos skills come from. The repo's name, with your GitHub CLI login or saved token if you have one. | github.com, api.github.com, raw.githubusercontent.com | When you open a catalog skill or add a repo, then once a day for repos you added. Forget a repo in Settings, Skill sources |
| Plan limits. For Claude Code and Codex, Fleet asks their own programs. For Grok, when the Grok program isn't running, Fleet sends the login Grok keeps on your Mac to Grok's billing service, as Grok does. It never stores or syncs that login. | cli-chat-proxy.grok.com, for Grok | While Fleet runs, every five minutes, and when you open the menu bar menu (at most once a minute) |
| Provider update checks. The request only, with Homebrew's analytics off. | Where each provider and tool is published: registry.npmjs.org, Homebrew, api.github.com, and a provider's own site: downloads.claude.ai, opencode.ai, storage.googleapis.com (Grok), static.ampcode.com (Amp) or downloads.factory.ai (Droid) | While Fleet runs, at most once an hour for each provider |
App and tool update checks. Homebrew fetches its list of newest versions, with its analytics off. If mas is installed, it asks the Mac App Store which of your App Store apps have updates, so Apple sees which apps those are. | Homebrew's servers (formulae.brew.sh and github.com), and the Mac App Store | Homebrew once its last fetch is six hours old, and on Check again. The App Store when Software reads what's installed: after those, after you change an app, or when its last read is over 15 minutes old |
| Provider installs and updates. Fleet runs the provider's own installer, which downloads it. | That provider's own site: claude.ai, chatgpt.com, opencode.ai, pi.dev, x.ai, gh.io (Copilot), cursor.com, ampcode.com, app.factory.ai (Droid), code.kimi.com, or Alibaba Cloud for Qwen Code (aliyuncs.com) | Only when you click Install or Update |
| Apps and tools you install, update or remove. From the Software page. Install Homebrew downloads Homebrew's own installer. | Where each one is published: Homebrew's servers, the Mac App Store, your apt sources, registry.npmjs.org, pypi.org or crates.io; github.com and api.github.com for Homebrew itself | Only when you click Install, Update, Remove, or Undo on one of them |
| Icons. An MCP server's name or package. In Discover, also the GitHub account a skill comes from. | The official MCP registry (through getfleet.cloud when you're signed in), registry.npmjs.org, pypi.org, and the MCP server's own site. getfleet.cloud for an MCP server Fleet picked. github.com and avatars. | Once for an MCP server or skill owner with no icon, again after 30 days. Turn off Fetch icons for MCP servers and skills in Settings, General |
| Voice models. The model you picked, by name. What you say never leaves this Mac: a model on it turns your words into text. | huggingface.co | Only when you click Download voice model, or Download in Settings, Voice |
| MCP server versions. An MCP server's package name, to find its newest version, so Clean up can pin the MCP server to it. | registry.npmjs.org or pypi.org | As Fleet works out Clean up for an MCP server that always runs whatever version is newest |
| An MCP server's key. When a provider can't add a key to a remote MCP server, Fleet passes its messages to the MCP server and adds the key from your vault. | That MCP server's own host, the one you set up | While your provider uses the MCP server |
| An MCP server's sign-in. For an online MCP server that signs in with your account: a request with no sign-in, to learn whether it wants one; Fleet registering itself with it; and once you approve Fleet in your browser, the code it gets back, then a token it keeps in this Mac's Keychain and renews. Fleet passes your provider's messages to the MCP server with that token. | That MCP server's own host and the sign-in host it names | When you add one or open MCP servers (at most every 6 hours), when you sign in, and while your provider uses it |
Machines you reach with SSH. Fleet runs fleet top there with your own ssh to read what it's doing for the Machines page, and Add machine sets Fleet up there: it copies this Mac's own Fleet to a Mac with the same chip, and otherwise runs the join command there, which downloads Fleet from getfleet.cloud. | Your own machine, the way your SSH settings reach it | While Machines shows that machine, or when you add one |
| Fleet's own update checks. Fleet's version, its build number, the channel (Stable or Nightly), your operating system's version and your computer's chip, nothing about you or your setup. We count these per day, by version, and keep no IP address with them. | getfleet.cloud | Every few hours, while Fleet runs |
| Usage counts, crash reports and feedback, each described below. | getfleet.cloud, which passes crash reports on to Sentry | Usage counts at most once an hour, unless you turn them off. A crash report when you say Send, or at once with Always send or on Nightly. Feedback when you send it |
With sync
Sync is optional. Once you sign in, getfleet.cloud keeps what this table says it keeps, and passes on the rest. Your Mac encrypts your setup before it sends it. The key that opens it is kept on the server too, encrypted with a secret only the server holds, so you can sign in on another machine and have your setup there with no other step. That means we could open your synced setup, though a copy of the server's storage alone can't. We don't look at it. Nothing there deletes on a timer: each row says what does.
| What | Kept? |
|---|---|
| Your account. Your email address. With Google or GitHub, also your account's id there, the name and picture they send, and the tokens they hand over at sign‑in, which the server stores but never uses. | Until you delete your account at getfleet.cloud/account |
| Each sign‑in. Where it came from: the IP address and the browser (or, for a machine, Fleet itself). | A browser's lasts about a week after it was last used. It's deleted when you click Use another account on the sign‑in page, or when that browser comes back after it ran out. A machine's is deleted once the machine is added; if adding it fails, it's kept like a browser's |
| Sign‑in by email, Google or GitHub. The emailed code, or the Google or GitHub sign‑in under way, and whom it's for. | It works for 10 minutes. Deleted once it's used, or at the next sign‑in by anyone after that |
| A new machine's sign‑in code, and whom it's for. | It works for 30 minutes. Deleted once that machine signs in with it, or asks after it ran out. One left unfinished stays on the server |
| A join code's id, a hash of its secret, and whom it's for. The new machine sends the secret once, to join; the server checks it against the hash and doesn't keep it. | It works once, for 15 minutes. Deleted when you cancel it, remove the machine that made it, or make another join code a day or more later |
| Sign‑in requests. From each IP address, a count of requests to each page of the sign‑in service, with when the last came, to slow down guessing. | At least half an hour after the last request, then deleted the next time any count starts over |
| Your devices. The server keeps each machine's name, its public key, when it joined and was last seen, whether it's been let in, and, while it waits, the join code it came with. | Until you remove the machine |
| Your account key, encrypted with a secret only the server holds. It opens your synced setup, and goes to each machine you sign in on. | Until you delete your account at getfleet.cloud/account |
| Your setup, encrypted, including the dotfiles you keep in Fleet: each version, sealed with your account key, with which machine made it, when, and how big it is. Secrets are never part of it. It goes on to your other machines. | The newest 100 versions, plus any from the 30 days before the newest. Each new version deletes older ones, and the files no kept version uses |
| Each machine's report, sealed: its providers and their versions, Fleet's own version, build and channel, its model, chip and memory, the names (never the values) of the secrets it holds, the names of the automations meant for it and whether each is on there and its last run worked, and what waits there for an answer, such as a new provider, a dotfiles change or a crash report. Passed on to your other machines. | No. Sent when a machine connects, when something changes, and every ten minutes |
| A machine's activity, sealed: CPU, memory, disk and what's running, including project folders and MCP servers' commands. Passed to another of your machines while its Machines page shows this one. | No |
| Actions from another machine, sealed: Quit, Free up and Measure from Machines, bringing in or answering a dotfiles change, reading what that change would do, Usage asking for its chats in figures (tokens by day, provider, model and project, never what was said), your answer to a provider that arrived there, and Send or Don't send for a crash report waiting there. Passed to the machine that does it, and its answer back. | No. An offline machine doesn't get them |
| Install and update requests, sealed, for a provider on another machine. Passed on to that machine. | Until that machine connects, up to 7 days. An older one is deleted unsent the next time one of your machines connects |
| Keys you send, sealed so only the receiving machine can open them. The request for keys names the secrets it asks for, in the clear; a refusal says why. Passed to the machine that asked. | A key, never. A request waits the same way, up to 7 days |
| Your cloud agents, such as Cloudroom or Claude Code on the web: each one's name and platform, which machine added it and when, when it last pulled your setup and which copy, a hash of its token's secret, and a key that only its token opens. The server never gets the token. | Until you remove that cloud agent, start fresh, or delete your account |
| The cloud copy, encrypted: your skills, instructions and the MCP servers that work away from your machines, sealed with a key from your account key, with when it was made and by which machine. Secrets are never part of it. It goes to your cloud agents. | The newest copy only, replaced by the next. Deleted when you start fresh or delete your account |
| Cloud agents' MCP sessions, sealed: what a cloud agent's provider and an MCP server that needs a key, running on your key machine, say to each other. Passed between them. | No. When the key machine is off, the cloud agent hears so |
The waitlist
If you leave your email on getfleet.cloud to hear when Fleet ships, the server keeps your email address, when you left it, and the site that linked you to us, as one word such as X or LinkedIn (see Website visits). We use it to tell you when Fleet ships, and now and then with news about Fleet, and for nothing else. It's kept until you ask to come off the list.
To slow down bots, Cloudflare counts tries at the form from each IP address over a minute. Fleet doesn't store the IP address.
Website visits
Each page of getfleet.cloud tells our server it was opened: which page, and the name of the site whose link brought you here, the part your browser already shares, such as t.co for a link on X. The server adds one to a count for that day, page and site, and keeps nothing else: no cookie, no IP address, no ID, and nothing that tells one visitor from another. The links we post are plain links, with nothing added to them.
Your browser keeps that site's name for the open tab only, so if you join the waitlist, it goes with your email. Close the tab and it's gone. Too many page views from one IP address in a minute go uncounted; Cloudflare keeps that count, not us.
Usage counts
Fleet counts a few things it does, so we can see where people get stuck and fix it. It's on by default: the first time Fleet opens, it says so in one line, with Turn off beside it.
- What's counted is a fixed list of events: Fleet opened, a scan finished (how many providers and skills, and how long it took), Clean up shown and applied (how many changes, and whether a provider fixed the rest), Undo, a page opened (which page), the menu bar menu opened, a switch flipped (on or off, and whether it was a skill, MCP server or plugin), a skill or MCP server added, a secret locked away (which kind of vault), Ask Fleet asked, an automation made (a script or a prompt), a machine added (over SSH or with a code), a machine that couldn't be added over SSH (why, in one word), a sign-in, an apply that failed (the kind of error), and feedback sent (which kind).
- Each event also carries Fleet's version, build and channel, your macOS version, your Mac's chip, which of the five providers are installed, the day it happened, and how many days ago this copy of Fleet first ran.
- Every field is a number, a yes or no, or one word from a fixed list. Never the name of a skill, MCP server, plugin, project or file, never a path, a prompt, a setting's value or a secret.
- A random install ID, made when Fleet first runs and kept on your Mac, lets us count installs without knowing who you are. It never syncs and isn't linked to your account. Settings, Privacy has Reset, which makes a new one.
- Fleet keeps events on your Mac and sends them at most once an hour. Settings, Privacy, See what Fleet sent shows the last batch exactly as it went.
- To turn it off, click Turn off on the first run, or use the switch in Settings, Privacy. It's one setting for every machine in your account, so a Linux machine you added follows it.
DO_NOT_TRACK=1in fleetd's environment turns it off on that machine too.
getfleet.cloud doesn't keep the IP address an event came from.
Crash reports
- Asked for each time. When Fleet quits unexpectedly, the next launch asks "Fleet quit unexpectedly. Send the report?", with View report, Send and Don't send. Tick Always send to stop being asked; that choice syncs like the usage switch. Nightly builds send reports without asking, and the switch that turns on Nightly says so.
- Scrubbed before it leaves. Your home folder becomes
~, environment variables are dropped, anything that looks like a key or token is removed, and the steps leading up to the crash carry no names. - A minidump, for a native crash. When Fleet's own code crashes outside Rust's checks, the report also carries a minidump: a snapshot of the crashed process's threads and the memory of their stacks at that moment. It's binary, so View report can't show it as text before it goes, and stack memory can hold pieces of whatever Fleet was handling right then.
- Through our server. Reports go to getfleet.cloud, which drops your IP address and passes them on to Sentry, in the United States.
Feedback
Send feedback, in the menu bar menu and in Settings, sends what you write and the kind you picked (Love it, Something's off or Idea), with Fleet's version, build and channel, your macOS version and your Mac's chip. When you include diagnostics and Fleet has crashed, they name the last crash report's ID, so we can find the report.
A screenshot of Fleet's window and diagnostics (versions, macOS, providers and fleetd's last log lines, scrubbed like a crash report) are optional, and Fleet shows you both before anything is sent. Feedback isn't linked to your account or your install ID. We keep it in our database and get it by email.
Release builds only
Only the Fleet you download from getfleet.cloud sends update checks, usage counts, crash reports and feedback. A development or test build sends none of them.
How long we keep it
- Usage events are kept for 3 months in Cloudflare Analytics Engine, and for up to 2 days in our database. There they're rolled into daily totals, such as how many installs opened Skills on a day, which hold no install ID and are kept for good.
- Update checks become a count per day and version, kept for good.
- Crash reports stay in Sentry for its 90-day retention.
- Feedback stays until you ask us to delete it.
- Waitlist emails stay until you ask to come off the list.
- Website visits become a count per day, page and site, kept for good.
- Your account and synced setup stay until you remove them, as below.
Who helps us run it
- Cloudflare hosts getfleet.cloud and stores encrypted sync data, usage counts, website visit counts and feedback. Like any web server, it keeps request logs (IP address, time, the address asked for) for a few days to keep the service running and safe.
- Sentry stores crash reports, in its US region. It gets them from getfleet.cloud and never receives your IP address.
- Resend sends sign‑in emails, and delivers feedback to our inbox.
- Vercel runs the small service that reads skills.sh for the catalog. It sees catalog requests, not you.
- Google and GitHub, only if you choose them to sign in.
No one else gets your data.
Your choices
- Use Fleet without an account: nothing about your setup leaves your Mac except the requests in the first table.
- Turn off usage counts in Settings, Privacy, and choose Don't send when Fleet asks about a crash.
- To have feedback you sent deleted, write to privacy@getfleet.cloud with roughly when you sent it and what it said.
- Remove a machine from sync in Machines. Its access ends at once.
- Uninstall Fleet from Settings, General. It turns every link back into a real file and leaves nothing that needs Fleet.
- To come off the waitlist, write to privacy@getfleet.cloud.
- To delete your account and everything stored with it, sign in at getfleet.cloud/account and choose Delete account. It's gone at once: your machines sign out, and your synced setup, its history and your sign‑in are deleted. Or write to privacy@getfleet.cloud and we delete it within 30 days.
Changes and contact
If this page changes, so does the date at the top, and the old version stays available on request. Questions about privacy: privacy@getfleet.cloud. Anything else, or feedback: hello@getfleet.cloud.