Privacy Policy
Last updated 18 November 2026
Taskhouse runs on your Mac. There is no Taskhouse account and no telemetry, and your code and your agents' output never reach a Taskhouse server in a form it can read.
The short version
The coding agents you run in Taskhouse are the vendors' own command-line tools, and they talk to their vendors exactly as they would in your terminal. Taskhouse runs two small services of its own: an update feed, and a relay for the phone app that connects your phone to your Mac and delivers its notifications. Everything it carries is encrypted on your Mac and your phone, so the relay can't read it. If you buy Taskhouse Pro, Polar handles the payment.
What stays on your Mac
- The app's data: projects, tasks, agent state, the Inbox, pipeline runs, automations, budgets and settings, in
~/Library/Application Support/Taskhouse/. History of archived tasks stays there too. - Terminal output. Each agent's screen and scrollback are kept on disk so they survive a crash or a restart. That output can contain anything your agents printed, including secrets, so treat the folder like your shell history.
- Docs: plans, notes and reports are markdown files in
~/Taskhouse Docs/. Older versions are kept: every version from the last 30 days, then one a day, and labelled versions always. - Usage and cost: the token and dollar ledger is a local file, filled from the transcripts your agent CLIs already save on your Mac. Usage-limit history is kept for 90 days.
- Layout and sketches: where things sit on each canvas, and anything you draw on it.
- Voice: when you dictate, speech is turned into text on your Mac. Nothing is recorded or sent anywhere.
What leaves your Mac, and where it goes
Only these, and only when you use the feature:
| Feature | What is sent | Where |
|---|---|---|
| Your agents | Whatever the agent CLI sends normally | The agent's vendor (for example Anthropic or OpenAI), under that vendor's terms. Taskhouse runs the CLI untouched and never sees or stores your sign-in tokens. |
| Usage meters | A usage request through the CLI itself, every 5 minutes per signed-in account. It asks for limits only and sends no prompt. | The agent's vendor |
| Pull requests and CI | Requests made by your own signed-in gh or glab | GitHub or your GitLab server |
| Jira and Linear | Ticket reads and status changes, with the token you gave it | Your Jira or Linear workspace |
| Phone app and browser client | Inbox items, approvals, replies and agent text that you choose to see, encrypted end to end between your Mac and your phone | Your phone, through Taskhouse's relay or directly over your own Tailscale network, and a browser on another machine over Tailscale only. Only while Phone access is on. The relay passes the encrypted bytes on without being able to read them. While it does, it sees the IP addresses of your Mac and your phone, when a connection starts and ends, and how many bytes pass. It keeps your Mac's relay id (a random route id), the Mac's link public key, a hash of the Mac's access token, when the Mac first and last connected, and this month's byte count, and deletes them after 180 days without a connection. |
| Push notifications | Each phone's push token, the app's bundle id, your Mac's IP address, and the notification sealed with your phone's key | Taskhouse's relay, then Apple (or Google, for Android), then your phone. The relay runs on Fly.io in Frankfurt, Germany, and keeps the push token (on iPhone, the APNs device token), the bundle id and a hash of a key for your phone in its own database on that server. It deletes them after 180 days without a push. Its logs hold your phone's relay id, the last six characters of the push token and of your Mac's route id, status codes, and how long each connection lasted and how many bytes it carried; at its normal log level, never an IP address, and never what a notification or a message says. Until 16 November 2026 the relay ran on Google Cloud in Belgium, whose standard request logs (your Mac's IP address, the time, the request path, which can include your phone's relay id, and the client's user agent) are kept for 30 days, so the last of them are deleted by mid-December 2026. You can run your own relay or turn the relay off, which turns off push and connections through it. |
| SSH hosts and containers | Your project's setup and your agents' terminals | The hosts you add and the containers you choose to run |
| App updates | A request for the update feed, which carries your IP address and the app's version. No system profile is sent. | taskhouse.zoel.io, when automatic checks are on (Settings, General, Updates) or you choose Check for Updates |
| Computer use (off by default) | Screenshots, button labels and text from the window of an app you allowed for a task | The agent using it, and so that agent's vendor. Password fields are never captured or typed into. |
| Browser previews (optional) | A one-time download of Chrome for Testing and the Playwright tools | Google's and npm's download servers |
What Taskhouse never does
- No telemetry. Nothing about how you use the app is collected. If crash reporting is ever added, it will be off until you turn it on.
- No credentials handled. Agent CLIs keep their own logins. Jira, Linear and relay secrets are stored in your login Keychain.
- No silent approvals. An agent's permission request is answered only by you. Taskhouse never types "yes" into an agent, and destructive commands need a second confirmation.
- No agent speaking as you. A message one agent sends another is always labelled with who sent it.
Phone access
- It is off until you turn it on in Settings, Phone.
- Phones pair by scanning a QR code shown on your Mac, and browsers with a code. Nothing is paired until you allow it on the Mac. A paired device is read-only unless you give it more.
- Every remote action is written to an audit log on your Mac, kept for 90 days.
- You can revoke a device at any time. A phone that hasn't received a push for 180 days is removed from the relay, and so is a Mac that hasn't connected to it for 180 days.
Buying Taskhouse Pro
Polar (polar.sh) is the merchant of record for Taskhouse purchases. Polar collects your payment details and billing address, handles tax, and sends us your name, email address, country and order details so we can deliver your licence and help you with it. We never see your full card number. Polar's own privacy policy covers what Polar does with your data.
This website
taskhouse.zoel.io has no analytics, no tracking cookies and no third-party scripts. It is hosted on Vercel, which keeps standard request logs (such as IP address and user agent) to run and protect the service.
Reporting a problem
Help, Report a Problem writes a zip to your Downloads folder with a summary and the ends of the app's and the daemon's logs. Tokens, keys and your home folder's path are removed first. Nothing is sent anywhere; you choose whether to attach it to an email.
Keeping and deleting your data
Everything Taskhouse stores is on your Mac, so you decide how long it stays. To stop the daemon, use Settings, General, Daemon, Remove. Your data stays in the folders above until you delete them. For purchase records, email us and we'll delete what we hold, apart from what we must keep for tax and accounting.
Changes
When a feature that sends data anywhere is added or changed, this page is updated first, and the date at the top changes.
Contact
Questions about privacy: narek@zoel.io.