How we verify and select apps

The directory contains 23 app records and 38 problem guides. Each record compares a specific public statement with its source and records what that evidence can establish.

Four checks behind a record

1. A specific reader question. Start with the exact app name and message: a pending withdrawal, KYC request, missing credit, lock message or install error. A familiar name alone does not identify the product.
2. A useful comparison. Identify what changes the decision: conflicting amounts, a clause absent from the terms, a different product with the same name or an official closure route. Repeating a landing-page claim does not resolve the question.
3. Something public can be checked. A landing page, published terms, a Play listing, a support address or a closure notice. We need at least one artifact to quote, and we date it.
4. The scope is honest. If the public record does not support a fact, the page says “a public claim” instead of inventing a test. A public-source comparison does not require, and must not imply, a deposit or a payment test.

Why these records are covered

Yono 777 illustrates why a same-name website, directory card and store reference must not be combined into one authenticated product. Diwa 777 gives a direct slot-first comparison. Yono Rummy is now the problem-first rummy example. Yono Games illustrates a deposit amount being confused with a cash-out floor, and fee statements that apply to different transaction tiers. A current Yono VIP page claims a ₹100 floor, which is absent from its terms. Diwa 91’s single current page could not be tied to the app, so no amount is recorded for it. Rummy 365, Win Rummy, GOGO Rummy, Rummy Cue and Ok Rummy have published terms; RummyCulture has a closure notice. Rummy Wealth, Rummy Noble, Rummy Mars, Rummy Leader and Rummy Ultra illustrate third-party file-host and identity gaps. Money Rummy, Rummy 888, ABC Rummy, Max Rummy and Yono VIP also have brand-domain terms; those documents support particular clauses without confirming the advertised amounts or installed file. Bingo 101 separates promotional expiry from turnover. Cash Rummy adds a specific example of a fantasy-cricket amount embedded in a different brand’s page, as well as download and player figures whose measurement bases must not be mixed.

Review scope and status labels

The ₹ rule

We keep three numbers separate. A bonus claim is advertising. A cashier claim is what a public page or cashier description says. A credited payout is a measured result. This build has public claims but no credited-payout measurement. We do not turn a ₹777 headline into a “₹777 payout”.

What we record

• The public URL, the checked date and the exact claim.
• Where two public pages disagree, both figures and the conflict.
• The exact product, page section and date to which an amount, document statement or time window belongs.
• The support route a user can try, without claiming a response time.
• The legal/region note and the 18+ status.

What we refuse to do

We do not invent a device, a package name, a payout screenshot, a support reply or a “safe” rating. We may quote a published withdrawal window as a source claim, but never present it as a measured payment time without dated transfer evidence. We do not accept a bonus headline as cash. We do not advise a deposit. We do not host APKs.

Source grades: A, B and C

A identifies an original document: brand-published terms, a privacy policy, a closure notice, an official authority publication, or a measured file/HTTP response where the row says so. It supports only the statement or measurement actually recorded; a brand page does not authenticate its operator or APK. B identifies published feedback, labelled as an individual report or a platform aggregate. C identifies a third-party marketing or reference claim, including a directory card or an affiliate page. These labels classify source types, not truth, safety or account outcomes. Several pages from one website are not independent confirmations.

A grade describes the source, not the truth of your account. An A-level terms page can still be incomplete, and a B-level review can describe a different build. No linked, app-specific independent user report is presented as evidence in these dossiers; affiliate testimonials are not treated as independent user evidence. Amounts quoted from third-party directories and promotions are C-type claims. A brand’s own marketing statement can be recorded in an A-type original source; neither label establishes an account credit or payout. A source grade does not authenticate an app or establish how a user’s account was handled.

Updates and limits

Each source row shows the date that particular material was checked. An editorial revision can change the page date without implying that every external source was rechecked. A source change, a correction or a device log triggers a targeted review. A public-source review cannot confirm your account’s cashier, KYC or payout. Where that matters, the page says so. Use the corrections page to send a better data point.

Start with the app directory or the problem hubs.