Minors
Any depiction of, or alongside, a person under 18, and any framing that presents an adult likeness as a minor.
Why this line exists
A creator can consent to their own likeness being used. Nobody can consent on behalf of a child, and no adult's permission makes output that juvenilises their likeness acceptable. This is checked before a creator's own rules are read, so the outcome does not depend on how carefully their boundary set was filled in.
How a request is matched to it
Terms naming children, ages below adulthood, or school contexts, matched on word boundaries against the normalised request.
Matching is deterministic and anchored to word boundaries, so a term inside a longer innocent word does not fire. The matched term is returned in the refusal, which means a creator can see why their rule caught something and a requester can see what to change.
Whether creators permit it
Never. This category cannot be permitted by any boundary set.
Questions
- Can a creator permit minors?
- Never. This category cannot be permitted by any boundary set.
- What happens to a request that breaches it?
- It is refused before any model is called, with the rule name and the matched term quoted back. The refusal is recorded in the creator's audit log. It is never rewritten into something permitted.
- Does the API enforce this too?
- Yes — the licensed-likeness API and the MCP server call the same evaluation the website calls. There is one implementation of the consent gate, so an automated integration cannot get a weaker check than a browser.