Private-beta policy draft

Community guidelines

Draft — pending owner and legal approval

These statements describe the proposed curated-beta baseline, not finalized legal terms or a claim of compliance. Public self-service submissions remain locked until policy approval. The owner must approve age handling, creator licensing, retention and escalation procedures.

Create responsibly

  • Submit only browser games and artwork you have rights to use. Disclose AI development assistance, generated assets, tools and human contributions accurately.
  • No malware, credential collection, deception, abusive or unlawful content. The beta does not make a mature-content or age-eligibility commitment; those policies require owner approval.
  • Hosted games must be self-contained and fit the reviewed baseline sandbox. No arbitrary creator backends, external SDKs, platform-funded inference, service workers or threaded WebAssembly.
  • Manual review applies to exact metadata, media, links and immutable builds. Approved publication is not an independent verification of AI claims or a guarantee that a game is harmless.

Give useful feedback

  • Critique the work, not the person. Be specific and include reproduction steps in bug reports.
  • Feedback, bug reports and questions are plain text. One reply level keeps discussions focused.
  • First guest comments, suspicious posts and flagged edits may remain pending moderation. Creators can acknowledge or mark bugs fixed; they cannot change another person’s text or ratings.
  • Member-origin and guest-origin ratings are separate. Do not manipulate scores, reset identities to evade quotas, or impersonate another creator.

Report and appeal

Use “Report” on a game or comment for unsafe content, rights concerns, abuse, broken builds or spam. Reports are private and moderators record a reason for decisions. Security restrictions may immediately disable a game or revoke a build. Rights and takedown procedures, appeal availability and response windows require a named operational owner.

Contact and escalation

Policy contact is not configured

The owner must assign a moderation and rights/takedown escalation contact before launch. In-product reports are available when participation is configured; do not treat this beta as having an operational response-time guarantee.