07Legal
Privacy
The site has two forms and one analytics script. This page lists what each collects, where it goes, and how long we keep it. There are no accounts, no advertising pixels and no third-party cookies.
Effective 2026-09-07
Standing noticeFindings describe published certificates on the dates listed, and nothing about the products themselves.
01Intake
The request form
The request form asks for a storefront address, and a company name if you know it. That is the whole form. It used to also take a note and an email address; both are gone, because the audit reads the storefront rather than the note, and a public queue tells you more than a reply would.
The address and the name are written into the public queue in our repository, which is how the request appears on the queue and how the pipeline picks it up. Both are shown publicly. Do not put anything in the name field you would not want published.
The request also carries your IP address, which the server uses for a rate limit of 5 requests per minute. It is not written into the queue, not stored beyond that minute, and not published.
The form carries a hidden field that people do not see or fill. Requests that fill it are discarded without being read.
02Intake
The response form
The response form takes a company response, a correction request or a question. It asks what the message is about, a storefront or record, a company name, a sender name and role, an optional contact, and the message.
The message is written into a private file in our repository and a copy is sent to the operator. A company response is published on the record in full once a person has read it, with the company name and the date it arrived. The contact field is never published; it is used only to reply.
The same rate limit of 5 messages per minute, the same handling of the IP address and the same hidden field apply as on the request form.
03Measurement
Analytics
The site uses Vercel Analytics to count page views. It records the page path, the referrer, the country derived from the request, and the browser and device category. It sets no cookies, does not fingerprint, and does not follow you to other sites. We see aggregate counts, never an individual visit.
04Published data
Vendor and laboratory data
A vendor record holds information the vendor published on its own site: the domain, the reports it posted, and the contact address it lists. Company responses are published because the company sent them for that purpose, and the record says so. Laboratory entries hold information the laboratory publishes about its verification path.
We do not publish the names of individuals, and we redact personal names from exhibits where a report names a private client rather than a business. A person named on a published exhibit can ask for redaction under the corrections policy.
05Retention
What is kept, and for how long
06Requests
Your requests
To see, correct or delete anything you sent us, ask through the response form and give the contact you used, so the request can be matched to the submission. Deleting a submission does not remove a vendor record opened because of it. That record rests on documents the vendor published, not on your message.
Changes to this page carry a new effective date at the top. The rules for the register itself are in the methodology.