Built to be
the sanctioned zone.
Studios now publish rules for how their partners may use generative tools. Previz — temporary, non-final, pre-production planning — is exactly the use those rules sanction. This page shows how the platform maps to them, and where our own compliance work stands, in the open.
The commitments
Never trained on
Your scripts, frames, and sequences are never used to train our models or anyone else's. Inference-only vendor contracts, one server-side chokepoint, named-vendor exclusions enforced by the router.
The enforcement mechanicsTemporary by design
This is a previz platform. Its outputs are planning artifacts — boards, animatics, camera tests — built to be replaced by real photography. The export path (EDL, FCPXML, PDF boards) hands the plan to your cutting room; it does not compete with it.
Provenance on every asset
Lineage records which engine produced every frame, from which inputs, automatically — a per-asset birth certificate you can show a rights holder, a client, or a compliance review.
Five rules the studios wrote. How we hold each one.
In 2025 the major streamers published guiding principles for generative AI use by their production partners. Paraphrased below — we claim no affiliation or endorsement — with, against each one, what the platform actually does. Every row is verifiable in the product.
Generated material should not replicate identifiable elements of works you don't own.
Generation anchors to YOUR references: continuity locks pin your characters, props, and locations, and the drift loop re-checks every reappearance against them. Per-asset lineage shows exactly which inputs shaped which frame, so an IP review is a lookup, not an investigation.
Tools must not store, reuse, or train on production inputs or outputs.
The zero-training-retention architecture: commercial inference endpoints only, no consumer tiers, process-and-return vendor terms, server-side keys, and your work persisting only in your tenant-scoped storage.
Use enterprise-secured environments, not personal accounts.
Row-level security on every table, tenant- and project-scoped storage paths, org accounts, and per-project vendor and jurisdiction exclusions enforced server-side before anything is generated. Private deployment — dedicated tenant, VPC, air-gapped — is the funded roadmap for engagements where the answer must be 'no third party at all'; the platform running today is the shared one.
Outputs are temporary working material, not final deliverables.
The product is previz: storyboards, animatics with scratch audio, camera and lens exploration. Final-frame delivery deliberately exits to your NLE via EDL/FCPXML — the platform's own renders are labeled animatics.
Performances and union-covered work are not replaced without consent — when in doubt, escalate.
Scratch dialogue is labeled scratch and exports as comments, not audio stems. Voice cloning ships behind a consent gate: a clone is refused, before any charge, unless it is made against a consent record for that voice — one naming whose voice it is and, for another person's voice, linking the release they signed — and a cloned voice stops performing if that record lapses. There is no face-swap, and no tooling that builds a model of a performer's face or body. Provenance gives productions the disclosure trail their agreements require, and anything beyond these guardrails belongs in your approval chain — not silently in a render.
Whose face, and who said yes.
Continuity means holding a person's likeness steady across hundreds of frames, which makes permission a product problem rather than a paperwork one. Here is exactly where that stands. The rows marked planned are not shipped, and we would rather you know that from us than discover it in a rights review.
One thing worth saying plainly: the platform ships no library of real people to generate from, and it has no tooling for building a replica of a performer's face or body. The one replica it can make is a voice, and only against a consent record your production writes — a record of what you tell us, not a verification of it. Every identity the system holds steady got there because someone on your production put it there.
Frames made in Previz. Each carries the lineage record described above — which engine, from which inputs.
Where we stand, control by control.
Our self-assessment against the MPA content-security best practices — the framework behind Trusted Partner Network assessments — published here rather than kept in a drawer. Statuses are conservative: "Live in product" means enforced in the running platform today, and we say "Planned" where the work has not shipped. No certification is claimed before it exists.
The full policy set behind the "Policy in place" rows — access control, data protection & deletion, incident response, secure development, vendor management, and the rest — ships as a versioned documentation pack, published and readable now rather than held behind an NDA.
Bring your compliance team. We like it that way.
Every claim on this page is either visible in the product — lineage, isolation, exports — or documented in the policy pack, which is published rather than gated. Security questionnaires get answered directly, with engineers in the room.
This page is our own statement of practice — an honest self-assessment, not a contract. The legal centre carries a plain-language summary of it. The binding documents are the Terms, Privacy Policy, and Acceptable Use.
Terms of service
The agreement covering accounts, plans, ownership and termination.
/privacyPrivacy policy
What is collected, why it is held, and for how long.
/acceptable-useAcceptable use
The content and the conduct the platform will not carry.
/cookiesCookie policy
Which cookies are set, by whom, and how to refuse the optional ones.
Trust centre
Partner principles, rights and consent, and an open self-assessment.
Security
The architecture: isolation, retention, and deployment modes.
/security-docsSecurity documentation
The published policy, architecture and evidence set.
/legalLegal centre
Plain-language summaries of five of these documents, in one room.