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.

Boundary type

Non-consensual framing

Depictions framed as taken without knowledge or against the subject's will — hidden-camera, leaked, coerced or restrained framing.

Why this line exists

The product exists to make consent legible. Output that performs the absence of consent — hidden-camera framing, leaked framing, coercion — contradicts the manifest that would be stamped on it. Permitting it would mean issuing a consent record for a depiction of somebody not consenting.

How a request is matched to it

Terms describing covert capture, incapacity, restraint or coercion.

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 non-consensual framing?: 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.