Use pass, unknown and concern labels
| Dimension | Evidence requested | Record separately |
|---|---|---|
| Identity | Named publisher and confirmed release channel | A copied logo is not identity |
| File | Package, version, byte size, digest, signer | One specimen is not every release |
| Privacy | Current policy and observed prompts | Policy text and behaviour may differ |
| Product model | Purchases, stakes, redemption and account conditions | “Free download” does not mean no cost |
| Support | A channel linked by the actual publisher | A search result is not authentication |
| Availability | Current product-specific eligibility | Download reachability is not permission |
Compare without hiding unknowns
Create one row per product and fill each evidence field. Leave unknown values unknown; do not convert them into a guessed pass. An app with more available documentation may be easier to inspect, but that alone does not prove better behaviour. Weight your needs explicitly rather than averaging unrelated facts into a single number.
New app does not necessarily mean new publisher
A new name, launch banner or page date can appear without a new codebase. To examine a claimed update, compare package and signing history plus dated release documentation. A new signer can have legitimate explanations, including documented key rotation, but unexplained changes should pause the comparison.
A directory is not a recommendation list
Our app-name directory collects names from the supplied reference sitemap and links them to appropriate checks. It has no affiliate ranking, fabricated rating or automatic download. The Master assessment shows how an incomplete file record is reported.
For a rules-only reader
If your aim is to learn, use Teen Patti examples or a Rummy hand layout before sharing data with an app. Both lessons are readable without an account or install.