You used ChatGPT to rough out a draft, tidy some copy or debug a function, and the client never asked how the work was made. Then a client's contract arrives with a clause about "third-party tools", or a colleague asks who owns the output, and you realise you have no answer. Most freelancers either hide the tool use or paste whatever is in front of them into a chatbot and hope. Neither is a plan.
Using AI in client work comes down to three duties: keep client information out of tools you are not allowed to use, own up to the parts you cannot promise, and put the arrangement in writing. This post covers disclosure, ownership of AI output, the 2025-26 developments, contract wording and a simple one-page policy. It is general information, not tax or legal advice.
Whether you must tell clients you use AI depends on your contract and the brief
Usually no: Indian law does not require you to tell clients you use AI, but your contract or the client's brief can. If either restricts third-party tools or requires approval for them, follow it. Where they say nothing, telling the client is good practice, not a legal requirement under any Indian rule covered here, and it protects you if they later object.
The practical case for telling them is simple. A client who learns about AI use from someone else assumes you hid it, even when the work is good. A line in your proposal or onboarding message ("I use AI tools for first drafts and research, and I review and take responsibility for everything I deliver") costs nothing and closes the argument before it starts. If a client says no, you have lost nothing and avoided a breach.
Ownership of purely AI-generated work in India is unsettled
Indian law has no settled answer on who owns copyright in purely AI-generated output. Section 2(d)(vi) of the Copyright Act 1957 names the "person who causes the work to be created" as the author of a computer-generated work, but its drafters did not have generative AI in mind, and commentators read "person" as a natural person. The Act also does not say how much human creativity is needed, and no statute or Indian court ruling has settled it for AI output. Do not tell a client that AI output is "public domain" or "owned by whoever wrote the prompt", because neither is established.
What is safer to say is narrower. The parts of a deliverable that you wrote, designed or edited yourself are human-authored, and the usual rules apply: you hold the copyright by default and pass it on through a written assignment. The guide to IP ownership for freelancers covers that default and how to transfer ownership on full payment. The unsettled part is only the portion that a tool produced with little human input, so avoid promising exclusive rights over it.
The 2025-26 developments do not settle who owns AI output
Two developments get quoted often, and neither answers the ownership question. In December 2025 the Department for Promotion of Industry and Internal Trade (DPIIT) released Part I of its working paper on generative AI and copyright. It deals with training data and proposes a licensing approach with royalties. It is a proposal, not law.
DPIIT has announced a Part II on authorship and copyrightability of AI outputs. Check the DPIIT website for its current status before you rely on anyone's summary of it.
The second development is the Delhi High Court's interim order of 24 July 2026 in ANI v OpenAI, which refused an injunction and held training use prima facie to be fair dealing. That case is about training and infringement, the suit is still pending, and it did not decide who owns AI output. For your own work, the contract is still your best protection.
Your contract should say whether AI tools are allowed and who is responsible
A good AI clause does three things: it says whether you may use AI tools, it says you remain responsible for the final deliverable, and it says you do not warrant copyright in AI-generated portions. Put it next to your IP and confidentiality clauses, where a reader will look for it. The full structure of a freelance agreement is in the freelance contract guide for India.
If the client wants AI left out entirely, agree it in writing and then keep to it. If they allow it, name any limits: no client data in public tools, no AI on confidential sections, or approval for specific tools. A lawyer should review the final wording, particularly for larger engagements.
Never paste client data, NDA material or credentials into AI tools without permission
Do not paste client data into an AI tool unless you have permission. That covers customer lists, unreleased product details, financials, personal data of the client's users, login credentials and anything marked confidential. The duty comes from your contract and NDA, and it applies whether information leaks through a chatbot, an email or a shared drive. The guide to a freelance NDA in India explains how those duties are written.
Where you do have permission, reduce the risk. Use a paid tier with training on your inputs switched off where the tool offers it, and anonymise what you paste: swap the client's name for "Client A", strip figures and remove anything that identifies a person. Do not assume any tool is safe because of its brand, since vendor data policies change often. Read the current terms of the tool you actually use.
A one-page AI-use policy keeps you consistent across clients
A one-page policy that you write once and attach to proposals saves you from deciding afresh every time. It should state which tools you use and for what, what you never put into them, that you review all output before delivery, and that you follow any client's stricter rules. Most freelancers need only six or seven lines.
For example, a designer might write: "I use AI tools for mood-board research and rough variations. Final artwork is made and edited by me. I do not upload client files or unreleased brand material to public AI tools." A developer might add that generated code is read, tested and checked for licence issues before it goes into the client's repository. The point is to be specific enough that a client can hold you to it.
Ask a lawyer when the stakes or the ambiguity are high
Ask a lawyer when the client is large, the deliverable will be sold or registered, personal data is involved, or the contract has a clause about AI or third-party tools that you cannot read confidently. A short review costs far less than a dispute over ownership or a data leak.
Rinto lets you send contracts for e-signature (Pro plan), so the client signs in the browser, and a signed contract can create the project with details pre-filled. The free freelance contract template generator needs no signup.
Frequently Asked Questions
Do I have to tell my client I used ChatGPT?
Your contract and the client's brief decide this. If either restricts third-party tools or requires approval, you must follow it, and breaking it could be a breach even if the work is good. Where they say nothing, telling the client is good practice, not a legal requirement. A single line in your proposal, saying which tools you use and that you review and take responsibility for the final work, prevents most disputes. If the client objects, you can adjust before any work is done rather than after delivery.
Who owns copyright on AI-generated content in India?
It is unsettled. Section 2(d)(vi) of the Copyright Act 1957 names the person who causes a computer-generated work to be created as its author, but commentators read "person" as a natural person, and the Act does not say how much human input is needed. No statute or Indian court ruling settles ownership of purely AI-generated output. Do not assume it is public domain or that the person who typed the prompt owns it. The human-authored parts of your work follow the usual rules, so keep a written assignment for those.
Can I copyright AI-generated work in India?
For purely AI-generated material, nobody can give you a certain yes. The law is unsettled, and the DPIIT's Part I working paper from December 2025 deals with training data, not output. DPIIT has announced a Part II on authorship of outputs, so check its website for the status. What you can protect with more confidence is the human contribution: your own writing, design choices, edits and arrangement. If copyright registration matters for a deliverable, speak to an IP lawyer before you apply, and avoid promising your client rights you cannot be sure of.
Is it legal to paste client data into ChatGPT?
There is no single answer, because the limits come from your contract and NDA rather than from the tool. Confidentiality duties apply whether information leaks through an AI tool, an email or a shared folder, and a client's contract may restrict third-party tools outright. Without clear permission, do not paste client data, NDA material, credentials or personal data. If you have permission, use a paid tier with training turned off where available, and anonymise the input. Do not rely on any tool's brand as proof it is safe, and read its current terms.
What should a freelance contract say about AI?
Three things at minimum. First, whether you may use AI tools, and any limits such as no client data in public tools or approval for specific tools. Second, that you remain responsible for the final deliverable, including checking it for errors. Third, that you do not warrant copyright in AI-generated portions, while still assigning the rights you hold in the human-authored parts. Put the clause beside your IP and confidentiality terms, and have a lawyer review the wording for larger projects. The risks of working without a contract show why writing it down matters.