Privacy Policy

Last updated: October 21, 2026

The short version: RunWatch works on your Mac. It reads your Claude Code sessions locally to show their status, and your sessions, titles, and prompts stay on your Mac. The one exception is Better headlines, which is off unless you turn it on (see section 2). The only thing sent to our licensing server is a hashed device ID. We have no user accounts, and this website only counts visits and downloads, without cookies or anything that identifies you (see section 8).

1. Session data stays on your Mac

To show each session’s status, title, and your latest prompt, RunWatch reads Claude Code hook events and the end of each session’s transcript locally on your Mac. It keeps the current state of each session in a folder on your Mac (~/Library/Application Support/RunWatch). This information is never sent to us. It is not sent anywhere else either, unless you turn on Better headlines (section 2). Quitting the App and deleting that folder removes it.

2. Better headlines (optional)

Better headlines is off by default. If you turn it on in Settings, RunWatch asks Claude Haiku to write a short headline for each session. For each session it sends the project folder name, the session’s current title, and the first line of your latest prompt to Anthropic, through your own Claude Code and its login on your Mac. Nothing goes through us. Anthropic handles that request under the terms of your Claude account, and it counts toward your Claude plan or API usage. Turning the setting off stops these requests.

3. Your Claude Code settings

When you connect Claude Code, RunWatch adds its hooks to ~/.claude/settings.json and saves a backup of the original file next to it, on your Mac. Nothing from that file is sent anywhere.

4. Jumping to a session

To bring the right Terminal or iTerm tab to the front, RunWatch asks macOS for permission to control those apps (Automation). It uses that permission only to select the tab or window where a session runs.

5. Licensing

To check whether your Mac has an active subscription, the App sends a hashed device identifier to our licensing server. It is a one-way hash derived from your Mac’s hardware identifier, so it cannot be turned back into that identifier. This is the only information the App sends to the licensing server.

6. Payment information

Card payments are handled by Whop, which collects the billing information needed to take payment (such as your name, email, card details, and country for tax). RunWatch never sees your card details. Whop’s handling of that data is described in the Whop Privacy Policy.

7. Update checks

The App checks for new versions by fetching a small version file from this website. Like any web request, this reveals your IP address to the website’s host. The request carries no information about you or your sessions.

8. This website

This website is a static information and download page. It uses no cookies and no tracking. It only counts: when the home page opens, or when you click a download button, your browser sends one anonymous count (which app, and whether it was a visit or a download) to our counter on Cloudflare. We keep only the number of visits and downloads per day. Like any web request, the count reveals your IP address to Cloudflare, but we never store it or anything else about you. It is hosted on Vercel, which may keep standard server logs, such as IP addresses, to operate and secure the service. Fonts are loaded from Google Fonts.

9. Your rights

Because your session data stays on your Mac and payment data is held by Whop, we hold very little about you. Questions about billing data are best directed to Whop. For anything concerning the App itself, contact us and we will help.

10. Children

RunWatch is not directed to children under 13, and we do not knowingly collect information from them.

11. Changes

We may update this Privacy Policy from time to time. The “Last updated” date above reflects the latest version.

12. Contact

Privacy questions? Contact us at admin.dev1tch@gmail.com.