What we allow, and how a game gets stopped.
The rules every game on Unispawn is held to, who applies them, and what happens when one is broken. This is the page the Digital Services Act asks us to write, and it is meant to be readable rather than exhaustive.
What this covers
In short — games, listings, and the text around them.
Everything an author publishes here: the game itself, its title and description, its cover image, its age rating, and the six seconds of it we record for the store. Reviews and reports are covered too.
Unispawn hosts games written by other people. We are not their author and we do not check every build by hand before it goes live. What we do instead is described below, and being honest about the difference is the point of this page.
What is not allowed
In short — four lines, and the first is the hard one.
Code that attacks the person playing it. Malware, miners, anything that tries to reach outside the sandbox it runs in, anything that harvests a player's data or credentials. This is the line that gets a game removed fastest and with the least sympathy.
Material you have no right to publish. Someone else's art, audio, fonts, code or characters — including where a model produced them from that material. If a rights holder can point at it, clearing it was your job before you uploaded.
Content that is illegal where we operate, and content that sexualises children, incites violence against people, or exists to harass a specific person. There is no version of these we host while we work out the nuance.
Deception about what the game is. A listing that promises one game and ships another, an age rating chosen to slip past a filter, or a description written to be found rather than to be true.
What machines do, and what they never do
In short — they detect; they never decide.
Every build is scanned automatically before it can be published. The scan reads the archive's structure, looks at what the code is capable of, and sweeps for credentials that should not be in a public bundle. A model may also read a build and raise a concern.
No automated system removes a game, refuses one, or closes an account. Detection can only ever raise a concern to a person — by construction, not by policy: the code takes the higher of the automated and the human assessment, so a machine can add a flag and can never clear one. Every restrictive decision on this platform is made by a human being.
What happens to a game
In short — three states, and only one of them is a sanction.
A flag means someone is looking. The game stays live and behaves normally, because a flag is a signal to us, not a punishment for the author or an interruption for the player.
A suspension takes the game off the shelf while a decision is made. A removal takes it off permanently and clears the game's data from the browsers of people who played it — that last part is why a removal is not used lightly and never for a billing problem.
A game that is behind on hosting payments stops being served and is not moderated at all. It keeps its saves, its reviews and its listing, and comes back when the account is settled. Money and moderation are separate systems here and neither writes to the other.
What the author is told
In short — the reasons, in writing, every time.
Every restrictive decision produces a statement of reasons for the author: what was decided, which rule it rests on, what evidence was used, whether automated tools were involved in detecting it, and whether they were involved in deciding it. The answer to that last one is always no, and saying so is the strongest sentence in the document.
The author can contest any of it. We offer that as our own policy rather than as a formal mechanism under Article 20, which does not apply to us — and we would rather say that plainly than imply a route that does not exist.
Telling us about a game
In short — two doors, and most people want the first.
If a game is broken, slow, or not what its listing says, the fastest fix is the report button on the game itself. That goes to the author, and it is not a legal notice.
If you believe a game breaks the law or infringes your rights, use the notice form: unispawn.io/legal/notice. Copyright specifically has its own page and a registered agent — see copyright.
Repeat breaches
In short — recorded when a person confirms one, not when a machine suspects one.
An account that repeatedly publishes material it has no right to publish, or that repeatedly ships code that attacks players, is closed. A breach is recorded against an account only when a human has confirmed it, and what was confirmed is written down at the time rather than reconstructed later.
Changes to this policy
In short — 15 days, the same as the terms.
We will change this page as the platform grows and as we learn what these rules miss. Material changes get an email and at least 15 days' notice before they apply.