# Your data

[Agent HUD Docs](https://agenthud.app/docs/en/)

What Agent HUD reads and keeps on your Mac, what leaves it and when, how it is protected, and what is never collected.

Updated 2026-10-28

Agent HUD does its work on your Mac. It reads the records your agents already keep, asks each vendor for your quotas with the sign-in your agents already have, and keeps what it works out in a local database. Data leaves your computer only for features you turn on, and for update checks.

## At a glance

| Data | On your Mac | Leaves it |
| --- | --- | --- |
| Your agents' logs and transcripts | Read in place, never changed | Never as files |
| Token and quota history | Local database, 30 days | Only with local network sharing or Agent HUD Remote |
| Credentials and API keys | Read only to make a request; never stored | Only to the vendor they belong to |
| Requests waiting for you | Held while they wait; not kept as history | Only with **Remote sessions** on |
| Conversations | A working copy of the last 7 days | Only with **Share conversation** on |

## What stays on your Mac

- **Usage history**: token counts by kind, model and session, cost estimates, and quota readings, in a local database, kept for 30 days.
- **A working copy of your conversations**: the release keeps the last 7 days of your sessions' turns, read from your agents' logs, in a data folder that only your macOS user account can open. It serves conversations on your phone and messages between agents.
- **Requests**: a permission request, question or plan is read to draw its card, and your answer goes straight back to the agent. Request bodies are not kept as history.
- **Messages for Claude Code**: a message Agent HUD hands to a Claude Code session waits in a folder only your user account can read, until the session takes it, for at most an hour.

## What Agent HUD reads

- **Your agents' records**: the logs, transcripts and local databases each agent writes on your Mac, opened read-only. [Supported agents](https://agenthud.app/docs/en/agents/supported/) lists what is read for each one.
- **Your quotas and balances**: Agent HUD asks each vendor with the agent's existing sign-in or configured key, or asks the installed agent itself, as it does for Claude Code and Codex. A credential is read only to make that request and goes only to the vendor it belongs to, over HTTPS with redirects refused. Tokens, headers and raw responses are never stored, shown or written to error messages. No read sends a message to a model.
- **GitHub Copilot's quota**: only after you turn on **Read GitHub Copilot quota**.
- **Relays**: only after you switch a relay on in **Settings → Relays**. The key the agent already sends that relay goes to the same address, over HTTPS, and nowhere else.
- **Model servers on your network**: when a Claude Code session uses a model server on this computer or your local network, Agent HUD asks that server which model it serves and with what context window. Nothing else on your network is contacted.

Agent HUD also writes into your agents' settings: its hooks, only while you have client hooks on; the additions you ask for; and one entry in Claude Code's settings that trusts Agent HUD's own task folder. [Client hooks](https://agenthud.app/docs/en/agents/hooks/) lists each one.

## What leaves your computer, and when

### Your iPhone on the same network

Off until you turn on **Local network sharing** in **Settings → Local Network** and pair a device.

- The Mac sends its quotas, usage and sessions straight to the paired phone, over HTTPS with the Mac's certificate pinned when the phone pairs. Nothing passes through a server.
- The phone gives the Mac its app installation identifier and device name, and the Mac sees the phone's local address while it is connected. With Agent HUD Remote and **Remote sessions** on, the phone can also hand a message to the Mac over this connection; a phone paired only on the network can read, not send.
- **Revoke paired devices** stops further reads. It does not erase what a phone has already cached.

### Agent HUD Remote, through your own iCloud

With Agent HUD Remote, your Mac stores records in the private database of your own iCloud account, and your iPhone, its widgets and your Apple Watch read them from there on any network.

- **Encryption**: record contents are end-to-end encrypted with keys in your iCloud Keychain. Neither Apple nor the developer of Agent HUD can read them.
- **Outside the encryption**: each record's kind and time, and for alerts and requests, the alert's title and text and the session it belongs to, so iOS can show the alert.
- **What the Mac stores**: its name and app version; usage totals with cost estimates; each account's quota windows, balances and plan, with the name or email address the vendor returns; sessions with their title, agent, project path, times, tokens and the agent's last visible reply; and reminders.
- **Share conversation**, off by default: also the text of the turns of the sessions it follows, meaning your prompts and the agents' visible replies. Tool calls, their results and the agents' reasoning are never included. Turning it off deletes the conversations it shared.
- **Remote sessions**, off by default: also the requests your agents are waiting on (tool approvals with the tool, a summary, the command or file path and snippets of a proposed edit; questions with their options; plans in full), and the agents and project folders a new session can start in. Answers and messages from your phone and watch are written back the same way, encrypted, and the Mac deletes them when it picks them up.

Without Agent HUD Remote, a Mac writes to your iCloud only its claim to a Remote seat and a device record: its name, its app version and, while local network sharing is on, its encrypted connection details.

### Alerts and Live Activities

These need Agent HUD Remote.

- **Alerts** reach your iPhone and Apple Watch through Apple's push service.
- **Live Activities** of running sessions pass through Agent HUD's relay, `push.agenthud.app` on Cloudflare, to Apple's push service. For sessions running, waiting or ended in the last 5 minutes, each Mac sends the relay its installation identifier and name, a hashed session key, the agent, the title, the state and the times. The relay keeps no iCloud account identity and logs no tokens, credentials or session text. It deletes a Mac's sessions 24 hours after its last report, and an account it has not heard from in 30 days.

### Update checks

With **Automatically check for updates** on in **Settings → Updates**, the release looks for a new version once a day at `agenthud.app/updates/stable.json`, or `beta.json` on the beta channel, which forwards to the release on GitHub. Updates download from GitHub. A check sends no usage, sessions, licence or installation identifier. Cloudflare and GitHub receive ordinary request information such as your IP address, and the website counts checks by channel only.

### Licence keys

If you turn on Agent HUD Remote with a licence key instead of the App Store, the Mac checks the key with Lemon Squeezy, which receives the name and activation identifier of each Mac you activate, and with Agent HUD's licence service, which lists the Macs on a licence and stores nothing. The key stays in your Mac's Keychain and is shared through your iCloud with your other Macs.

### A build from source

A build from the source on GitHub uploads nothing.

## Your agents and HUD tools

When you give an agent HUD tools, it can read your usage, sessions and statistics through Agent HUD's MCP server on your Mac. What a tool returns becomes part of that agent's conversation, which the agent sends to its own model vendor. Screenshots of the HUD taken for an agent mask your accounts. See [Built-in MCP](https://agenthud.app/docs/en/mcp/).

## Never collected

- AI account credentials, API keys and vendor tokens are never stored or uploaded.
- Shared conversations never include tool arguments, tool results or the agents' reasoning.
- Log paths and your Mac's hardware model are never uploaded.
- The apps contain no advertising, analytics or crash-reporting SDK, and nothing in them tracks you.

## Turning things off

| To stop | Do this |
| --- | --- |
| Your phone reading the Mac on your network | Turn off **Local network sharing**, or **Revoke paired devices** |
| Conversations in iCloud | Turn off **Share conversation**; the shared conversations are deleted |
| Requests and messages through iCloud | Turn off **Remote sessions**; the requests it published are deleted |
| Hooks in your agents' settings | Turn off **Client hooks**; see [Client hooks](https://agenthud.app/docs/en/agents/hooks/) |
| All collection and uploads | Quit Agent HUD |

The full policy, with retention periods and the websites, is at [agenthud.app/privacy](https://agenthud.app/privacy).

---

简体中文: https://agenthud.app/docs/zh/privacy/