Photo by RDNE Stock project from Pexels

When a vendor updates their Terms of Service, the indemnification clause often changes, sometimes for the better, sometimes to push more legal risk onto your shoulders. This worksheet helps you spot those shifts and decide whether the new version is acceptable for your team or if you need to negotiate before signing.

TL;DR

  • Indemnification clauses force one party to pay for the other's legal defense and damages; broad language can bankrupt you if the vendor gets sued.
  • Compare old and new versions side-by-side to catch softened limits, removed caps, or expanded triggers (like "any claim arising from your use").
  • Use our step-by-step checklist to classify changes as red flags, yellow flags, or acceptable tweaks.
  • Look for mutual indemnification (both sides protect each other) instead of one-way clauses that shift all risk to you.
  • Document every comparison in writing so your team has a paper trail if a dispute arises later.

What is indemnification and why it matters

legal documents
Photo by RDNE Stock project from Pexels

An indemnification clause is a promise to cover someone else's legal costs and damages if they get sued. In a Terms of Service, it typically means: "You agree to pay for our legal defense and any settlement if someone sues us because of something you did on our platform."

Broad indemnification language is dangerous because it can force you to pay for disputes that aren't your fault. For example:

  • Narrow clause: "You indemnify us only for claims that you breached this agreement."
  • Broad clause: "You indemnify us for any claim arising from your use of our service, even if we were negligent."
The second version could stick you with a bill for the vendor's own mistakes. If the vendor's security fails and customer data leaks, and someone sues the vendor, a broad indemnity might require you (the customer) to pay for their defense, even though the vendor caused the breach.
"This ensures your team starts from a strong, consistent position in every negotiation; in fact, 91% of in-house counsel report that such resources give them a better starting point for drafting."
>, The Indemnification Clause in Commercial Contracts
0
Consumer-protection checks in Terms Doctor

When a vendor releases a new version of their ToS, they may tighten or loosen the indemnity. Your job is to catch those changes before you agree to the new terms.

How to compare indemnification clauses side-by-side

comparing papers
Photo by RDNE Stock project from Pexels

Key takeaway: Indemnification clauses often hide in plain sight, buried in longer sections about liability or disputes. Learn to spot them first, then compare the exact wording.

Step 1: Locate the indemnification language

Indemnification clauses rarely stand alone. Search your old and new ToS for these keywords:

  • "indemnif…" (indemnify, indemnification, indemnified)
  • "defend" (we will defend you, you will defend us)
  • "hold harmless" (keep us harmless from claims)
  • "liable for" or "liability" (who pays for lawsuits)
Most clauses live in sections titled:
  • Limitation of Liability
  • Indemnification
  • Your Obligations
  • Dispute Resolution
  • Warranty Disclaimers
Copy the entire indemnification section from both the old and new ToS into a document or spreadsheet so you can compare them word-for-word.

Step 2: Identify the direction of indemnity

Who protects whom?

  • One-way indemnity: Only the customer (you) agrees to indemnify the vendor. This is riskier.
  • Mutual indemnity: Both parties agree to indemnify each other. This is fairer.
  • Vendor indemnity: Only the vendor agrees to indemnify the customer. This is rare and very customer-friendly.
Mark which type appears in the old clause, then check if the new version changes the direction.

Step 3: Compare the scope (what triggers indemnification)

The scope is the list of things that require one party to indemnify the other. Broad scopes force you to pay for more disputes. Look for these phrases:

Trigger LanguageRisk LevelWhat It Means
"Your breach of this agreement"LowYou pay only if you break the rules. Fair.
"Your use of our service"HighYou pay even if the vendor is partly at fault. Risky.
"Claims arising from your data"MediumYou pay for disputes about data you uploaded, even if the vendor mishandled it.
"Any claim, demand, or liability"Very HighYou pay for almost anything. Extremely risky.
"Even if caused by our negligence"Very HighYou pay even when the vendor messed up.
Mark each trigger in the old and new clause. If the new version adds broader language (e.g., "any claim arising from your use" instead of "your breach"), flag it as a red flag.

Step 4: Check for caps and carve-outs

Caps limit how much you have to pay. Carve-outs (exceptions) say what the indemnity does not cover.

Examples of protective language:
  • "Indemnification is capped at the fees you paid in the last 12 months."
  • "We do not indemnify for claims caused by our gross negligence."
  • "Indemnification does not apply to disputes resolved by arbitration."
If the new version removes a cap or carve-out, that's a red flag. If it adds one, that's progress.

Step 5: Look for notice and control language

Who gets to manage the lawsuit?

  • Notice requirement: "The indemnitee must notify the indemnifier within 30 days of a claim."
  • Defense control: "The indemnifier has the right to control the defense and settlement."
If the new clause shortens the notice window or strips the indemnifier's control, you lose leverage to defend yourself in court.

Step-by-step worksheet: comparing two versions

Worksheet: compare broad indemnification language across two ToS versions process
Figure 1: Worksheet: compare broad indemnification language across two ToS versions at a glance.

Use this checklist to work through the comparison systematically.

Indemnification Comparison Checklist

Your progress is saved automatically in your browser.

Red flags to watch for in updated indemnification language

Not all changes to an indemnification clause are created equal. Some tweaks are harmless; others expose you to serious financial risk. Use this red-flag guide to prioritize your review.

Critical red flags (do not sign without negotiating)

  1. "Any claim arising from your use of the service", This is extremely broad. You could pay for the vendor's own mistakes if they happen "during your use."
  1. Removal of a dollar cap, If the old clause capped indemnification at "$50,000 per incident," and the new version removes that cap entirely, your exposure is unlimited.
  1. "We do not indemnify for our own negligence" becomes "We do not indemnify for our gross negligence only", This shift means you pay for ordinary vendor mistakes, not just gross ones. Major risk increase.
  1. Notice period shortened from 90 days to 30 days, You get less time to respond to a claim before your indemnity kicks in. Tighter deadlines can trap you.
  1. "You control the defense and settlement" becomes "We control the defense and settlement", If the vendor controls the lawsuit strategy and settlement, they could settle cheaply (leaving you exposed to appeals) or spend lavishly (running up your bill).
  1. Removal of mutual indemnification, If the old clause protected both parties and the new one protects only the vendor, all risk now falls on you.

Yellow flags (negotiate or seek legal advice)

  • Broadened scope (e.g., "use of the service" instead of "breach")
  • Removal of a carve-out for the vendor's negligence (but still present for gross negligence)
  • Notice period shortened from 90 to 60 days
  • New language about "including but not limited to" (suggests broader scope than listed)
  • Shift from "mutual" to "one-way" indemnity
  • Removal of caps but addition of a broader notice requirement

Green flags (acceptable or positive)

  • Addition of a dollar cap or lower cap
  • Addition of a carve-out for the vendor's negligence
  • Narrowed scope (e.g., "only for your breach of this agreement")
  • Extension of the notice period
  • Tighter definition of what claims trigger indemnity
  • Shift to mutual indemnification

How to document and communicate your findings

Keep a written record of every comparison you make. This protects you if a dispute arises later and someone asks, "Why did you agree to this?"

Create a short memo that includes:

  1. Date of review, When did you compare the clauses?
  2. Old version date, What version was previously in effect?
  3. New version date, When does the new version take effect?
  4. Clauses compared, Include the exact sections or page numbers.
  5. Key changes, List the 3–5 most important differences.
  6. Risk assessment, Green / Yellow / Red.
  7. Action taken, Did you sign, negotiate, or escalate?
Example memo snippet:
"Comparison of XYZ SaaS ToS dated 2024-01-15 (old) vs. 2025-03-01 (new). Section 8 (Indemnification) now uses 'any claim arising from your use' instead of 'your breach.' Scope broadened; no dollar cap added. Risk: Yellow. Recommendation: Request narrower language or a $100K cap before renewal."

If the new terms are a yellow or red flag, draft a short email to the vendor:

Hi [Vendor],
>
We're reviewing the updated ToS dated [DATE]. The indemnification clause (Section X) is broader than the previous version, specifically [SPECIFIC CHANGE]. To move forward, we'd like to propose [YOUR EDIT]. Can you accommodate this?
>
Thanks,
[Your name]

Vendors often accept reasonable edits if you ask early and stay professional.

SaaS contracts with broad, one-way indemnification clauses
0%

FAQ

Frequently Asked Questions

Indemnification is a clause in a contract that forces one party to pay for the other's legal costs and damages. Insurance is a separate policy from an insurance company that pays claims if something covered by the policy goes wrong. You can have both: indemnification in your ToS and insurance to back it up. However, indemnification often covers scenarios that insurance does not, which is why reading the exact language matters.
Yes. Most vendors expect some back-and-forth on indemnification, especially if you're a mid-market or enterprise customer. Start by proposing a narrowed scope, a dollar cap, or mutual indemnification. If the vendor refuses all changes, escalate to your legal team and consider whether the risk is acceptable. Many vendors will compromise rather than lose a customer.
Push back. "Standard" does not mean fair or protective for you. Ask to see a redline showing what the vendor changed from the previous version. Request a meeting with their legal team. Offer to sign within a specific cap or carve-out. If they refuse all compromise, document your decision and the vendor's refusal in writing so your team has a record if a lawsuit later arises.
Your company's tolerance for risk depends on your industry, size, and financial reserves. A startup may not afford to indemnify a large SaaS vendor for unlimited liability; an enterprise may be able to absorb a $100K cap. Discuss your threshold with your finance and legal teams, then use that threshold to evaluate each clause. If the new indemnity exceeds your threshold, flag it as Red and do not sign without approval from leadership.
Yes. Terms Doctor's 101 consumer-protection checks include detection of broad indemnification language, and the extension can highlight changes across ToS versions if you run it on both the old and new pages. While automated tools are not a substitute for careful human review, they can help you spot risky clauses quickly and flag them for your team's closer inspection. This worksheet pairs well with Terms Doctor's automated scanning to give you both speed and depth.

Get started with clearer ToS reviews

Comparing indemnification language across ToS versions takes time, but it protects your company from unlimited legal liability. Use this worksheet every time a vendor updates their terms, and keep a record of your findings. If you spot a red flag, loop in your legal team early, most vendors will negotiate if you ask.

Terms Doctor makes this process faster by automatically highlighting risky indemnification clauses and tracking changes across versions. Download the free Chrome, Edge, Brave, Opera, or Vivaldi extension to scan any ToS for broad indemnification language, forced arbitration, auto-renewal traps, and 98 other consumer-protection red flags. Your ToS grades are saved, so you can compare them over time and catch updates as they happen. Terms Doctor is always free and never sells your data. Download now to take back control of the legal fine print.

Note: This worksheet and the Terms Doctor extension are not legal advice. Consult a qualified attorney before signing any contract that exposes your company to financial liability.

Additional Resources