The AI Clauses Every Freelance Contract Needs in 2026

The law settled. Most contracts did not move with it. The clauses below close the gap.

The ownership trap

Start with the clause that surprises people most, because it is the one a silent contract gets most dangerously wrong.

A standard freelance contract says something like "all deliverables and the intellectual property in them transfer to the client on final payment." That language assumes the deliverable *can* be owned. After the rulings above, that assumption no longer holds for everything.

If a portion of a deliverable was generated purely by AI — with no meaningful human authorship of that portion — that portion may not be copyrightable by anyone. Not the freelancer, not the client. A contract that promises to "transfer ownership of all deliverables" is, for purely AI-generated material, promising to transfer something that does not exist as property. The Copyright Office's registration guidance, in place since March 2023, already requires applicants to identify and disclaim AI-generated portions of a work and to claim copyright only for their own human contributions (US Copyright Office AI policy guidance).

The fix is a clause that is honest about this. It should distinguish between AI-assisted work — where the freelancer used AI as a tool but exercised meaningful human authorship — and AI-generated material with no such authorship, and it should transfer to the client whatever rights actually exist rather than promising rights that do not. Sample starting language:

"The Freelancer assigns to the Client all intellectual property rights the Freelancer holds in the Deliverables upon final payment. The Client acknowledges that portions of a Deliverable generated solely by an artificial-intelligence tool, without sufficient human authorship, may not be subject to copyright protection under applicable law, and that this Agreement transfers only such rights as exist."

That sentence does two things: it still assigns everything assignable, and it stops you from warranting ownership of something the law says nobody owns.

Disclosure and confidentiality clauses

Two more clauses follow directly.

Disclosure. Clients increasingly want to know whether, and how, AI was used in their deliverable — partly for their own copyright registration, partly for their own comfort. Rather than leave this to an awkward conversation, a disclosure clause sets the expectation: the freelancer will disclose, on request or as standard, the general nature of AI tool use in producing the deliverables. This protects the freelancer too — disclosed AI use cannot later be characterised as something hidden.

Confidentiality. This is the clause with the most immediate practical risk. Many AI tools, on their consumer tiers, may use submitted inputs to improve their models. A freelancer who pastes a client's confidential brief, unreleased product details, or customer data into such a tool may be breaching the confidentiality clause they already signed — without realising it. The AI-era confidentiality clause should state plainly that the freelancer will not input the client's confidential information into AI tools that train on user inputs, or will use only tools and settings that contractually exclude training on the submitted data. This is not a new obligation so much as making an existing one survive the arrival of AI tools.

Indemnification: who pays if it infringes

Indemnification is the clause that decides who carries the financial risk if something goes wrong — and AI raises a specific version of "wrong": an AI-assisted deliverable that turns out to infringe a third party's copyright.

There is real legal uncertainty here. The US Copyright Office's third report, issued in May 2025, addressed AI training on copyrighted works and warned that commercial use of large troves of copyrighted material to produce content that competes with it "goes beyond established fair use boundaries" (US Copyright Office, Copyright and Artificial Intelligence hub). That is the Office's stated position, not a settled court ruling — fair use is decided case by case — but it signals that infringement risk in AI-assisted work is a live issue, not a hypothetical one.

For a freelancer, the danger in a silent contract is an open-ended indemnity. A standard clause where the freelancer indemnifies the client against "any and all claims arising from the deliverables" can, if read broadly, make the freelancer personally liable for an infringement claim rooted in how an AI vendor trained its model — something entirely outside the freelancer's control. Legal analysis of AI contracts notes that IP-infringement indemnities are often deliberately carved out of general liability caps, so exposure on IP claims can stay uncapped even when other liability is limited (Parsons Behle, indemnification clauses in AI contracts).

The freelancer-protective move is to scope the indemnity. Limit it to claims arising from the freelancer's own breach of the contract or own wrongful conduct, exclude claims arising solely from the conduct of a third-party AI vendor, and make sure any indemnity is subject to the overall liability cap rather than carved out above it. The exact balance is a negotiation — but a freelancer should never sign an uncapped, all-claims indemnity in an era where part of the deliverable's provenance is an AI vendor they have no contract with.

When the client sets the AI rules

The clauses above are written from the freelancer's side. In 2026, more contracts also arrive with the client setting AI rules — and a freelancer needs to read those just as carefully.

Some clients now require disclosure of AI use, or restrict which tools may touch their data, or forbid AI use entirely on certain deliverables. Others, particularly those serving EU markets, are responding to regulation: the EU AI Act's transparency obligations under Article 50 — which include marking AI-generated content — begin to apply from August 2026 (EU Artificial Intelligence Act, Article 50). A client subject to those rules may pass an equivalent obligation down to you in the contract.

The point is not to resist client AI clauses reflexively. It is to make sure you can actually comply with what you sign. If a contract says "no AI tools may be used in producing the deliverables," and your real workflow uses AI, you have a choice to make before signing — not a breach to discover afterwards. For the broader regulatory context, see the EU AI Act and freelancers using LLMs for client work.

The six-clause checklist

Pulling it together, the freelance contract that is ready for 2026 addresses six things:

1. Ownership — assigns all rights that exist, without warranting ownership of purely AI-generated material that may not be copyrightable.
2. Disclosure — sets the expectation that AI tool use will be disclosed.
3. Confidentiality — bars feeding client confidential data into tools that train on inputs.
4. Indemnification — scoped to the freelancer's own conduct, capped, not open-ended.
5. Warranties — the freelancer warrants their own human contribution and original work, not the provenance of an AI vendor's training data.
6. Client-side AI rules — read, understood, and genuinely compliable-with before signing.

If your current contract is a template you found years ago, it almost certainly addresses none of these. A good starting point for a clean base is the roundup of free freelance contract templates, which you can then extend with the six clauses above.

Delivvo gives freelancers a branded client portal where proposals and contracts are sent, signed, and stored alongside the deliverables and invoices they govern — so when you update your contract for the AI era, every client is working from the current version, not a years-old template. See how it works →

The takeaway

AI is in three out of four freelance deliverables, and the law on who can own AI-assisted work has now settled — human authorship is required, and purely AI-generated material may not be ownable by anyone. A contract that is silent on all of this is not neutral; it is a contract that quietly promises things the law no longer supports and leaves the freelancer carrying risks they never agreed to.

The fix is not complicated and it is not expensive. Six clauses — ownership, disclosure, confidentiality, indemnification, warranties, and a careful read of any client-side AI rules — bring a freelance contract back in line with how the work is actually done in 2026. Update the template once. Send the current version every time.