Peptide Policy Watch

Editorial Standards

Last updated

Last updated: October 25, 2026.

This page pulls together the rules we hold ourselves to. Each rule is explained in more detail on the page it links to.

Ownership and funding

Peptide Policy Watch is owned and run by an independent individual publisher. It is not part of a company, network, government agency or advocacy group. No outside party funds it or has any say in what we publish. As of the date above, the site has no advertising, sponsors, affiliate links or other income. See About and Affiliate Disclosure.

Editorial independence

  • Nobody can pay for coverage, for placement in a post, or for a change to a post.
  • We are not affiliated with the FDA, the FTC or any company, pharmacy or telehealth provider we write about.
  • If a financial relationship ever exists, we will say so on the affected page, close to the relevant text, and update our Affiliate Disclosure and Disclaimer and Disclosures.

Who writes and checks the posts

Posts appear under the byline "Peptide Policy Watch editorial team." In practice, that means one independent publisher working with AI-assisted drafting tools and a written checklist. We have no medical, pharmacy or legal credentials, and nothing here is professional advice. See Editorial Team.

Sourcing

  • Primary documents come first: FDA, Federal Register, FTC, court and company filings, linked directly.
  • Secondary reports are labeled as secondary, and anything we could not confirm is labeled unverified.
  • Each post shows the date we retrieved each source and the date of any status we describe.
  • Full details: How We Source.

What we do not publish

We do not publish dosing, protocols, sourcing or vendor information, or medical advice, and we do not link to sellers. See Disclaimer and Disclosures.

Corrections and updates

We fix errors of fact quickly, aim to do so within 24 hours of a credible report, and log each correction publicly. Updated posts show an "Updated" date. See our Corrections policy and log. To report a problem, use Contact.

Privacy

See our Privacy Policy.