Copyright vs Trade Secret for Software: Which Protects Your Code Better?

For software source code in India, copyright and trade secret protection do different jobs. Copyright protects the written expression of the code against copying and arises automatically, while trade secret protection guards confidential information, including unreleased code and underlying logic, only for as long as it stays secret. Most software founders in Jaipur and elsewhere end up relying on both, supported by contracts.

Key Takeaways

• Copyright covers expression, not ideas: a computer programme is a literary work under the Copyright Act, 1957, so the code as written is protected, but the algorithm or logic behind it is not.
• Trade secret has no statute of its own in India: protection rests on contracts, confidentiality clauses and the law of breach of confidence, and it lasts only while the information stays confidential.
• Disclosure is the real trade-off: registering copyright involves depositing a copy of the work, and sharing code with developers, investors or customers can weaken secrecy if no written controls exist.
• The usual answer is layering: copyright on the codebase, trade secret and contract controls on the unreleased and most sensitive parts, and trade marks on the product name.

Copyright vs Trade Secret for Software at a Glance

This note is general information for founders weighing how to protect a codebase. It is not legal advice, and every point below depends on facts that differ from one business to another.

What Does Copyright Protect in Software Under the Copyright Act, 1957?

Under the Copyright Act, 1957, a computer programme is a literary work, so original source code and object code are protected against unauthorised copying from the moment they are written down. Copyright covers the expression in the code, not the underlying idea, algorithm or logic, and registration is optional.

IP India's FAQs confirm that software can be registered as a literary work, because section 2(o) of the Act includes computer programmes, tables and compilations, including computer databases. The USPTO's India IPR toolkit makes the same point in plain terms: literary works include computer programs, and the work must be original and fixed in a tangible form.

Originality and fixation

Two conditions matter. The code must originate with its author rather than being copied, and it must exist in a fixed form, which a committed file in a repository satisfies. Skill and labour in writing the code are what count. Novelty in the patent sense is not required.

What copyright gives the owner

The owner holds exclusive rights over the work, including the rights to reproduce it, adapt it and issue copies to the public. For a literary work with an identified author, the term is the author's lifetime plus sixty years under section 22 of the Act.

In practice, the term matters far less than the question of who the author is. Software ages quickly, and a codebase may be rewritten long before any term expires.

Who owns the code in the first place

This is where founders most often run into trouble. As a general rule, an employer owns copyright in work created by an employee in the course of employment, unless the contract says otherwise. An outside developer or agency is different. Without a written assignment, the author usually keeps the copyright, even if the founder paid for the work.

An assignment must be in writing and should state its scope, duration and territory. If those are left silent, the Act applies default rules that may be narrower than the founder assumes. Our own note on copyright protection for software and digital works in India covers ownership and registration in more detail.

What copyright does not stop

Copyright does not give a monopoly over a method. A competitor who studies what your product does and writes fresh code to achieve the same result has not necessarily copied your expression. Whether a particular rewrite crosses the line is a question of fact, usually decided by comparing the two codebases and the evidence of access.

That gap is why the protection of logic, data structures and unreleased features is usually pushed towards trade secret and contract rather than copyright.

Registration: optional but useful

Copyright subsists without registration. Registration with the Copyright Office produces an official record of the claim and is commonly used as evidence of ownership in a dispute. The Copyright Office's practice and procedure manual sets out registration prerequisites for literary works, and the iStart Rajasthan portal notes that, after an application is examined, an applicant is ordinarily given 45 days to resolve any discrepancy found.

What Does Trade Secret Protection Require in India?

India has no separate trade secret statute, so protection comes from contracts such as NDAs and employment confidentiality clauses, backed by courts' willingness to restrain a breach of confidence. In practice the information must be genuinely confidential, valuable because it is not public, and guarded by reasonable steps.

WIPO's India country sheet states that there is no separate and exclusive statute to protect undisclosed information, and that trade secrets and confidential information can be protected to a large extent by contracts, such as non-disclosure agreements and confidentiality clauses in employment agreements. Indian courts have also granted relief on general principles of breach of confidence, even where no contract covers the situation.

The practical elements of a trade secret

Because there is no statutory checklist, a founder should be able to show three things if the matter ever reaches a court:

• The information is not public. It is not in a published repository, a marketing deck, a conference talk or a patent specification.
• It has value because it is secret. A ranking model, pricing logic, a data pipeline or an unreleased feature set are typical examples.
• Reasonable steps were taken to keep it secret. Written confidentiality terms, restricted repository access, logging and a documented exit process are the usual evidence.

Reasonable steps are judged on the facts. A one-line confidentiality clause in a template contract, with no access controls at all, is a weak record.

What a trade secret does not protect against

Trade secret law does not stop someone who arrives at the same solution independently. It also does not give relief against a person who obtained the information lawfully and without any duty of confidence. Whether reverse engineering of a distributed product is permitted depends largely on the licence terms, which is why customer-facing terms matter.

Once the secret becomes public, even through someone else's leak, the protection is generally gone for everyone.

Contracts, employees and Section 27

Section 27 of the Indian Contract Act, 1872 makes void any agreement that restrains a person from exercising a lawful profession, trade or business, to that extent. Indian courts apply it strictly, and post-termination non-compete clauses in employment contracts are generally treated as void. A confidentiality obligation is a different thing from a non-compete, but the drafting must stay on the right side of that line.

A narrow definition of confidential information, a stated purpose for use and a clear return-or-delete obligation are far more likely to hold than a broad ban on working in the same field. Our employee exit checklist for protecting trade secrets deals with the practical steps when a developer leaves.

Side-by-Side Comparison

The table below puts the two regimes next to each other on the points that usually drive a founder's choice for a codebase.

Why neither is the same as a patent

Founders sometimes ask whether a patent solves the gap. In India, section 3(k) of the Patents Act, 1970 excludes a computer programme per se, a mathematical or business method, and algorithms from patentability, so software claims need a technical effect framing and careful drafting.

A patent application also requires public disclosure of the invention, which is the opposite of secrecy. Our note on patent protection for software startups in India looks at when that route is worth considering.

Disclosure Trade-Offs When Filing or Sharing Source Code

Every form of protection asks the founder to reveal something, and every disclosure to a third party is a decision about how much secrecy to give up. The trade-off differs for each route.

Copyright registration and the deposit

Registering copyright for software involves giving the Copyright Office a copy of the work. The Copyright Rules, 2013 allow a partial deposit for software, but the exact portions allowed, and any provision for withholding sensitive sections, should be checked against the current rules and the Office's practice manual before filing.

WIPO's guide notes that certain jurisdictions do not permit an owner to assert both trade secret and copyright, especially if the copyrighted software discloses a majority of the source code. How that tension would be treated for an Indian deposit is not a point a founder should assume is settled. The cautious course is to deposit only what the rules require and keep the most valuable modules out of any public record.

Sharing with developers, investors and customers

Most real leaks of confidential code are not break-ins. They happen through ordinary business sharing. Each of these needs a written term before the code leaves your control:

• Outsourced developers: an assignment of copyright plus a confidentiality clause that survives the end of the contract.
• Investors and acquirers: a signed NDA before any repository access, with a view-only data room rather than a code export.
• Customers: licence terms that prohibit copying, decompiling and sharing, with object code delivered rather than source code.
• Source code escrow: where a customer demands access in case the vendor fails, a neutral escrow arrangement with defined release conditions.

Patent filing as the extreme case

A patent application is published, so anything described in it is public. If a particular piece of logic may be kept as a trade secret, it should be decided before filing whether it is going into the specification at all. A patent cannot be used to protect something that is then also kept confidential.

How Do Founders Combine Copyright and Trade Secret Protection?

Founders usually layer the two: copyright covers the codebase as written, while trade secret and contract controls cover unreleased code, algorithms and data that must stay confidential. Written assignments from every contributor, NDAs and access controls hold the layers together, and trade marks protect the product name.

The WIPO guide itself points out that copyright is another form of protection available to code and algorithms alongside trade secret, which is why a layered approach is common. Commentary on Indian technology businesses describes the same practical stack: copyright in the code, contract and confidentiality for what is never disclosed, trade marks for the product and platform brand, and design registration where an interface qualifies.

A hypothetical worked example

Consider a hypothetical Jaipur startup that sells an inventory-planning SaaS product. It has a web front end, a back end, a forecasting model, an unreleased feature branch and a brand name. A sensible allocation of protection might look like this:

No numbers are attached because the allocation turns on the startup's facts, not on a formula.

Common scenarios where both regimes apply

• SaaS delivered over the web: customers never receive the code, so trade secret protection does most of the work for the back end, with copyright as the fallback if someone copies the code.
• On-premise or distributed software: the code reaches customer machines, so copyright and licence terms matter more, and any secret logic should stay on the vendor's servers.
• Outsourced development: the main risk is ownership, not secrecy, so the assignment comes first.
• Open source components: licence conditions can require publishing source code, which can undo secrecy for the modified part. This should be checked before any such component enters the product.
• Developer departures: a documented exit process is the evidence that reasonable steps were taken.

A Practical Checklist for a Software Startup

This sequence suits an early-stage company that has code in a repository and several contributors. It is a general outline, not advice on any particular business.

1. List what you have. Separate the codebase, the confidential logic, the data, the documentation and the brand.
2. Trace authorship. For each contributor, find the signed document that sets out who owns the work. Where none exists, a written assignment should be put in place.
3. Sign confidentiality terms. Employees, contractors, advisers and prospective investors should be covered before they see the confidential parts.
4. Control access. Use role-based repository permissions, multi-factor login and access logs, and keep records of who had what.
5. Mark and licence. Add copyright notices to the code and documents and issue customers a licence that bars copying, decompiling and onward sharing.
6. Review open source use. Keep a list of third-party components and their licence conditions.
7. Decide on registration. Consider copyright registration for the core product where ownership evidence is valuable, bearing the deposit point above in mind.
8. Run an exit process. On every departure, revoke access, collect devices and remind the person of continuing confidentiality duties.

The passing standard for step 2 is simple: if a stranger asked who owns the payment module, you could produce a document. If you cannot, treat that gap as the first thing to fix, ahead of everything else on the list.

Which Should You Rely On? A Decision Rule

Rely on copyright for everything that is shipped or visible, and on trade secret for anything whose value depends on staying hidden. If the logic would be obvious to a competitor from using your product, secrecy adds little, and copyright with strong licence terms is the more realistic protection.

A workable rule has three parts. Ask first whether the item reaches the customer. If it does, plan on copyright and contract, because secrecy will not hold. Ask second whether the item would hurt you if a competitor knew it. If so, keep it off customer devices, out of public filings and behind written controls. Ask third whether you own it. If ownership is unclear, fix that before spending anything on either regime.

A few points remain open. How courts will weigh a partial copyright deposit against a later secrecy claim, and how far an Indian court will go in restraining a departed developer who knew the system, depend on facts and are not predictable from the general rules. Founders with a specific codebase or a specific dispute should obtain independent legal advice on those facts.

Frequently Asked Questions

Can I register source code as a trade secret?

No. There is no registry for trade secrets in India. The protection comes from keeping the information confidential and documenting that effort through contracts and access controls. Nothing is filed with a government office, and the right ends if the information becomes public through any route.

Does copyright stop a competitor from rewriting my software?

Not by itself. Copyright prevents copying of the expression in your code, not the idea or function behind it. A competitor who writes new code independently to achieve a similar result may not infringe. Evidence of access and similarity in the code itself usually decides such disputes.

Is an NDA enough to protect my source code?

An NDA is necessary but rarely enough. It binds only the people who sign it, and it helps in court only if the information was really kept confidential. It works best alongside access controls, assignment of copyright, exit procedures and a narrow, clearly drafted definition of confidential information.

Can I use copyright and trade secret protection together?

Yes, and most software businesses do. Copyright covers the code as written, while trade secret covers confidential logic and unreleased material. The care point is disclosure: depositing code for registration or publishing it under an open licence can affect what remains secret, so each step should be chosen deliberately.

This content is published for general information only. It is not legal advice, an advertisement, or a solicitation of work, and reading it does not create an advocate-client relationship. In keeping with the Bar Council of India Rules, Riva Legal Associates does not solicit work or advertise.