Method and Evidence

Last updated: 28 October 2026

This page describes the evidence behind a record and the limits of the method. It is the reference for the labels used across the index.

Sources

We read public listing pages, store metadata, package headers and published terms. We do not install, run or scan the apps. A package string, version or size is recorded only when it can be read from a public file record; otherwise the field is left empty and the page says so.

Evidence states

• Measured. Read from a file or package record.
• Advertised. Read from a listing page; marked †.
• Category pattern. A repeated interface pattern, not a capture of one build.
• Editorial. The desk’s reading, not a measurement.

Package identity

A package string can be copied by a repackaged build. The signing certificate is the stronger identity check. We record the package string where it is public; we do not claim that the string alone proves the app is the original.

Bonus and cashier claims

Advertised amounts are reproduced as claims. The release condition, turnover, expiry and forfeiture are recorded where a source states them. Where no condition is published, the record says the condition is missing rather than assuming one.

Limitations

The index is not a live crawler, not a security audit and not a legal review. Listings change without notice. A record can be incomplete, and a package can be repackaged after the review date. We do not assert that a product is safe, lawful or payable.

Updates and corrections

Records are refreshed when a source changes or a correction is accepted. The last-modified date shows the last review. Corrections are handled through Corrections; the evidence label changes only when the underlying source supports it.