Privacy Notice
The index is built to collect almost nothing. Browsing it collects nothing beyond what the web host logs. Submitting a server collects an email address. Asking for a lost purchase to be sent again uses the address you type, once.
Who is responsible
Media Yard LLC is the controller of personal data described here. Contact: support@leashkit.com.
Browsing
The index uses no cookies, no analytics and no advertising. It loads a third-party script on exactly one page: the payment page, which shows Stripe's card form in place rather than sending you to Stripe's site, and so loads Stripe's script and talks to Stripe. Nothing you type there reaches us — it goes to Stripe, the merchant of record. Every other page, the stack check, the report and the pre-publish check included, is served with a policy that refuses every network request. Like any website, its host records technical request data — IP address, time, page requested and browser type — to deliver and protect the site.
Some pages keep something in your own browser, never sent to us: the stack check saves the server names and addresses it read (not your config, and no keys) for the length of the browser tab, so the report page can offer them; and a bought report or pre-publish check keeps its signed unlock code for 30 days so you can use it again, and a data licence keeps its code for 365 days so you can download again. Each is needed for the feature you are using; clearing your browser's site data removes them.
Servers listed from the registry
| What we collect | What a server's author has published in the official MCP registry, and what the server itself returns: its registry name (which can include a personal or account name), title and description; its published endpoint, or package name and version; the tools it declares; the date the registry first listed it; and, when its endpoint did not list its tools, the kind of response it returned. We collect nothing about a server's users, and we never call a tool. |
| Why | To publish the index, each listing's dated history, the unanswered ledger and the list of newly registered servers, and to include the same records in the dataset licensed on the data licence page. |
| Lawful basis | Where GDPR or UK GDPR applies: our legitimate interest, and the public's, in an accurate dated record of what publicly registered software declares it can do (Art. 6(1)(f)). The information was made public by its author in a public registry. |
| How long | Records are kept as part of the dated public history. A record that is wrong is corrected, and a record is removed where the law requires it. |
| If a record names you | You can object to it, or ask for it to be corrected or erased, by writing to support@leashkit.com. Say which server. We answer every such request; the section on your rights, below, says what else you can ask for. |
Submitting a server
| What we collect | Your email address; the server's name, category and manifest; the URL where you published your ownership proof; and the date. |
| Why | To verify that you maintain the server, to publish the listing you asked for, and to contact you about that listing — including disputes and corrections. |
| Lawful basis | Where GDPR or UK GDPR applies: performing the listing you requested (Art. 6(1)(b)), and our legitimate interest in being able to reach a listing's maintainer about disputes (Art. 6(1)(f)). |
| What is published | The server's name, category, manifest, score and findings, and the domain or repository path you verified ownership from. If you verify from a personal domain, that domain will appear on your listing. Your email address is never published. |
| Who receives it | Media Yard LLC, and Netlify, Inc., which delivers submissions to us. A submission is deleted from Netlify, Inc.'s form storage when it is taken in to be checked, so it is not kept there. From then on it is held in private storage that Netlify, Inc. hosts for us and that the site's pages cannot read. The check is automatic: your proof is fetched and compared, and no one reads the submission first. We do not sell or share your details, and we do not use them for marketing. |
| How long we keep it | A submission whose proof cannot be confirmed within 7 days is rejected. A rejected submission, including its email address, is deleted 90 days after rejection. An approved submission is kept while its listing is published, so that you can be reached about it, and is deleted within 30 days of the listing's removal. |
Audit requests made before 2026-10-13
We no longer take audit requests, and the form that collected them has been removed. A request sent before then held a name, work email, company and a description of what was to be audited. It reached Media Yard LLC through Netlify, Inc., was used only to reply, and was never published, sold, shared or used for marketing. A request that did not become an audit is deleted 12 months after our last exchange with its sender. One that did is kept with the engagement records.
Buying a stack report, a pre-publish check or a data licence
| What we collect | Nothing on this site. Link, by Stripe runs the checkout as merchant of record and collects your email address and payment details. We can see the resulting payment record in our Stripe account — email, amount, country and date — and never your full card number. Your MCP config is never part of a purchase; the report is built in your browser. The same is true of the pre-publish check and the manifests you paste into it. A data licence download sends only the signed proof of purchase and the name of the file; we keep no record of who downloaded what beyond our host's ordinary request logs. |
| Why | To take the payment, confirm it so the report unlocks, handle refunds, and keep the records tax and accounting law require. |
| Lawful basis | Where GDPR or UK GDPR applies: performing the contract you entered (Art. 6(1)(b)), and complying with record-keeping duties (Art. 6(1)(c)). |
| Who receives it | Media Yard LLC and Stripe, Inc. Because Stripe is the merchant of record, it decides how the payment data is handled for the sale under its own privacy policy, rather than only acting on our instructions. Stripe also writes to you directly about the transaction — receipts, refunds — from Link. That is Stripe's own message as the seller of record, not ours, and nothing on this site can add you to a mailing list. Nothing is sold, shared or used for marketing. |
| How long we keep it | Payment records are kept in Stripe for as long as tax and accounting law requires. The unlock itself is a signed code stored only in your browser. |
Asking for a lost purchase again
The lost purchase page takes one thing, the email address you paid with. It is sent to Stripe, to look for a paid purchase made with it, and, if one is found that is still inside its time, to Resend, Inc., which sends the unlock link to that address and to no other. We do not store the address, and the page gives the same answer whether or not a purchase was found, so it cannot be used to learn who has bought something. The Guard Team page's licence form works the same way. The lawful basis, where GDPR or UK GDPR applies, is performing the contract you entered (Art. 6(1)(b)).
Leash Grant
When a product sends you to our consent page, its request travels in the part of the address that browsers do not send to any server, so opening the page tells us nothing. If you approve, the request and your choices are sent to this site once, used to sign the grant, and not stored. The request includes a handle the product uses for you; products are told it must not be an email address or a name, and we neither show it nor keep it.
If you switch a grant off, we store the grant's identifier, the time you did so and the time it would have ended. That record identifies no person and no product. It is published to anyone who asks about that identifier, which is how the product learns of it.
A product may choose to send us a log of what its agent did under your grant, so that you can read it from your grant page. If it does, we store that log under the grant's identifier. Each entry holds a time, whether the action was allowed, blocked or held for your approval, the name of the tool, the kind of action, the reason for a refusal, and the product and agent identifiers already in the grant. We refuse an entry that holds anything else, so a log has no field for your name, your contact details, or the content of anything the agent read, wrote or sent, and products are forbidden to put personal data in the fields it does have. We do not link a log to a person: we are not told who a grant belongs to. Only the link you were given on approval opens the log, and only the product holding your signed grant can add to it. We use the log to show it to you and for nothing else. It is not published, sold, shared or used to train anything.
Where you chose to be asked before an action, a product may leave a request for your approval, which you answer from your grant page. We store the request under the grant's identifier: the tool, the kind of action, when it was asked, and whether you approved or refused it and when. A request cannot carry a message from the product. We pass your answer to the product that asked, which reads it by the request's identifier. If the product gave us an address for the purpose, we also send it a short signed note when you switch a grant off or answer a request, saying which grant and what you chose. The note goes only to the address the product named, on the same site you were sent back to when you approved. We do not know who you are and cannot tell you a request is waiting; the product does that.
A log, a request and a revocation are all deleted 30 days after the grant ends. Because we cannot tell who you are, we cannot find your log from your name or email address; to ask us to delete it sooner, send us the grant's identifier, which is shown on your grant page. Where GDPR or UK GDPR applies, we rely on our legitimate interest in letting a customer see what an agent did on their behalf (Art. 6(1)(f)). Our host's ordinary request logs apply to these requests as to any other.
Guard Team
A Guard Team subscription is bought the same way, and the table above applies to the payment. After that, the shared policy, the receipts and the alerts go only to the storage and the webhook your team names. They are never sent to us, and we could not read them if asked.
One request does reach this site. When a machine's licence is close to its end, Guard sends the licence code, and nothing else, to ask for the next one. We check with Stripe that the subscription behind it is paid and answer with a new code. The licence code names the subscription and identifies no person or machine. We keep no record of the request beyond our host's ordinary request logs, which hold the IP address and time like any other request.
If you ask the Guard Team page to email a lost licence, the address you type is sent to this site, checked against Stripe for an active subscription, and used to send that one message through our email provider. We do not store it, and the page gives the same answer whether or not a subscription was found. Managing or cancelling a subscription happens on Stripe's own pages, under its privacy policy.
Emailing us
Email sent to support@leashkit.com is received by Resend, Inc. and forwarded to our inbox. It is kept only as long as needed to answer it, and is not used for anything else.
Other policies
How to reach a person is on the support page. What processing we do and do not do on your behalf is set out in the data processing statement. What part software models play in the index is on the AI policy. If you are in the UK or EU, consumer rights collects what applies to you in one place.
Your rights
You can ask to access, correct or delete your personal data, or object to how it is used, by writing to support@leashkit.com. Deleting your email address does not by itself remove a published listing; ask for that too if you want it. If you are in the EU, UK or another jurisdiction with a data protection authority, you may complain to it.
International handling
Media Yard LLC may process your details outside the country you submit from, including in the United States.
Changes
If this notice changes, the new version is published here with its date.