Do not upload unreleased client footage merely because a service says you retain ownership. Keep customer and private material out of exploratory AI workflows, and resolve confidentiality questions before considering any separately authorised production process.
Ownership is not a data-handling answer
Runway's usage-rights statement says that, as between you and Runway, you retain ownership and rights to uploaded and generated content. It also permits generations without non-commercial restrictions imposed by Runway and requires no formal credit.
Those statements do not establish retention periods, training use, deletion behaviour, access controls or confidentiality commitments. The supplied moderation source does not establish those terms either. Treat each missing answer as an evidence gap, not an implied protection.
Assemble a confidentiality evidence checklist
Before discussing a possible production upload, ask the responsible client and service reviewers:
- Material classification: Does the footage reveal an unreleased product, internal conversation, identifiable person or confidential location?
- Authority: Who can approve disclosure to this specific service and access arrangement?
- Applicable terms: Which current provider documents address retention, training, deletion and access?
- Contract boundaries: What does the client agreement say about external processing and subcontracting?
- Account control: Who controls the account, recovery methods and access removal?
- Minimum input: Can the workflow be assessed without any client footage?
- Evidence record: Who has reviewed the relevant documents, and what remains unanswered?
These are review questions, not assurances about any provider's practices or legal conclusions about a contract.
Hypothetical example: an unreleased launch film
Imagine a Chennai agency preparing a fictional electronics launch. Its 90-second draft reveals packaging, a launch date and a spokesperson's unreleased remarks. The producer has only the supplied usage-rights and moderation passages.
The upload decision is “not yet”: neither source answers the confidentiality questions. For workflow planning, create a separate, wholly fictional five-second storyboard using generic objects and invented text. Do not reproduce the client's packaging, remarks or launch details.
Evaluate the planning exercise against narrow questions such as whether the proposed shot structure communicates the intended idea. It cannot establish how the service handles confidential files, nor can a successful demonstration substitute for documentary review.
Keep procurement separate from upload approval
Stop if any material data-handling or authority question remains unresolved. Next, request the applicable documentation through the responsible procurement or client-review process. Continue with synthetic planning material only.
When checking the AI tools catalog, review access format and save terms before buying. Marketplace account/code/token offers are not proof of official subscription equivalence. Seller assurances and provider documentation are separate evidence, particularly when account control matters.
Sources and scope
Source material checked 29 October 2026; features/policies may change. Runway usage rights supports the ownership and commercial-use statements. Runway's Usage Policy describes harm-focused moderation. Neither supplied source establishes retention or training terms. The upload gate is editorial confidentiality advice.