AI Rights & Provenance

This document is designed to be forwarded to your legal team, your distribution partners (streaming platforms, broadcasters), and your compliance reviewers. It covers four questions: who owns the output, what we do with your canon data,how providers are licensed, and how downstream parties can verify provenance.

1. Output ownership

You own every shot generated through your workspace.Milk&Ink claims no copyright, no license-back, and no rights of exploitation over your finished content.

This applies to draft generations, final renders, approved versions, and release manifests. You may publish, license, sell, and sublicense your output without attribution to Milk&Ink (though we appreciate it).

Note: the underlying AI models that generate video (fal.ai Wan 2.1, Runway, Veo, Pika) have their own terms regarding output ownership. As of April 2026, all providers we integrate grant customers ownership of generated output. We maintain a current audit of provider terms at legal@milkink.studio on request.

2. Training data — opt-in only

We do not train AI models on your content unless you explicitly opt in. The opt-in control lives in Workspace Settings; it is off by default.

When a workspace opts in, the following is captured per approval decision:

• The canon snapshot at time of approval (characters, locations, style rules, palette constraints)
• The generation packet that was sent to the provider
• The rendered output URL
• The approval or rejection decision, and the reviewer's user ID
• The visual continuity score (if run)

Opt-in is reversible at any time. Toggling it off stops future captures immediately. To request deletion of previously captured samples, email privacy@milkink.studio. We delete within 30 days and provide written confirmation.

We never train on workspaces that have not opted in, regardless of plan tier or usage volume.

3. Provider licensing

Milk&Ink is a routing layer over third-party video models. When you generate a shot, your prompt and reference images are transmitted to the provider you selected (e.g., fal.ai). That provider performs the generation under its own terms.

Current providers and their terms at-a-glance:

• fal.ai (Wan 2.1) — customer owns output; provider retains no license. Model weights not accessible to Milk&Ink.
• Runway Gen-4 (pending integration) — customer owns output under Runway's commercial terms.
• Google Veo 3 (pending integration) — output rights per Google Cloud terms.

Where a provider offers enterprise terms with additional indemnification, Milk&Ink Enterprise customers can route their traffic through workspace-scoped API keys (BYOK) to receive those terms directly. Contact sales for setup.

4. Provenance & verification

Every release package you export includes a cryptographically-signed manifest (HMAC-SHA256) listing every shot, its approving user, the generation provider, and the timestamp of every decision.

Streaming platforms, broadcasters, or legal reviewers can verify a manifest at:

POST https://milkink.studio/api/provenance/verify

with the full signed envelope in the request body. The response states whether the manifest is authentic and unmodified. This endpoint is public and unauthenticated, so third parties don't need Milk&Ink accounts to audit.

The signing key is rotated quarterly. Historical keys are retained so manifests signed under prior keys remain verifiable indefinitely.

5. Human oversight & disclosure

Every shot that ships through the Milk&Ink release workflow has a named human approver recorded in the manifest. We recommend (but do not require) that customers disclose AI-assisted production to their distribution partners in accordance with emerging industry standards (SAG-AFTRA 2024 AI provisions, EU AI Act Article 52 transparency requirements, SOC 2 AI-transparency addendum).

6. Data residency

Content and canon data are stored in Supabase US-East-1 by default. Enterprise customers can request data residency in EU, Asia-Pacific, or on-premise — contact sales.

7. Indemnification

Our commercial indemnification terms for Pro and Enterprise customers are in the Terms of Service, Section 9. Enterprise tier includes a specific indemnification rider for AI-generated content claims — talk to sales.

8. Contact

Questions for legal: legal@milkink.studio.
Privacy requests: privacy@milkink.studio.
Enterprise terms & indemnification: sales@milkink.studio.