Limitation of Liability Clauses in Indian Technology Contracts

A technology company can sign large customer, reseller or services contracts while leaving its downside exposure unclear. A limitation of liability clause is supposed to make that risk measurable. In practice, many clauses fail because the cap, exclusions, indemnities, warranty language and remedy structure do not work together.

For investors, acquirers and founders, the question is whether exposure is proportionate to revenue, insurance and delivery control, or whether one claim could distort valuation.

Why This Matters

Indian technology contracts are usually negotiated under the wider framework of the Indian Contract Act, 1872. Sections on breach, compensation and enforceability matter because a liability cap is part of the agreed risk allocation that will be tested if performance fails, a platform is interrupted, software misses specifications or a customer alleges infringement.

Section 73 addresses compensation for breach and excludes remote or indirect loss. Section 74 matters where the contract states a sum payable on breach or uses penalty-style drafting. Section 28 also matters where drafting restricts enforcement rights too aggressively.

Technology contracts often add electronic acceptance, online order forms and click-through flows. The Information Technology Act, 2000 is relevant to electronic contracting, including section 10A. Where the contract covers software, documentation, platform content or implementation materials, the Copyright Act, 1957 is also relevant to IP ownership, licensing and infringement-risk allocation.

The business risk is direct. A company may think liability is capped at fees paid, but the same contract may leave confidentiality breaches, IP indemnities, payment claims, fraud, service credits or termination assistance outside the cap. If those carve-outs are not deliberate, the contract may not match the risk model.

What Counsel Should Review

Start with the cap formula. Counsel should check whether liability is capped at total fees paid, fees paid during a lookback period, fees payable under the relevant order form, a fixed rupee amount or insurance proceeds. The formula should match the revenue model. A 12-month fee cap may suit recurring SaaS revenue, but not implementation-heavy services, channel arrangements or one-time licence deals.

Next, review the carve-outs. It is common to exclude some claims from the general cap, but every exclusion should be intentional. IP infringement indemnities, confidentiality breaches, payment obligations, misuse of credentials, regulatory fines, gross negligence and fraud are often treated differently. The issue is whether the company can price, insure and operationally control the risks that remain uncapped or separately capped.

Indirect loss language needs careful drafting. Parties often exclude consequential, special, indirect, punitive or loss-of-profit damages without defining how those labels apply to the contract. In a technology deal, lost revenue, replacement software cost, business interruption, customer claims and remediation expense can sit in contested categories. Counsel should test realistic claim scenarios instead of reviewing the clause in isolation.

Indemnities should be mapped against the cap. A customer-friendly IP indemnity may be acceptable if it is limited to third-party infringement claims, excludes client materials and modifications outside the vendor's control, and gives the vendor conduct of defence. The same indemnity becomes dangerous if it covers every IP-related allegation, all affiliates and uncapped settlements without process controls.

Finally, review the operational documents. Order forms, statements of work, service level agreements and support policies can override the master limitation clause. A diligence team should check precedence language and confirm that negotiated exceptions are visible.

Relevant Judicial Guidance

In Nabha Power Limited v. Punjab State Power Corporation Limited, Civil Appeal No. 8478 of 2014, reported as 2024 INSC 833, the Supreme Court considered the interpretation of express contractual language. Paragraph 41 of the official judgment is useful for the limited point that business efficacy cannot be used to contradict clear contractual wording.

That matters for limitation clauses in technology contracts. A founder, investor or buyer should not assume that a court or tribunal will rebuild a sensible liability model if the executed contract leaves caps, carve-outs and indemnity priorities unclear. The allocation should be visible in the signed terms.

Typical Timeline and Cost Range

A focused review of one master agreement, one order form and one SLA can often be completed within 3 to 7 business days once the full document set is available. A broader review across customer templates, reseller terms and negotiated side letters usually takes 2 to 4 weeks.

Fees should be scoped by template volume, revenue concentration, redline depth, insurance coordination and whether the output is a diligence memo or repeatable clause playbook.

Common Mistakes

1. Putting a cap in the contract without checking carve-outs. The headline cap may not protect the company if key claims are excluded without separate limits.
2. Using generic indirect-loss exclusions. Labels like consequential loss and loss of profits need scenario testing against the actual technology service and revenue model.
3. Letting order forms change the risk allocation quietly. Customer-specific order forms, SLAs or support exhibits can override the master clause if precedence wording is weak.

How KAS & Co. Can Help

KAS & Co. helps technology companies, investors and acquirers review limitation of liability clauses, indemnities, SLA remedies, IP risk allocation and contract exposure across Indian technology deals. For a focused review of liability terms in a technology contract, contact KAS & Co..

FAQs

1. What is a limitation of liability clause in a technology contract?

It is a clause that limits the amount or type of liability a party may face if the contract is breached or a claim arises from the technology relationship.

2. Should IP indemnity claims be outside the liability cap?

Not automatically. Some customers request uncapped IP indemnities, but vendors and investors should test the scope, exclusions, defence control, settlement rights and insurance position before accepting that risk.

3. Is a 12-month fees-paid cap always appropriate for SaaS contracts?

No. It may be a useful starting point, but the right cap depends on contract value, customer dependency, implementation obligations, service-criticality, insurance and negotiated carve-outs.

4. When should investors review limitation clauses during diligence?

Review them early when a company has enterprise customers, large implementation projects, revenue concentration, uncapped indemnities, material SLAs or customer templates that override standard terms.

Sources

• The Indian Contract Act, 1872 - India Code
• The Information Technology Act, 2000 - India Code
• The Copyright Act, 1957 - India Code
• Nabha Power Limited v. Punjab State Power Corporation Limited - Supreme Court judgment dated 5 November 2024