Peptide Record

Methodology

Corrections and removal

Every record here came from a document with a URL and a fetch timestamp, and every one can be corrected or removed against that source.

If you are quoted here

Mentions are recorded with a source link and a short verbatim excerpt. We never paraphrase a named person’s position — a summary of what someone “thinks” about a compound is precisely the artefact that turns a warning into an endorsement.

If a mention attributed to you is wrong, mischaracterised, or you want it removed, it can be corrected or deleted. Stance can be corrected independently of the mention itself: a physician saying “there is no good evidence for this” is being accurate, not opposing anything, and if we have labelled that as anything other than what it was, that is our error to fix. Ask for a correction or removal

If you are a vendor

Transparency scores are computed by one rule applied identically to every seller, with no adjustment for any commercial relationship. Every component links to the document it was read from.

If a document was misread, if a disclosure exists that we did not find, or if an entity has been merged with one that is not yours, that is a factual correction and we will make it. We will not adjust a score for any other reason. A disclosure you publish after we scored you is a re-score, not a correction — recollect and it recomputes. Exercise a right of reply

If you hold rights in a retained document

Source documents are retained in full so derived fields can be re-verified, and are never served publicly. If you hold rights in a retained document and want it removed, removal is executed by source host and by collector identifier, so it can be scoped precisely rather than approximated.

How to ask

Both routes are live
  • Vendor right of reply — a recorded input behind a transparency score is wrong, a disclosure was missed, or a record names a business that is not yours.
  • Correction or removal of a mention — a mention attributed to you is wrong, mischaracterises your position, or should come down.

Both forms ask for the URL of the page carrying the record and the source link printed on the record itself. Those two identify a row exactly, and where a public surface offers a record reference the link carries it for you.

A request is recorded, not applied. It is stored, reviewed by a person, and decided with a written reason that stays on the record whichever way it goes. Nothing you submit changes a grade, a score, a stance, or removes anything on its own — because both of these processes are used by someone with an interest in the outcome, and a route that applied requests automatically would let a vendor delete its own warning letters.

The forms are bounded, because they are unauthenticated: fixed choices, capped lengths enforced by the database, a limit of three open requests per record, five per address per day, and a ceiling on how many arrive in an hour across everybody. Each page states its own limits and what they cost.

If you hold rights in a retained document, neither form is the right route — removal there is executed by source host and collector identifier, which is a different operation. Say so in a request on either form and it will be handled as such.

Nothing on this site is published or indexed yet either way. See the publication status page, which reads both of these gates from live state rather than asserting them.