Don't take the policy on trust. Ask us for the evidence: the tool list, the vendor terms, and a chain-of-custody record for an asset you pick.
Outright bans on AI are giving way to disclosure terms in the contracts we're asked to sign. Your question has changed with them, from whether we use AI to whether we can say what's in the file.
Several studios have shipped titles carrying AI artefacts nobody decided to put there, then had to patch and explain. None of it was strategy; each was a gap in review, and a policy doesn't close one. A process does.
Not a list of what we like. A list of what's been read, negotiated and approved, each under an agreement that meets your confidentiality, security, IP and no-training terms. Most tools don't pass.
Who made it, which tools touched it, what reference was used, what a human authored. Ask how any single asset was made and the answer comes with the record attached.
Your IP never enters a third-party model, directly or indirectly, aggregated or not. Deletion certified in writing when you ask.
Documented diligence per deliverable. A named human reviewer accountable for each pass. The file available to you on reasonable notice.
Including us. It's the fastest way to find out whether a studio has done this work or written a paragraph about it.
One of our largest clients writes a full AI addendum into its master agreement: prior approval, tool-vendor terms, an absolute training prohibition, marking and explainability, documented diligence, indemnity and audit rights. We've delivered under it for 2 years. The standard is the publisher's, and it's a higher bar than we'd have set ourselves.
The compliance spine underneath it already existed: Cyber Essentials certified, TPN in renewal, ISO 27001 in progress. AI governance was bolted onto that spine, and this page describes it.
Reference gathering, blockout and layout exploration, texture variation through WispR, our own tool, and the parts of a pipeline that check work without producing any.
None of it happens on your work, and every artist on the project is told so in writing. A prohibition that lives only in a contract isn't a prohibition.
Because the honest answer to your legal team is a process they can inspect, not a promise they have to take. Several clients have written their own AI terms into our contracts. This is the policy that lets us sign them, and it's the same for everyone. If yours is stricter, send it and we'll work to it.

An art and tech-art studio of 100+ artists, credited on 82 shipped titles since 2017.
Don't take the policy on trust. Ask us for the evidence: the tool list, the vendor terms, and a chain-of-custody record for an asset you pick.
Outright bans on AI are giving way to disclosure terms in the contracts we're asked to sign. Your question has changed with them, from whether we use AI to whether we can say what's in the file.
Several studios have shipped titles carrying AI artefacts nobody decided to put there, then had to patch and explain. None of it was strategy; each was a gap in review, and a policy doesn't close one. A process does.
Not a list of what we like. A list of what's been read, negotiated and approved, each under an agreement that meets your confidentiality, security, IP and no-training terms. Most tools don't pass.
Who made it, which tools touched it, what reference was used, what a human authored. Ask how any single asset was made and the answer comes with the record attached.
Your IP never enters a third-party model, directly or indirectly, aggregated or not. Deletion certified in writing when you ask.
Documented diligence per deliverable. A named human reviewer accountable for each pass. The file available to you on reasonable notice.
Including us. It's the fastest way to find out whether a studio has done this work or written a paragraph about it.
One of our largest clients writes a full AI addendum into its master agreement: prior approval, tool-vendor terms, an absolute training prohibition, marking and explainability, documented diligence, indemnity and audit rights. We've delivered under it for 2 years. The standard is the publisher's, and it's a higher bar than we'd have set ourselves.
The compliance spine underneath it already existed: Cyber Essentials certified, TPN in renewal, ISO 27001 in progress. AI governance was bolted onto that spine, and this page describes it.
Reference gathering, blockout and layout exploration, texture variation through WispR, our own tool, and the parts of a pipeline that check work without producing any.
None of it happens on your work, and every artist on the project is told so in writing. A prohibition that lives only in a contract isn't a prohibition.
Because the honest answer to your legal team is a process they can inspect, not a promise they have to take. Several clients have written their own AI terms into our contracts. This is the policy that lets us sign them, and it's the same for everyone. If yours is stricter, send it and we'll work to it.
