How to negotiate intellectual property indemnity for third-party tools in SaaS agreements

To negotiate IP indemnity for third-party tools, explicitly limit the vendor's obligation to software they own or control. Exclude open-source components, cap total liability at 1x–2x annual fees, and ensure the vendor retains sole control over the legal defense to manage costs and strategy.

The Scope of IP Indemnity in SaaS

In a SaaS context, IP indemnity is the vendor's promise to cover your legal costs if their software infringes on a third party's patent, copyright, or trade secret. When third-party tools are involved, the risk profile shifts. If the vendor integrates a third-party API or library, they must stand behind that integration.

Defining 'Covered' Third-Party Tools

You must distinguish between tools the vendor mandates and tools you choose to integrate. If you connect your own third-party software to the vendor's platform, the vendor should not be liable for infringement caused by that external tool.

• Vendor-Provided Tools: Indemnity must apply.
• Customer-Integrated Tools: Indemnity must be excluded.
• Open Source: Negotiate a 'reasonable efforts' standard rather than a strict indemnity for open-source libraries.

Key takeaway: Always define the 'Software' in the indemnity clause to explicitly include or exclude third-party components to prevent ambiguity during litigation.

Action Item: Audit your SaaS agreement to see if the indemnity clause covers 'all components' or specifically 'the proprietary software.' Narrow this scope to protect the vendor from your own tech stack decisions.

Structuring Liability Caps and Exclusions

Uncapped indemnity is a non-starter for most SaaS vendors. You must balance your protection with the vendor's financial viability. Industry standards typically place indemnity obligations under the general liability cap, though high-risk enterprise deals often carve out indemnity as an 'unlimited' liability item.

Critical Exclusions to Negotiate

Vendors will push for specific exclusions to their indemnity obligations. You must ensure these exclusions are narrow:

1. Modification: The vendor is not liable if you modify the software.
2. Combination: The vendor is not liable if the infringement arises from combining their tool with your unauthorized software.
3. Failure to Update: The vendor is not liable if you fail to implement a provided patch that would have resolved the infringement.

Action Item: Ensure the 'Combination' exclusion requires that the infringement would not have occurred *but for* the combination with your software. This prevents the vendor from escaping liability if their tool is inherently infringing.

The 'Duty to Defend' vs. 'Duty to Indemnify'

Many contracts conflate these two. The 'Duty to Defend' requires the vendor to pay for legal counsel immediately upon a claim. The 'Duty to Indemnify' requires them to pay for damages after a judgment or settlement. You want both.

Why Defense Matters

Legal fees in IP litigation often exceed the actual damages. If the vendor only agrees to indemnify (pay damages), you are left footing the six-figure legal bill to prove the infringement occurred. Always insist on the vendor's obligation to 'defend, indemnify, and hold harmless.'

• Immediate Trigger: The vendor must provide counsel upon notice of a claim.
• Settlement Authority: The vendor should not settle without your consent if the settlement requires you to admit fault or restricts your business operations.

Key takeaway: If a vendor refuses to defend, demand a 'reimbursement of reasonable legal fees' clause as a fallback to ensure you aren't bankrupted by a meritless claim.

Action Item: Review your contract for the phrase 'sole control of the defense.' If present, add a proviso: 'provided that the vendor shall not enter into any settlement that imposes an obligation on the Customer without the Customer’s prior written consent.'

Jurisdictional Considerations

IP indemnity is governed by federal law (in the US), but the contract interpretation is governed by state law (e.g., Delaware, California, New York). Ensure your choice of law clause aligns with your indemnity expectations. Delaware law is generally preferred for its predictability in corporate and commercial disputes.

Action Item: Verify that the governing law of your contract supports the enforcement of indemnity obligations. If you are dealing with international vendors, ensure the indemnity covers cross-border IP claims, which can be significantly more expensive to litigate.

TermScore uses advanced AI to instantly scan your SaaS agreements for these specific indemnity pitfalls, highlighting missing 'duty to defend' language and overly broad exclusions so you can negotiate with confidence and speed.