Consent & Likeness Policy

Version 1.0 · 14 August 2026

Status: working document. This policy describes what the platform actually enforces today and is written to be operationally true rather than decorative. It has not been reviewed by a qualified lawyer. Obtain that review before relying on it with any external customer, and before publishing it as a binding term.

A likeness is not just data — it belongs to somebody. This policy explains how OnlyHub records that permission, what evidence each kind of permission requires, and what happens when it is withdrawn.

1. Nothing runs without a declaration

Before a character can be used on any asset, its origin must be declared. There is no default and no implicit permission; a persona with no consent record cannot be approved, and an unapproved persona cannot be applied to anything.

Type	Meaning	Required evidence
SYNTHETIC	A wholly invented character. No real person is depicted or referenced.	A description of how the likeness was created.
SELF	The account holder's own likeness.	Identification of the account holder as the subject.
THIRD_PARTY_CONSENTED	Another identifiable person's likeness, used with permission.	A signed release, referenced by the record and retained. The system refuses this declaration without a reference.

2. What a release must cover

Consent to be photographed is not consent to be synthesised. A release should state, explicitly:

that the subject's likeness may be used to create synthetic or altered media;
the scope — face, voice, body, or full likeness — and any content limits the subject sets;
that the resulting content may be commercial, and where it may be published;
how long the permission lasts and how the subject withdraws it;
that the subject is 18 or over, and verification of that.

3. Scope is enforced, not assumed

A consent record names what it covers. A module asking to use a face will be refused if consent covers only likeness generally; a voice module will be refused if voice was never granted. The check happens at execution time.

4. Withdrawal

Withdrawal takes effect immediately and retroactively. Revoking a consent record retires every persona version it authorised. Work already queued will stop, because the consent check runs again when the job executes rather than only when it was created.

Withdrawal does not by itself delete content already produced and published. Where a subject requests erasure, the operator must action it under the Privacy Policy and record the outcome.

5. Real people who have not consented

There is no legitimate route to using an identifiable person's likeness on this platform without a release. This is not merely a licence matter: publicity and personality rights are a separate legal claim from copyright, and non-consensual intimate imagery is a criminal offence in the UK and many other jurisdictions. Attempting to route around the consent gate is grounds for immediate termination.

6. Training material

Where a character is produced by training an adapter, the training material is subject to this policy in full. Adapters must be trained on synthetic or properly consented imagery only. A permissive licence on a model does not launder the rights in the data it was shown.