Methodology: How This File Is Compiled
Sources, evidence tiers, update cycle and the rules that keep this file descriptive.
This site is a reading file, not a testing programme. It compiles public artefacts about a supplier and the compounds it lists, sorts those artefacts by what they can support, and states where the record runs out. The methodology below is the whole of the editorial policy; there is no separate scoring system, because the file does not produce scores.
Sources
Four source classes are used. Primary documents are certificates, invoices, terms pages and regulatory registries. Dated public accounts are forum posts and review pages that carry a date and enough detail to check. Catalogue snapshots are listings captured at a stated moment. Secondary commentary is everything else, including pages that aggregate the above. Secondary commentary is used for leads, never as the sole basis for a factual statement.
Evidence tiers
Tier one is a lot-mapped, verifiable laboratory report. Tier two is a dated, specific public account with a resolution. Tier three is a catalogue snapshot or a listing claim. Tier four is undated commentary. A statement is labelled with the tier it rests on, and claims that cannot reach tier three are carried as context rather than evidence.
What the file refuses to do
It does not publish quantities, human protocols or outcome claims. It does not declare a product safe or unsafe, because safety determination requires controlled studies and reporting systems that a reading file does not have. It does not accept payment for inclusion, and it does not use affiliate links. Ad units are labelled and are not endorsements.
Update cycle
Records are reviewed quarterly and revised when a primary document changes or a dated account materially updates the picture. Each page carries a date. Pages are not rewritten to follow short-term sentiment, and a stale page is preferable to a page that has been quietly reframed without a date change.
Corrections
Corrections are published with the date and the specific change. If a vendor believes a statement is inaccurate, the response is to supply the document that resolves it; the file will record the document and revise the statement. Assertions without documents are noted as assertions.
Does this site test products?
No. It compiles and grades public documents. Testing requires a laboratory and a sampling programme.
Are vendors allowed to pay for coverage?
No. There is no paid placement and no affiliate revenue. Ad units are labelled separately.
How are errors corrected?
With a dated note and a specific revision. A document that resolves the question is the fastest route.