From the journal

Selling AI-generated code: copyright, licences and indemnities

Before selling software built with AI-generated code, establish the rights in the released components, perform the conditions attached to third-party code, and define the promises the customer will receive. Exclusive ownership should cover identified rights the supplier actually holds. An uncapped intellectual property (IP) indemnity requires a separate decision about the claims and costs the supplier will bear, including exposure outside any coding-assistant provider's commitment.

32 min read

A supplier uses coding assistants for a product and bespoke customer modules. Some suggestions match public repositories. Employees or contractors heavily revise other suggestions. Its customer wants exclusive ownership and an uncapped indemnity. The workable response is a version-specific rights schedule, a release decision for each unresolved component, and a contract that distinguishes ownership, permitted use and responsibility for claims.

Copyright treatment differs across the jurisdictions below. The relevant countries include those connected to creation, copying, delivery, hosting and the rights asserted by a claimant. The commercial agreement also needs its own governing law and forum. This comparison addresses the release and contract decision. It states the law and provider terms as at 19 November 2026. The actual repository, contributor agreements, accepted provider terms and customer contract determine which conditional route is available.

Separate the rights that the customer is buying

The review should answer six questions for each material component. A single statement that the supplier “owns the output” is too imprecise to perform that work.

  • Does copyright subsist? What the supplier needs to establish: The particular expression satisfies the applicable originality and authorship rules. Consequence for the customer grant: Define the protected contribution that supports the exclusive grant.
  • Who initially owns it? What the supplier needs to establish: The author, employment, commissioning or other statutory rule applies to the actual creation facts. Consequence for the customer grant: Identify every person or entity from which rights must reach the supplier.
  • Has title passed? What the supplier needs to establish: The necessary assignment or exploitation-right grant covers the work, uses and onward rights, with required formalities. Consequence for the customer grant: Complete missing instruments before promising those rights.
  • Does it incorporate protected third-party expression? What the supplier needs to establish: The retained expression and its source have been compared under the relevant infringement test. Consequence for the customer grant: Obtain permission, establish a supported exception or replace the affected material.
  • What use does the licence permit? What the supplier needs to establish: The exact source licence covers the intended copies, modifications, distribution and network use. Consequence for the customer grant: Supply required notices and source, and preserve the recipient's applicable rights.
  • Who bears an infringement claim? What the supplier needs to establish: The customer indemnity and provider defence each cover the relevant party, claim, product, conduct and remedy. Consequence for the customer grant: Negotiate and record any liability the supplier retains.

These distinctions follow from the separate subsistence, ownership and restricted-act rules. For example, US copyright in a derivative work extends to the new contribution under 17 USC §103(b). EU software protection concerns the author's own intellectual creation, while reproduction and adaptation have their own rules under Directive 2009/24/EC, Articles 1–4. A contractual assignment can convey only the rights available for transfer.

Use separate categories for supplier-owned bespoke code, supplier background technology, third-party components, customer materials and generated material whose exclusive protection remains unestablished. The customer may receive an assignment of bespoke rights, a continuing licence to background technology, and the permissions attached to third-party components. Define any promised restriction on the supplier's own reuse separately from exclusive copyright against other people.

Record provenance at the component and release level

A software bill of materials identifies dependencies. The rights schedule must also connect each component to its source, contributor, permission and actual delivery. Engineering should maintain the technical record, procurement should retain the provider agreement, and legal should record the rights decision. The release owner should confirm that the approved evidence matches the shipped build.

  • Component and released version. Evidence to retain: File or module identifier, build and commit hashes, source and object-code location. Release decision it supports: Which material the decision covers.
  • Source and licence. Evidence to retain: Repository, file and commit; licence version; file-level exceptions; copyright and NOTICE text. Release decision it supports: Permission and obligations for retained third-party expression.
  • Assistant workflow. Evidence to retain: Account holder, procurement route, plan, model, feature, generation date and relevant settings. Release decision it supports: Applicable output terms and any defence conditions.
  • Suggestions and references. Evidence to retain: Original suggestion, returned references, accepted text, recorded negative results and the scope of the check. Release decision it supports: What was detected and what still needs investigation.
  • Human contribution. Evidence to retain: Named contributors, design choices, relevant commits and before-and-after changes. Release decision it supports: The expression for which authorship is claimed.
  • Personnel title. Evidence to retain: Employment duties, commissioning terms, assignments, permitted onward grants and moral-right treatment. Release decision it supports: The supplier's authority to grant the promised rights.
  • Inputs. Evidence to retain: Rights to submitted code, prompts, retrieved context and customer material. Release decision it supports: Compliance with input permissions and relevant provider exclusions.
  • Integration and delivery. Evidence to retain: Covered files, combined works, server code, browser assets, containers, customer copies and network interaction. Release decision it supports: The licence conditions triggered by the actual deployment.
  • Compliance materials. Evidence to retain: Delivered notices, source package or access route, build scripts and installation information where required. Release decision it supports: Completion of conditions before the triggering act.
  • Customer promise and claim route. Evidence to retain: Rights category, warranty exceptions, applicable provider terms, notice/control requirements and remediation. Release decision it supports: The precise grant and retained financial exposure.
  • Decision. Evidence to retain: Release, hold, obtain permission or replace; reason; responsible reviewer; date; evidence location. Release decision it supports: A reproducible decision for this build and use.

This is a recommended evidence structure derived from the rights and contract conditions discussed below. It is not a prescribed statutory form. Keep confidential prompts and code under appropriate access controls, and retain the evidence needed to explain the decision without making an unsupported claim that every generated token has a known origin.

Can AI-generated code be copyrighted?

Human contribution must be assessed in the expression that survives in the program. Hours spent prompting, numbers of edits and the usefulness of the result are weak substitutes for that examination. A heavily revised suggestion can contain protectable human work and retained third-party expression at the same time. Each needs its own finding.

In the United States, Thaler v Perlmutter affirmed refusal of registration for a work presented as autonomously created with a machine as sole author. The D.C. Circuit applied a statutory human-authorship requirement and left other AI-assisted boundaries outside that holding. The Supreme Court denied certiorari on 2 March 2026. The Copyright Office's January 2025 report identifies perceptible human inputs, original selection or arrangement, and creative modifications as relevant forms of human authorship. Its assessment of prompts is agency analysis tied to the technology it considered. Thaler, 18 March 2025, pp. 9–16, 18–24; Supreme Court docket 25-449; Copyrightability report, pp. 18–27.

Canada uses the author's exercise of skill and judgment beyond a trivial or purely mechanical exercise. CCH supplies that test; it predates generative AI. Singapore's Court of Appeal likewise directs attention to authors and original expression in the work. These authorities support preserving human expressive decisions. They leave the supplier to establish how those decisions appear in the delivered code. CCH Canadian Ltd v Law Society of Upper Canada, 2004 SCC 13, paragraphs 16 and 24–25; Asia Pacific Publishing v Pioneers, [2011] SGCA 37, paragraphs 69–74; Global Yellow Pages v Promedia, [2017] SGCA 28, paragraph 24.

Australia supplies a particularly relevant software example. In Acohs v Ucorp, the Full Federal Court rejected the claim of originality in the generated HyperText Markup Language (HTML) source at issue. Human creation of the generating system did not establish the claimed authorship in that output. The court distinguished potentially original routines or tags from the claim actually pleaded. Record the particular human contribution for which protection is sought. Acohs, [2012] FCAFC 16, paragraphs 50–59.

The UK, India and New Zealand have express rules identifying an author for specified computer-generated works. Applying them requires the statutory creation facts and originality analysis. The UK's March 2026 proposal to remove its rule must be distinguished from the statutory text, which retained the rule as at 19 November 2026. An arranger provision alone supplies no uniform worldwide exclusivity. UK CDPA, sections 9(3) and 178; UK government report, 18 March 2026; India Copyright Act, section 2(d)(vi); New Zealand Copyright Act, sections 5(2)(a) and 14.

Mexico's May 2026 amendment expressly includes AI computer programs in its protected software category. Article 12 continues to identify a natural-person author. In Amparo Directo 6/2025, Mexico's Supreme Court upheld refusal of registration for an avatar the applicant attributed to Leonardo's creativity. That final judgment addresses those registration facts. Human revisions in a software module still require their own assessment. LFDA, Articles 3, 12 and 101–103, text as at 19 November 2026; signed judgment, 2 July 2025, paragraphs 42–59 and 82–85.

Employee and contractor rules change the ownership schedule

Use the contributor's actual engagement and creation record. Paying for development has different effects under the laws below. The following differences determine which documents the supplier must obtain before granting exclusive rights.

  • United States. Material rule for software supply: Qualifying employee work within employment scope falls under work made for hire. Commissioned work needs an eligible statutory category and the required signed agreement; software is not a freestanding category. 17 USC §101, work made for hire; §201(b); §204(a). Required contract or evidence response: Obtain a signed contractor assignment covering relevant rights instead of relying solely on a work-for-hire label.
  • Canada. Material rule for software supply: In-course employment can vest copyright in the employer, absent contrary agreement. Transfers require signed writing. Moral rights can be waived and are not assigned by the economic transfer. Copyright Act, sections 13 and 14.1. Required contract or evidence response: Check employment scope, obtain contractor title and secure the moral-right waivers needed for agreed use.
  • Germany. Material rule for software supply: Employee software follows §69b. Copyright itself is generally non-transferable between living persons; exploitation rights can be granted. UrhG §§29, 31 and 69b. Required contract or evidence response: Specify exclusive exploitation rights, permitted uses and onward grants. Check any consent requirements under §§34–35.
  • France. Material rule for software supply: Employee software and documentation made within duties or instructions have a specific employer economic-right rule. Author transfers require writing and defined rights, scope, purpose, place and duration. CPI L113-9; L131-1–3. Required contract or evidence response: Check contractor grants separately and identify the deliverables. Preserve the applicable moral rights and software-specific limits.
  • United Kingdom. Material rule for software supply: In-course employee works ordinarily belong to the employer, subject to agreement. Assignments require signed writing. CDPA sections 11 and 90–91. Required contract or evidence response: Obtain contractor assignments and examine the human or computer-generated authorship route before promising exclusivity.
  • India. Material rule for software supply: The employment exception concerns a contract of service. Assignment terms must address work, rights, duration and territory; statutory defaults can apply where duration or territory is omitted. Copyright Act sections 17 and 19. Required contract or evidence response: Use a signed work-specific assignment. Check the five-year and India-only defaults, and the non-exercise rule, against the actual instrument.
  • Singapore. Material rule for software supply: Sections 133–134 set the author-first and qualifying employment defaults, subject to the specified periodical-work exception and contrary agreement. For agreements made on or after 21 November 2021, the contrary allocation must be written. Assignments and exclusive licences require signed writing under sections 138 and 142. Copyright Act 2021, sections 133–134, 138 and 142, Singapore Statutes Online consolidation in force from 9 March 2025; Intellectual Property Office of Singapore ownership guidance, updated 8 January 2026. Required contract or evidence response: Establish the contract-of-service facts and any written contrary allocation. For independent software contributors, obtain the necessary signed assignment or exclusive licence from the entitled person.
  • United Arab Emirates (UAE) federal/onshore. Material rule for software supply: Article 28 addresses commissioned and employee economic rights. Work created for another can place economic rights with that beneficiary unless otherwise agreed in writing. Article 9 requires a defined written disposal of economic rights. FDL38/2021, Articles 9 and 28, controlling Arabic. Required contract or evidence response: Check whether the customer already benefits from the commissioning default. Identify background materials and the agreed allocation before work begins.
  • Saudi Arabia. Material rule for software supply: The replacement 2026 law gives a related-work employee rule. Article 18(2) states an author default for commissioned work; implementing Regulation 15(2) points to the commissioner for a specified non-employee special contract. Law, Article 18; Regulation, Article 15. Required contract or evidence response: Resolve the actual category and record an express work-specific allocation. The conflicting default wording makes a silent contractor arrangement unsuitable support for an exclusive-ownership promise.
  • South Africa. Material rule for software supply: Program authorship depends on control over making the program; the distinct computer-generated category concerns necessary arrangements. Employment and assignment rules then determine title. Copyright Act, sections 1, 21–22. Required contract or evidence response: Preserve actual control and instructions, apply the personnel rule, and obtain signed assignments or exclusive licences where needed.
  • Nigeria. Material rule for software supply: Section 28 starts with the author, subject to agreement. Its special government employment/service rule does not establish private employer ownership. Copyright Act 2022, sections 28–30 and 108. Required contract or evidence response: Obtain the private employee and contractor vesting or assignment agreements. Identify specific future work and avoid a transfer of all future works.
  • Brazil. Material rule for software supply: Software Law Article 4 can give the employer or service commissioner rights in qualifying development connected to the engagement, unless otherwise agreed. Unrelated work made without the listed resources has a separate rule. Law 9.609, Article 4. Required contract or evidence response: Preserve the service scope, duties and resource-use facts. Obtain an express grant where the statutory conditions do not establish the intended title.
  • Mexico. Material rule for software supply: Article 103 supplies the employee software/documentation rule and exempts software assignments from Article 33's general duration limits. Commissioned works require the Article 83/83 bis analysis and clear terms. LFDA, Articles 30–34, 83–84 and 103. Required contract or evidence response: Identify remuneration, rights, work and term in writing, and address registration for third-party effectiveness under Article 32.
  • Australia. Material rule for software supply: In-course employee literary works can belong to the employer. A general paid software commission does not by itself supply the same default. Assignments require signed writing. Copyright Act, sections 35 and 196. Required contract or evidence response: Secure contractor title and separate the original human contribution from automatically generated source.
  • New Zealand. Material rule for software supply: A person commissioning and paying, or agreeing to pay, for making a computer program can be first owner, subject to contrary agreement. Copyright Act, section 21(3)–(4). Required contract or evidence response: Set the customer, supplier and contractor allocations expressly. Preserve reusable background code and obtain signed assignments where the default does not fit the intended chain.

South Africa's control test needs evidence beyond a purchase order. Haupt applied authorship control on its particular instructions and approval record. In Bergh, functional requirements, progress reporting and testing did not prove the necessary control over an independent developer. The release file should record who controlled the making of the program, so that the ownership rules can then be applied. Haupt, [2006] SCA 39 (RSA), paragraphs 31–35 and 41–42; Bergh, [2020] ZASCA 30, paragraphs 61–66.

For an adjacent asset workflow, Licentium's South African game-asset supply analysis examines human contributions, contributor title and territorial protection in an art delivery. Computer programs require the software-specific tests and licence conditions discussed here.

Match the retained code to its actual licence

Start with the file and revision that contain the retained expression. A repository badge can conceal file-specific terms, vendored code, alternative licences or a later change. Confirm the licence actually offered by an entitled person and record the copyright and attribution information. Public access to a repository leaves that permission question open.

A match needs a legal comparison. Functional similarity can arise from ideas, methods, standards or constrained ways of writing an operation. In SAS Institute, the Court of Justice of the European Union (CJEU) excluded program functionality, programming language and data-file formats from protection as program expression, while preserving the separate analysis of copied source/object code and other original works. Brazil's software law also addresses similarity arising from functional characteristics, technical standards or limited forms of expression. SAS Institute, C-406/10, paragraphs 39–46 and 65–70; Brazil Law 9.609, Article 6(III).

Assess the quality of any protected expression retained. Canada's Cinar treats substantiality as qualitative and fact-sensitive, including non-literal copying, and expressly recognises that software can require an appropriate analytical approach. South Africa's Haupt treated a small number of valuable copied lines as substantial on its facts. An arbitrary line count or percentage of changes supplies no general clearance threshold. Cinar v Robinson, 2013 SCC 73, paragraphs 24–28 and 35; Haupt, paragraphs 44–45.

The following licence routes apply only when the identified source carries that text and the relevant act triggers its conditions.

  • MIT, grant and notice condition. Duties that change the release: Include the copyright and permission notices in copies or substantial portions. Effect on proprietary sale and customer rights: Commercial use, modification, distribution, sublicensing and sale are permitted. There is no corresponding-source delivery condition. Preserve upstream rights and the licence's warranty disclaimer.
  • Apache 2.0, §§2–4 and 6–9. Duties that change the release: Supply the licence, mark changed files, retain applicable notices and handle any NOTICE attribution as §4 requires. The contributor patent grant and its termination condition have defined scope. Effect on proprietary sale and customer rights: Additional terms for the supplier's modifications can coexist with the upstream conditions. A general trademark licence is excluded. Additional warranties or indemnities are the supplier's responsibility under §9.
  • GPLv3, §§0–6 and 10. Duties that change the release: Conveying covered source or object code activates the relevant licence and Corresponding Source requirements. Modified covered works and qualifying aggregates have different rules. Effect on proprietary sale and customer rights: Charging is permitted. Covered recipients retain GPL rights. Select an actual §6 source-delivery route for binaries, including installation information where the User Product provision applies.
  • LGPLv3, §§0–4. Duties that change the release: For a conveyed Combined Work, preserve library-modification and debugging reverse-engineering permissions, required notices and licence copies. Supply the required relinking material or use the qualifying shared-library mechanism; provide Installation Information where §4(e) requires it. Effect on proprietary sale and customer rights: The Application can have different terms under this route. Check the actual Library, Application, header material and integration; a static or dynamic linking label alone does not establish compliance.
  • AGPLv3, §13. Duties that change the release: A modified Program that supports remote network interaction must prominently offer all interacting users free network access to the Corresponding Source of that version. Ordinary conveyance conditions also apply. Effect on proprietary sale and customer rights: Hosted access can trigger this source offer. Determine the modified covered program and its interactions before extending the obligation to other services.
  • MPL 2.0, §§1.4, 1.7, 1.10 and 3.1–3.5. Duties that change the release: Distribution requires source availability and MPL rights for Covered Software, including changed covered files and new files containing it. Effect on proprietary sale and customer rights: Separate files in a Larger Work can have different terms. Executable terms must preserve the required source rights. Map actual covered content and file boundaries.

“Open source” leaves several questions unanswered. Identify the exact licence and version, whether the supplied code forms a covered modified work or a separate work, and the terms the customer wants to impose. GPLv3 expressly distinguishes a qualifying aggregate from a covered modified work. Apache defines derivative works for its own grant. MPL uses a covered-file structure. Architectural labels alone cannot establish which category the released code occupies.

A missing licence or incompatible customer restriction leaves three principal routes: secure a suitable grant from an authorised right holder, comply and revise the customer bargain, or replace the component. A dual licence is useful only when the alternative is genuinely available for the material and acts at issue. Rewriting requires a fresh examination of the expression retained.

For a different transaction involving delivery of a model itself, Licentium's open-source AI model licensing analysis addresses model assets, upstream permissions and supplier obligations. The licence review discussed here concerns code retained in the supplier's software release.

Distribution, hosted use and private delivery need different checks

Map each copy before selecting the licence route. The EU software directive expressly includes reproduction involved in loading, running and storage. Comparable local restricted acts are addressed in the national laws discussed above. Operating a server therefore requires a lawful basis for the software copies used there. The separate distribution or network condition follows the actual licence. Directive 2009/24/EC, Article 4.

  • Server-only hosted service. What the recipient receives or does: Results, with no transfer of the server program. Required licence and contract response: Under GPLv3 §0, mere remote interaction without transferring a copy is outside conveying. Check lawful server copies and any modified-network-program condition under AGPLv3 §13.
  • Browser application. What the recipient receives or does: JavaScript, WebAssembly or other executable assets. Required licence and contract response: Review the delivered assets and their source/notice duties. The SaaS label does not remove a transfer of those program copies.
  • Installer, library, container or appliance. What the recipient receives or does: Object code, source or both. Required licence and contract response: Identify the actual components. Perform the selected licence's distribution conditions and test source access for the matching release. A generic repository link may omit required source, scripts or installation information.
  • Bespoke delivery to one customer. What the recipient receives or does: A private source package or customer-deployed container. Required licence and contract response: Assess conveyance even where the transaction is confidential. Preserve applicable GPL recipient rights and distinguish proprietary components in the grant.
  • Contractor or hosting operator. What the recipient receives or does: Copies used to modify or run the supplier's software. Required licence and contract response: GPLv3 §2 contains a limited route for specified work exclusively for the supplier under its direction and control. Establish those facts before treating an external transfer as covered by that route.

These distinctions come from the GPLv3 definitions and §§2, 4–6, AGPLv3 §13, and the other identified licences. Source obligations do not always require publication to the whole world: the relevant recipients, written-offer beneficiaries and network users depend on the chosen route. A non-disclosure agreement must preserve whatever rights the applicable licence gives the recipient.

France illustrates the consequence of actual delivery facts. In the 2024 Entr'ouvert/Orange remand, the Paris Court of Appeal treated the integration and customer delivery of Lasso under GPLv2 as material to infringement, even though the deployed product was later used through a website. The decision concerns its integration, delivery and licence record. Paris Court of Appeal, 14 February 2024, RG22/18071, official export pp. 21–24 and 29. The CJEU's IT Development ruling also requires the Directive 2004/48 safeguards for a software-licence breach falling within the right holder's IP rights, irrespective of the national contractual or tort classification. C-666/18, paragraphs 42–49.

A statutory exception needs the same discipline. India's general fair-dealing provision expressly excludes computer programs, with specific permitted software acts addressed separately. Nigeria protects specified necessary program uses and voids terms restricting an act the Act permits. The supplier must identify the exact permitted purpose and satisfy its conditions before relying on either route. India Copyright Act, section 52(1)(a) and (aa)–(ad); Nigeria Copyright Act, section 20.

Saudi Arabia's 2026 AI-development reproduction exception also has defined conditions, including the implementing regulation's treatment of sources, records and protected expression in final outputs. Commercial delivery of retained protected code requires its own permission analysis. Copyright Law, Article 26(4); Implementing Regulation, Article 30. As at 19 November 2026, South Africa's software exceptions remained proposals. The Constitutional Court's 26 June 2026 decision was a pre-assent reference on a Bill. CCT306/24, [2026] ZACC26, paragraphs 184–185 and 200–209.

What code references and filters establish

GitHub documents a periodically refreshed index of public GitHub repositories for its code-reference feature. Private repositories and public code hosted elsewhere fall outside that index. In the described inline workflow, the comparison uses the suggestion and approximately 150 surrounding characters, with reference checking for accepted unchanged suggestions. Chat and agent surfaces need their own documentation and records. GitHub integrated development environment documentation, code referencing.

A negative result records what that feature returned within its scope and index state. A positive reference identifies code for examination of protected expression, copying, provenance and permission. Keep both kinds of result with their limitations. Review changes made after acceptance and material introduced through other channels. The tool's character window has no status as a statutory copying threshold.

Preserve copyright, author, owner and licence information during refactoring and packaging. Rights-management-information claims have their own elements. Canada, India, Nigeria, the UAE and Saudi Arabia each have local provisions requiring their own conduct and knowledge analysis. The US case discussed next cannot displace them. Canada Copyright Act, section 41.22; India section 65B; Nigeria sections 51–52; UAE Article 40; Saudi Article 47.

Doe v GitHub leaves the release decision with the supplier

On 16 September 2026, the Ninth Circuit affirmed dismissal of the pleaded output-based claims under 17 USC §1202(b) in Doe v GitHub. The interlocutory appeal concerned whether the allegations showed removal or alteration of copyright-management information from an existing work. The court treated the alleged output-generation process as insufficient for that claim and accepted the relevant standing allegations at the pleading stage. Official opinion, pp. 9–18.

The court rejected literal identicality as an independent statutory requirement and explained that minor cosmetic changes need not defeat a removal claim. It treated the input/training theory as forfeited and expressly reserved any view on copyright infringement based on similarity. The opinion recorded surviving contract claims at the time of that decision. Each of those limits matters when a supplier is asked to clear a matched component or promise licence compliance. Opinion, pp. 9–11 and 15–18.

The practical consequence is to continue the source and licence review. Permission to sell a retained component must come from the applicable rights and licence analysis. Licentium's Doe case note explains the appeal; the commercial release decision additionally needs contributor title, compliance materials and a customer agreement that reflects the actual code.

A provider's public copyright commitment must be traced through the agreement actually purchased. Keep the contracting entity, order, plan, renewal and generation dates, feature, applicable product terms, incorporated requirements and negotiated changes. The supplier then needs to compare its promised customer remedy with the provider's obligations for the same claim.

For direct GitHub volume purchases governed by the March 2026 Generative AI Services Terms, those terms extend an existing agreement's third-party defence to generative services and Outputs. They replace the earlier Copilot terms for new subscriptions and renewals from 5 March 2026; retain the version governing earlier generation and any later renewal. GitHub terms update, March 2026. The underlying General Terms cover specified paid Products and contain unmodified/uncombined wording. The output extension and document-precedence rule must be read together. A substantially revised suggestion integrated into a product therefore requires an express coverage determination before the supplier budgets on reimbursement. The General Terms require prompt written notice, defence and settlement control, and assistance. The covered defence is excluded from the ordinary liability limits; its subject and conditions remain defined. Generative AI Services Terms, §§1–5 and 7–9; General Terms, §§6, 7.1(d), 10.3 and 10.8.

For GitHub purchased through Microsoft, read the applicable Microsoft agreement and Product Terms. Microsoft's Customer Copyright Commitment expressly reaches use or distribution of covered Output. Its conditions include the relevant safeguards, input rights, incorporated mitigations, trademark-related exclusions and use, modification or distribution with knowledge, or constructive knowledge, of likely infringement. The condition concerning modification has that knowledge element. The applicable base agreement must also be obtained. The publicly available March 2023 US Microsoft Customer Agreement (MCA) document is labelled a specimen and cannot establish a supplier's executed bargain. Online Services Product Terms, Customer Copyright Commitment; Covered Product definition; MCA GitHub Offerings terms; MCA specimen catalogue.

One date-sensitive condition has changed. Microsoft's incorporated mitigation page states that from 3 April 2026 GitHub offerings have no additional required mitigations, and Duplicate Detection is optional for that purpose. Keep the other agreement conditions and source-licence obligations in view. Earlier filter wording should be matched to the date and contract to which it applied. Required mitigations, GitHub offerings section, updated 20 March 2026.

Other routes require their own coverage check

  • Personal GitHub terms. What the published terms establish: Section J leaves output review and third-party licence compliance with the user. The personal terms do not supply the business defence merely because a subscription is paid. Terms of Service, §§J and O–Q. Gap to resolve before making the customer promise: Identify the actual account and contracting route used by each contributor.
  • GitHub pre-release features. What the published terms establish: The preview terms extend an existing agreement defence under §10; §12 excludes that defence from the general monetary limit. Section 2 limits use of the preview software to the permitted non-production purposes. Pre-release License Terms. Gap to resolve before making the customer promise: Check permitted development, the actual feature and output rights. Distinguish using preview software in production from later shipping code generated during permitted development.
  • Azure OpenAI. What the published terms establish: The mitigation requirements address a copyright-directed metaprompt, retained evaluation/remediation evidence, protected-code detection, Prompt Shield and licence compliance for annotated or specified flagged material. Required mitigations. Gap to resolve before making the customer promise: Prove the required configuration and records for the covered deployment. Qualifying Azure OpenAI coverage does not extend by inference to every external model.
  • OpenAI API and defined Enterprise services. What the published terms establish: The Service Terms updated 13 November 2026 contain output-indemnity exclusions for modified, transformed or combined Output, among others. Codex/code-generation output can carry third-party and open-source software licences. Service Terms, §§1–4. Gap to resolve before making the customer promise: Establish the actual API, Codex or subscription route. The Service Terms heading that mentions Business does not itself make Business part of the defined Enterprise output-indemnity group.

For the OpenAI route, the Services Agreement assigns OpenAI's rights, if any, in Output as between the parties and recognises that others can receive similar output. Its defence procedure, damages provisions and absence of intended third-party beneficiaries require separate reading. The service-specific IP indemnity has no monetary cap under its wording, while claim exclusions and the separate indirect-liability provision remain relevant. Services Agreement, effective 1 January 2026, §§4, 12–14 and 16.

Across these routes, a customer's direct claim for breach of the supplier's ownership warranty can fall outside a provider's promise to defend specified third-party infringement claims. The customer may also be outside the provider agreement's beneficiary class. Preserve prompt/input permissions, feature and settings records, required evaluations, the actual output and later changes, and timely claim notice. The supplier's downstream procedure should let it comply with upstream defence and settlement conditions.

Offer distinct warranties and price the retained exposure

The customer can reasonably want an accountable supplier. The contract should answer that concern with verifiable commitments, specified remedies and an identified allocation of loss. A single absolute promise about every line obscures the rights and evidence available.

  • Originality. Supported form of commitment: Identify the bespoke human contribution and describe the review actually undertaken. Evidence and upstream gap: Design and contribution records; third-party components have their own authors. A provider output grant supplies no factual originality verification.
  • Ownership. Supported form of commitment: Transfer scheduled economic rights held by the supplier, using the locally effective form. Evidence and upstream gap: Personnel title, assignments and onward rights. German exploitation-right grants and the different commissioning defaults need specific treatment.
  • Non-infringement. Supported form of commitment: Define the deliverable, protected rights, authorised uses, territories and agreed exclusions. Evidence and upstream gap: Component clearance and claim procedure. Provider warranty disclaimers and claim exclusions leave possible supplier liability.
  • Licence compliance. Supported form of commitment: Promise completed compliance for the identified components and delivery method, with customer duties for later acts. Evidence and upstream gap: Notices, matching source access and any required installation information. Preserve the actual licence/version and recipient rights.
  • Exclusivity. Supported form of commitment: Specify the supplier-owned bespoke rights granted exclusively and any separately agreed limits on supplier reuse. Evidence and upstream gap: Exclude prior third-party permissions and unsupported exclusive protection. Give the customer sufficient rights to use background components.
  • IP indemnity. Supported form of commitment: Define covered third-party claims, defence costs, damages, settlements, cooperation, control and remedies. Negotiate any monetary cap or uncapped category expressly. Evidence and upstream gap: Compare beneficiary, claim type, territorial scope, modifications, combinations and loss categories against the actual provider agreement. Record the supplier's retained exposure.

These are drafting recommendations drawn from the ownership, licence and provider terms above. The actual law governing the customer contract can constrain them. Brazil has a particularly relevant rule: Software Law Article 10(1)(II) voids specified liability exemptions in contracts licensing commercialisation rights in foreign-origin software. First establish whether the agreement falls in that category, then examine the effect of the proposed clause. The provision does not itself prescribe the customer's requested uncapped indemnity. Law 9.609, Article 10.

Germany's rules on advance exemption for intent and standard terms, and Australia's unfair-contract-terms rules for covered standard-form contracts, also require clause-specific review. Consumer or small-business status matters where the relevant rule uses it. BGB §§276(3), 307 and 310; Australian Consumer Law, sections 23–24. US state and Canadian provincial laws are outside this comparison; the final indemnity and cap need the actual chosen-law analysis.

For UAE contracts, identify the federal/onshore, Dubai International Financial Centre (DIFC) or Abu Dhabi Global Market (ADGM) connection and the relevant instruments before applying a default or cap. The federal Civil Transactions Law was replaced from 1 June 2026. The replacement law's provisions on harmful-act exemptions, fraud/gross fault and agreed compensation require attention to the claim and clause. A familiar article number from the repealed law is inadequate support for an indemnity opinion under the replacement law. FDL25/2025, promulgating Articles 2–3 and Civil Transactions Law Articles 257, 334 and 340, controlling Arabic.

DIFC. The published March 2022 consolidation of IP Law 4/2019, Article 22, applies where the employment relationship involves work in or from DIFC or is subject to DIFC law. It includes workers engaged through a work-for-hire arrangement, allocates qualifying work to the employer and permits a different written allocation. Articles 34–35 require written assignments and specified licence terms. March 2022 consolidation, Articles 22 and 34–35; official law record.

ADGM. Its Application of English Law Regulations receive English common law and specified statutes under separate rules. The UK Copyright, Designs and Patents Act 1988 is absent from the Schedule in the 17 March 2022 consolidation. Establish the substantive copyright law and federal-law interaction for the particular right, act and forum before relying on the UK's computer-generated-authorship rule or an ADGM-specific ownership default. Regulations, sections 1–2 and Schedule, 17 March 2022 consolidation; ADGM application guidance.

Agree a sequence of remedies: obtain the necessary permission, supply a compliant modification or replacement, and provide an agreed termination/refund route where lawful performance cannot continue. Specify how the customer may operate during remediation and who controls admissions or settlements. A settlement that restricts the customer's business needs the protections negotiated in the contract. Insurance can be considered only against the actual insured entity, policy, claim, territory and exclusions.

Release, hold or replace

Use the following decision tree for the defined build and intended delivery. Each failed condition should identify the affected component, responsible person and required cure.

  • Identify build and intended use. Next: rights and permissions supported?
  • Rights and permissions supported? No: hold affected component. Yes: licence conditions completed?
  • Hold affected component. Next: suitable permission available?
  • Suitable permission available? Yes: obtain permission and recheck. No: replace or remove code.
  • Obtain permission and recheck. Next: rights and permissions supported?
  • Replace or remove code. Next: rights and permissions supported?
  • Licence conditions completed? No: complete notices and source duties. Yes: rights grant accurate and performable?
  • Complete notices and source duties. Next: licence conditions completed?
  • Rights grant accurate and performable? No: revise grant or replace affected code. Yes: indemnity terms and retained risk approved?
  • Revise grant or replace affected code. Next: rights and permissions supported?
  • Indemnity terms and retained risk approved? No: negotiate terms or obtain authorised risk acceptance. Yes: release approved build and records.
  • Negotiate terms or obtain authorised risk acceptance. Next: indemnity terms and retained risk approved?

The last risk decision concerns contractual exposure. It cannot cure a missing right or an unperformed licence condition at the earlier gates. If exclusive copyright is essential and the supplier cannot establish the necessary protection or title, narrow the grant with the customer's agreement or replace the affected material. If a provider defence remains uncertain, obtain the actual coverage position or decide explicitly what exposure the supplier will retain.

Before release, the engineering and legal owners should confirm four connected records: the component rights schedule; the licence and notice/source package; the human-contribution and personnel-title record; and the customer/provider contract comparison. Deliver the customer materials required by the licence and agreement. Retain the full internal evidence needed to explain those materials and respond to a claim.

After a later match or claim, preserve the challenged build, suggestion, changes and notices. Determine the relevant rights and licence conditions, follow the actual claim-notice procedure, and stop affected deliveries where continued supply would be unlawful. A cure, alternative licence or replacement should be checked against the existing recipients' rights and the source licence's termination/reinstatement conditions. Avoid a universal cure period or promise of provider payment.

Reopen the affected review when code, dependencies, licence terms, generation feature, delivery architecture or customer promises change. Release approval should identify the version and use that were assessed.

Review the contracts before release

For a scoped contract review, assemble the proposed customer agreement, provider order and incorporated terms, contributor documents, component schedule, matched-source records and deployment map. Licentium's AI supplier contracts service describes review of customer commitments, provider dependencies and procurement evidence for EU and UK enterprise sales. Those documents allow the parties to identify the rights that can be granted, the conditions that must be completed and the liability requiring a commercial decision.

Planning a launch somewhere new?

Prefer email? Write to hello@licentium.io. By sending, you accept our privacy policy.