What we look for when reviewing submitted games
A transparent guide to our moderation checklist: safe embeds, working builds, metadata quality, and age-appropriate content.
Transparency builds trust. This post walks through the checklist our moderators use when reviewing developer submissions.
First, the build must load: a valid index.html, no broken asset paths, and reasonable load time on a mid-range laptop. We reject archives with executable files, obfuscated malware patterns, or zip-slip path traversal attempts.
Metadata matters — write a clear title, short description, and controls summary. Upload a thumbnail that represents gameplay, not a generic stock image.
Content must match the declared age rating. Excessive gore, hate symbols, or misleading casino mechanics will be rejected. When in doubt, mark a higher age rating and explain in the description.