MCPatrol — Privacy Policy

Effective 28 July 2026 · applies to the MCPatrol Android app (package com.detentpoint.mcpatrol) and the web console at app.mcpatrol.com

MCPatrol monitors MCP (Model Context Protocol) servers you choose to add. This page describes exactly what data the app handles, where it lives, and how to delete it.

Two modes, two data locations

Local mode (no account): everything you add — server URLs, probe results, incidents — is stored only in the app's private database on your device. Nothing is sent to us.
Cloud mode (with an account): the servers you register are monitored around the clock by our backend, and the data below is stored on our servers (Microsoft Azure, East US region).

What we store in cloud mode

Account: your email address and a salted hash of your password (PBKDF2-HMAC-SHA256 via ASP.NET Identity's password hasher — we never store the password itself), plus the API key the app uses to talk to the backend.
Monitoring configuration: the names and URLs of the MCP servers you register, and optional metadata you add (such as a repository URL for registry submissions).
Probe outcomes: health state, response latency, and timestamps from each check, plus incidents derived from them.
Server inventory: the tools, resources, and prompts your MCP servers report, and a history of changes to that inventory.
Bridge data (optional): if you run the PC bridge agent, the machine name and the stdio servers it relays, and per-request traffic metadata (method names, payload sizes, durations). Request/response payload capture is off by default; if you enable it explicitly, captured payloads are redacted before storage and you can turn it off at any time.
Push tokens: if you enable notifications, the Firebase Cloud Messaging token for your device, used only to deliver your alerts.

The web console, and the one cookie it sets

app.mcpatrol.com is a browser view of the same account and the same data described above. It reads and writes nothing else: signing in there shows you the estate your app already shows you. Using it is optional — the app works exactly the same whether you ever open it or not.

A session cookie, set when you sign in. It holds the credential that identifies your account to the backend. It is marked HttpOnly, so the page's own JavaScript cannot read it, and Secure, so it is sent only over TLS. Signing out revokes it at the server, not just in your browser.
A companion token, in a second cookie. The page reads this one and echoes it back on every request that changes something, which is what stops another site from acting as you. It identifies nothing on its own.

Both are strictly necessary to keep you signed in, so no consent banner is shown for them. There are no advertising, analytics or tracking cookies on the console, and none on this website either.

What we don't do

No advertising SDKs, no analytics or tracking SDKs, no location, no contacts, no advertising identifiers.
We don't sell data or share it with third parties. The only processors involved are our infrastructure providers: Microsoft Azure (hosting and database) and Google Firebase Cloud Messaging (push delivery).
Data from your servers is used only to show you your own monitoring — never for anything else.

Security

All traffic between the app, the bridge, the web console and the backend uses TLS. Backend access requires your per-account API key — held in the Android Keystore on your phone, and in an HttpOnly cookie your browser will not hand to a script. Passwords are stored only as salted PBKDF2 hashes.

Delete your account and data

You can delete your account and all associated data directly in the app, without contacting anyone:

Open MCPatrol and go to the Manage tab.
In the account card, tap Delete account.
Confirm with Delete everything.

Deletion is immediate and complete: your account, servers, probe history, incidents, inventory records, traffic records, captured payloads, bridge registrations, and push tokens are all removed from our database. Nothing is retained after deletion — there is no backup-restore of deleted accounts. Your API key and login stop working the moment deletion completes.

If you can no longer access the app, email us from your account email address and we will run the same deletion for you.

Delete some of your data, without deleting your account

You do not have to choose between keeping the account and removing something in it. Each of these is self-serve, takes effect immediately on our servers, and needs no request to us:

A monitored server, and its whole history. Servers tab → select the server → Remove. This deletes its probe history, incidents, recorded inventory changes and traffic records along with it. Your MCP server itself is untouched — this only stops MCPatrol watching it.
An individual incident record. Alerts tab → the incident → Delete, once it is resolved.
A bridge, and everything it relayed. Manage → Bridges → Forget. Removes the machine name, its registration and the stdio servers it reported.
Captured request and response payloads. Off by default. If you turned capture on, turning it off stops collection, and removing the server or bridge removes what was captured.

The same actions are available in the web console at app.mcpatrol.com. If you would rather we did any of it for you, email [email protected] from your account address.

To remove everything at once instead, see Delete your account and data.

Data retention

Cloud data is retained while your account exists and is deleted when you delete your account. Local-mode data lives only on your device and is removed when you clear the app's data or uninstall it.

Your rights (GDPR / CCPA and similar laws)

Depending on where you live, you have legal rights over your personal data. We honor them for everyone, wherever you are:

Access & portability: email us and we'll send everything associated with your account email in a machine-readable form.
Correction: the only personal data we hold is your email; email us to change it.
Deletion: self-serve, in the app, immediate (see above) — or by email if you've lost access.
No sale, no sharing for advertising: we don't sell personal data or share it for cross-context behavioral advertising, so there is nothing to opt out of.
Complaint: you can lodge one with your local data-protection authority; we'd appreciate the chance to fix the problem first.

Legal bases for processing (GDPR art. 6): performance of the service you signed up for (account, monitoring data, push tokens) and legitimate interest in keeping the service secure (server-side logs). Data controller: Detent Point, LLC (United States), reachable at the address below. No automated decision-making, no profiling.

Changes and contact

If this policy changes, the effective date above will be updated. Questions and deletion requests: [email protected].