Remove everything
Validated against app ae3b0ef2 and Collector 0.9.0 (54621da), 11 November 2026. This page as Markdown
Follow the order below: each step needs something the next one removes. To remove one thing only, go straight to its section.
| To remove | Section | Needs |
|---|---|---|
| The Collector and its local folder | 1 | a terminal, online; you answer one question |
| One agent’s access | 2 | a browser, then a terminal for the client |
| Your profile | 3 | a browser |
| Everything the service stored about you | 4 | a browser, your mailbox |
1. Uninstall the Collector
Section titled “1. Uninstall the Collector”Run humanload uninstall before brew uninstall. Homebrew alone removes the binary and leaves the hooks, the two
background jobs and the Device key behind.
Run this line while online: humanload uninstall starts by revoking this Device on the service, and && runs
Homebrew only once it succeeded, so a failed uninstall leaves you the command to run it again.
humanload uninstall && brew uninstall humanloadhumanload uninstall does this, in order:
- revokes this Device on the service and removes the Device key from your Keychain;
- removes its hooks from
~/.claude/settings.json, and its status line when setup added it; - removes the two background jobs;
- asks “Erase local Humanload data? [y/N]”. Answer
yto erase~/Library/Application Support/Humanload/.
A person answers that question. The command reads the answer from the terminal; an agent that runs the command for you leaves the question to you.
You should see:
Installation removed; key revoked.Uninstall before the Erasure of step 4: until you uninstall, the hooks keep writing event lines on this Mac. If you
erased first, run humanload uninstall all the same. The service answers that it no longer knows the Device key; the
command takes that answer as a revocation and removes everything on this Mac.
If the service cannot be reached, the command stops with a line that starts with Failed: and removes nothing. Run it
again when you are online.
If you already ran brew uninstall, install again with brew install cmdai-hq/tap/humanload, run
humanload uninstall, then brew uninstall humanload.
Uninstalling does not erase the Counts the service already stored. Step 4 does.
2. Disconnect an agent
Section titled “2. Disconnect an agent”- Open
https://app.humanload.eu/me/account. - Under Connected agents, choose Disconnect… next to the agent, then confirm.
You should see the agent gone from the list. Its next call is refused with status 401. To use it again, connect it
again from the agent.
Then remove the server from the client, so that it stops asking to sign in:
-
Claude Code:
Terminal window claude mcp remove humans -
Codex: its
codex mcpcommand has aremovesub-command. Its arguments are not checked here;codex mcp remove --helpprints them.
3. Delete your profile
Section titled “3. Delete your profile”- Open
https://app.humanload.eu/me/profile. - Under Delete my profile, choose Delete…, then confirm.
You should see “Your profile and its read log are deleted.” The agents of your teammates receive nothing from then on.
4. Erase everything on the service
Section titled “4. Erase everything on the service”Erasure (Effacement in the French interface) deletes all the service stored about you: your account, your Devices, your Counts, your notes, your profile and its read log, and your agents’ connections.
Before you start, read two conditions:
- Erasing needs a sign-in from the last 15 minutes. The app sends a third kind of code for that: 8 digits, by e-mail, on the page Confirm it is you.
- If you are the Owner of a Team that has other people, transfer or delete the Team first. The page says so and links to the Team’s settings.
Then:
- Open
https://app.humanload.eu/me/data. - Optional: choose Download my data (JSON) to keep a copy.
- Under Erase all my data, read what remains and why.
- Type your e-mail address to confirm, then choose Erase all my data.
You should see the confirmation on the sign-in page. Your sessions are closed and your Devices revoked at once.
The page gives the full list of what remains after an Erasure. During the beta it comes down to:
- the security log, 12 months, with its lines detached from you;
- technical logs, 7 days, without an address or a Device identifier;
- backups, 28 days at most (the Erasure notice in the app promises “within 30 days”);
- the Cells already published in your Teams, which carry no identifier.
Your address stays invited until the person who invited you removes it. If you open the app again, it creates a new, empty account. To leave for good, ask that person to remove your address.