Privacy Policy

Who we are

Jazzen Chen, the developer of Agent HUD (“we”), is responsible for this policy. It covers Agent HUD for Mac, its preview for Windows, the Agent HUD apps for iPhone, Apple Watch and HarmonyOS with their widgets, and the websites agenthud.app and agenthud.cn. The support form at forms.agenthud.app has its own privacy notice.

What is involved depends on the features you use. A build from the source on GitHub uploads nothing. The release sends data off your computer only for the features below. Agent HUD Remote is available on macOS only.

On your Mac

Agent HUD reads the records your agents already keep on your Mac and asks each vendor for your quotas and balances, and Cursor for your usage, using the agent's existing sign-in or the key you configured. From them it shows activity, quotas, token usage, sessions and reminders. No account query sends a message to a model.

This involves vendor, plan and model names, the account name or email address a vendor returns, session titles, project paths and times, token counts, balances, device names and your settings.

Credentials are read only to make these requests and are sent only to the vendor they belong to. Agent HUD never stores or uploads them.

Usage history stays in a local database on your Mac for about 30 days. Settings and the latest readings stay on the Mac until they are replaced.

While client hooks are on, Agent HUD writes hooks into your agents' own settings to receive their requests and replies. Turning client hooks off removes them.

On the same network

When you pair a phone with the release on your network, the Mac sends its quotas, balances, token statistics, sessions, reminders and any conversations it shares straight to the phone over HTTPS, with the Mac's certificate pinned at pairing. The phone gives that Mac its app installation identifier and device name, and the Mac sees the phone's local network address while it is connected.

The phone keeps the pairing credential in its secure storage and caches the latest data so it can show it offline. Where the Mac accepts it, the phone can also hand a message to the Mac over this connection.

The HarmonyOS app uses only this local connection. It uses no Apple or Huawei cloud account and sends nothing to our services. Scanning a pairing code uses the system scanner, and Agent HUD neither keeps nor uploads the camera image.

Agent HUD Remote and your iCloud

With Agent HUD Remote, your Mac stores records in the private database of your own iCloud, and your iPhone, its widgets and your Apple Watch read them from there on any network. Without Agent HUD Remote, a Mac writes there only its claim to a Remote seat and a device record with its name, its app version and, while local network sharing is on, its encrypted connection details.

Record contents are end-to-end encrypted with keys in your iCloud Keychain, so neither Apple nor we can read them. Only what iCloud needs to deliver alerts stays outside that encryption: each record's kind and time and, for alerts and requests, the alert's title and text and the session it belongs to.

The Mac stores its name, its app version and, while local network sharing is on, how to reach it on your network; usage totals with cost estimates at list prices; 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.

While Share conversation is on, the Mac also stores the turns of Claude Code, Codex, Antigravity and DeepSeek Harness sessions: your prompts and the agents' visible replies, plus text added during Claude Code and Codex turns, for turns that started in the last 7 days. Tool calls, their results and the agents' reasoning are never included. Full conversations from other agents stay on your Mac.

While Remote sessions is on, the Mac also stores 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; and plans in full. It also lists the agents and project folders a new session can start in.

Your iPhone and Apple Watch can then allow or deny a request, answer a question, and approve a plan or send it back with a note. Your iPhone can send messages to Claude Code and Codex sessions and start new sessions, a note from your watch included. These answers and messages are written to the same database, encrypted the same way, and the Mac deletes them when it picks them up.

Until a message is delivered or refused, the phone keeps its text on the device, so an interruption never sends it twice. A message for Claude Code waits on the Mac, readable only by your Mac user account, until the session takes it, for at most an hour.

Alerts and Live Activities

Alerts reach your iPhone and Apple Watch through Apple's push service. An alert for a request shows the requesting agent, the project and a one-line summary; for a question, what is asked; for a plan, its title. To show a short question's options on its alert, the iPhone app reads that request from your iCloud on the phone.

Live Activities of running sessions pass through Agent HUD's relay at push.agenthud.app, which runs on Cloudflare, to Apple's push service. Each Mac sends the relay its installation identifier and name and, for sessions running, waiting or ended in the last 5 minutes, a hashed session key, the agent, the title, the state and times. Each iPhone registers its installation identifier, push environment and push tokens. A Live Activity shows up to three sessions with their titles, states, durations and Mac names, and lasts at most 8 hours.

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, a phone's registration when Live Activities are turned off, and an account it has not heard from in 30 days.

Apple Watch, recordings and notes

Apple Watch gets quotas, balances and recent sessions from your paired iPhone. While a session's page is open, it also reads that session's latest reply and waiting requests from your iCloud. It keeps them only in memory and writes nothing there except your answers. It can read a reply aloud with its own voice.

To message a session by voice, the watch records up to 3 minutes, using the microphone only while the recording screen is open. The recording goes to your paired iPhone, which turns it into text on the phone itself with a speech model built into the app. The watch deletes its copy when the text arrives, when you record again or when the screen closes. The iPhone keeps the recording and its text in its recording library, with the session's agent and title, for 7 days. Nothing is sent until you confirm the text; the iPhone then sends it like a message typed on the phone.

On iPhone, an empty reply box in a session's conversation has a microphone. The iPhone uses the microphone only while you record, turns the message into text on the phone with the same model and puts it in the box for you to read before sending, then deletes the recording.

A note for later can run up to 12 hours. The watch keeps it until the iPhone has it. The iPhone keeps the recording and its text until you delete them, and returns the text to the watch. When you send a note to an agent, its text goes to your Mac like any message from the phone and starts a new session.

Recordings and notes never go to iCloud, your Mac or any server. The speech model is part of the app, so turning speech into text needs no network and no speech recognition service. The watch app needs microphone access to record, and the iPhone app only to record in the reply box; the system asks you for each.

Agent HUD Remote purchases

Agent HUD Remote is sold as an App Store subscription in the iPhone app, and Apple handles the payment. The iPhone writes the store, the original transaction ID, the number of Macs, when the current period or grace period ends and whether it renews to your iCloud, so your Macs can confirm access.

A Mac can also turn on Agent HUD Remote with a licence key issued through Lemon Squeezy, which handles payment for licences. For a licence we use the purchase email, order and subscription status, the licence, and the name and activation identifier of each Mac you activate, which label it in your list of Macs, to provide Agent HUD Remote, keep to its number of Macs and help with billing. The key stays in the Mac's Keychain and is shared through your iCloud with your other Macs. Our licence service at license.agenthud.app lists the Macs on a licence and stores nothing.

We never receive your full payment card details.

Update checks

The release checks for new versions at agenthud.app/updates/stable.json or beta.json, which forward the request to the release on GitHub, and downloads updates from GitHub. A check sends no usage, sessions, licence or installation identifier. Cloudflare and GitHub receive ordinary request information such as your IP address. We count the checks as the next sections describe.

Visiting our websites

When you visit agenthud.app, agenthud.cn or forms.agenthud.app, the hosting provider receives your IP address, browser and device details, and the time and address of each request, to deliver and protect the sites. agenthud.app runs on Cloudflare and agenthud.cn on Alibaba Cloud in Hangzhou. The sites' own code writes no logs.

Cloudflare Web Analytics measures visits and page performance on agenthud.app and forms.agenthud.app, except for visitors in the European Union. It records the page, referrer, country, device and performance, without cookies or query strings, and keeps them for 6 months. We use it to diagnose visits and performance.

agenthud.app and agenthud.cn set no cookies and keep nothing in your browser's storage. The motion switch at the foot of a page lasts only while the page is open.

What the websites count

Both sites keep a few counts of their own, as daily totals. A count says what happened, never who did it. Each total is kept with the site, the page or address, the language, an operating-system category (Mac, Windows, Linux, iOS, Android or other), and a source, medium and campaign category from a fixed list, such as a search engine, an AI assistant or a social network. Anything outside those lists is counted as “other” or left empty.

What the counts never hold

None of these counts holds an IP address, an account or visitor identifier, a full referrer address or a query string. They cannot tell visitors apart and do not confirm downloads, installs or purchases. They are kept for 180 days and deleted daily after that.

The counts honour Do Not Track and Global Privacy Control: a browser that sends either signal is not counted, on the pages or at /mac, /windows and /linux. Local previews, automated browsers and search crawlers are not counted. Agent HUD's update checks send neither signal, so every check is counted.

Contacting us

If you write to support@agenthud.app or use the form at forms.agenthud.app, we use your email address, your message and anything you attach to answer and look into the issue. Applications for Community Rewards go through the same form and are reviewed by hand.

What is never sent or tracked

• AI account credentials, API keys and vendor tokens are never 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.

Who else handles data

The providers below receive information only as far as these services need it. Providers that act for us must use it only for these services and protect it as this policy and applicable law require. We may also disclose information at your request or when the law requires it. These services may process information outside your country or region. We take reasonable measures to protect information but cannot guarantee absolute security.

• Apple: iCloud, push notifications, Live Activities and App Store subscriptions.
• Cloudflare: agenthud.app, the site counts, the Live Activity relay, the licence service and the support form.
• Alibaba Cloud: hosting for agenthud.cn.
• Lemon Squeezy: licence keys.
• GitHub: update checks and downloads.
• Your agents' vendors: the quota and balance requests made with your own sign-in.
• Our email provider: email you send us and new form submissions, which are forwarded to us.

How long data is kept

Each kind of data is kept for the time below. An expired iCloud record is deleted by the Mac that wrote it the next time that Mac is online with Agent HUD Remote, so actual timing depends on the apps running. Settings, the latest data shown and device registrations may stay longer, until they are replaced or deleted.

Your choices

• Removing a Mac in the phone app deletes its pairing credential and the data cached on the phone. Revoking paired devices on the Mac stops further reads but does not erase what a phone already cached.
• Turning off Share conversation on a Mac deletes the conversations it shared.
• Turning off Remote sessions on a Mac stops answers and messages from your phone and watch, and deletes the requests it published.
• Turning off Live Activities in the iPhone app removes the phone's registration from the relay. Turning off notifications alone does not stop data moving between your devices.
• Without microphone access, the watch app records nothing and the iPhone app cannot record in the reply box. You can still type a message, or write one with the watch's own text input.
• Deleting a note on the iPhone app's Recordings page removes its recording and text from the phone. Recordings for a session are deleted after 7 days.
• Signing out of iCloud or switching accounts on the iPhone deletes the cloud data cached on it and removes its relay registration.
• Quitting Agent HUD on your Macs stops new collection and uploads. Stored records can be managed in your iCloud storage settings; a device still running Agent HUD may upload them again. Uninstalling an app does not necessarily remove iCloud data or backups.

Access, correction and deletion

Write to support@agenthud.app or use the form at forms.agenthud.app to ask for access to, correction or deletion of information we hold, or for help removing other Agent HUD data. We may need to verify the request. Information needed for legal obligations, security or an open support issue may be kept for those purposes, and providers' backups follow their own schedules.

Changes to this policy

Changes appear on this page with a new date. Where the law requires further notice or your consent, we will give notice or ask for it.