Voice likeness licensing deserves its own workflow because a voice sample and a generated performance can carry different expectations from a visual likeness. Teams should explain the proposed use and apply the agreed limits to each request.
Separate voice enrollment and consent
Explain how a voice is captured, modeled, stored, accessed, and used. A contributor should understand whether the license covers a particular recording, a generated voice, or a broader set of performances.
Use a separate consent step when voice has different risks or terms from visual likeness. Protect raw samples with access and retention controls, and use an authorized provider when identity or voice verification is required.
Include script and context in the request
A voice request should include the client, use category, campaign, script or representative context, distribution plan, territory, and term. A category alone may not tell a person what words the generated voice will deliver.
Prohibit deceptive statements attributed to the person and define whether endorsement, political, sensitive, or high-impact contexts require additional review. The exact policy should be reviewed by counsel and applied consistently.
Record each use and preserve boundaries
Link a generated output to the voice asset, license version, client request, model or provider, and timestamp when those data are available. Keep the actual provider event separate from an internal estimate or saved draft.
If a contributor updates terms or pauses new requests, apply the change to future work according to the agreement. Explain what happens to prior outputs before the contributor enrolls.
Keep voice and visual controls aligned
A video may use a person's image with a different voice, or a voice with no visible likeness. The system should identify which permissions apply to the final combination rather than assuming one grant covers every element.
Approved.video's rights workflow direction supports asset-level distinctions for studio and app teams. Voice enrollment and generation require secure, authorized provider paths and are not implied by the current scaffold.
CLARIFICATIONS
Questions & answers
Should voice likeness have a separate license from visual likeness?
It may need separate consent and terms when the material or risks differ. The agreement should describe what is actually licensed.