Computer MCP / Privacy
Privacy
This page is short because there is very little to say. Computer MCP has no account, no API key, no telemetry and no server of ours. It makes no network calls of its own, and neither does this website.
The one-line version: we collect nothing, because there is nothing built into the software that could send us anything. That is not a policy we promise to keep. It is a property of the code, and you can check it in one command.
What the software collects
Nothing. The server runs on your machine, started by your MCP client, and speaks to that client over standard input and output. It has no HTTP client, no socket, no analytics, no crash reporter and no update check.
git clone https://github.com/Agent360dk/computerMCP
cd computerMCP
grep -rnE "fetch\(|https?://|net\.|axios" mcp-server/ helper/Sources/What comes back is bundle identifiers and documentation links, nothing that opens a socket. If you ever find an actual outbound call in there, that is a bug report we would want immediately, and we would treat it as the most serious kind there is.
What stays on your machine
| What | Where, and who can read it |
|---|---|
| The audit log | ~/.local/state/computer-mcp/audit.jsonl, mode 0600, so only your user
account can read it. One line per call: the tool, the target app, the outcome, a session
mark. Typed text is a scrambled fingerprint, with a random ingredient so it cannot be looked up, never the text itself. |
| Screenshots | Written to your system temp directory, handed to your MCP client, and that is the end of our involvement. Secure text fields and password-manager windows are blacked out on the bitmap in memory before the file is written, so the unredacted image never exists on disk. |
| Nothing else | No preferences file, no database, no hidden directory, no login item, no launch agent. The only write anywhere in the source is the audit log. |
Where your screenshots actually go
This is the honest part, and it is the part that matters more than anything we do. Screenshots go to the MCP client you configured, which sends them to whichever model provider you chose. That is the same route the rest of your conversation takes, and their privacy terms apply, not ours. We never see them, and we also cannot protect them once they leave.
What we can do, and do, is make sure that what is in the picture has already had the password fields painted out. The limits of that are written down plainly: only what macOS itself marks as secure is covered.
This website
No analytics, no cookies, no third-party requests, no fonts loaded from anyone else. The
only <script> element on any page is application/ld+json
structured data, which browsers read and never execute. The site is static files served by
GitHub Pages, who will see your IP address in their own server logs as they would for any
website; we do not receive those logs and have never looked at them.
Changes and contact
If this ever stops being true, it will stop being true in a commit, in public, in a repository you can watch. There is no version of this page that quietly grows an analytics section. Questions, or something you think is wrong here: open an issue.