Match the identity, not just the name
Compare the publisher name, the publisher’s own domain and the product identity stated in its documentation. A search ranking or a polished logo does not establish ownership.
If a page uses one brand name and its destination displays another, treat the relationship as unresolved until the publisher explains it. Do not transfer screenshots, versions or support details between products because their names sound similar.
What each piece of evidence tells you
| Evidence | Useful for | Does not establish |
|---|---|---|
| Publisher statement | What the named publisher claims. | That an unrelated page is authorised. |
| Package identifier | Comparing Android product identities. | Safety or publisher ownership by itself. |
| SHA-256 hash | Checking whether two file copies match. | That the file is safe or official. |
| Screenshot | Documenting an observed screen. | Current features, cash balances or completed payments. |
Keep claims tied to their source
Record where a claim appeared and when you checked it. A version number or feature list can become outdated. A payment image is not a verified transaction, and a file being available is not proof that it came from the publisher.
Do not treat a site’s visitor estimate as an app’s user count. Search position, total site traffic, installs and active users are different measures.
Protect personal information during a check
You do not need to disclose passwords, one-time codes, UPI PINs or card security codes to compare a public product claim. Keep device protection enabled and use the provider’s established account-recovery process if you need account help.