Editorial policy

This policy governs every peptide profile, guide, comparison and FAQ published on Peptide Library. It sets out what we publish, where the information comes from, how it is reviewed, and how to get something corrected.

Purpose and scope

Peptide Library is a reference and comparison platform for people researching peptides. We publish structured peptide profiles, research guides, peptide comparisons, vendor price comparisons and calculators. We do not publish clinical advice, treatment plans or dosing recommendations for humans, and nothing on the site should be read as a substitute for a qualified professional.

Who writes and reviews content

Content is produced and reviewed by the Peptide Library editorial team, operated by Superfime LLC. Profiles and articles are published under the organisation rather than individual bylines. Each peptide profile records the date it was last reviewed and a content version number; blog articles show their publication and update dates.

Sourcing standards

  • Scientific statements are attributed to peer-reviewed literature indexed in PubMed or resolvable by DOI, to regulatory records (FDA, WADA), or to chemical registries (PubChem, ChEMBL, DrugBank, FDA UNII).
  • Vendor marketing copy, product listings and social-media posts are never used as sources for claims about mechanism, effect or safety.
  • Every linked citation is verified against the publisher of record by an automated audit before it appears on a profile; the methodology page reports the latest results.
  • Where the evidence is preclinical, limited to small studies or absent, profiles say so. We do not describe animal or cell findings as effects in humans.

Research-use framing

Peptide Library covers compounds that range from FDA-approved prescription medicines to research chemicals with no approved use. Profiles state the regulatory status of each compound. Protocol fields (dose ranges, frequency, route, reconstitution) describe what published research and product labelling report; they are reference data for research planning and are not recommendations. We will not publish content that presents an unapproved compound as a treatment, or that instructs readers on human self-administration.

Independence and affiliate disclosure

Peptide Library does not sell peptides. Some outbound vendor links include affiliate or coupon parameters, and the site may earn a commission when a reader makes a purchase through them. Affiliate relationships do not influence vendor rankings, which vendors cannot pay to change, and do not influence the content of any peptide profile or article. Vendor links are marked as sponsored links for search engines. See how rankings work.

Use of AI tools

The editorial team uses software, including AI-assisted tools, to help draft structured summaries, check citations and keep data consistent across 200+ profiles. Every published statement is tied to a verified source, and the automated citation audit is run against the NCBI and Crossref records rather than trusting generated text. AI tools are not used to invent studies, statistics or outcomes.

Corrections policy

We correct errors when they are found. To report one, use the support page or email support@peptidelibrary.app with the page URL and the source that supports the correction.

  • Reports are acknowledged and reviewed against the cited sources.
  • Factual errors in a peptide profile are corrected in place; the profile's review date and version number are updated so the change is visible.
  • Articles that are materially wrong are corrected with the update date shown; articles that are withdrawn return a “gone” status rather than silently redirecting.
  • Regulatory status fields are reviewed when FDA or WADA records change and on a scheduled basis.

Update cadence

Peptide profiles are reviewed on a rolling schedule and whenever new approvals, trial results or registry changes are identified. Vendor price snapshots are refreshed automatically. The date shown on each page is the date the content itself was last reviewed, not the date the page was regenerated.