Sexual content
Sexual acts, sexualised posing, or explicitly erotic framing.
Why this line exists
The highest-stakes category a creator can decide about, and the one where silence must not read as agreement. It is forbidden unless a creator has explicitly permitted it — a boundary set that simply does not mention it has not licensed it.
How a request is matched to it
Explicit terms and sexualised-posing language.
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
Only where the creator has added it to their permitted list deliberately, and only within the contexts and realism ceiling they set separately.
Questions
- Can a creator permit sexual content?
- Only where the creator has added it to their permitted list deliberately, and only within the contexts and realism ceiling they set separately.
- 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.