How do you handle licence and intellectual-property risk in generated code?
Clients also ask it like this:
- Who owns the code that an AI tool writes for us?
- How do you stop copied or copyleft code from reaching our deliverables?
- Does the AI vendor give you any indemnity for generated code?
What the client is checking
The client wants to know that you have thought about ownership and about code that carries a licence. They will compare your answer with the contract between you and them.
Three draft answers
Pick the level that is true for you today. Every statement marked [VERIFY]
must be true for your organisation before you send it. Delete a statement that is not true. Fill each
{{placeholder}}.
Not yet in place
We have not yet assessed licence and ownership risk for AI-generated code. [VERIFY] We have not yet read the providers' terms on ownership of output. [VERIFY] We will take legal advice and report to you by {{date}}. [VERIFY]
Policy only
Our policy says that developers must review generated code for licence issues and must not paste in code from sources whose licence we cannot confirm. [VERIFY] We use {{tools and plans}}. We read the providers' terms on output and on any indemnity on {{date}}. [VERIFY] Whether those terms cover your project is a question for the contract between us. [VERIFY] A lawyer has not yet reviewed this approach. [VERIFY]
Enforced, with evidence
Our contract with you covers ownership of deliverables and the use of AI tools in {{clause reference}}. [VERIFY] A lawyer reviewed our approach on {{date}}. [VERIFY] Licence and dependency scans run on every pull request: {{tools}}. [VERIFY] These scans cover dependencies. They do not detect copied code snippets, unless {{snippet tool}} is in use. [VERIFY] We use {{tools and plans}}. We recorded the providers' terms on output and on indemnity on {{date}}. [VERIFY] We keep the scan results and the terms records. [VERIFY]
Before you send
This question touches contracts and law.
This answer touches ownership of code, licences and indemnity. These depend on the contract, on the provider's terms and on the country. They can change.
Do not write in the answer who owns AI-generated code. Do not say that generated code is free of licence risk. Do not repeat an indemnity from a provider unless you hold the written terms and a lawyer has read them. A lawyer must review the final wording.
Evidence to attach for the strongest answer
- The contract clause, with the date of the lawyer's review.
- The licence and dependency scan configuration and results.
- Dated copies of the providers' terms on output and indemnity.
- The policy text on licence review.
How to move up one level
From not yet in place to policy only
Read the providers' terms on output and indemnity for the plans you use. Write down what they say, with link and date. Add a licence review step to your code review. Ask a lawyer what your contracts must say.
From policy only to enforced, with evidence
Add automated licence and dependency scans to every pull request. These scans cover dependencies. They do not detect copied code snippets. A snippet tool is a separate choice. Put the agreed position on ownership and on AI use into the contract. Keep dated copies of the provider terms.
KYA and this question
No. KYA does not answer this question. KYA does not check the licence or the ownership of generated code.
Get all 13 answers in one document
Choose the level that is true for each group. You get a preview at once and the full pack by email.
Previous question Next question
These are drafts. Send only what is true for your organisation. This is not legal advice.