AI likeness rights concern how a recognizable person's image, voice, or other identifying traits may be captured, adapted, or generated. Teams should make the permission, scope, and decision path explicit before building a likeness into a product or campaign.
Treat likeness as a relationship, not a file
A reference photo or voice sample is only one part of a likeness workflow. The person, the rights holder, the permitted use, and the terms governing later generations all matter. A file stored in a production system should not be treated as permission to use it.
For each likeness asset, document who supplied it, who may authorize its use, how consent was obtained, and what activities are permitted. Keep voice and visual likeness records distinct when the terms differ. Restrict access to the source material and collect only what the workflow needs.
Make scope understandable to the people depicted
Consent is more meaningful when a person can understand what they are agreeing to. Explain the types of content, clients, channels, territories, time periods, and restrictions in plain language. A broad phrase such as any purpose may be difficult for a contributor to evaluate and for a client to operationalize.
The record should capture material boundaries: excluded topics, named brands, approval requirements, exclusivity, and how changes will be handled. A useful system makes it possible to see those boundaries before a creative team requests or generates work, rather than burying them in an old attachment.
Version terms and respect future changes
When a contributor changes a term, preserve the previous version and identify when the new rule takes effect. A version history helps the team determine which terms applied to a particular request. It also makes the limits of a permission easier to explain during an audit or dispute.
Pause and revocation should follow the agreement and operational policy. Teams should know how new requests are stopped and how existing work is handled before they offer these controls. The exact legal effect depends on the agreement and jurisdiction, so counsel should review the process.
Keep approval status separate from consent
A person's consent does not automatically satisfy a model provider's eligibility or review requirements, and a provider response does not replace the person's agreed boundaries. Systems should represent these as separate checks with clear owners and evidence.
Approved.video is designed around this distinction: rights, permitted use, and review status belong with the asset and the workflow that consumes it. The current availability of any downstream provider action depends on an authorized integration; a documented likeness is not a guarantee of generation access.
CLARIFICATIONS
Questions & answers
Are AI likeness rights the same as owning a photo?
No. Ownership of an image and permission to use a person's likeness are different questions and may involve different rights and agreements.
Can a likeness license cover every future use?
That depends on the agreement and applicable law. Define the scope clearly and have qualified counsel review the terms.