Fact-Checking Policy

Most pages about app downloads are full of numbers nobody can trace to anything. Here is the standard we hold ourselves to instead.

Source hierarchy

We weight sources in this order:

First-party platform documentation: Android Developers, Google Play Help, Apple developer and support documentation. This is what our instructions about install prompts, permissions and Play Protect are built on.
Directly observable behaviour: what the install flow actually does when we run it on a phone, recorded with the date and the Android or iOS version we saw it on.
Primary government sources: statutes on India Code, MeitY, Press Information Bureau, RBI and CERT-In publications, used for anything about app distribution rules in India.
Reputable secondary reporting — used for context, never as the sole basis for an important claim.

Other download sites are not treated as evidence for anything, including claims about the app they are distributing. A domain containing a brand name confers no authority, which is why we link to the operator’s own mobile page rather than to aggregators.

What we will not guess at

Some details genuinely change from build to build, and publishing a confident number for them is how the rest of this niche ends up contradicting itself. Rather than invent figures, we leave them out and tell you how to read the real value off your own device:

Exact version numbers. The build you install today may not be the one we saw. Your phone shows the installed version under Settings → Apps, which is always more accurate than a number on a web page.
Exact file sizes in megabytes. These shift with every release and differ by device architecture. We give a practical ceiling to plan storage around instead.
Download counts, user numbers and star ratings. There is no store listing to source these from, so we do not print them.
Licence numbers and corporate details we cannot tie to an issuing authority.
Anything about winnings. We make no claims about outcomes, returns or odds.

How instructions are kept current

Android and iOS both move menu items and reword prompts between releases, which is the most common way a guide silently goes stale. When we re-review a page we walk the flow again on a current device and update the wording to match what is actually on screen. The last-reviewed date on each page reflects that check and nothing else — it never moves just to look fresh. The wider process is in our editorial policy.

Corrections

When we get something wrong, we correct the page, update the reviewed date, and add a note where the error was material. If a step does not match what your phone shows, or a fix no longer works, tell us through the contact page — the device model and Android version help us reproduce it quickly.

Policy last reviewed: 26 August 2026