Privacy

This notice applies to the ECZ-ID MCP Trust agent plugin, published by EcoCitizenz as eczid-mcp-trust at version 0.1.1. The plugin consists of a manifest, one skill document, one review script, one evidence-class reference and a declaration of one MCP server.

It does not cover, and must not be read as covering:

• the agent host or AI platform you run the plugin inside, which is operated by a third party under its own terms;
• the free ECZ-ID MCP Trust extension for VS Code, which is a separate product with its own privacy notice and its own capabilities;
• the ECZ-ID Verifier package the plugin declares, which is separately published and has its own privacy notice;
• EcoCitizenz websites, TrustOps, the Resolver or any other EcoCitizenz service you may visit afterwards by following a link.

It supplements the EcoCitizenz Privacy Policy, which is the general policy for EcoCitizenz services and explains your rights and how to contact us about personal information. Where this notice describes the plugin's behaviour specifically, it is the more specific statement.

When you ask the agent to review a workspace, the bundled script walks the directory you named and builds a list of workspace-relative file paths. That list is the entire input to the review.

The review makes no network request. The script imports two standard Node.js modules — the directory-listing and path-handling functions — and nothing else. It contains no HTTP client, no socket, no fetch call and no code that starts another process. You can confirm this by reading review.mjs, which has no dependencies and no build step, so the file you read is the file that runs.

One boundary deserves its own heading, because it is easy to blur and a reviewer will ask about it.

The skill's guidance suggests useful next steps for a human — for example, opening the MCP configuration and listing each server, its transport, the command that launches it and the environment key names that look credential-shaped. If you ask your agent to do that, it may open the file, using the file-reading tools its host gives it. Those tools are your agent host's, not ours.

That is a real difference in effect and this page will not pretend otherwise: what the plugin reads and what your session ends up containing are two different things. The plugin reads names. Your agent, if you ask, may read contents, and whatever it reads becomes part of a conversation held by the platform under its own terms. We do not receive any of it either way.

The plugin stores nothing. The script has no code that writes a file, creates a directory or opens a database. It keeps no cache, no history and no record of previous reviews.

The result exists as output in your agent session. If you want to keep it, you have to save it yourself — for example by redirecting the command output to a file. That copy is yours, in a location you chose, and this notice does not govern what you do with it.

Because nothing is transmitted by the review and nothing is stored by us, there is no retention period, no archive, no backup and no server-side copy of anything it observed.

Nothing from the review. It transmits no data to EcoCitizenz, so we do not receive and cannot hold:

• your name, email address, account identifier or organisation;
• the name, path or contents of any file in your workspace;
• the servers declared in your MCP configuration, or anything about them;
• the results of any review, or the Review Priority it produced;
• the fact that you installed the plugin, or that you ran it;
• your IP address, machine identifier, operating system or agent host;
• usage counts, timings, feature analytics or crash reports.

There are no advertising, tracking or data-broker integrations, because there is no data path to integrate. The two ways we learn anything are if you use the Verifier tools, in which case a public read-only surface of ours receives a request naming the target you chose, and if you email support, in which case we hold that message and whatever you put in it. The Support page sets out what is useful to send and what should never be sent.

The plugin never asks for a credential, has no field in which you could enter one, and needs none to run. It performs no authentication and holds no token.

Because it does not read file contents, it cannot read a secret value out of a .env file, an MCP configuration, a keystore or a settings file. Files beginning with a dot are skipped before matching apart from the allowlist above, and being on the allowlist means the entry is listed, never opened.

One consequence is worth stating plainly: an evidence class can be reported as OBSERVED together with the path of the matching file. A path is not a secret value, but a path can still be revealing in an unusual repository. You see that path before anyone else does, and you decide whether to share the result.

This is the distinction that matters most, and we would rather over-explain it than let it be assumed.

The plugin is a developer tool. It is not directed at children and knowingly collects information from nobody, because it collects information from nobody at all.

If the plugin's handling of information changes, this page is updated before or alongside the release that changes it, and the effective date is revised. Where the plugin is distributed through a marketplace listing, the updated notice is the one linked from that listing.

The version this notice applies to is stated at the top of the page. If you are running an older version, read the notice published with it.

Questions about this notice, or about privacy in relation to this plugin, can be sent to support@ecocitizenz.com. The same address is the route for data-protection requests under the general EcoCitizenz Privacy Policy.

See also the Support and Terms pages for this plugin, and the source if you would rather check than be told.

ECZ-ID MCP Trust is published by EcoCitizenz Ltd, trading as EcoCitizenz, company number 17348848, registered in England and Wales.