UPDATED 2026-09-22
NO ACCOUNT. NO ANALYTICS.
Vigil requires no account or sign-in. It has no analytics or crash reporting and sends no usage data.
WHAT STAYS ON YOUR MAC
Lifecycle hooks report agent activity. Before writing an event, Vigil discards:
- prompt text, assistant messages, and generated summaries;
- tool output and every tool argument except a short
description; - transcript paths and contents.
Each event file holds only session and process identifiers, the working directory, the event name, and short task or agent labels capped at 160 characters. Vigil deletes the file after reading it and keeps session state in memory.
The developer log in Settings > Advanced stays on your Mac and contains the same sanitized events.
Capture raw hook payloads is the exception. This debugging setting is off by default; while it is on, Vigil saves unredacted payloads, which can hold prompt text, assistant messages, tool arguments, tool output, transcript paths, and your Cursor email address. They stay on your Mac until the size cap removes them or you delete the file.
THE TWO NETWORK REQUESTS
Vigil makes only two kinds of outbound request. Neither carries agent, session, hook, project, or path data.
1. Updates. Sparkle checks an appcast on GitHub Pages about once a day and downloads releases from GitHub Releases. Its system profile is off, so the check appends no profile parameters; GitHub sees your IP address and a User-Agent with the Vigil and Sparkle versions. No setting turns checks off. Quitting Vigil stops them until an installed lifecycle hook starts it again for the next agent run, and Check for Updates… in Settings > About makes the same request.
2. Licensing. Vigil contacts Polar only while a license key is stored: once to activate a new key, then about weekly to check it. Requests send:
- the license key and Vigil's Polar organization ID;
- your Mac's activation ID;
- at activation, the Mac model identifier and activation date.
Polar also receives your IP address and the Vigil and macOS versions. The activation label excludes your computer name, user name, serial number, and hardware ID, and Vigil keeps only the license state from Polar's response. The key and activation stay in your Mac's Keychain and do not sync through iCloud.
Website, release-note, purchase, and license-portal links open in your browser; Vigil does not request them.
BUYING VIGIL
Polar is the merchant of record and Stripe processes cards. Checkout collects your name, email, billing address, and payment. Polar's privacy policy covers checkout, and Polar provides the license key by email and in its customer portal.
THIS WEBSITE
vigilmac.com sets no cookies. The home page counts page views with Plausible Analytics, loaded through Google Tag Manager. Plausible, Google, and Cloudflare, which hosts the site, each see your IP address and User-Agent. /download redirects to GitHub, and /buy and /license to Polar, so Cloudflare sees the click first.
QUESTIONS
Use the public Vigil issue tracker. Do not post prompts, agent output, paths, project names, or license keys.