Our source ladder
| Level | Use | Example |
|---|---|---|
| 1 · Attributable primary | Product identity and current disclosures | Google Play developer/package record; publisher site |
| 2 · Technical observation | Verifiable page or URL behaviour | Package ID, link destination, visible disclosure |
| 3 · Common convention | Rule education where no single owner exists | Six standard hand categories |
| 4 · Third-party claim | Question discovery or conflict documentation | An unofficial APK/referral page |
| 5 · Editorial guidance | Practical safety steps and interpretation | Match developer + package + destination |
A lower-level source cannot silently override a higher-level attributable record. If sources conflict, the conflict is part of the article.
From research to publication
- Define one primary search intent for the page.
- Collect attributable sources and note access dates.
- Separate observed facts from source claims and common rules.
- Write an answer-first summary, examples and explicit limitations.
- Review identity, internal links, metadata, structured data and accessibility.
- Publish with an owner, date, source trail, correction route and review trigger.
We do not publish invented ratings, download counts, bonus amounts, personal testimonials or expert credentials.
AI assistance and human responsibility
AI tools may assist with research organisation, drafting, consistency checks, code generation and quality assurance. They are not presented as authors or sources. The Editorial Desk remains responsible for selecting evidence, resolving conflicts, removing unsupported claims and approving publication.
AI-generated prose does not make a claim true. Product facts must still trace to a source readers can inspect.
Corrections policy
Email [email protected] with the affected URL, exact statement, why it appears wrong and a supporting source.
Typos and clarity
Corrected in place without changing the meaning.
Identity or safety facts
Corrected promptly; review date and visible note updated where useful.
Conflicting evidence
Claim may be qualified while the source conflict is reviewed.
No inspectable support
We explain the evidentiary gap rather than publishing pressure-based changes.
Commercial and conflict rules
- No payment may buy a factual conclusion or “official” label.
- Sponsored material must be clearly identified before the reader acts.
- Affiliate links, if introduced, must not be disguised and must not auto-download files.
- Bonuses, withdrawals and legality require attributable, current evidence and cannot be inferred from keywords.
- Editorial corrections are not conditioned on a commercial relationship.
Review dates and triggers
“Last reviewed” means the page’s material claims and live sources were checked, not merely that a date string was changed. Event triggers include a developer or package change, new distribution domain, revised purchase model, source removal, material rules update or responsible-play control change.
Pages should also receive a scheduled source review even without a known trigger. See who owns the work and how to contact the desk.
Policy effective and last reviewed: 27 August 2026. Future material revisions should be described on this page.