Indemnity vs Limitation of Liability Under Indian Law: Why the Cap Clause Matters More

Damages: the default machinery everyone forgets

Start with what happens if a contract says nothing. Under Section 73 of the Indian Contract Act, 1872, a party breaking a contract must compensate for loss that arose naturally from the breach or that both parties contemplated when contracting, and expressly not for remote and indirect loss. The injured party must also mitigate. Section 74 handles agreed sums, liquidated damages, allowing only reasonable compensation not exceeding the stipulated amount, with courts empowered to trim penalties. So Indian law already gives every contract a compensation engine with built in speed limits: causation, contemplation, remoteness, mitigation. Indemnities and caps are modifications to this engine, one widening the intake, the other narrowing the exhaust.

Indemnity: the widener

An indemnity, under Section 124, is a promise to save the other party from loss caused by defined events. Its power lies in what it does not require. A damages claim needs a breach; an indemnity needs only its trigger. If a vendor indemnifies a customer against third party claims alleging IP infringement, the customer can call on it even though the vendor broke no promise, the moment such a claim arrives. Well drafted indemnities can also reach losses that Section 73’s remoteness rules might exclude, cover defence costs as they are incurred rather than after trial, and, on the strength of long standing Indian case law, be enforced when liability becomes absolute rather than only after the indemnified party has actually paid. That is why the drafting battle over indemnities is a battle about triggers and scope. Losses arising out of or in connection with this agreement is an indemnity for everything, effectively replacing the Contract Act’s careful machinery with an open pipe. Disciplined indemnities name their events: third party IP claims, breach of confidentiality, death or property damage from negligence, fraud, violation of law, and increasingly, data breaches, a category the DPDPA’s penalty regime has made vivid. They also come with procedure: prompt notice, the indemnifier’s right to control the defence, no settlement without consent, and mitigation preserved.

Limitation of liability: the narrower

The limitation clause runs the opposite direction: whatever the theory of claim, breach, indemnity, or otherwise, total liability shall not exceed an agreed ceiling, commonly the fees paid in the preceding twelve months, and neither party is liable for indirect or consequential loss, lost profits, or lost data. Indian courts have generally respected such allocations between commercial parties as expressions of freedom of contract, with boundaries: a clause cannot launder fraud, and drafting that strips a party of all statutory remedy has been struck down as opposed to public policy under Section 23, the Delhi High Court’s Simplex Concrete line of reasoning being the standard citation. Between sophisticated businesses negotiating at arm’s length, though, the cap is the law of the deal, and courts enforce it.

The fight between them, and why the cap wins

Now put the two clauses in one contract and ask the only question that matters in a crisis: is the indemnity inside the cap or outside it? If indemnity claims are subject to the cap, then however broad the indemnity’s language, your worst case is the cap. If the indemnity is carved out of the cap, uncapped, then the modest twelve months of fees ceiling on page nineteen is decoration, because real disputes arrive dressed as indemnity claims. This is why experienced counsel read the carve out list before anything else, and why we ranked the cap first in our tour of the twelve highest liability MSA clauses. Some carve outs are legitimate and market standard: fraud and wilful misconduct, typically uncapped everywhere; third party IP infringement and confidentiality breach, often uncapped or subject to a separate higher super cap; and increasingly data protection failures, where a negotiated super cap, two or three times fees, is the emerging midpoint. What should never happen silently is the general indemnity sitting outside the cap, which converts a fee for service contract into an insurance policy you never priced. Run the arithmetic that makes this concrete. A SaaS vendor earns twelve lakh rupees a year from a customer, with a twelve month fee cap. A data incident triggers the customer’s losses of two crores. Indemnity inside the cap: vendor’s exposure twelve lakhs. Data indemnity carved out: exposure two crores, sixteen years of contract revenue, from one clause’s placement. Same facts, same indemnity wording, the cap’s geometry decided everything.

A negotiator’s order of operations

Negotiate the architecture before the adjectives. First, establish mutuality: caps and exclusions protect both parties or neither. Second, set the cap number against realistic exposure, fees based for ordinary services, higher where the vendor touches production data or safety. Third, write the carve out list consciously, shortest defensible list, super caps rather than uncapped where the counterparty insists. Fourth, tame indemnity triggers into named events with procedure. Fifth, only then argue wording. Teams that negotiate in this order close faster and carry less silent risk; teams that start with adjectives end up with beautifully drafted clauses in a dangerous arrangement.

Can AI help with indemnity and cap analysis?

Very effectively, at the reading layer. AI tools can map a contract’s entire liability architecture in one pass: every indemnity trigger, the cap number, the carve out list, and, most valuably, the interaction, flagging any indemnity that escapes the cap, quantifying worst case exposure under each clause against contract value. Reviewing a portfolio, they can find every legacy contract where a data indemnity sits uncapped, exactly the audit the DPDPA era demands. That is hours of associate work compressed into minutes, with better consistency. The judgment layer stays human: whether a carve out is worth conceding for this deal’s price, whether a clause would survive an Indian public policy challenge, how an indemnity interacts with your insurance program, and the negotiation itself. AI reads the geometry; a qualified human decides which shapes you can live inside.

When to Review This

• Indemnity and limitation of liability are opposing modifications to the Contract Act’s default compensation engine: the indemnity widens what flows in, the cap narrows what can ever flow out, and the entire game is whether the first sits inside the second. Read the carve out list before the indemnity’s adjectives, negotiate architecture before wording, keep fraud uncapped and everything else consciously priced. In the end, the broadest indemnity in the world is exactly as dangerous as the cap lets it be, which is why, clause for clause, the cap matters more.