Code you write as part of your job almost always belongs to your employer. Indian copyright law makes the employer the first owner of work made in the course of employment, and most tech contracts go further with written IP assignment clauses. A weekend project built on your own time and laptop is not automatically the company’s, but whether you can keep it depends heavily on what you signed.

This guide explains the default legal rule, how assignment clauses widen it, and the practical steps that keep a side project, open-source work or freelance gig clearly yours.

The default rule: Section 17 of the Copyright Act

Software is protected in India as a literary work: the Copyright Act, 1957 includes computer programmes in that definition. The general rule is that the author of a work is its first owner. Section 17(c) carves out an exception for employees: where a work is made in the course of employment under a contract of service, the employer is the first owner “in the absence of any agreement to the contrary”.

Two phrases decide most disputes:

  • “In the course of employment” means work connected to what you are employed to do. Code for your team’s product clearly qualifies. A mobile game written at home by a payroll analyst is much less likely to.
  • “Agreement to the contrary” means your contract can change the default either way. In practice, employers use it to claim more, not less.

How your contract widens the default

Most offer letters and IP agreements contain an assignment clause. Under Section 18 of the Act you can assign copyright in a future work, and the assignment takes effect when the work comes into existence. That is how a clause signed on day one can capture code written years later.

Section 19 sets the formalities. An assignment is valid only if it is in writing. If it does not state a period, it is deemed to last five years from the date of assignment, and if it does not state a territory, it is presumed to cover India only. Well-drafted employment contracts therefore spell out “worldwide” and “for the full term of copyright”. If yours is vague, that matters, and a lawyer can tell you how much.

Common clause types and what they mean for you:

ClauseWhat it usually saysRisk to side projects
Broad IP assignmentAll IP you create during employment that relates to the company’s actual or anticipated business is assignedHigh if your project overlaps the business, even when built after hours
Company resourcesAnything made using company devices, accounts, code or confidential information belongs to the companyHigh if you ever open the project on a work laptop
Invention disclosureYou must report and assign inventions; you help with patent filingsMedium; patents in India follow whoever holds the assignment
Prior inventions scheduleYou list existing projects you own; they are excludedProtective, if you fill it in
ConfidentialityNon-public information stays secret during and after employmentApplies whatever happens to ownership

On patents, the Patents Act, 1970 does not have a special employee-inventor rule. An application can be made by the inventor or by the inventor’s assignee, so the contract again decides who owns the invention.

Three scenarios

1. Fintech developer builds a budgeting app

Riya works on payments at a fintech and builds a personal-budget app at weekends on her own laptop. Her contract assigns IP “relating to the company’s business, actual or anticipated”. Even though she used no company resources, the subject overlaps her employer’s field, so the company has a credible claim. Getting written clearance before launch is the only safe route.

2. ERP consultant writes a chess engine

Arjun configures SAP for clients and writes a chess engine on his home PC. There is no overlap with the business, no company resources and nothing confidential involved. His claim to ownership is strong, and listing the project in his prior-inventions schedule (or emailing HR about it) makes it stronger.

3. A “quick fix” from the office laptop

Kabir pushes one commit to his personal open-source library from his work laptop during a lunch break. Many contracts treat anything made with company equipment as company property. One commit may never be raised, but it muddies the record. Keep a strict separation.

Protecting your side projects: a checklist

  1. Read your documents first: the offer letter, employment agreement, IP or confidentiality agreement and any code of conduct or outside-work policy.
  2. Fill in the prior-inventions schedule when you join. If you missed it, send HR a dated email listing existing projects.
  3. Use only personal devices, accounts, networks and time. No company code, data, tools, cloud credits or paid licences.
  4. Stay outside your employer’s business area, including areas it is clearly moving into.
  5. Ask for written permission for anything significant, and keep the reply. A specific “we waive any claim to project X” is better than a general “no objection”.
  6. Keep dated evidence: commit history on a personal account, design notes and timestamps showing when and how the work was done.

Open source contributions

Many companies allow open-source work under a written policy, often with a pre-approval step. Check three things before contributing:

  • Whether the project is related to your job. If it is, the company may want you to contribute under its name and email.
  • Whether the project asks for a Contributor License Agreement (CLA), and who must sign it. If your employer owns your code, you may not be able to sign alone; some projects need a corporate CLA.
  • The licence of the project, so that you are not mixing code your employer owns into a licence it has not approved.

Moonlighting and second jobs

Moonlighting is a contract issue as much as an IP one. Many contracts have exclusivity clauses that bar outside work without permission, and courts generally accept restrictions that apply during employment. In September 2022, Wipro said it had dismissed about 300 employees found to be working for competitors at the same time, which made the issue a national talking point.

Some employers now allow approved gigs that do not compete or conflict with your role. The safe approach is simple: disclose, get approval in writing, avoid competitors and clients, and never use work hours or equipment. Remember that a second salaried job can show up in records such as your EPF account or tax data. Our guide to background verification in Indian IT companies explains what employers can check.

When you leave

  • Do not copy company code, documents or customer data to personal storage. Doing so can lead to civil claims and, in some cases, criminal complaints.
  • Return devices, and delete company data from personal phones and laptops as the policy requires.
  • Your general skills, experience and know-how stay with you. Specific confidential information, such as source code, client lists and pricing, does not.
  • Confidentiality obligations continue after you leave, even though post-employment non-competes are generally unenforceable in India. Our guide to resigning in India covers notice periods, non-competes and bonds.

Quick questions

Can my employer claim an app I built before I joined?

Not through Section 17, because you did not make it in the course of that employment. A broadly worded clause could still cause arguments if you keep developing it after joining, which is why listing it as a prior invention matters.

Does registering copyright in my name protect me?

Registration with the Copyright Office is optional and serves as evidence, but it does not override a valid written assignment. It helps most for clearly independent work.

Is a verbal “go ahead” from my manager enough?

It is better than nothing, but managers often lack authority to waive IP rights. Get confirmation from HR or legal by email.

Sources


This article is general information, not legal advice. Contract terms vary widely. For a specific situation, consult a lawyer who handles employment or IP matters.

Last reviewed: 9 October 2026.

Leave a Reply

Trending