3JSGames · Legal & Trust
Creator Terms
Responsibilities and permissions for hosting your browser games.
Version 1.0-draft · Last updated 2026-09-05 · Effective pending approval
Your content and hosting permission
You retain ownership of your games and assets. By submitting content, you give 3JSGames a limited, non-exclusive permission to store, host, technically reproduce, scan, serve, display and distribute it through the platform as needed to operate the service.
That permission includes displaying submitted thumbnails and metadata in discovery surfaces and platform promotion. It does not transfer ownership or give other creators permission to reuse your source or assets. The licence wording and its duration remain subject to professional review before these draft terms become effective.
Rights and third-party materials
Upload only code and materials you own or have permission to distribute in a browser game. This includes music, sound, images, models, fonts, libraries and other dependencies. Comply with open-source attribution, notice and source-distribution obligations that apply to your build.
You are responsible for resolving conflicting third-party rights and describing your game accurately. An upload passing automated checks is not verification of your rights.
Executable code and security
Review the complete production build, including dependencies. Do not submit malware, phishing, credential harvesting, crypto mining, browser exploits, sandbox escape attempts, platform/API abuse or remote administration functionality. Do not evade scanners, build validation or runtime restrictions.
Do not hide tracking or collect player personal information without authorization and an appropriate disclosure. Never embed credentials or secrets. Technical upload limits and restricted files are described in Docs and enforced by the upload pipeline; they can change.
SDK and player data
Use supported SDK APIs within their game and player authorization boundaries. Do not use shared JSON, multiplayer messages, saves or leaderboards as a personal-data collection channel. Do not attempt to obtain player email addresses or authentication tokens.
Keep external requests intentional and documented. Games run under the platform's current shared play-origin architecture; do not assume isolation from every other uploaded game or attempt to access another game's browser storage.
Publishing, moderation and removal
Uploads are validated and scanned before eligible publication. Preview, staged builds and retained build history do not guarantee public availability. Operators may disable a game in response to policy, safety or IP concerns. New game moderation decisions are available to the affected creator in Appeals.
You can unpublish supported games or request their deletion through creator tools. Unpublish is not deletion. Deletion requires asynchronous artifact and relational cleanup; reports, moderation evidence and selected operational records can remain. Do not assume immediate deletion from backups, caches or vendor logs.
Complaints and future commercial features
Rights holders can submit a Copyright and Intellectual Property Notice through Report Content. Provide relevant evidence if you appeal a decision; do not include secrets or unnecessary personal data.
Payment integrations, advertising and creator revenue sharing are outside this foundation. Any future monetization requires separate or additional terms and implementation. These terms promise no revenue or payment.