Methodology
Every piece of app information has an origin, a date and a limit. Keeping those visible is the foundation of this reference.
Updated November 12, 2026Identify the exact app
A profile is attached to an exact store identity: an Android package name or an Apple App Store ID. The display name is a label, not a unique identifier. A numeric iOS ID is normal, and a package name does not need to resemble the app name.
Additional store links are shown separately. A similar name or icon does not establish identical code, ownership or behavior across platforms.
Preserve the source and the date
Listing data may come from a captured store record or a public listing archive. Developer names, categories, sizes, download bands and ratings are presented as recorded, with capture dates where available.
Publisher screenshots show what was displayed in a listing; they do not independently verify the features shown. Store ratings remain store figures, not ratings issued by this website.
Missing, unavailable and zero are different. An unrecorded install count is not treated as zero, and an absent permission list is not treated as a clean bill of health.
Separate metadata from artifact findings
Listing-based profiles describe public records. Android artifact profiles may additionally include a file hash, version, declared permissions, signing information and strings or SDK references found through static analysis.
These findings apply to the identified artifact only. A declared permission is not proof that it was used. A host string is not proof that a connection occurred. Widely used SDKs and platform signing keys do not establish shared app ownership.
iOS profiles are listing-based. They do not imply that an encrypted application binary was examined or that the service behind an app was tested.
Describe availability without a verdict
When the source records a removed store listing, the profile shows that recorded date. Apps may leave a store for multiple reasons. Unless an authoritative explanation is available in the record, we do not supply one.
A historical removal record is not a live availability check. Store references may redirect, return an error or show a different version today.
Read the profile as a whole
Start with the exact identifier, then compare dates and sources. Treat app claims as claims, and distinguish a listing snapshot from observations about a specific file. No single field provides a complete evaluation of an app or the organization behind it.
We do not publish a risk score or guarantee an app’s safety, performance or suitability. For corrections to a record, use Contact.