AI Video Privacy and Commercial Use: Uploads, Outputs and Licenses

Before uploading a client image or delivering an AI video, identify the service processing it, who can access its media links and which terms apply to the selected model. This website, Pika’s hosted service and a local Flex installation are separate routes. A subscription here does not grant a license for independently downloaded weights.

Checked November 9, 2026 against this site’s implementation, its policy text and the official Flex release license. This guide explains the documented boundaries; it is not a storage-erasure test, provider contract audit or guarantee of copyright clearance.

What happens to uploads on this website?

This site sends prompts, generation settings and relevant reference media to the processing services needed for the selected task. These can include a model gateway, generation provider and content-safety processing. Inputs and outputs can also be stored or delivered through cloud storage. Using the browser tools does not mean the computation stays on your device.

The Privacy Policy describes our handling of account, generation and transaction data. Do not assume that all models have the same processor, storage location, retention period or training policy. We have not established a single, independently verified promise of zero retention or no training across every upstream service. If a project requires those conditions, obtain confirmation for the exact route before uploading.

Private creation, public listing and media URL are different

Layer	What it controls	What it does not establish
Account task history	Access to your account’s task records	That every underlying media URL requires your login
Public/private generation setting	Whether a creation is eligible for the site’s public creation surfaces	Secrecy of a copied source or output URL
Media delivery URL	Access according to the storage/provider’s URL rules	A universal expiry, revocation or account-level authentication guarantee

The current browser generation controller starts with public visibility off, but reused settings or links can change the selection. Check it before each submission. Public creations can expose the output and its displayed prompt/model. The public-listing paths treat a task without an explicit private flag as eligible for public display; API callers should send options.visibility: "private" explicitly when they want it excluded from those listings. See the updated API quickstart.

Uploaded and generated media may be served through public or signed URLs. Anyone with a public URL may be able to open it, and a signed URL may be usable until it expires. A private listing setting does not convert those links into authenticated private storage. Avoid putting sensitive URLs into public prompts, bug reports, analytics or shared workflows.

Does deleting a creation erase every copy?

No immediate, universal erasure is promised. The current remove-creation flow marks the task record as deleted; that action does not itself prove physical removal of the underlying media object. Upstream providers, caches, backups or copies already downloaded may have separate lifecycles.

For access, correction or deletion requests, contact support@tikdek.com with the account identifier, relevant task IDs, requested scope and urgency. Do not send passwords, API keys or extra confidential source files. Ask which records and media copies can be removed, which processors are involved and which retention obligations apply. We do not publish one verified deletion deadline covering every processor. See the Privacy Policy for the controlling description.

Can I use this site’s videos commercially?

Paid outputs generated with a Lite, Pro or Ultra subscription, or a one-time Credit Pack, may be used commercially subject to this site’s Terms of Service, the selected model’s terms and applicable intellectual-property law. Pro or Ultra is not the only paid route covered by that statement.

That permission does not grant rights to someone else’s photo, face, voice, music, brand or protected character. You must have the necessary input permissions and review the final output for the intended use. Payment does not guarantee exclusive ownership, copyright registration, accuracy, a successful advertising review or freedom from third-party claims. Other users may obtain similar outputs.

A signup Credit grant is not a paid plan or an independent commercial license. This guide makes no blanket commercial-rights promise for free outputs; establish the applicable terms before using one for client delivery. Model availability and output rights should be checked together: Flex itself is not currently offered here.

What license applies to local Pika H3 Flex?

The official Flex model card places the adapters under the MiniMax H3 Community License. Its separate Apache-licensed code and components do not turn all weights or example media into Apache-licensed assets.

The model card links a specific license revision. Read the complete agreement and AUP for your actual release. Key conditions include:

• The listed excluded territories are the EU, UK, South Korea and US. The territorial restrictions address works and outputs, not just where a GPU is located; separate authorization must be resolved with the licensor where needed.
• Section IV requires prior written authorization when commercial products/services exceed US$20 million annual revenue, and requires MiniMax H3 identification in commercial product/service interfaces.
• Redistribution and hosted services have notice, downstream terms and safeguard obligations. Use restrictions also address other-model training and public AI-content disclosure.

The license says MiniMax claims no rights over generated outputs; this does not cancel those restrictions or clear third-party rights. These are pointers to the checked revision, not a substitute for the agreement or proof that a particular deployment is authorized. This site’s paid plan cannot override it.

Is local ComfyUI automatically offline and confidential?

No. A local interface can still run cloud API nodes or custom nodes that send data elsewhere. Initial model/dependency downloads, remote input URLs and extensions may also access the network. A cloud ComfyUI instance is remote processing even if the workflow resembles a local one.

For a confidential local project, inspect the workflow and node code, audit outbound access, protect model/input/output directories and verify operation with non-sensitive samples under the required network policy. Also review workflow metadata, logs and exported files before sharing. Follow the ComfyUI local setup guide; it does not claim that an offline or hardware test has been completed here.

Before a client delivery

1. Record the actual service, model, date, settings and applicable terms; keep the input permissions and paid-task records.
2. Confirm whether the contract permits cloud processing and which privacy conditions are required. Resolve unverified retention or processor questions before upload.
3. Inspect the final picture and sound for unauthorized identities, brands, copyrighted elements and required disclosures.
4. Agree with the client on usage scope, disclosure, confidentiality and handling of remaining copies. Do not promise exclusive rights or total deletion that has not been verified.

For account-specific questions, use support. For service behavior and obligations, the Privacy Policy, Terms of Service and applicable model agreement govern.