Why a Software Fight Feels So One-Sided
You bought 50 user licences for the accounting software your company runs. The renewal notice arrives, the price has jumped 40 percent, and somewhere on page 14 of the original agreement is a line saying the vendor can change pricing "from time to time". Or you are a small design studio. The vendor sends a stiff email claiming you have installed the software on more machines than you paid for, and demands a six-figure "true-up". Or the worst version — your access is suddenly switched off and a year of client files sits behind a login screen you cannot open.
Software disputes feel one-sided because the vendor wrote the agreement, the vendor controls the licence key, and the vendor often controls the data too. They are not, however, one-sided in law. Software in India is treated as a kind of book. The same Copyright Act that protects a novelist also protects a coder, and it gives the paying user a small but real set of rights that the vendor cannot completely write away. Knowing where the law ends and the contract begins is the difference between paying a panicked settlement and paying what is actually due.
Software Is a Book, Legally Speaking
The Copyright Act, 1957, defines a "literary work" in Section 2(o) to include computer programmes, tables and compilations including computer literary databases. That is the foundation of every software dispute in this country. Section 14 then sets out the bundle of exclusive rights that flow from copyright — for a programme, the owner alone has the right to reproduce it in any material form, store it on any medium, issue copies to the public, sell or commercially rent it, and to make adaptations and translations of it.
What this means in plain language: when you "buy" software, you are not buying the programme. You are buying a copy plus a permission slip. As the Delhi High Court said in Sap Aktiengesellschaft v Sadiq Pasha while dealing with pirated copies of SAP R/3, the buyer of a CD or download is the owner of that copy but not the owner of the copyright in the work stored on it.
That distinction is the centre of most disputes. A vendor saying "you cannot use my software except as I allow" is not bullying — it is the statute. A user replying "but I paid you fair money" is also right — and the law has tools for both sides.
Your EULA Is a Contract — Not the Final Word
The End User Licence Agreement, the click-wrap, the master services agreement on letterhead — all of these are governed by Section 30 of the Copyright Act and the Indian Contract Act, 1872, working together. Section 30 says a copyright owner may grant any interest in his copyright by licence in writing signed by him or his authorised agent. The licence has to specify, among other things, the work, the duration, the rights granted, the territorial extent, the royalty payable and the terms of revision, extension and termination.
So the basic floor is set by statute: every legitimate software licence is a written grant. The terms inside it then have to satisfy ordinary contract rules. Free consent, lawful object, certainty, no fraud or undue influence. A click-wrap EULA accepted by clicking "I Agree" is treated as a contract in India today; courts have repeatedly enforced them. But terms that are wildly oppressive, hidden, or inserted without notice can be challenged on the grounds available under the Contract Act — particularly when the user is a consumer and the bargaining power is uneven.
The practical takeaway is unromantic but important. Read the licence before you click. Once you click, the terms bind you, subject only to whatever the law refuses to enforce.
The Real Fights: Seats, Audits and Sudden Termination
Most software disputes that walk into a lawyer's office are some flavour of these:
Scope of use
Per-user, per-device, per-seat, named-user, concurrent-user — every model defines a different counting method. Confusion between "we have 50 employees" and "we paid for 50 named-user licences but rotate them through 80 employees" is a classic over-deployment dispute. The vendor claims under-payment; the customer says they followed common sense. The contract decides who is right.
Territory and entity
Was the licence granted to one company or to the whole group? Can the Indian subsidiary use software bought by the holding company in Singapore? If the agreement does not say "and its affiliates", the answer is usually no.
Term, renewal and termination
Auto-renewal traps catch many small businesses. A licence might quietly roll over for another 12 months unless cancelled 60 days before expiry. Termination for breach should ordinarily come with a written notice and a cure period. A vendor who terminates without following its own contract is in breach itself.
Audit clauses
Most enterprise licences carry an audit right — the vendor can verify how many copies you are running. Reasonable audit clauses require advance written notice, conduct during business hours, a confidentiality obligation, and reimbursement only if material under-licensing is found. An aggressive audit conducted without these guardrails can be pushed back.
Post-termination data and source-code escrow
Where do your records go after the licence ends? A well-drafted agreement gives a clear export window. For mission-critical software, a source-code escrow clause — code deposited with a neutral agent, released to the customer if the vendor goes bankrupt or stops supporting the product — protects against the vendor disappearing.
IP indemnity
If a third party sues you claiming the software infringes their copyright or patent, the vendor should indemnify you. This is the user's protection against being dragged into someone else's IP fight.
What the Statute Quietly Gives the User
The most under-used part of Indian software law is the cluster of small permitted acts in Section 52 of the Copyright Act. These are statutory rights given to the lawful possessor of a copy of a computer programme that no EULA can fully take away.
Backup copies. Section 52(1)(aa) permits the lawful possessor of a copy of a computer programme to make copies or adaptations from such copy in order to use the programme for the purpose for which it was supplied — and explicitly to make back-up copies purely as a temporary protection against loss, destruction or damage. If the vendor's clause says you cannot make any copy at all, that clause is in tension with the statute.
Interoperability and reverse engineering. Section 52(1)(ab) allows acts necessary to obtain information essential to the interoperability of an independently created programme with another programme, where that information is not otherwise readily available. Section 52(1)(ac) allows observation, study or testing of how the programme works in order to understand the ideas and principles underlying it, while you are using it for its intended purpose. These are narrow gates — they do not authorise wholesale copying — but they do let you build connectors and plug-ins.
Personal non-commercial use. Section 52(1)(ad) permits making copies or adaptations from a personally and legally obtained copy for non-commercial personal use. This protects ordinary users tinkering with their own machines.
Together with normal contract law, these provisions give a paying user real ground to stand on. A vendor cannot, for instance, treat the making of a single backup as if it were piracy.
What Should I Actually Do Now?
If you are in the middle of a software licence fight, work through this list before you write a cheque or fire off an angry email.
- Pull out the licence. The actual signed document — not a sales brochure, not a forum post. If the agreement is online, save a PDF copy with the date.
- Map your usage. List the actual deployments — number of users, number of devices, locations, environments. Compare against what you paid for.
- Read the four hot clauses. Scope, territory, audit, termination. These are where most disputes live. Mark them up.
- Preserve email trails. Quotation, purchase order, invoice, vendor confirmations of seat counts, support tickets. They tell the real story of what was promised.
- Reply, do not ignore. If a vendor sends an audit notice or a cease-and-desist, respond within the deadline. Silence is treated as acceptance of their version.
- Demand the protocol. For an audit, ask for the auditor's identity, the scope, the methodology, the confidentiality undertaking and the dispute mechanism in writing — before letting anyone connect to your systems.
- Negotiate before litigating. A genuine over-use is usually settled by a "true-up" payment. Most vendors prefer a paid customer to a court fight. Trademark and IP-related disputes often resolve faster at the negotiating table than in court.
- Protect the data first. If termination looks likely, export your records, take database backups, and download invoices while you still have access. Do this even before sending a legal reply.
- Take qualified advice early. Once the vendor is in litigation mode, what you said in the first reply email becomes evidence. A short consultation at the start is cheaper than a long argument later.
If your business is staring at a steep audit demand or a sudden cut-off and you are not sure whether to fight or settle, the team at Pinaka Legal in Delhi handles exactly these situations regularly. A short, paid first consultation usually clarifies whether the vendor's claim is solid or inflated.
Pay for the Software, Keep Your Sanity
Software licensing is not a fight between a giant and a citizen. It is a contract between two commercial parties, sitting on top of a Copyright Act that protects creators but also gives users a small statutory shield. Pirate copies are indefensible — Indian courts have not hesitated to award damages and injunctions in cases like the SAP one cited above. But a paying user, with a signed licence and a clean compliance record, has a strong position too. Read the agreement, count your seats honestly, save your data and respond to notices on time. Most disputes deflate the moment the user shows up prepared.
Frequently Asked Questions
Is a click-wrap EULA legally binding in India?
Yes, generally. A click-wrap EULA is treated as a contract once you click accept and pay. It must still satisfy normal contract rules — fair terms, no fraud, lawful object. Wildly one-sided clauses can be challenged on unconscionability, but the safer path is to read before clicking. The Copyright Act protects the vendor; the Contract Act protects you. Both apply at the same time.
Can the vendor cut off my software without notice?
It depends on what your licence says. Most licences allow termination only on a specified breach with a cure period. If the vendor switches off access without following its own contract, that is a breach by the vendor — you can claim damages and, where the contract permits, restore access. A sudden cut-off that destroys your business operations is rarely defensible.
Am I allowed to make a backup of my paid software?
Yes. Section 52(1)(aa) of the Copyright Act allows the lawful possessor of a copy of a computer programme to make backup copies purely as a temporary protection against loss, damage or destruction. The vendor's EULA cannot completely override this fair-use right granted by the statute itself.
What is a software audit clause and can the vendor really come into my office?
An audit clause lets the vendor verify that you are using only what you paid for. The audit usually requires advance written notice, conduct during business hours, and a confidentiality undertaking. The vendor cannot barge in. If your licence has no audit clause, the vendor has no contractual right to inspect your systems.
My subscription ended. Can I still access my old data?
Your data belongs to you, not the vendor. A reasonable post-termination clause should give you a window — often 30 to 90 days — to download or export your records. If your contract is silent, you can still demand return of your own data. Refusal can amount to wrongful retention. Before signing, always insist on a clear data-export and transition clause.
Can I reverse-engineer software to make my own product work with it?
In a limited way, yes. Section 52(1)(ab) permits acts necessary to obtain information essential for the interoperability of an independently created computer programme with another, provided the information is not otherwise readily available. This is not a free pass to copy code. It is a narrow exception aimed at making products talk to each other.
The vendor sent me a legal notice claiming over-deployment. What now?
Do not ignore it and do not panic. Pull out your licence agreement, your purchase orders and your deployment records. Compare paid seats against actual installations. If there is a genuine over-use, negotiate true-up fees. If the claim is inflated, reply through a lawyer. Courts dislike inflated demands made without proper audit procedure.
Does buying a CD or downloading software make me the owner of the software?
No. You own the physical media or the downloaded file, but the copyright stays with the vendor. You only get the limited rights given by the licence — installing, running, possibly making a backup. The Copyright Act is clear that buying a copy is not the same as buying the work.
For more articles on Indian law, visit the Pinaka Legal Blog. For queries, call +91 8595704798 or email info@pinakalegal.com.