Data processing
Procurement usually asks for a signed data processing agreement. For the index, the stack report and the pre-publish check there is nothing to sign, because nothing of yours reaches us to process. This page says exactly why, so you can file it and move on.
Why there is no DPA for the index or the report
A data processing agreement governs a processor handling personal data on a controller's behalf. Media Yard LLC does not do that here:
- The stack check and the report run in your browser. Your configuration is read, classified and rendered on your own
machine. The page is served with a content security policy of
connect-src 'none', which means the browser itself refuses to let it open a connection back to us or anywhere else. It is not a promise about our intentions; it is a rule your browser enforces. - The pre-publish check runs the same way. The manifests you paste are scored on your own machine, on a page with the same policy.
- A data licence download carries no personal data. It is the one request a purchase makes to us: a signed proof of purchase and the name of a file. The files are our records of public software, not your data, and we keep no record of who downloaded what beyond our host's ordinary request logs.
- Guard Team keeps your records in your own storage. The shared policy, every receipt and every alert go to the bucket, address and webhook your team names. None of it is sent to us. The one request a machine makes here carries its licence code and nothing else, and that code identifies a subscription, not a person.
- Leash Grant stores a revocation, and a log only if you send one. A grant is signed and handed to the product; we keep no copy. If its customer switches it off, we keep the grant's identifier and two times. If you choose to send your agent's receipts so the customer can read them, we keep those under the grant's identifier: times, decisions, tool names and the identifiers already in the grant. An entry holding anything else is refused, and you must not put personal data in one. If you ask your customer to approve an action, we keep the tool, the action, the times and their answer. A webhook address you give us is not stored; it travels in your customer's own link. All of it is deleted 30 days after the grant ends.
- There is no account. Nothing to sign in to, nothing stored against you, nothing to export or delete.
- A purchase does not carry your data to us. Link, by Stripe is the merchant of record and takes the payment; we see a payment record, not your configuration.
So for these, Media Yard LLC is not your processor, and a DPA would govern a relationship that does not exist.
What we are a controller of
Three narrow things, each set out in the Privacy Notice with its lawful basis and retention period: the email address and proof URL on a server submission; the contact details on an audit request made before the audit was withdrawn; and the payment record behind a purchase. In each, Media Yard LLC decides the purpose, so we are a controller rather than your processor, and the rights in that notice apply.
Who we use
| Netlify, Inc. | Hosting, delivery of the submission form, and private storage of submissions while they are checked and kept. |
| Resend, Inc. | Receiving and forwarding email sent to us. |
| Stripe, Inc. | Merchant of record for a purchase: checkout, tax, receipts, refunds and disputes. |
These process data on the site's behalf, not yours, and the list changes only with this page.
When we would sign one
Nothing sold here puts your customers' data in our hands, so there is no engagement that needs one. The hand-reviewed audit, which did, is no longer offered.
International transfers
Media Yard LLC operates from the United States and the services above are US-based. Where UK or EU data protection law applies to a submission or a purchase, that is a transfer out of the UK or EEA, made on the transfer terms each provider publishes.