UPDATED 2026-10-25
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 IDs, the working directory, the event name, and short task or agent labels of up to 160 characters. Vigil deletes the file after reading it. So that tracking can resume after a relaunch, Vigil keeps a snapshot of its sessions in ~/Library/Application Support/Vigil/session-registry.json: the same kind of data, plus repository names and timers. It holds no prompts, transcripts, tool arguments or output, or license data, and only your macOS user can read it.
The developer log in Settings > Advanced stays on your Mac and holds the same sanitized events.
Capture raw hook payloads is the exception. It is off by default. While it is on, Vigil saves unredacted payloads, which can include prompts, assistant messages, tool arguments and output, transcript paths, and your Cursor email address. They stay on your Mac until the size cap removes them or you delete the file.
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 and the page you see after buying count page views, and clicks on the download buttons and the buy link, with Plausible Analytics.
QUESTIONS
Use the public Vigil issue tracker. Do not post prompts, agent output, paths, project names, or license keys.