01 — Establish the destination
Start with the game's official publisher or an official page that identifies the operator. Record the destination address and the source used to establish ownership. Similar names, fan pages and promotional landing pages are not interchangeable. An unfamiliar redirect or a changed domain calls for another review.
02 — Describe the actual game
Identify what the player does: arranging cards, solving a board or word puzzle, or planning a transport network. Distinguish a browser version from a downloadable app. Explain registration, optional purchases and virtual items where the publisher discloses them. Do not present virtual tokens as cash, savings, earnings or withdrawable rewards.
03 — Check visible privacy and security information
Look for HTTPS, accessible privacy information, publisher contact routes and clear account guidance. These are visible signals, not proof that a platform is secure. A public-page review cannot inspect a publisher's internal systems, establish how every payment is processed or replace a professional security audit. No security certification is awarded by this directory.
04 — Assess access and stability honestly
A direct play test should record its date, device, browser, region and result. Check page loading, navigation, readable controls and the route into the game. A successful visit is a snapshot; it is not an uptime guarantee. Where only publisher information has been checked, describe it as a source review rather than a hands-on gameplay test.
05 — Explain the judgement
Prioritise a clear starting path, understandable rules, transparent costs and the ability to stop. Separate editorial opinion from factual features. An editorial label does not represent regulatory approval, Google Ads certification or an endorsement from the publisher. The current catalogue should not be read as a published security audit or measured uptime study.
06 — Make corrections possible
If a title, destination, feature or commercial condition changes, the entry needs a fresh check. Send the affected page address and a link to the official correction to support@arcadelevelindex.com. Avoid sending account credentials or private payment information.
Questions or corrections? support@arcadelevelindex.com