Corrections policy

A directory about a fast-moving app ecosystem will contain errors from time to time — promo statuses go stale, apps rebrand, details change. This page explains how to tell us and what happens when you do. Corrections make the directory better, and we treat them as contributions, not complaints.

How to report an error

Use the contact formwith the "report an error or correction" topic, or email [email protected]. The most useful reports include: the page address, the specific statement you believe is wrong, what you believe is correct, and — where possible — a source we can check, such as an operator's own page or documentation.

How reports are reviewed

1. We acknowledge the report and check the claim against available sources.
2. If the error is confirmed, we correct the listing's data record, which updates every page built from it, and refresh the page's last-updated date.
3. If the claim cannot be confirmed either way, the relevant field is set to "awaiting verification" rather than left asserting something contested.
4. If the report concerns a promo code, the code's status is updated using our fixed status vocabulary — expired codes are relabelled as expired, not deleted, so readers can see the history.

What we correct versus what we won't

Factual errors, stale statuses, broken links, and misattributed details are all in scope. Requests to make a listing more promotional, to remove accurate safety cautions, or to add unverifiable claims ("mark our code as working") are declined — the editorial policy governs those decisions regardless of who asks.

Timing

We aim to review correction reports within a few working days. Corrections affecting safety-relevant information are prioritised.