Software Copyright Registration India — Form XIV

Overview

Every line of code your team writes is already protected. Under Indian law, a computer programme is a literary work, and copyright in it arises the moment the code is written — no filing, no fee, no ceremony. Most software companies will never register a single work and will be perfectly fine.

Registration matters at the moments when proof matters: a funding round where investors diligence your IP chain, an acquisition where the buyer discounts anything undocumented, a piracy dispute where you need the court to presume you own what you say you own. Section 48 makes the Register of Copyrights prima facie evidence of ownership — the certificate short-circuits arguments that would otherwise consume months.

This page covers what software copyright actually protects (and what it does not), who owns the code in employment and contractor relationships, how open-source licensing fits in, the registration process with its source-code deposit rules, and how infringement is enforced.

What software copyright actually protects

Section 2(ffc) defines a computer programme as a set of instructions — in words, codes, schemes or any other form — that makes a computer perform a task or achieve a result. Section 2(o) then folds computer programmes into "literary work". The statute treats your codebase the way it treats a novel: as an original expression fixed in a tangible medium.

What is protected is the expression: the specific code as written, its structure and organisation, the literal text of the programme. Copying substantial portions of code — even with variable names changed — infringes, because the expression has been taken.

What is not protected is equally important:

• Ideas, algorithms and functionality. The idea of a ride-hailing app, the algorithm for route optimisation, the functionality of a dashboard — none of these is copyrightable. This is the idea-expression dichotomy, and it is absolute. Your competitor can build the same features; they cannot copy your code to do it.
• Programming languages and interfaces as such. (The global position after *Google v. Oracle* in the US is instructive, though not binding here.)
• Titles, names and short phrases. Your app's name is trademark territory.
• Facts and data. A database's structure may be protected as a compilation; the raw facts are not.

The practical consequence: copyright stops code theft, not competition. If your moat is the idea, you need patents or trade secrecy — discussed below.

Ownership — the question that decides acquisitions

More software deals have collapsed over code ownership than over code quality. Section 17 sets the defaults, and you must know them before you sign anything.

Employees — Section 17(c). A work made in the course of employment under a contract of service belongs to the employer, in the absence of an agreement to the contrary. Code your developers write on the job is the company's. This is the default every startup relies on — but "in the course of employment" has boundaries. Side projects built on personal time, on personal equipment, unrelated to the employer's business, are arguable. Good employment agreements define the scope explicitly: what counts as company IP, what happens to pre-existing IP, and what the employee must do on exit (assignment of anything missed, cooperation with registrations).

Contractors and freelancers — the gap. A contractor is not under a contract *of service*, so Section 17(c) does not apply. Without a written assignment, the freelancer owns the copyright in the code they delivered — even though you paid for it, even if your entire product runs on it. This is not a theoretical risk; it surfaces in every acquisition diligence where contractor-built modules lack assignment paperwork. Rule: no contractor writes a line without a signed agreement containing an express IP assignment, covering present and future works, all media, worldwide, with a waiver of moral-rights objections to the extent permissible.

Founders. Co-founders who write code before incorporation own it personally until they assign it to the company. The incorporation paperwork should include IP assignment from each founder — otherwise the company's core asset sits in individuals' names when investors arrive.

Government and public undertakings (Section 17(d)): works made under government direction or control belong to the government absent contrary agreement — relevant for govtech contracts.

Joint authorship applies to code as much as to art: where contributions are inseparable, all contributors are joint owners.

Open source — copyright's most misunderstood child

Open source is not the absence of copyright. It is copyright, deliberately licensed. Every open-source licence — MIT, Apache 2.0, GPL — begins with the licensor *owning* the copyright and granting permissions under conditions. No copyright, no licence; the code would simply be public domain.

The distinctions that matter commercially:

• Permissive licences (MIT, Apache 2.0, BSD): use the code in proprietary products with minimal obligations — typically just preserving the copyright notice. Low friction, which is why most commercial software stacks are built on them.
• Copyleft licences (GPL v2/v3): if you distribute a derivative work, you must release your source under the same licence. Incorporating GPL code into a proprietary product and distributing it triggers the disclosure obligation. This is the classic compliance landmine.
• Contributor Licence Agreements (CLAs): projects that accept outside contributions usually require contributors to assign or license their copyright to the project — without this, the project cannot relicense.

For Indian product companies, the audit discipline is simple: maintain a software bill of materials, know the licence of every dependency, and get legal review before shipping anything containing copyleft code. "We didn't know it was GPL" is not a defence; it is an admission.

Dual licensing — offering the same code under both an open-source licence and a paid commercial licence — is a legitimate business model built entirely on owning the copyright. You cannot dual-license code you do not own, which circles back to contractor assignments and CLAs.

Why register — the moments proof matters

Registration is optional. Here is when it stops being optional in practice:

• Fundraising and acquisition diligence. Investors and acquirers verify IP chains. A registration certificate for the core codebase, with clean founder and contractor assignments behind it, removes a diligence flag that otherwise gets priced into the deal.
• Litigation. Section 48's prima facie presumption means the court starts from your ownership. Against a piracy defendant, that head start is decisive.
• Licensing revenue. Registered works license cleanly; the certificate anchors royalty agreements and escrow arrangements.
• US enforcement. If you sell into the United States, note that US law requires timely registration with the US Copyright Office before you can claim statutory damages and attorney's fees there. Indian registration does not substitute for this — it is a separate, parallel step worth taking for flagship products.

What registration covers — and what needs separate filings

One Form XIV covers one work. For software, plan the boundaries:

• The programme itself (source code as literary work) — the core filing.
• Screen displays and UI — covered by the registration *if* the code generating them is submitted. Mere screenshots of an app's screens, without the underlying code, are not registrable on their own.
• Documentation and manuals — separate literary works, separate applications.
• Databases — registrable as compilations where the selection or arrangement is original.
• Each version? Major versions are commonly registered separately; minor iterations are not. There is no statutory rule — it is a judgment call about what you might need to prove.

The registration process

Step 1 — Identify the work and the applicant

Define exactly what is being registered (which programme, which version) and who applies — the company as owner, or the author. If the applicant is not the author, the chain of title (employment, assignment deeds) must support the claim.

Step 2 — Assemble the chain of title

Before filing, confirm ownership paperwork exists: employment agreements with IP clauses, contractor assignment deeds, founder IP assignments. Filing in the company's name without the underlying assignments creates a certificate built on sand.

Step 3 — Prepare the source-code extract

Under Rule 70(5) as relaxed in 2021: submit the first 10 and last 10 pages of source code — or the entire code if it is under 20 pages — with no redacted or blocked-out portions. The relaxation exists precisely because companies feared exposing trade secrets; the 10+10 format is the compromise. Both source code and object code are referenced in the rule's framework.

Step 4 — Create your account on copyright.gov.in

Register on the Copyright Office e-filing portal. All correspondence, objection notices and the eventual certificate flow through this account — use an official company email, not a personal one.

Step 5 — Fill Form XIV online

Form XIV is the application for registration under Rule 70 of the Copyright Rules, 2013. Select the literary-work category (computer programme), and complete the title, language, author and applicant particulars, and dates of creation and publication. The form, the Statement of Particulars and the Statement of Further Particulars must be signed by the applicant personally — Rule 70(3) does not allow an attorney to sign these.

Step 6 — Attach documents and pay

Upload the source-code extract, applicant identity/address proof, the assignment chain documents, and a power of attorney (on stamp paper, duly accepted) if filing through counsel. Pay the ₹500 fee per work and collect the diary number.

Step 7 — The 30-day objection window

The application lies open for 30 days for objections. Software applications are rarely objected to — disputes here usually involve ex-employees or co-founders contesting ownership, which is exactly why Step 2 matters. If an objection arrives, the Registrar holds a hearing.

Step 8 — Examination and certificate

The Registrar examines the application and, if satisfied, enters the work in the Register of Copyrights. Uncontested software applications typically conclude in 6 to 12 months.

Fees and timelines

Copyright vs patent vs trade secret — choosing the shield

Most serious software companies use all three: copyright for the codebase, patents for genuinely novel technical methods (within India's computer-related-invention guidelines), and trade secrecy for algorithms and data that never leave the building. They are complements, not alternatives.

Infringement and enforcement

Software infringement in India typically looks like: a former employee or contractor reusing code at a new venture, a client refusing to pay and continuing to use the software, or outright piracy of a licensed product.

Civil remedies (Section 55): injunctions, damages or account of profits, delivery-up of infringing copies. The Delhi High Court routinely grants John Doe orders (against unknown defendants) in software piracy cases — a practitioner tool worth knowing, since pirated software is often distributed by unidentified parties.

Criminal remedies (Sections 63, 63A): knowing infringement carries 6 months to 3 years imprisonment plus a fine, enhanced on repeat conviction. Commercial-scale piracy is pursued criminally with some regularity.

Moral rights (Section 57) apply to software authors too — the right of paternity and against prejudicial distortion. In practice this surfaces in open-source attribution disputes.

Practical enforcement ladder: preserve evidence (code comparisons, access logs, distribution records) → cease-and-desist → takedown with platforms/hosts → civil suit for injunction and damages → criminal complaint for wilful commercial piracy. Start preserving evidence before you send the first notice.

The SaaS and cloud wrinkle

When software is delivered as a service rather than distributed as copies, the traditional infringement model strains: nobody "copied" your code, they just used your service. Copyright still protects the underlying code against extraction and reproduction, but SaaS businesses should layer their protection: strong Terms of Service prohibiting reverse engineering and scraping, API access controls, and trade-secret discipline over the code that never ships. Copyright is one wall of the fortress, not the whole fortress.

How ComplyKart helps — and what we do not do

What we do: IP chain-of-title audits (employment agreements, contractor assignments, founder IP); Form XIV drafting and e-filing with correct source-code extracts; objection handling and hearing representation; software assignment and licence agreements; open-source licence compliance reviews and SBOM discipline; dual-licensing structures; escrow arrangements; infringement notices, takedowns and litigation support; parallel US registration coordination through foreign counsel.

What we do not do: we do not file registrations where the ownership chain is broken — we fix the chain first; we do not advise redacting source code in the filing (the rules prohibit it); we do not guarantee timelines — the Registrar decides; we do not treat a GitHub repository as proof of ownership in a dispute without more.

Verification register

Sources

• The Copyright Act, 1957 (as amended)
• The Copyright Rules, 2013 (as amended 2021)
• copyright.gov.in — e-filing portal and fee schedule
• Press Information Bureau Release ID 1710417 (Copyright Rules amendments)
• 17 U.S.C. §412 (US registration prerequisite for statutory damages)