Review permission, implied conduct and distribution before generating an identifiable person's likeness. Do not treat possession of a photograph, public visibility or platform acceptance as sufficient evidence that the proposed depiction is appropriate.
Define the depiction before requesting approval
Write down what the audience will see the person apparently doing, saying or endorsing. Include clothing, location, accompanying text and other people in the scene. Context can change the meaning even when the face remains recognisable.
For an Indian creator preparing regional-language variants, include translated speech and captions in the review. Approval of one script should not be treated as approval of materially different claims in another language. This is a practical review boundary, not a legal conclusion.
Build a likeness-risk brief
Use the following fields before any generation involving a real person:
- Identity basis: Why would viewers identify this person?
- Permission evidence: What approved record covers this proposed synthetic depiction?
- Scope: Does the record address speech, appearance, alteration and campaign purpose?
- Misleading context: Could the scene imply attendance, support, misconduct or an experience that did not occur?
- Distribution: Which channels, languages, territories and dates are proposed?
- Review owner: Who can approve changes or require withdrawal?
- Policy question: Which current provider-policy provisions need checking for this exact scenario?
Reference permission records securely; do not paste personal documents or private correspondence into a generation prompt.
Hypothetical example: a founder introduction
Suppose a Pune startup wants a synthetic depiction of its founder introducing a fictional product concept. The inputs are a public headshot, a 60-word draft and a proposed Hindi adaptation. No approval has yet been obtained for synthetic speech or likeness use.
The brief is incomplete even if the founder has previously appeared in company videos. Ask for review of this specific depiction, script, translation and distribution plan. If approval covers only a silent internal concept, do not extend it editorially to a public spoken endorsement.
Evaluate the final storyboard by asking whether a viewer could reasonably infer that the founder actually recorded the message. If so, review disclosure and context before proceeding.
Choose a lower-risk next step
Stop when authority or scope remains unclear, or when the concept relies on a misleading implication. Use an original non-identifiable character or a text-led presentation while questions are resolved. Never clone a person's likeness or voice without consent.
If comparing access options, inspect the AI tools catalog for access format and save the offer terms before buying. Marketplace account/code/token offers are not proof of official subscription equivalence or permission to depict anyone.
Sources and scope
Source material checked 29 October 2026; features/policies may change. Runway's Usage Policy establishes a harm-mitigation policy supported by automated systems and internal human review. The supplied passage does not establish categorical permission for real-person likenesses. Review the current policy for the proposed use. The brief is editorial advice, not legal advice.