A Bangalore-based SaaS startup spent eighteen months and ₹40 lakhs building a B2B inventory management platform. They hired four freelance developers through a gig platform, paid them milestone-based fees, and launched successfully. Three months after launch, one of the freelancers — working independently — released a nearly identical product. When they consulted an IP lawyer, the answer was uncomfortable: because there was no written assignment of copyright in the freelancer contracts, the freelancers retained ownership of the code they had written. The startup had paid for development but did not legally own what they had built.
This scenario plays out across India’s startup ecosystem with alarming regularity. Copyright law for software is widely misunderstood — by founders who assume paying for development automatically transfers ownership, by developers who don’t realise their code is a creative work with statutory protections from the moment it’s written, and by businesses that file patent applications for software innovations when copyright would have been the faster, cheaper, and more appropriate protection.
India’s Copyright Act, 1957 provides robust protection for computer software through a framework that is relatively easy to understand once you know the right provisions. This guide answers the questions Indian developers, founders, and tech companies most commonly get wrong: what copyright protects in software, what it does not, who owns the code, how to register it, and what remedies are available when someone copies your work.
The governing provision: Computer software is protected as a literary work under Section 2(ffc) of the Copyright Act, 1957, which defines “computer programme” as a set of instructions expressed in words, codes, schemes, or in any other form including a machine-readable medium capable of causing a computer to perform a particular task or achieve a particular result. This definition is deliberately broad — it covers source code, object code, scripts, and compiled executable files across all programming languages and platforms.
What Does Copyright Actually Protect in Your Software?
What elements of software receive copyright protection under Indian law?
Copyright protects the expression of your software — how you have written and structured your code — not the underlying ideas, concepts, algorithms, or functionality it implements. This distinction is the single most important principle in software copyright law, and it governs what you can enforce and what you cannot.
Protected elements under the Copyright Act, 1957 include:
Source code — the human-readable instructions written in a programming language. Each file of original source code is a protected literary work from the moment it is written, without any registration requirement.
Object code — the compiled, machine-readable version of your source code. Under Indian law, object code and source code are both protected as computer programmes under Section 2(ffc).
Screen displays and user interface design — original graphical elements, layout arrangements, and visual presentations in your software may qualify as artistic works under Section 2(c) of the Copyright Act. However, purely functional UI elements — standard buttons, common navigation patterns — receive limited protection.
Databases — original compilations of data that involve creative selection, arrangement, or presentation are protected as literary works under Section 2(o) of the Copyright Act.
Software documentation — user manuals, technical specifications, API documentation, and similar materials are literary works protected independently of the underlying code.
What is NOT protected — the idea-expression divide
Copyright does not protect ideas, algorithms, mathematical formulae, programming techniques, or the functionality that your software achieves. It protects only the specific expression — the particular way you have written the code to implement those ideas.
This means a competitor can legally write their own code that performs exactly the same function as yours, using the same underlying algorithm, as long as they write it independently in their own expression. What they cannot do is copy your source code, reverse-engineer your object code to reproduce your source, or substantially reproduce your software’s structure, sequence, and organisation without your permission.
In Eastern Book Company v. D.B. Modak (Supreme Court, 2008), the Court confirmed that the threshold of originality required for copyright protection is that the work must originate from the author — skill, judgment, and creative choices must be exercised. Purely mechanical copying of data without creative selection fails this test. Applied to software, this means cookie-cutter, entirely formulaic code receives weaker protection than code involving genuine architectural creativity and original problem-solving.
Copyright vs. patent for software — which do you need? Copyright protects how you wrote the code. Patent (where available) protects the technical process or method the code implements. Under Section 3(k) of the Patents Act, 1970, computer programmes per se are excluded from patentability in India — though software with a demonstrable technical effect on hardware may qualify. For most Indian software companies, copyright is the primary and most accessible protection. Patent is relevant only where the software implements a novel, non-obvious technical method with real-world industrial application beyond the software itself.
Key Takeaway: Copyright protection for your source code arises automatically the moment you write it — no registration required. Registration creates an evidentiary record that dramatically strengthens your position in any dispute. The protection covers your expression, not your ideas. [INTERNAL LINK: Copyright Registration Services — Unimarks Legal Solutions]
Who Owns the Copyright in Software Written in India?
Does paying a developer for their work automatically transfer copyright ownership?
No — and this is the most commercially consequential misconception in Indian software copyright law. Paying someone to write code does not automatically transfer the copyright in that code to you. Ownership follows the rules in Sections 17 and 19 of the Copyright Act, 1957, which differ critically depending on the employment relationship.
What are the ownership rules for different developer relationships?
Salaried employees writing code in the course of employment: Under the proviso to Section 17 of the Copyright Act, 1957, where a work is made by an author in the course of their employment under a contract of service or apprenticeship, the employer owns the copyright — not the employee — unless there is an agreement to the contrary. This applies to full-time employees whose job includes software development. A startup that employs developers on a salary contract owns the copyright in their work, without needing a separate assignment.
Freelancers and independent contractors: This is where the ownership gap arises. A freelancer is not an employee — they work under a contract for services, not a contract of service. Under Section 17, a freelance developer owns the copyright in the code they write, even if you commissioned and paid for it, unless they have expressly assigned the copyright to you in a written agreement. Without a written copyright assignment, the commissioning party receives only an implied licence to use the work — not ownership.
This distinction has destroyed IP portfolios at acquisition stage. When a startup is acquired, the acquiring company conducts IP due diligence. If a significant portion of the codebase was written by freelancers without written assignment agreements, the acquirer faces a situation where the startup does not legally own its own product. Deals have collapsed or been significantly devalued for exactly this reason.
Co-developers and startup co-founders: Where two or more persons collaborate on a software product and the contributions are not separable, the work is a joint work under Section 2(z) of the Copyright Act. Joint authors own the copyright together, and neither can assign or licence the copyright without the other’s consent. Co-founder IP agreements should specify copyright ownership clearly and include assignments of each founder’s individual contribution to the company entity.
The contractor fix: Every freelance developer engagement should include a written agreement with two clauses: (1) a copyright assignment — explicitly transferring all copyright in work created under the engagement to the company — and (2) a waiver of moral rights, to the extent permitted by law. These clauses should be in the agreement before work begins, not added afterward. An IP lawyer can draft a standard freelance IP agreement for your company in a few hours — the cost is trivial compared to the risk of not having one.
Key Takeaway: Paying for code does not transfer copyright. If your codebase was written by freelancers or contractors without written assignment agreements, you may not own your own product. Audit your developer contracts now — before a dispute, acquisition, or investment round surfaces the problem. [INTERNAL LINK: Business Contracts and Agreements — Unimarks Legal Solutions]
Open Source Licences and Proprietary Software: The Compliance Obligation
What happens when your software uses open source components?
Most production software incorporates open source libraries, frameworks, or components. The copyright in open source code belongs to its authors — and they have licensed it to you on specific terms. Violating those terms is copyright infringement.
The key open source licence categories relevant to Indian software companies are:
Permissive licences (MIT, Apache 2.0, BSD) — allow use in proprietary software with minimal obligations. Typically require attribution (retaining the original copyright notice) but do not require you to release your own code as open source.
Copyleft licences (GPL, LGPL, AGPL) — impose “share-alike” obligations. Code derived from GPL-licensed software must itself be distributed under the GPL. Using GPL-licensed components in a commercial SaaS product without complying with the GPL’s distribution requirements is copyright infringement against every copyright holder who contributed to that open source project.
The GNU Affero General Public License (AGPL) is particularly significant for SaaS companies. Unlike the GPL, which is triggered by distributing software, the AGPL is triggered by using software to provide a network service — meaning if your SaaS product incorporates AGPL-licensed components, you may be required to make your entire source code available under the AGPL.
Indian companies that have received DPIIT startup recognition or venture funding face particular scrutiny on open source compliance during due diligence. A product built on undisclosed AGPL components that has never released its source code has a material IP compliance liability that affects both valuation and investment risk.
Open source compliance audit: Conduct a software composition analysis (SCA) scan of your codebase using tools such as FOSSA, Black Duck, or Snyk before any investment round or acquisition process. The scan identifies every open source component and its licence. Your IP counsel can then advise on compliance requirements and remediation where necessary. This is significantly cheaper to do proactively than in response to a legal claim.
Key Takeaway: Open source licence obligations are real copyright obligations. Violating a GPL or AGPL licence is infringement against the original copyright holders. Audit your open source dependencies before your next funding round or M&A process.
How to Register Copyright for Software in India: Step-by-Step
Does software copyright require registration to be valid?
No. Copyright in your software arises automatically under Section 13 of the Copyright Act, 1957 the moment you write original code. Registration is not a prerequisite for protection. However, registration with the Copyright Office (under the Ministry of Commerce and Industry) provides several practical and legal advantages that make it strongly advisable.
A copyright registration certificate: creates a public record of ownership and creation date; serves as prima facie evidence of ownership in disputes and litigation; enables faster platform takedown requests; strengthens your negotiating position in licensing discussions; and is frequently required by investors and acquirers as part of IP due diligence.
What is the registration procedure for software copyright in India?
Step 1 — Prepare the application
Software copyright is registered in the Category II: Literary Works category. The application is filed on Form XIV under the Copyright Rules, 2013, accompanied by:
- Statement of particulars (Form I)
- Statement of further particulars (Form II), specific to computer programmes — describing the software, its purpose, the programming language, operating environment, and whether it has been previously published
- A copy of the software — typically submitted as source code extracts (discussed below)
- The prescribed fee
Step 2 — Address the source code deposit question
This is the most practically sensitive aspect of software copyright registration. The Copyright Office requires a copy of the work to accompany the application. For software, this creates a tension: submitting full source code to a government registry that is technically a public record raises legitimate confidentiality concerns.
The accepted practice is to deposit representative extracts of the source code — typically the first 25 and last 25 pages of the source code for the most significant module, or a deposit of equivalent representative content. This practice is aligned with international norms (comparable to the US Copyright Office’s deposit rules for software). For trade secret protection of the remaining code, a Trade Secret Non-Disclosure Agreement with appropriate parties and internal access controls provides the complementary layer of protection.
Step 3 — File online and pay the fee
Applications are filed at the Copyright Office e-filing portal at copyright.gov.in (not any third-party website). The current official registration fees are:
| Work Category | Fee per Work |
| Literary work (including computer programme) | ₹500 |
| Artistic work | ₹500 |
| Cinematograph film | ₹5,000 |
| Sound recording | ₹2,000 |
For a SaaS platform with multiple distinct software modules, each module that constitutes an independently created work may be filed as a separate application — providing granular protection across the product architecture.
Step 4 — Mandatory diary period
Upon receipt, the Copyright Office enters the application in a diary and issues a diary number. The application is then open for 30 days for objections from any person who claims to have an interest in the work. If no objection is filed within 30 days, the examiner proceeds to scrutinise the application. If an objection is filed, both parties are heard.
Step 5 — Examination and registration
The Copyright Office examines the application for completeness and consistency. If satisfied, the Registrar registers the copyright, makes an entry in the Register of Copyrights, and issues a Registration Certificate confirming the author’s name, title of the work, date of creation, and registration number.
The current processing time for straightforward software applications is approximately 1 to 3 months from submission, depending on the Copyright Office’s workload at the time of filing.
Registration of updates and new versions: Each substantially revised version of your software that involves significant original creative contribution qualifies as a new copyright work. Register major version releases — particularly where new features, new modules, or significant architectural changes have been made — as separate applications. This ensures your registration coverage keeps pace with your product development.
Key Takeaway: The software copyright registration procedure is straightforward, inexpensive (₹500 per work), and online. The 30-day diary period and examination process complete in 1 to 3 months. The deposit question is manageable through representative source code extracts. File early — before any dispute arises.
Enforcing Software Copyright in India: What Remedies Are Available?
What are the civil remedies for software copyright infringement?
Under Section 55 of the Copyright Act, 1957, the owner of a registered copyright in software may seek the following civil remedies from a court of competent jurisdiction:
Injunction — a court order immediately restraining the defendant from continuing to reproduce, distribute, or use the infringing software. Urgent interim injunctions under Order XXXIX Rules 1 and 2 of the Code of Civil Procedure, 1908 can be obtained ex parte (without the defendant being heard first) within 24 to 72 hours in appropriate cases, particularly where evidence of systematic copying is clear and irreparable harm is established.
Damages — compensation for the financial loss caused by the infringement, including lost profits, licence fees that would have been payable, and consequential harm to the copyright owner’s business.
Account of profits — requiring the infringer to disgorge the profits made from the infringing activity.
Delivery up — a court order requiring the defendant to surrender all infringing copies of the software for destruction.
What are the criminal penalties for software copyright infringement?
Software piracy in India is a criminal offence. Under Section 63 of the Copyright Act, 1957, knowingly infringing or abetting the infringement of copyright in a computer programme is punishable with:
- Minimum imprisonment of 7 days (no fine in lieu for computer programmes — unlike other copyright works where fines are an alternative)
- Maximum imprisonment of 3 years
- Fine ranging from ₹50,000 to ₹2 lakh
For second and subsequent offences, enhanced penalties apply. Criminal complaints can be filed with the Economic Offences Wing or Cybercrime units of the police, as software piracy increasingly occurs through digital channels.
How do you take down infringing software online?
For software distributed through app stores, GitHub repositories, cloud platforms, or social media, the enforcement pathway combines Indian law with platform-specific mechanisms:
GitHub and code repositories — file a DMCA takedown notice (GitHub accepts these from copyright holders globally, including Indian copyright owners). GitHub acts within 24 to 48 hours on clear infringement claims supported by a copyright registration certificate or clear evidence of ownership.
Google Play and Apple App Store — both platforms accept IP infringement reports with copyright certificate support for substantially copied applications.
Websites distributing pirated software — under Section 79 of the Information Technology Act, 2000 read with the IT (Intermediary Guidelines) Rules, 2021, intermediaries hosting infringing content must remove it within 36 hours upon receiving notice from the copyright owner. A notice citing your copyright registration certificate and the specific URL of the infringing content triggers this obligation.
Civil vs. criminal — which to pursue? For commercial-scale infringers — a competitor systematically copying your product — civil proceedings provide faster, more commercially meaningful relief (injunction + damages). For organised piracy rings, criminal complaints to the Cybercrime Investigation Cell at cybercrime.gov.in are the appropriate escalation, as criminal investigations have powers of search and seizure that civil proceedings do not.
Key Takeaway: Indian copyright law gives software owners a robust enforcement toolkit — civil injunctions achievable in 24 to 72 hours, criminal penalties up to 3 years imprisonment, and online takedown mechanisms under both the IT Act and platform-specific procedures. Registration amplifies every one of these remedies.
Practical Roadmap: Protecting Your Software’s Copyright From Day One
- Establish clear ownership through contracts — all developer contracts (employment and freelance) must contain explicit copyright assignment clauses. Do this before any development work begins.
- Register core modules with the Copyright Office — file Form XIV at copyright.gov.in for your most commercially significant software components. Fee: ₹500 per work.
- Conduct an open source audit — run a software composition analysis scan to identify all open source components and their licence obligations before your next funding round.
- Date-stamp your development — maintain version control records (Git commits with timestamps), design documents, and development correspondence as contemporaneous evidence of authorship and creation date.
- Add copyright notices to your code — include a standard notice in the header of every source file: “Copyright © [Year] [Company Name]. All rights reserved.” This is not legally required in India but supports ownership claims in foreign jurisdictions and platform enforcement procedures.
- Register new major versions — file a fresh copyright application each time you release a substantially revised version that involves significant original contribution.
- Monitor for infringement — set up Google Alerts for your product name, conduct periodic searches on app stores for competing applications with similar functionality, and scan code repositories for copies of your distinctive modules.
- File takedown notices promptly — when you identify infringement, file platform notices immediately. Delay in enforcement can be used to argue acquiescence.
- Consult IP counsel before open sourcing any component — releasing your code under an open source licence is a copyright decision with significant commercial consequences. Take legal advice before making any code public under any licence.
- Conduct an IP audit before fundraising or M&A — verify that your company owns the copyright in all components of your product, that all freelance assignments are in writing, and that all open source obligations are being met.
Conclusion: Your Code Is a Copyright Asset — Treat It as One
Every line of original source code your developers write is a copyright work the moment it is created. The Copyright Act, 1957 protects it automatically — but automatic protection without registration, without clear ownership documentation, and without active enforcement is protection in theory only.
Indian software companies that treat copyright as an afterthought consistently discover its importance at the worst possible moment: when a dispute arises, when an investor or acquirer asks for IP documentation, or when a freelancer asserts ownership over a critical component of their product. The companies that build durable software businesses treat copyright as infrastructure — established early, documented clearly, and maintained consistently.
At Unimarks Legal Solutions, we advise Indian startups, SaaS companies, IT service providers, app developers, and digital product teams on software copyright registration, developer agreement drafting, open source compliance, and copyright enforcement. If your software business needs an IP foundation that supports growth and investment, contact our team for a consultation.
Protect your code today → [INTERNAL LINK: Copyright Registration Services — Unimarks Legal Solutions]
About the Author
Advocate Suresh Kumar has a law practice specialising in Intellectual Property Rights, Commercial legal advisory, debt recovery, commercial litigation, and dispute resolution for domestic and international clients. He is enrolled with the Bar Council of Tamil Nadu and Puducherry and represents clients before all courts and forums in Chennai, Tamil Nadu. This article reflects his understanding of the current legal position and is intended solely for informational purposes.
Disclaimer
This article is published by Unimarks Legal for informational purposes only. It is not intended to constitute legal advice or to create an attorney-client relationship. The contents are based on Indian law as applicable at the time of writing and are subject to change. Readers should not act upon the information in this article without seeking independent legal counsel. Every legal situation is unique, and the application of law depends on specific facts and circumstances. Past results do not guarantee future outcomes. This publication is made in compliance with the Bar Council of India Rules, which prohibit advertising or solicitation by advocates. Any information received through this article should not be construed as legal advice.
For specific legal guidance on your matter, you may consult a qualified advocate in your jurisdiction.
