Indemnity Clauses Explained: What They Mean in Indian Contracts

An indemnity clause is a promise that one party will make the other whole for a specific kind of loss, usually a loss caused by a third-party claim (a customer sues you because of a bug in software you built for someone else) or by the other party's own conduct (their team breaches confidentiality and you get sued for it). In India, indemnity is not just contract boilerplate copied from a US template. It is a defined term under the Indian Contract Act, 1872, with its own case law on when you can force payment. The one thing most people get wrong: they think indemnity and "you're liable for damages" are the same thing. They are not. Indemnity is a separate, often broader promise that can sit outside your liability cap unless you specifically write it in. This guide (published by Adira, which makes contract review and CLM software, so we have a commercial stake in you understanding contracts well, but this explainer stands on its own) walks through what the clause actually does, what Indian law says, and what to check before you sign.

Plain meaning

Strip away the legal language and an indemnity clause says: "If X happens, I will cover your loss, including money you have to pay someone else and reasonable costs of dealing with it." X is usually a defined list: a third party sues you for IP infringement caused by our product, a data breach caused by our negligence, a breach of confidentiality by our staff. The clause does two things at once. First, it allocates a specific risk to one party regardless of whether a court would have made them pay damages for it anyway. Second, it usually sets up a process, who controls the defence of a claim, who gets notified, how quickly, and who pays legal costs along the way, not just at the end.

This matters because ordinary breach-of-contract damages under Indian law (Sections 73 and 74 of the Contract Act) require the loss to be proximate and, for unliquidated damages, often litigated over "was this loss foreseeable and proven." An indemnity clause is often drafted specifically to sidestep that fight: pay on proof of liability, rather than proof of actual, litigated loss.

Who it protects and what triggers it

Indemnity clauses are almost always asymmetric by design, even when they look mutual on paper. The party more likely to cause the risk (the vendor whose software might infringe someone's patent, the contractor whose staff might leak confidential data, the service provider whose negligence might injure someone at a client site) is usually the indemnifier. The other party, the "indemnity holder," is protected.

The trigger is not "any loss." It is defined loss from a defined event, commonly a third-party IP infringement claim, a data breach or confidentiality breach caused by the indemnifier, death or injury caused by the indemnifier's personnel, or breach of a fundamental warranty like title or authority to contract. If the trigger list is vague ("any loss arising out of this agreement"), the indemnity effectively becomes a second, broader liability regime layered on top of ordinary breach claims. That is usually not an accident.

What to look for

Four mechanics decide whether an indemnity clause is fair or dangerous, and none of them show up if you only skim the headline promise:

1. Scope: third-party claims only, or first-party losses too? A narrow indemnity covers only losses from third-party claims. A broad one also covers direct, first-party losses, which starts to look like general liability and should usually flow through your limitation of liability clause instead.
2. Cap or no cap. Does the indemnity have its own cap, sit inside the general liability cap, or is it silent, which usually means uncapped?
3. Notice and defence control. Who must be told, how fast, and who controls litigation or settlement? Section 125 gives default rules if the contract is silent, but a well-drafted clause should say this explicitly.
4. Baskets and carve-outs. Is there a minimum threshold before indemnity kicks in, and are categories like fraud carved out of any cap that otherwise applies?

The Indian position: Sections 124 and 125

Indemnity in India is not just a contract-drafting convention, it is a named, defined contract type under the Indian Contract Act, 1872. Section 124 defines it:

"A contract by which one party promises to save the other from loss caused to him by the conduct of the promisor himself, or by the conduct of any other person, is called a 'contract of indemnity'." Source: Section 124, Indian Contract Act, 1872

Two things stand out. First, the loss can be caused by the promisor's own conduct, a first-party promise, or by "any other person," a third-party promise. Most commercial indemnity clauses lean on the third-party limb, but the statute plainly allows both, which is why the clause needs to say explicitly which one you are getting.

Second, Section 125 sets out what an indemnity-holder can actually recover once sued, if the contract is silent on process:

"The promisee in a contract of indemnity, acting within the scope of his authority, is entitled to recover from the promisor... all damages which he may be compelled to pay in any suit in respect of any matter to which the promise to indemnify applies... all costs which he may be compelled to pay in any such suit... all sums which he may have paid under the terms of any compromise of any such suit..." Source: Section 125, Indian Contract Act, 1872

Section 125 talks about costs and settlement sums "he may be compelled to pay," which raised a hard question: does the indemnified party have to actually pay out of pocket first, before they can force the indemnifier to act? Indian case law answered that.

A named Indian case: Gajanan Moreshwar v Moreshwar Madan

In Gajanan Moreshwar Parelkar v Moreshwar Madan Mantri (Bombay High Court, AIR 1942 Bom 302), the plaintiff had taken a lease from the Bombay Municipal Corporation, then assigned the benefit of it to the defendant, who agreed to indemnify him against the lease obligations. When the defendant failed to pay the ground rent and the Corporation began proceedings, the plaintiff (the indemnity-holder) did not wait to pay out of his own pocket. He asked the court to order the defendant to make good the liability directly, before any money had left his hands.

The Bombay High Court held that once the indemnity-holder's liability has become absolute, either because a decree has been passed against him or the amount is otherwise certain, he can call upon the indemnifier to save him from that liability by paying it off directly, rather than waiting to be reimbursed after paying it himself. The court read Sections 124 and 125 as not exhaustive of the indemnity-holder's rights and applied broader equitable principles drawn from English law to reach that result. See the full judgment on Indian Kanoon.

Why this matters practically: if your indemnity clause is silent on timing, Indian law does not force you to pay a third-party claim out of your own funds first and fight for reimbursement later. Once your liability is fixed and certain, you can call on the indemnifier to step in and pay directly. This depends on your liability actually being "absolute," a signed decree or an admitted, quantified claim, not merely a threatened one. A good indemnity clause should spell out this mechanic rather than leaving you to rely on a 1942 judgment to fill the gap.

Indemnity vs guarantee (Section 126)

People often use "indemnify" and "guarantee" loosely as if they mean the same thing. Under the Contract Act they are structurally different. Section 126 defines a contract of guarantee as "a contract to perform the promise, or discharge the liability, of a third person in case of his default," involving three parties: the surety, the principal debtor, and the creditor. A guarantee is secondary and conditional on that third party's failure to perform. An indemnity under Section 124 is a direct, primary promise between two parties about a loss, it does not require a third person to default first. If your contract mislabels one as the other, the actual mechanics matter more than the word used, but getting the label right avoids confusion about who the real obligor is.

Red flags

Normal	Red flag	Why it matters
Indemnity capped, often at 1x-3x fees paid or a stated sum	No cap stated anywhere in the clause	Uncapped indemnity can expose you to unlimited liability for one claim, far beyond what you were ever paid
Indemnity sits inside, or is expressly carved out of, the liability cap, clearly stated	Indemnity is silent on how it interacts with the limitation of liability clause	Silence lets the indemnity swallow the cap; whoever argues harder later wins that fight
Indemnity covers defined triggers (IP infringement, confidentiality breach, injury)	Indemnity covers "any loss arising out of or in connection with this agreement"	Turns indemnity into an unlimited second liability regime layered on your damages clause
Both parties give reasonably matched indemnities for risks each one controls	Only one party gives indemnities; the other gives none	A one-sided indemnity often signals a one-sided negotiation, not a one-sided risk profile
Indemnifying party controls defence of the claim, with reasonable cooperation from the other side	Indemnified party is stuck defending itself, or the indemnifier has no obligation to actually defend	You end up funding litigation on someone else's risk with no recourse until the case ends
Indemnity for confidentiality/IP breaches carved out of the cap, but itself capped at a stated multiple	Carved out of the cap and also has no cap of its own	The single most common trap: an "unlimited" carve-out with no ceiling attached

Bad clause → better clause

Bad: "Vendor shall indemnify, defend and hold harmless Client from and against any and all losses, damages, costs and expenses arising out of or in connection with this Agreement."

What is wrong: no trigger definition, no cap, no notice mechanism, no mention of who controls the defence, and it is one-directional.

Better: "Vendor shall indemnify Client against direct losses, and reasonable legal costs, arising from a third-party claim that (a) the Deliverables infringe an Indian patent, trademark or copyright, or (b) Vendor's personnel breached the confidentiality obligations in Clause [X], provided that Client (i) notifies Vendor in writing within 15 business days of becoming aware of the claim, (ii) gives Vendor control of the defence and settlement of the claim (Vendor not to settle in a way that admits fault by Client without Client's consent), and (iii) provides reasonable cooperation at Vendor's expense. Vendor's aggregate liability under this Clause shall not exceed [2x fees paid in the preceding 12 months / a stated sum], except that this cap shall not apply to claims arising from Vendor's fraud or wilful misconduct."

What changed and why: the trigger is defined, there is a notice deadline, defence control is assigned explicitly instead of left to Section 125's defaults, and there is a stated cap with a narrow, honest carve-out for fraud and wilful misconduct.

How it interacts with related clauses

Indemnity does not sit alone. Three clauses in particular decide whether your indemnity clause actually behaves the way it reads:

• Limitation of liability. If your indemnity clause is silent on whether it counts toward the liability cap, you have effectively created two separate, uncoordinated liability regimes. Most negotiated contracts either fold indemnity into the same cap or create a clearly stated, separate "super-cap" for specific indemnified risks. Read indemnity and limitation of liability together, never in isolation.
• Insurance. An indemnity is only as good as the indemnifier's ability to pay. A cyber-liability or professional-indemnity insurance requirement, matched to the size of the cap, is what makes the promise real rather than a paper right against a company that may not have the money when a claim lands.
• Confidentiality and IP assignment. These are two of the most common indemnity triggers. If those clauses are themselves loosely drafted, the indemnity built on top of them inherits the same ambiguity.

You can mark up how these clauses interact directly in a document, for free, using Weave, which lets you flag and comment on clauses like this before you send a contract back for negotiation.

US and global contrast

US indemnification clauses are heavily negotiated but run on broadly similar mechanics, defined triggers, caps, notice, defence control, because most US states also treat indemnity as risk allocation layered on top of ordinary breach damages, not a replacement for it. The bigger difference is procedural: US contracts routinely spell out a "duty to defend," an obligation to fund defence as claims arise rather than reimburse afterward, in explicit language, because American case law on implied defence obligations is patchier than India's. In India, as Gajanan Moreshwar shows, courts have been willing to read a right to compel pre-payment into indemnity relationships even where the clause says little about process. That is a genuine advantage for an Indian indemnity-holder facing a silent clause, but it is not a substitute for writing the mechanics into the contract yourself.

FAQ

Is an indemnity clause the same as a damages clause? No. Damages under Sections 73 and 74 require you to prove your loss was a natural and foreseeable result of a breach. An indemnity clause is a specific promise to cover a defined category of loss, often without needing to litigate foreseeability from scratch, which is why it is drafted and negotiated separately.

Can I get paid before I actually pay the third party? Under Gajanan Moreshwar v Moreshwar Madan (Bombay HC, 1942), once your liability has become absolute, a decree passed against you or an amount that is fixed and undisputed, you can call on the indemnifier to pay it off directly rather than waiting to pay out of pocket first. This is not automatic for a merely threatened or disputed claim.

Does an indemnity clause need to state a cap? Not as a matter of law, but as a matter of risk. If the clause is silent, courts will generally enforce it as written, which can mean uncapped exposure for one triggering event. Treat "uncapped" as a red flag unless it is deliberately narrow, such as fraud only.

What is the difference between indemnity and a guarantee under Indian law? A guarantee (Section 126) is a promise to answer for a third person's default, it involves a surety, a principal debtor, and a creditor. An indemnity (Section 124) is a direct, two-party promise to cover a loss, it does not depend on any third person defaulting first.

Who should control the defence of an indemnified claim? Usually the party paying for the loss, subject to reasonable consultation with the indemnified party and a restriction on settlements that admit fault without consent. If the clause is silent, Section 125 gives some default protection, but it is safer to write the mechanic in.

This guide gets you to understanding what an indemnity clause does under Indian law and what to check before you sign. It does not tell you whether a specific clause in your contract is enforceable or advisable for your situation, that depends on facts and drafting history, and is not legal advice. Talk to a lawyer before you rely on, or walk away from, an indemnity clause in a live negotiation.