An AI likeness workflow should connect verified identity, reviewed consent and signed scope to production decisions, registered release evidence and revocation. Each step leaves a record another party can inspect.
The order matters more than it looks. Consent comes before capture, scope comes before a protected operation, and the signed rules determine what can proceed. Each step is arranged so that the evidence it produces is useful to somebody who does not trust us.
A company checks and honors face or voice permission by resolving six questions in order: who the person is, what they agreed to, which campaign and identity elements are covered, whether the production request is inside scope, whether the released output matches the approved route, and whether the licence is still active.
| Decision | Record | Stop condition |
|---|---|---|
| Who can authorize the identity? | Verified person and representative authority. | The person or authority is unclear. |
| What use was approved? | One signed scope naming buyer, campaign, face or voice use, distribution and term. | The request falls outside the signed terms. |
| How may production happen? | Covered asset version, operator and supported production route. | The asset or route cannot be connected to the licence. |
| What may be released? | Required approvals, output inspection and registered release record. | The final file or approval cannot be connected to the authorized workflow. |
| May future use continue? | Current status, expiry and revocation event. | The licence is expired, paused or revoked for future controlled use. |
Bring a campaign briefUse the agency clearance workflow
An identity check establishes that the person licensing a likeness is the person in it. This is the step that makes everything after it worth anything: a licence granted by somebody who is not the rights holder is not a licence, it is a liability.
Nobody is onboarded, cloned or listed before they say yes. Consent of record is a signed agreement plus a passed identity check. It is deliberately not a recorded verbal statement, because a signed document has a hash a third party can check, and a video of somebody saying yes does not.
You record a short capture of your face and voice, with consent on the record from the first frame. From that, a licensed digital version of you is built. It only exists because you said yes, and it only appears where you said yes.
Face and voice have different operating details. See AI face licensing and AI voice licensing for the scope and evidence each identity element needs.
A licence names five things: the brand, the campaign, the format, the territory and the duration. Those are the terms a brand is buying access to, and outside them there is no permission.
Duration is what makes it a licence rather than a sale. Your face and voice stay yours. When the licence ends, their right to use you ends with it, and because the end date is part of the record, an expired use is something anyone can detect rather than something you have to argue about.
Supported production routes check the actual request against the signed scope. Routine work inside the approved rules can clear automatically. A prohibited or materially out-of-scope request is denied, while any approval obligation written into the agreement remains binding.
A supported registered release can carry evidence linking the person, asset, licence, generation and output record. The record shows what was authorized, by whom, and when future controlled use ends. It does not claim to discover every off-route use on the internet.
You do not have to take our word for any of it. The verifier is public, it runs on your own machine, and its source is published so you can check the tool as well as the answer. It returns pass, fail, or unknown, and it reports unknown honestly instead of rounding it into a yes.
Bring a campaign briefEvaluate the evidence chain
The agreement records talent compensation, production costs and permission-clearance conditions. Registered releases and current licence status make settlement reviewable without turning a receipt into proof of unregistered use.
Yes. Licences are agreed per scope. Uses outside that scope are denied, and any approval obligation written into the agreement remains binding.
A takedown unpublishes your listing and opts you out of new licensing. That is deliberately not deletion: licences already issued have to stay verifiable, or the receipts attached to them stop meaning anything. Erasure of your data is a separate, explicit request, and where a receipt has already been published, what remains of it is a hash. The privacy policy is the authority on this, not this page.
If you are represented, your agency can run all of this with you.
Yes. Human voice and video identity are both product scope. Each supported provider and media route still needs its own production controls, inspection and evidence.