Indemnification Clauses Under Indian Law (2026 Drafting Guide)

Why indemnification clauses are different in Indian commercial contracts

Most Indian commercial contracts copy indemnification language from US or UK precedents, then negotiate the caps. That's a mistake — the underlying legal framework is genuinely different. Section 124 of the Indian Contract Act, 1872 codifies the indemnity contract, and Section 125 spells out the indemnity-holder's rights. The Indian framework is narrower than English common law in some respects (it traditionally did not extend to acts of God or third parties unrelated to the contract) and broader in others (the Supreme Court has expanded the holder's rights to pre-payment recovery).

For in-house counsel drafting or reviewing indemnification clauses in vendor agreements, SaaS agreements, or NDAs, the practical question is not "is this enforceable" — it is — but "is the structure aligned with Indian-court interpretive defaults?" Three drafting principles follow:

1. Use Section 124 framing explicitly: refer to the indemnity as a "contract of indemnity within the meaning of Section 124 of the Indian Contract Act, 1872." This anchors the clause to the established statutory framework and avoids common-law ambiguity.
2. Specify pre-payment rights: the Gajanan Moreshwar line of cases permits the indemnity-holder to require the indemnifier to discharge the third-party liability directly, but only if the contract contemplates that mechanism. Bracketed pre-payment language should be drafted in.
3. Carve out from limitation of liability deliberately: India does not have a "fundamental breach" doctrine that automatically pierces liability caps. Carve-outs must be explicit.

What Sections 124 and 125 actually say

The statutory framework is short and worth quoting:

Section 124, Indian Contract Act, 1872 "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'."

Section 125, Indian Contract Act, 1872 "The promisee in a contract of indemnity, acting within the scope of his authority, is entitled to recover from the promisor — (1) all damages which he may be compelled to pay in any suit in respect of any matter to which the promise to indemnify applies; (2) all costs which he may be compelled to pay in any such suit if, in bringing or defending it, he did not contravene the orders of the promisor and acted as it would have been prudent for him to act in the absence of any contract of indemnity, or if the promisor authorised him to bring or defend the suit; (3) all sums which he may have paid under the terms of any compromise of any such suit, if the compromise was not contrary to the orders of the promisor, and was one which it would have been prudent for the promisee to make in the absence of any contract of indemnity, or if the promisor authorised him to compromise the suit."

Three operational consequences flow from the text:

• The indemnitee is entitled to damages, costs, and settlement amounts — but the costs and settlements must be "prudent" or authorised by the indemnifier.
• The indemnifier has a right to direct the defence, implicit in Section 125's reference to "orders of the promisor."
• The indemnity is scope-bound: it applies only to matters within the scope of the indemnity promise, not to general business losses.

The standard market structure

Indian B2B contracts use a three-tier indemnification structure that maps onto the limitation-of-liability framework. Each tier has a different cap and different carve-outs.

Tier 1: General indemnification

A reciprocal indemnity for breach of representations, warranties, or covenants under the contract. Usually capped at the same level as the limitation of liability — 12 months of fees paid in the immediately preceding contract year.

Each Party (the "Indemnifying Party") shall defend, indemnify, and hold harmless the other Party (the "Indemnified Party") from and against any loss, damage, liability, cost, or expense (including reasonable attorneys' fees) arising out of or in connection with any breach by the Indemnifying Party of its representations, warranties, or covenants under this Agreement. This indemnity is given as a contract of indemnity within the meaning of Section 124 of the Indian Contract Act, 1872. The liability of the Indemnifying Party under this Clause shall be subject to the limitation of liability set forth in Clause [13].

Tier 2: Super-cap indemnification

For IP infringement and breach of confidentiality. Capped at 24 months of fees, or — for IP — uncapped at the buyer's preference. The market norm in India tracks the global SaaS market: IP indemnity uncapped, with the supplier retaining the right to procure rights, modify the infringing portion, or refund. Confidentiality indemnity at 24 months is the typical compromise position.

The Provider shall defend, indemnify, and hold harmless the Customer from and against any claim brought by a third party alleging that the Service, when used by the Customer in accordance with this Agreement, infringes any patent, copyright, trade mark, or trade secret of such third party, and shall pay all damages and costs (including reasonable attorneys' fees) finally awarded in such claim or agreed to in settlement authorised in writing by the Provider. If a court of competent jurisdiction holds that any portion of the Service infringes, or if in the Provider's reasonable judgement such an injunction is likely, the Provider shall, at its option and expense: (i) procure for the Customer the right to continue using the affected portion, (ii) modify or replace the affected portion to make it non-infringing without materially impairing functionality, or (iii) terminate the affected portion of the Service and refund a pro-rata portion of pre-paid fees. This indemnity shall not be subject to the limitation of liability set forth in Clause [13].

Tier 3: Uncapped indemnification

For gross negligence, wilful misconduct, fraud, and (in the Indian context) breach of DPDP obligations triggering regulator penalties. These exceptions are uncontroversial in Indian-market negotiations — neither party should be able to cap liability for its own bad faith.

The DPDP-specific carve-out is the newer addition. Section 33 of the DPDP Act, 2023 imposes penalties up to ₹250 crore per breach. If those penalties arise from the supplier's failure to meet

Digital Personal Data Protection Act, 2023 § 8Section 8 imposes obligations on data fiduciaries; Section 8(5) requires the fiduciary to enter into a valid contract with any data processor obligating the processor to specific data handling standards.

processor obligations, the supplier should bear them — and they shouldn't be capped at 12 months of fees.

The Gajanan Moreshwar principle

The Bombay High Court in Gajanan Moreshwar Parelkar v Moreshwar Madan Mantri (1942) departed from the older English common-law rule that indemnification was reactive — i.e., the indemnity-holder had to pay the third-party loss first, then claim from the indemnifier. The Indian position is more practical: the indemnitee can compel the indemnifier to pay the third party directly, or to deposit funds in court, before the indemnitee has paid out.

The Supreme Court has subsequently endorsed this approach in State of Maharashtra v Saifuddin Mujjafarali Saifi and other cases. The practical result: Indian indemnification clauses can — and should — include explicit pre-payment language, often called "advance indemnification" or "first-dollar coverage."

Drafting note: Without explicit pre-payment language, an indemnitee facing a third-party claim must either (a) pay the claim from its own funds and recover later, or (b) join the indemnifier as a party to the litigation under Order 1, Rule 10 of the Code of Civil Procedure. Both options are operationally messy. Pre-payment language is cheap insurance.

Defence control: the negotiation lever

Section 125 implies that the indemnifier has some control over the defence — the indemnitee must act "as it would have been prudent" or follow the indemnifier's "orders." But the practical mechanics need contractual elaboration.

The standard market position in Indian B2B contracts:

1. Notice: indemnitee gives prompt written notice of the claim.
2. Election: indemnifier elects within 30 days whether to take over the defence, with sole control of strategy and counsel.
3. Cooperation: indemnitee provides reasonable cooperation, at indemnifier's expense.
4. Settlement: settlement requires indemnitee's consent (not unreasonably withheld) if it imposes any non-monetary obligation or admission of fault on the indemnitee.

The "settlement requires consent" provision is the key buyer-side protection. Without it, the indemnifier could settle on terms embarrassing to the indemnitee — for example, by admitting that the indemnitee misused IP. The carve-out for non-monetary settlement preserves the indemnitee's reputational interests.

DPDP indemnification: the new front

Indian commercial contracts entered into before 2024 typically have no DPDP-specific indemnification clause. They have a generic data-protection indemnity that referenced the IT Act, 2000 Section 43A or the SPDI Rules. Those clauses are now under-inclusive for the regulatory exposure created by the DPDP Act.

A DPDP-aware indemnity covers three categories of loss:

1. Regulator penalties under Section 33 — up to ₹250 crore per breach.
2. Data principal claims — civil claims by individuals for harm from processing in violation of the Act.
3. Investigation costs — costs of responding to Data Protection Board inquiries.

The drafting question is which party bears these losses. The general rule: each party indemnifies for losses arising from its own breach of its DPDP obligations. The fiduciary indemnifies for principal notice and consent failures; the processor indemnifies for security breaches and unauthorised processing. The full DPDP framework is in the DPDP compliance guide.

Common drafting mistakes

Three patterns recur in Indian B2B contracts that weaken indemnification clauses:

1. Indemnity bundled into LoL: the indemnification is drafted in one clause, the limitation of liability in another, and the relationship between them is unclear. The carve-outs from LoL must explicitly cross-reference the indemnification clause, otherwise the LoL cap defeats the indemnity.

2. No defence cost carve-out: the indemnity says "all losses, damages, and liabilities" but doesn't expressly include "reasonable attorneys' fees and defence costs." Indian courts have read this omission strictly — Section 125's reference to "costs" applies, but only for "any suit," not for pre-litigation legal advice or regulatory investigations.

3. Mirror indemnification without thinking: contracts default to a reciprocal indemnification structure even when the risk profile is asymmetric. A SaaS provider's IP infringement risk is real; the customer's IP infringement risk against the provider is usually nominal. Don't mirror what shouldn't be mirrored.

Standard caps: the negotiation reference

For Indian commercial contracts negotiated in 2026, the market-clearing positions:

A supplier insisting on capping the IP indemnity at 12 months should be read as either inexperienced with the Indian SaaS market or signalling that they have an unresolved IP risk in their pipeline.

How Clauseium reviews indemnification clauses

Clauseium parses every commercial contract into its indemnification structure and compares the result to the standard market positions above. It flags missing carve-outs, IP indemnities capped below market, absent DPDP-specific provisions, and ambiguous defence-control language. For most counsel, that turns a clause-by-clause indemnity audit into a short exception list.

Try Clauseium free →

Final checklist

When drafting or reviewing an indemnification clause in an Indian commercial contract, verify:

1. The clause expressly invokes Section 124 of the Indian Contract Act.
2. The three tiers (general, super-cap, uncapped) are clearly delineated, with each tier's cap unambiguously stated.
3. IP and confidentiality indemnities are excluded from the limitation of liability cap with explicit cross-reference.
4. Pre-payment indemnification (Gajanan Moreshwar style) is available for material claims.
5. Defence control mechanics — notice, election, cooperation, settlement consent — are specified.
6. Defence costs and reasonable attorneys' fees are expressly included.
7. DPDP-specific indemnification is included if personal data is in scope.
8. Reciprocal indemnification only where the risk profile is genuinely symmetric.
9. The clause survives termination and is included in the survival clause.
10. Limitation periods (under the Limitation Act, 1963) are contractually extended where appropriate, particularly for IP and confidentiality claims.

A well-drafted indemnification clause is one of the few places in a commercial contract where careful drafting genuinely changes outcomes in litigation. The defaults above are the result of two decades of Indian arbitration practice converging on what works.