Guide · Evidence checked 2026-10-15

AI Video Commercial Use and Provenance: A Procurement Guide

A practical, evidence-led decision guide. Product capabilities and limits are separated from anything that would require hands-on testing.

“Commercial use included” answers only one part of an AI video rights review. A campaign can satisfy the platform's plan terms and still fail because the uploaded image was unlicensed, a performer's likeness lacked consent, generated music has unclear terms or provenance disappeared during export.

The procurement task is to build an evidence chain from input to delivered asset. No badge or subscription tier can replace it.

Three checks before a commercial release

Question	Evidence to retain	Stop condition
Does the exact plan permit this use?	Dated plan terms and generation date	Licence unresolved
May we use every input and likeness?	Asset licence and consent reference	Missing permission
What provenance survives delivery?	Original/export records and final-file inspection	Claiming metadata that is absent

Luma's licensing guide distinguishes Free/Lite personal-use output from output made under Plus, Unlimited or Enterprise subscriptions. It says later upgrading does not convert older Free/Lite generations into commercially licensed assets; rights acquired for qualifying generations survive cancellation. This is the vendor's stated plan boundary, not clearance of third-party rights.

Do not extend Adobe's statements about its Firefly models to every partner model available inside the Firefly interface. Identify the selected provider and applicable terms. Content Credentials record provenance; they do not certify that an advertising claim is true or that every depicted person consented. The Luma, Adobe and Pika sources supporting these plan and provenance distinctions were rechecked on 15 October 2026.

For a training purchase, pair this checklist with Colossyan versus Synthesia. For dubbed versions, use the localisation buying guide. This is an evidence checklist, not legal advice or a jurisdiction-specific clearance.

Separate five rights questions

Platform output licence: what the service contract permits the account to do with generated output.
Input rights: whether the buyer may upload and transform every image, clip, logo, voice and track supplied.
Likeness and performance consent: whether identifiable people authorised this use, territory, duration and type of transformation.
Model/provider boundary: which model produced the asset and what additional terms or restrictions apply.
Destination rules: what an ad network, broadcaster, marketplace or jurisdiction requires for disclosure and claims.

An affirmative answer in one column does not flow into the others. Keep unresolved items unresolved.

Read “commercially safe” as a claim with scope

Adobe publicly describes Firefly commercial models as trained on licensed content and public-domain material and says it automatically attaches Content Credentials to certain types of exports using Firefly outputs. That is valuable first-party evidence for an Adobe procurement review. Adobe's FAQ, legal guidelines and the customer's exact contract still define the scope. It is not permission to upload someone else's campaign photography or imitate a person without consent.

Other providers may allow commercial use on paid tiers while restricting it on free or lower tiers. Luma, for example, documents plan-specific commercial rights and watermark conditions. Pika's terms allow commercial use only where the subscription plan expressly permits it; do not infer permission from a clean export. Capture the plan at generation time because an export's appearance does not prove its licence.

Treat broad vendor quality or safety statements as vendor claims until counsel maps them to the intended use.

Build an asset passport

For every approved output, retain:

Field	Why it matters
Asset ID and final file hash	connects the record to the delivered bytes
Provider, model and version/mode	identifies the generation system
Account plan and order date	anchors applicable commercial terms
Prompt and settings	supports reproduction and review
Input asset IDs and licences	establishes upload rights
Person/voice consent IDs	keeps permission separate from the model
Generated-content metadata	preserves provenance observed at source
Editor/export chain	explains transformations and metadata loss
Human approvers and date	records brand, legal and accessibility decisions
Destination/disclosure	ties the asset to the publication context

Store the consent or licence document in the governed system, not in the prompt text. The passport should reference it without exposing personal data unnecessarily.

Test whether provenance survives the real delivery chain

Download an original generated asset and inspect its metadata. Pass it through the exact editor, codec, ad uploader and content-management system used in production. Inspect it again at every boundary.

If Content Credentials or equivalent provenance survives, record what remained. If it disappears, do not claim the destination carries it. Keep an internal evidence record and decide whether a visible disclosure is required.

Hash both the original and final files. They should differ after an edit; the passport explains why and connects them.

Likeness consent needs a revocation path

Avatar and presenter tools such as HeyGen and Synthesia make consent a recurring operational issue. The organisation needs to know who approved avatar creation, which uses are permitted, who can publish, and how future use stops after consent changes.

For open-ended generation, reject prompts or references that attempt deceptive impersonation, non-consensual intimate content or unauthorised public-figure endorsements. Provider safeguards are a layer, not the organisation's policy.

Use a periodic access review for stored avatars, voices and confidential product references. Deleting an employee account is not proof that every derived asset or model remains governed correctly.

Procurement questions that reveal weak answers

Which terms apply to the exact plan and region on the order date?
Are commercial rights different for free, trial, paid and enterprise output?
Does the provider use customer inputs or outputs for training, and can enterprise accounts opt out contractually?
What deletion, retention and subprocessors apply to uploaded confidential material?
Which provenance metadata is generated, and what survives export?
How are model/provider changes disclosed in an aggregator?
What happens to usage rights after cancellation?
Is indemnification offered, to whom, for which models and under what exclusions?
How are abuse reports, likeness disputes and takedowns handled?

An answer such as “enterprise-grade” or “commercial use allowed” is not enough. Request the clause, documentation page or contract schedule.

Do not confuse provenance with truth

Provenance can help identify that an asset was generated or edited and by which system. It does not prove the scene is factual, the claim is substantiated or the person consented. Marketing review must still test product claims, disclosures, accessibility, cultural context and the risk of a reasonable viewer being misled.

Likewise, the absence of provenance metadata does not prove an asset is human-made. Use it as one evidence channel, not an authenticity oracle.

Release gate

An AI video should not ship until:

all source assets have a recorded right of use;
every identifiable person's consent covers the intended campaign;
the exact provider/model/plan is recorded;
brand and factual claims are approved;
provenance behaviour is documented through final delivery;
required disclosure is present;
a responsible owner can answer a complaint or takedown request.

If one item is unknown, the verdict is verification-first. Creative quality cannot compensate for a broken rights chain.

Primary next step: Open the AI video category and shortlist only tools whose evidence boundary your organisation can govern.