🤖AI Tools· 3 min read· Updated Oct 2026

Write an AI-video delivery clause without promising rights you cannot prove

Do not turn Runway's ownership wording into an unsupported promise of exclusive worldwide rights. Define the delivery and document the limits for qualified review.

Describe the deliverables and documented permissions precisely instead of promising that a client receives every conceivable right in an AI-assisted film. Runway's ownership wording is not, by itself, evidence for an unlimited client-facing ownership warranty.

Separate three different promises

A delivery promise identifies what files the client receives. A usage promise describes the documented uses available for those files. An ownership or exclusivity promise raises additional questions about what rights exist and what the creator can transfer.

Runway states that, as between the user and Runway, the user retains ownership and all rights to uploaded and generated content. That does not establish rights in every third-party component or resolve jurisdiction-specific copyright questions. For an Indian freelancer working with an overseas agency, list the intended jurisdictions for qualified review rather than relying on “worldwide” as convenient boilerplate.

Complete a contract discussion worksheet

Before drafting, answer:

  • Deliverables: Final films, aspect ratios, language versions, editable projects or source files?
  • Creator material: Which elements were independently created, and what evidence supports that description?
  • Third-party components: Which assets remain governed by separate permissions or restrictions?
  • Intended use: Which channels, territories, duration and campaign contexts were reviewed?
  • Unresolved questions: What ownership, exclusivity, AI-disclosure or clearance issues still need advice?
  • Change control: Who reviews a new soundtrack, altered claim, additional territory or later reuse?

Attach an asset schedule to the discussion. Avoid burying important limits in an email that the final contract does not address.

Hypothetical wording for adviser review

Suppose a Delhi studio is delivering one 20-second film and two cutdowns, with a licensed soundtrack and original artwork. The client asks for all source files and exclusive perpetual rights everywhere.

A discussion draft might say: “The proposed delivery comprises the final films listed in the schedule. Third-party components and their documented permitted uses are identified separately. Editable files, additional uses, exclusivity and any transfer of rights remain subject to express agreement following review.”

This is hypothetical discussion language, not a ready-to-sign clause. Evaluate it against the actual evidence: can the soundtrack be included in editable files, and what supports the requested exclusivity? If those questions remain open, changing the adjective to “full” does not resolve them.

Stop before signing unsupported warranties

Pause acceptance of rights promises you cannot substantiate. Next, narrow the scope, obtain missing permissions or seek qualified contract advice. Make approval responsibilities and unresolved items explicit before delivery.

If tool access is a project expense, check the AI tools catalog for access format and save offer terms before buying. Marketplace account/code/token offers are not proof of official subscription equivalence; seller terms do not establish client ownership rights.

Sources and scope

Runway usage rights establishes the bounded user–Runway ownership statement. Source material checked 29 October 2026; features/policies may change. The worksheet and draft are editorial discussion aids requiring qualified legal review, not enforceability assurances.

Compare current listings

Check the selected plan, price, availability and delivery terms before ordering.

Related reads