Documentation
FOR DEVELOPERS

Content Policy

What’s allowed on edu.games, how moderation works, and what happens if a published game is taken down. Questions? Email developers@edu.games.

What we allow

  • Games must be age-appropriate for the age range you declare at upload, and appropriate for a school setting more broadly — edu.games is used directly in classrooms.
  • Educational value: a clear connection to the subjects and learning outcomes you list. Pure entertainment with no learning framing will be rejected in review.
  • Original or properly licensed content. You must own or have the rights to every asset (art, audio, fonts, third-party libraries) your game ships.

What is not allowed

  • Violence, gore, sexual content, or content that sexualizes minors, in any form.
  • Hate speech, harassment, or content that denigrates a protected group.
  • Gambling mechanics, loot boxes, or real-money transactions inside the game itself.
  • Malware, cryptocurrency mining, deceptive ads, or any code that behaves differently from what was submitted for review.
  • Collection of student personal data beyond what your declared xAPI integration requires (see docs.edu.games/xapi).
  • Broken or non-functional builds — a build that fails to load is treated the same as a policy violation for moderation purposes.

How moderation works

  • Every submission goes through the review queue before publishing (2–5 business days — see the FAQ). A rejection includes written feedback so you can fix and resubmit.
  • After publishing, players and teachers can report a live game directly from its game page. Reports are reviewed by our moderation team.
  • If a published game is found to violate this policy, an admin can take it down. A takedown immediately and permanently revokes play access for everyone — including students and teachers who had already purchased or licensed it. There is no continued access for existing purchasers after a takedown; the roadmap intent is content removal, not a partial restriction.
  • A short residual window is possible for a session that started moments before takedown: signed play URLs are valid for up to 10 minutes, so an in-progress session may keep running until that URL expires. No new session can start once a game is taken down.
  • A takedown is a distinct status from rejection. It is not resubmittable — contact developers@edu.games if you believe a takedown was made in error.
AuthenticationxAPI Integration