Skip to content

Who owns the code when you hire a software company in India?

13 Nov 2026

·

8 minute read

In India, the software company that writes your code owns the copyright in it by default, even though you paid for it. Ownership passes to you only if your software development agreement assigns it in writing. India's Copyright Act makes the author of a work its first owner, treats computer programs as literary works, and accepts an assignment only when it is written and signed. So the assignment clause in your agreement decides who owns the code.

This is a practical guide for buyers, not legal advice. Have a lawyer review any agreement before you sign it.

Why does the developer own the code by default?

The Copyright Act, 1957 defines a "literary work" to include computer programmes, and defines a computer programme as "a set of instructions expressed in words, codes, schemes or in any other form" that makes a computer perform a task. Code is therefore protected the same way a book is. The World Intellectual Property Organization's copyright FAQ notes that software receives this protection automatically, without registration, and that the first owner is "generally the original creator or author of the work."

Section 17 then sets the starting point: "the author of a work shall be the first owner of the copyright therein." There is an exception for employees. When a work is made in the course of the author's employment "under a contract of service", the employer owns it, "in the absence of any agreement to the contrary."

That exception points away from you. The engineers who write your software are employed by the software company, not by you. Under the employee rule, the code belongs to their employer, which is the vendor. You are a client buying a service. Paying the invoice does not, by itself, move the copyright.

Section 19 of the Act sets the rules, and three of them matter for every software contract:

  • It must be in writing. "No assignment of the copyright in any work shall be valid unless it is in writing signed by the assignor or by his duly authorised agent."
  • It must say what is assigned. The assignment has to identify the work and specify the rights assigned, the duration and the territorial extent.
  • Missing details have defaults that may not suit you. If the period of assignment is not stated, "it shall be deemed to be five years from the date of assignment." If the territory is not specified, it "shall be presumed to extend within India."

The last point catches many buyers. An agreement that simply says "all IP belongs to the client", with no period and no territory, can leave you with rights that are limited in time and in geography. If you plan to sell the product abroad or use it for more than five years, say so in the clause.

Section 18 also allows the "prospective owner of the copyright in a future work" to assign it. You can sign the assignment at the start of the project, covering code that has not yet been written.

Which clauses should a software development agreement include?

Use this as a checklist when you read a draft.

ClauseWhat it should say
Assignment of copyrightAll deliverables (source code, documentation, designs, database schemas) are assigned to you for the full term of copyright, worldwide. State when it takes effect, for example on each payment
Source code deliveryYou receive the full source code, build instructions and deployment scripts, in a repository you control
Vendor's existing codeLibraries and tools the vendor built before your project stay theirs, and you get a permanent, royalty-free licence to use them inside your product
Open-source componentsA list of open-source packages used and their licences, so you know your obligations
Accounts and keysCloud, app store, domain and third-party API accounts are registered to your organisation, not to the vendor or one of its staff
Your dataData you supply stays yours and is used only for your project
AI modelsWho owns trained or fine-tuned model weights, prompts and evaluation sets, and whether your data may be used to improve anything else
Handover on exitWhat the vendor must hand over if the contract ends early, and how quickly

The data clause matters more if the software handles personal data. Under the Digital Personal Data Protection Act, 2023, your organisation can have a vendor process personal data on its behalf "only under a valid contract" (Section 8(2)), and stays responsible for that processing (Section 8(1)). The agreement should therefore cover security safeguards and how quickly the vendor tells you about a breach.

The vendor's existing code deserves attention. Most software companies reuse their own components across clients, and that is usually good for you, because it saves time. The fair arrangement is a licence for those components and an assignment for everything written specifically for you. Ask the vendor to list which is which.

Sample wording to take to your lawyer

Clause checklists are easy to agree with and hard to turn into text. Below is example wording we wrote to match the points above, including the details Section 19 asks for: what is assigned, which rights, for how long and where. Treat it as a starting draft for your lawyer, not as finished legal text, and adapt the defined terms to your agreement.

Assignment. The Developer assigns to the Client all copyright and other intellectual property rights in the Deliverables, including source code, object code, documentation, designs and database schemas created for this Agreement. The assignment covers all rights, for the full term of copyright, throughout the world, and takes effect for each Deliverable when the Client pays the invoice for it.

Developer's existing materials. Materials the Developer owned before this Agreement, or creates independently of it, remain the Developer's property. Where they are included in a Deliverable, the Developer grants the Client a perpetual, irrevocable, worldwide, royalty-free licence to use, modify and maintain them as part of that Deliverable. The Developer will list these materials in writing before delivery.

Source code and handover. The Developer will keep the complete source code, build instructions and deployment scripts in a repository controlled by the Client, and will hand over all credentials, keys and accounts held for the project within five working days of a written request or of termination.

Client data. Data supplied by the Client remains the Client's property, is used only to perform this Agreement, and is not used to train or improve any model or product for any other purpose without the Client's written consent.

Read your own draft against the same four points. If any of them is missing, the defaults in the Act, or the vendor's standard terms, will fill the gap.

What should you check before signing?

Five questions catch most problems:

  1. Is there a written, signed assignment clause, with the duration and territory stated?
  2. Does the clause name every deliverable, including documentation and designs?
  3. Which parts are the vendor's pre-existing code, and what licence do you get for them?
  4. Whose name is on the code repository, the cloud account and the app store listing?
  5. If the relationship ends badly, what do you receive, and when?

If a vendor resists answering any of these, treat it as information about how the handover will go.

Frequently asked questions

Does paying for custom software mean I own the code?

Not automatically. Under Section 17 the author is the first owner, and ownership moves only through a written assignment under Section 19. Your software development agreement needs that clause.

What happens if my agreement does not mention duration or territory?

Section 19 fills the gaps: the assignment is treated as lasting five years and as covering India only. State "for the full term of copyright" and "worldwide" if that is what you need.

Can a software company reuse code it wrote for me with other clients?

If the copyright was assigned to you, not without your permission. Code the vendor wrote before your project, and kept, can be reused. A clear split between assigned work and licensed components avoids disputes.

Who owns an AI model trained on my data?

The Act does not answer this directly for model weights, so the agreement must. Decide ownership of fine-tuned models, prompts and evaluation sets in writing, and state whether your data may be used for anything beyond your project.

Elroot Labs builds custom software and AI systems for organisations in India and abroad. If you are reviewing an agreement for a project, you can send us the brief, and our process explains how handover works.

AI tools

Ask ChatGPTAsk Claude

Start with the problem that matters