Respect rights and the law
Do not use the service to upload, distribute, promote, or sell material you know you are not permitted to use.
- Do not impersonate another person, publisher, tournament, rights holder, or official organization.
- Do not conceal ownership, remove required attribution, or route a sale externally to evade an agreed distribution path.
- Do not use exports, rankings, labels, or generated assets to make deceptive endorsement or affiliation claims.
Protect people and personal information
Do not publish harassment, threats, exploitative material, non-consensual private information, or sensitive information about children through projects, annotations, media, Live payloads, or packages.
- Collect and share only the participant information needed for a legitimate tournament purpose.
- Do not use the service for covert tracking, discriminatory profiling, or attempts to identify anonymous users.
Protect the service
Do not interfere with availability, bypass limits, probe another user's data, reuse credentials, automate abusive traffic, or disguise a harmful file as supported content.
- Do not submit malware, exploit code, credential theft, destructive routines, or instructions designed to escape package and capability boundaries.
- Do not use the monitor, Live tokens, shared links, or external image requests to attack another service.
Packages and automation
Third-party package intake is unverified and inert. A successful integrity check proves that bytes match a digest; it does not prove publisher identity, safety, ownership, compatibility, or legal permission.
Routines must remain within the current free, bounded preview model. Uploaded Extensions, Materials, and Routines do not receive authority to execute against a production board.
Reports and response
The operator may preserve evidence, restrict access, remove a submission, or refer a serious issue for review when a documented service process authorizes it. The current product does not yet provide a complete public moderation, appeal, or rights-report system.
A production policy needs clear reporting, notice, correction, appeal, emergency, retention, and regional escalation procedures before it is represented as an enforceable operations programme.
Regional review notes
These notes identify launch-review work; they are not legal conclusions. The app’s selected region is a presentation preference and does not establish residence, citizenship, governing law, tax position, or entitlement.
en-CA · CADEnforcement and complaint handling must preserve applicable Canadian rights and should not describe a private policy as a government finding.
en-US · USDA rights-report or removal process needs documented notice, evidence, repeat-abuse, correction, and appeal handling before public creator distribution.
en-GB · GBPAny moderation, account restriction, or complaint process must be implemented and explained consistently with the service actually offered in the United Kingdom.
ja-JP · JPYThe public policy and any enforcement notice need a reviewed Japanese-language version and a usable local complaint route.
en-NG · NGNComplaint, restriction, content, and appeal procedures need to match the service's actual Nigerian operations and available support channels.
Operator and contact
Operator: Operator legal name not configured. Placeholder identity or contact values are a production launch blocker, not anonymous legal terms.
This draft should not be relied on as final assent, a waiver of mandatory rights, or a substitute for qualified advice in a launch jurisdiction.
Legal and privacy contact not configured