Privacy policy
Last updated
Loadout is a Mac app that reads the assistant configuration already on your disk. It has no account, no telemetry and no sync, and there is no server of ours for anything to be sent to. This page says exactly what that means for the app, for this website, and for the two places data does leave your machine.
What the app collects
Nothing. Loadout does not create an account, does not ask for an email address, and does not report usage, crashes or errors to anyone. There is no analytics SDK in the app and no identifier is generated for your machine.
The usage counts the app shows are computed on your Mac from the session transcripts your assistants already write there. They are never uploaded.
What the app reads, and what it writes
This is the whole surface. Everything in it is a path on your own disk.
- Reads your assistant folders — ~/.claude, ~/.codex, ~/.<assistant> — for skills, slash commands, subagents, plugins and MCP servers.
- Reads the session logs under those folders to count activations. Read only; the app never writes to them.
- Reads a repository you point it at, for the skills that live in that project.
- Writes to those folders only when you save, create, disable, delete or share something.
- Writes its own files under ~/Library/Application Support/Loadout: the backups taken before every write, the rebuildable usage index, and the working copies the Ask conversation edits.
Deleting sends a folder to the Trash after a backup, so a wrong click is recoverable and nothing is removed with rm.
The one network call the app makes
At launch, Loadout asks the GitHub releases API whether a newer version of the app has been published. It sends nothing but the ordinary request GitHub receives from any client, downloads nothing, and does not act on the answer beyond telling you. GitHub logs that request the way it logs every request to its API; that is GitHub, under its own privacy policy, not us.
If you would rather it did not happen at all, block the app in a firewall: nothing else in Loadout needs the network.
What happens when you press Ask
Ask runs the assistant command-line tool already installed on your Mac — claude, codex or opencode — as a subprocess, using the credentials already on your Mac. Loadout never sees those credentials and never handles them.
That tool then talks to its own provider, and the content of the skill you asked about goes with it, exactly as it would if you had run the same tool in your terminal. What the provider does with it is governed by their terms and their privacy policy, not by this page. If a skill file holds something you do not want sent anywhere, do not ask about that file.
This website
No cookies, no analytics, no tag manager, no tracking pixels, no embedded video and no third-party fonts: the two typefaces are downloaded at build time and served from this domain, so your browser makes no request to anyone else while reading this.
The site is hosted on Vercel, which keeps the ordinary access logs any web host keeps — IP address, time, page, browser string — to serve the pages and to keep the service running. We do not read them for anything else and there is no dashboard here counting visitors.
The download buttons point at GitHub, and following one takes you to GitHub, which logs the download on its side.
Your data, and asking about it
Because none of your data is collected, there is nothing held about you here to export, correct or delete. Everything Loadout produced is on your own Mac: remove the app and the folder ~/Library/Application Support/Loadout, and it is gone.
If you think any sentence on this page is wrong about what the app does, open an issue and say so. The app is open source, so the answer is checkable rather than promised.
Changes to this policy
The date at the top of this page is the day it last changed. If a future version of the app ever collects anything, this page changes first and says what and why.