Copyright for Software and Code: What It Protects and Why Registration Matters

Software is one of the few assets where the thing you sell and the thing you own are the same file. The code is the product. Which is why, when a developer leaves with a copy of your repository or a competitor launches something suspiciously familiar, the first question a lawyer asks is: what can you prove you own, and when?

In India, software is protected as a literary work under the Copyright Act, 1957. That protection is automatic. But automatic protection and provable protection are two very different things — and the gap between them is where most software disputes are won or lost.

What copyright actually protects in software

Copyright protects the expression of your program, not the idea behind it. In practice that means:

• Source code and object code
• The particular structure, sequence and organisation of the program
• Documentation, manuals and technical specifications
• Original graphical elements — icons, illustrations, custom UI artwork
• Databases, where the selection or arrangement is original

What it does not protect is the functionality. If a competitor writes their own code, from scratch, that does the same thing your product does, copyright generally will not help you. That is a hard thing for founders to hear, and it is the single most common misunderstanding we correct in first meetings.

If the technical method itself is the advantage, you are looking at a different tool — either patent protection where the invention qualifies, or trade secret protection where it does not and secrecy is realistic.

Why registration matters when protection is already automatic

Copyright exists the moment the code is written. So why file at all?

Because a dispute is an evidence problem. Under Section 48 of the Copyright Act, the entries in the Register of Copyrights are prima facie evidence of the particulars recorded in them. A registration certificate with a dated entry does three things that a folder of commits on someone’s laptop does not:

• It shifts the practical burden. The other side now has to explain why your dated registration is wrong.
• It removes a fight about authorship before the real fight begins.
• It gives you something to put in front of a judge, a marketplace, or an acquirer in a week rather than a month.

For most software businesses, the trigger is not litigation. It is due diligence. Investors and acquirers ask who owns the code, and “we wrote it ourselves” is an answer that slows deals down.

The ownership problem nobody checks until it is expensive

The most common software IP problem we see is not copying by strangers. It is unclear ownership inside the company.

The general position is straightforward: work created by an employee in the course of employment usually belongs to the employer. Work created by a freelancer, an agency, or a co-founder before the company existed usually does not — unless there is a written assignment.

That means the company shipping the product may not own parts of it. We have seen this surface at the worst possible moment: during a funding round, during an acquisition, and once in the middle of an infringement suit, when the defendant’s lawyers asked a very good question about who actually wrote the module in dispute.

Before you register anything, fix this. Every developer, contractor and founder who has touched the codebase should have signed an assignment in favour of the company.

What the filing involves

The application for a computer programme is filed on the Copyright Office portal, in the literary works category, with the standard Form XIV. Along with the applicant and author details, you submit the work itself — in practice, the portions of the source code required by the Office rather than the entire repository.

Step	What happens	Typical time
Preparation	Category, authorship, NOCs and code extract prepared	1–3 days
Filing	Application filed online, diary number issued	Same day
Waiting period	Mandatory objection window	30 days
Examination	Registrar reviews; discrepancies answered	A few months
Certificate	Entry made in the Register of Copyrights	10–12 months overall

Founders often worry about disclosure. The filing requirement is limited, and where confidentiality is a genuine concern we advise on exactly what has to go in and what can be withheld.

Open-source components

Almost every commercial product today includes open-source libraries. Registration covers your original code — not the third-party components you have imported.

Keep a dependency list and know which licences you are relying on. Some open-source licences carry obligations that affect how you distribute your product, and those obligations do not disappear because nobody read them. This is worth a review before a release, not after.

When code is copied: what actually happens next

If you believe your code has been copied, the sequence is usually this:

• Preserve evidence. Repository history, timestamps, build artefacts, employment records, and the infringing product as it exists today.
• Compare. Similar output is not evidence. Similar structure, identical comments, the same variable names, or a bug reproduced identically — that is evidence.
• Send a notice. A well-drafted cease-and-desist resolves a surprising number of these matters.
• Escalate if needed. Civil action for an injunction and damages, and criminal complaints in appropriate cases.

Registration is what makes step three credible and step four fast.

What it costs and how long it takes

Government fees for copyright are modest and fixed by the type of work. For a computer programme, filed as a literary work, the fee sits at the lower end of the scale. Professional fees depend on how much preparation the application needs — a single product with clean ownership is straightforward; a portfolio built over five years by a rotating set of contractors is not.

The realistic timeline from filing to certificate is ten to twelve months, which includes the statutory thirty-day objection window and examination. That timeline is one more reason not to wait for a dispute before filing: the certificate you need in March is one you should have applied for last year.

Copyright, patent or trade secret for the same product

Software rarely sits inside a single category of protection. A typical product has three layers, and each is protected differently.

• The code itself — copyright, automatic on creation, strengthened by registration
• The technical method, where it solves a technical problem — potentially a patent, subject to the exclusions that apply to computer programmes as such
• The parts you never publish — algorithms, pricing logic, internal data structures — trade secrets, protected only as long as you actually keep them confidential

Deciding between a patent and secrecy is a commercial decision as much as a legal one. A patent requires publication; a trade secret requires discipline. We generally map this out once, early, and revisit it at each major release.

A checklist before you file

• Every contributor — employee, contractor, agency, co-founder — has signed a written assignment to the company
• The version being registered is tagged and archived, with a date you can prove
• Open-source dependencies are listed with their licences
• Confidential elements that should not be disclosed are identified in advance
• The person named as author in the application is the person the records support

Common questions

Do I need a separate registration for every version? No. Register a stable, commercially significant version. Ordinary updates do not need fresh filings; a substantially new product does.

Does registration in India protect my software abroad? India is a member of the Berne Convention, so works protected here enjoy protection in most member countries without separate formalities. An Indian registration is still useful evidence when enforcing abroad.

My developer says the code is theirs — is it? It depends entirely on the contract. Without a written assignment, a contractor may well retain rights in what they wrote, which is why this is worth fixing before it becomes a negotiation.

The bottom line

If software is the business, register it — and fix ownership first. Registration is inexpensive relative to what it protects, and it converts an invisible right into a document you can actually use.

If you are not sure what needs registering, what your contractors’ agreements say, or whether a patent is the better route for part of your product, talk to our team. It is a short conversation, and it is usually the cheapest hour you will spend on your IP.