Privacy policy

Last updated November 12, 2026

Workbench is made by Matt Birchler (Birchtree Productions). This policy covers the Workbench Mac app and the Workbench iPhone app.

The short version

Workbench has no accounts and no ads. Your code, prompts, and conversations go from your Mac to your own devices. The one exception is a prompt you queue while your Mac is offline: it waits on Workbench's server, encrypted so only your devices can read it. Both apps share anonymous usage counts to help improve Workbench, and you can turn that off. Notifications pass through Workbench's push service on their way to Apple, encrypted so only your phone can read them.

Anonymous usage data

Both apps send anonymous counts of what you use to PostHog, an analytics service. This is on unless you turn it off: on the Mac, Settings > General > Share anonymous usage data; on the iPhone, Settings > Share Anonymous Usage Data.

  • What's sent: which features you use, like opening a Claude tab, starting an agent, pairing an iPhone, sending a reply, or answering a permission prompt, plus simple counts such as how many projects you have, and which kind of Claude model a session uses (like Opus or Haiku) and its effort level. Each install gets a random ID that isn't linked to you.
  • What's never sent: your code, prompts, messages, file names, project or branch names, or your name or email.
  • What's left out: location, time zone, language, and device name are removed before anything is sent, and PostHog is set to discard IP addresses.

The Mac app

Workbench runs on your Mac and keeps its settings and project list there. Besides the usage data above, it connects to:

  • GitHub, to check this repository's feed for updates. If you install the GitHub CLI, Workbench also uses it to show your pull requests, checks, and deploys.
  • Anthropic, using Claude Code's own sign-in, to read your plan's usage limits for the rings in the sidebar. Recaps, the one-line summaries of finished work, are written by Claude Code on your plan.
  • Workbench's push service, when your iPhone has notifications or the Lock Screen dashboard turned on (see below). If you add your own Apple push key in Settings > iPhone, your Mac sends to Apple directly instead.
  • Workbench's queue service, while your iPhone connection is on in Workbench, to check for prompts you queued while your Mac was offline.

Claude Code, which you install separately, talks to Anthropic under Anthropic's own terms and privacy policy. Workbench doesn't change what Claude Code sends.

The iPhone app

The iPhone app connects directly to Workbench on your own Mac, over your own Tailscale network or, at home, directly over your local network. To be found at home, Workbench announces itself on your local network under a random ID, not your name or your Mac's name. Your projects, sessions, and code go from your Mac to your phone without passing through our servers. The one exception is a prompt you queue while your Mac is offline (see below).

  • Camera: used only to scan the pairing code Workbench shows on your Mac. Nothing is recorded or saved.
  • Pairing details: stored in your phone's keychain.
  • Notifications: off unless you turn them on, and only for the projects you choose on your Mac. Your phone's notification token goes to your own Mac. Your Mac encrypts each notification's text so only your phone can read it, then sends it through Workbench's push service to Apple. The service and Apple only see "Open Workbench to see what happened." Workbench doesn't store or log anything in the push service.
  • Lock Screen dashboard: if you turn it on, your Mac sends its updates through the same push service to Apple. These updates aren't encrypted yet: they include your Mac's name, project names, and a short line about each session, like what Claude is doing or asking. Workbench doesn't store or log anything in the push service. Turn the dashboard off and these updates stop.
  • Queued prompts: if your Mac is asleep or Workbench is closed, you can queue a prompt on your phone. Your phone encrypts it with a key made from your pairing code, then stores it on Workbench's queue service until your Mac picks it up, or until 14 days pass with no new prompts queued. The service keeps only the scrambled text, each waiting prompt's random id, a random mailbox number, and when it was added. For 14 days after your Mac picks prompts up, it also keeps the random ids of the prompts already picked up, so none start twice. A prompt your Mac has picked up stays, still scrambled, for up to a day until your Mac confirms it has it, so it isn't lost on the way. Nothing else is stored. Workbench, its host (Vercel), and its database provider (Upstash) can't read your prompts. When you make a new pairing code, your Mac first picks up anything waiting under the old one. After that, your Mac stops checking the old one, and anything still queued under the old code is deleted after 14 days. Your phone also keeps its own copy of your queued prompts, on your phone only.
  • Saved project list: your phone keeps a copy of your Mac's project list from the last time it connected, so it can show your projects while your Mac is offline. It stays on your phone only.

Server logs

Workbench doesn't log requests to its own services. The companies that host them, like Vercel, keep standard request logs that can briefly record the IP address and time of each request. Your queued prompts stay unreadable, but the requests themselves aren't invisible.

This website

This site doesn't use cookies. It counts page views and clicks on the download links with PostHog: each one sends which page it was on, and a page view also sends the site that linked you here, if any. A random ID lasts until you close the tab, so a visit counts once, and nothing connects one visit to your next. Location isn't looked up, and IP addresses are discarded. Nothing is sent if your browser has Do Not Track or Global Privacy Control turned on.

To show the latest version and the version history, your browser asks GitHub for Workbench's public release list. The site's fonts come from Google Fonts, and the version history page loads two small scripts from cdnjs. Those services see your browser's request the way any website would, under their own privacy policies. Your browser keeps the release list for 15 minutes so it isn't fetched again on every page, and it's never sent anywhere.

Children

Workbench isn't directed at children and doesn't knowingly collect information from anyone.

Changes

If this policy changes, the new version will be posted here with a new date.

Contact

Questions: matt@birchtree.me