Report a Yono Games listing

The report flow is the cleanest way to flag a broken download, a new version that the directory has not captured, an incorrect piece of metadata or anything else that does not match what you see on the app page.

Reports are stored locally in your browser for the editorial queue and are not published publicly. They do not auto-update the catalog, every flagged item goes through an editorial pass before the row changes.

For a quick fix, the report flow is the right tool. For a longer discussion about a publisher, a category or a policy, use the contact page instead. The directory keeps the two flows separate so the editorial queue stays tidy and the contact page stays usable.

Reports are intentionally lightweight. The form captures the minimum information needed to triage your submission — the app slug, the reason, an optional message and an optional evidence URL. We do not ask for an email by default; if you would like a follow-up, add one in the optional field. We do not store reports on a server unless you choose to send them — submissions made through this form are kept in your browser session only. When you submit, the form shows a confirmation message in your browser. The message is purely a UI signal; it does not mean the report has been received by an editor. The directory is editorial, and the report flow is the input to the editorial queue, not a synchronous channel. If a safety issue is urgent, use the Android install checklist and the report flow together — the checklist covers what to do in the meantime. Reports do not auto-update the catalogued row — every flagged item goes through an editorial pass before the row changes. Cosmetic copy edits are not flagged as reports; the report flow is for meaningful changes only. If you want to suggest an addition, send the app name, package, version, source URL and a short note via the contact page instead of the report flow — the contact form is the right tool for adding to the catalog. Every report you submit helps the directory stay accurate. Without the report flow, the directory would either publish stale numbers or auto-update rows from unverified sources. The report flow keeps the editorial queue honest. Use it whenever you spot something that does not match the catalogued row. If you want to follow up on a report, add your contact email in the optional field. The directory does not store reports on a server by default; the contact email is for follow-up only and is removed after the editorial pass. The report flow treats every submission with the same weight. A short note is enough — the editorial team follows up if a clarification is needed. Adding an evidence URL speeds up the editorial pass but is not required. The directory prefers a clear reason over a long message.

What happens after you submit

Once a report is in your browser session, it is queued for editorial review. The directory treats every report as an input to the editorial queue. The next time the editorial team refreshes the catalogued row, the report is read alongside the source review. If the change is meaningful, the row is updated; if the change is cosmetic, the report is logged and the row is not changed.

The directory does not promise a particular resolution or a particular timeframe. It promises that every report is read by an editor before the row changes. If a safety issue is urgent, treat the report as one input alongside the install checklist — the checklist covers what to do in the meantime.

Why this flow exists

Catalogued rows age. Source labels shift. New versions land on mirrors before the directory has reviewed them. Bonus campaigns expire. Without a report flow, the directory would either publish stale numbers or auto-update rows from unverified sources — both of which the editorial policy explicitly refuses.

The report flow is the cleanest way to flag a problem without losing the editorial independence of the catalogued rows. Use it. The directory reviews every report.

How the form is built

The form above is the simplest possible form for the job. It captures the app slug and the reason, both required, plus optional message and evidence. No login is required, no tracking pixel is loaded and no analytics event is fired. The submission is kept in your browser session only.