Privacy¶
MacMon watches your Mac for you, and the record it keeps stays on your Mac. This page says exactly what is stored, where, and the few things that ever leave.
What is stored, and where¶
Everything MacMon collects goes into one folder, ~/Library/Application Support/macmon, in a SQLite database. The folder is readable only by your account (mode 0700) and so are the files in it (mode 0600). Your settings, including allowlists, live in ~/.config/macmon/config.json. Both locations are shown in Settings › About, with a Reveal button.
Some of what is in that database is sensitive, and you should treat it the way you treat your shell history:
- The commands AI agents ran, as they ran them. If an agent ran a command that contained a token, the token is in the database.
- The prompt that preceded a flagged agent action, up to 600 characters, kept with the alert. Secrets the prompt scanner recognizes are replaced by a marker such as
[AWS access key ID removed]before they are stored. - Paths of files agents read and wrote. File contents are never stored.
- Login, unlock, sudo and SSH records from the system log, and the addresses downloads came from.
Secrets found in prompts are stored as their kind and a salted fingerprint, never the value. Secrets found in shell history are stored as a count per file. Passwords and keys in agent settings are shown as "set, N characters", never in the clear.
Granting Full Disk Access to MacMon's collector is optional. It is used only to read the two privacy-permission databases for the permission checks, but the grant lets the collector read anything you can, so give it only to a copy of MacMon you installed from the official download.
What never leaves the Mac¶
Every scan runs with network access refused. The checks, the inventory, the agent activity, the matches against threat-intelligence lists: all of it happens locally and the results are written to your database and nowhere else. MacMon has no accounts, no telemetry and no analytics, and it never sends a command, a prompt, a path or a file.
What does leave, and when¶
Four things make network connections. Each one is listed here with what it sends.
The daily update check. Once a day MacMon fetches the release feed and its signature from downloads.macmon.app, two small GET requests. Each carries the fixed user agent macmon and nothing else: no version, no identifier, no cookies. The host sees your IP address, as any web request reveals. Nothing is installed without your approval; see Updates. Turn the daily check off in Settings › Updates, or with "updates": {"check": false} in config.json. Check Now and macmon update check still work when you ask.
The daily threat-intelligence fetch. Once a day MacMon fetches a signed list manifest from intel.macmon.app and only the lists that changed. The requests carry the fixed user agent macmon, the validator the host sent last time so an unchanged set costs one small request, and nothing identifying; no cookies are sent or accepted. The host sees your IP address. The lists are matched on your Mac; no name, package or certificate you have ever leaves it. Turn it off in Settings › Updates, or with "intel": {"fetch": false}; the four threat-intelligence checks then skip and nothing else changes. See Threat intelligence.
macmon vulns --online, only when you run it. This command sends the names and versions of software packages found on your Mac to OSV.dev, together with your IP address, and downloads CISA's catalog of exploited vulnerabilities. Nothing runs it for you. Without --online the same command works offline and shows only what it can know locally.
Fleet enrollment, only if you enroll. A Mac you enroll in a fleet sends batches of its records to the server you enrolled with, outbound only; the Mac never accepts a connection. What it sends depends on the sharing tier the fleet sets, and Settings › Fleet shows the tier, what it means and a live count of what was sent. At the Metadata tier no command text, path or prompt leaves, and account and host names are replaced by pseudonyms. Standard adds the text of alerts and the commands and paths of the agent actions that caused them. Full adds every agent command and the prompts kept with alerts. Unenrolling removes the enrollment and its keys from the Mac. A Mac that is not enrolled sends nothing to any fleet server.
Exporting your own data¶
macmon export writes copies of your records to a folder you name, with the same file protections and the same tiers, so you can look at your history with other tools or keep a backup. Nothing is exported unless you run it.