SaaS · 7 min read

How to Read a SaaS Contract Before You Sign

Clicking "I agree" on a software subscription can lock you into a year, hand over data rights, and cap the vendor’s liability at almost nothing. Check these before you commit.

Key takeaways

  • Confirm you own your data and that the vendor cannot use it to train AI without permission.
  • Find the auto-renewal clause and the cancellation window before you sign, 60 or 90 days' notice is common.
  • A liability cap of "one month of fees" rarely matches your real exposure if the vendor loses your data.
  • Check for uncapped price increases and whether you can export your data on the way out.

Who owns your data, and can they train AI on it?

Start with the data clause, because it outlasts the subscription. The contract should say plainly that you own your data and that the vendor gets only a limited license to host and process it in order to provide the service. Then hunt for the quiet expansion: a right to use your data to "improve our services," to build "aggregated and anonymized" datasets, or, increasingly, to train AI or machine-learning models. "Improve" sounds harmless until you realize your customer records, support tickets, or documents may be feeding a model that serves your competitors.

If the vendor needs analytics to run the product, fine, but the license should be limited to providing the service to you. Ask for an explicit statement that your data will not be used to train AI models without your written consent. Vendors are getting this request weekly now; the good ones already have an opt-out.

Auto-renewal and the cancellation window

Most B2B SaaS contracts renew automatically for another full term unless you cancel within a notice window, commonly 30, 60, or even 90 days before the renewal date. Miss a 90-day window on an annual contract and you have bought another year, and courts generally enforce that, because you agreed to it.

Two defenses. First, put the deadline on your calendar the day you sign, with a reminder a month early. Second, negotiate the window down: 30 days is a reasonable ask, and some vendors will agree to renewal only on your affirmative consent. Several states also require vendors to send a renewal reminder for some contract types, but do not rely on a statute to save you from a missed date.

Liability cap vs. your real exposure

Nearly every SaaS contract caps the vendor’s total liability, and the default cap is small: often the fees you paid in the last 12 months, sometimes as little as one month. Now run the numbers on your side. If this tool holds your customer data and the vendor’s security failure causes a breach, your costs, notification, credit monitoring, legal exposure, lost customers, can run to many multiples of your annual subscription. A $500-a-month tool with a one-month cap leaves you carrying essentially all of that risk.

The standard middle ground in real negotiations: a general cap of 12 months of fees, plus carve-outs, higher or uncapped liability, for data breaches caused by the vendor, breaches of confidentiality, and the vendor’s indemnification obligations. Smaller vendors will resist unlimited exposure, but a "super-cap" of 2–3x fees for data incidents is a common landing zone.

Price increases

Check what happens to the price at renewal. Many contracts let the vendor raise prices unilaterally, sometimes with as little as 30 days’ notice, and the increase lands right when switching costs are highest, after your team is trained and your data is inside. Annual increases of 8–10% on renewal are not rare.

Ask for a cap: renewal increases limited to a fixed percentage (5–7% is a common ask) or to an inflation index. If the vendor will not cap it, at least secure a longer notice period, 60–90 days, so a surprise increase leaves you time to evaluate alternatives before the auto-renewal window closes. Note how those two clocks interact: a price-change notice that arrives after your cancellation deadline has passed is a trap worth negotiating away explicitly.

Uptime / SLA and data export

An uptime promise without a remedy is marketing. A real SLA states a number (99.9% is common), defines how downtime is measured, and gives you service credits automatically or on request when the vendor misses it. Check whether credits are your only remedy, and whether repeated failures, say, missing the SLA three months running, give you the right to terminate without penalty. That termination right is what actually keeps vendors honest.

Finally, plan the exit on the way in. The contract should give you a window after termination, 30 days is typical, to export your data in a usable format before the vendor deletes it, at no extra charge. Ask what "usable format" means for your data specifically; a CSV dump of a database you cannot reconstruct is technically an export. Vendors delete quickly after termination for their own compliance reasons, so if the export window is missing, add it.

Don't guess, check your actual contract

Upload your saas contract and our AI will flag the risky clauses in plain English, tuned to your state, with a downloadable report and redline.

Frequently asked questions

What should I check first in a SaaS contract?

Data ownership and AI-training rights, the auto-renewal and cancellation window, the liability cap, price-increase rights, and how you get your data out. Those five clauses drive most of the real risk in a subscription.

Can a SaaS vendor use my data to train their AI?

Only if the contract lets them. Look for language like "improve and train our services" and, if it is there, ask to strike it or limit it to aggregated, anonymized data, especially if you handle client or regulated data.

Is a one-month liability cap normal in SaaS?

It is common, but common is not the same as fair. If a breach or data loss could cost you far more than a month of fees, negotiate a higher cap and make sure data breaches and IP claims sit outside the cap.

Related SaaS guides

This guide is general information from ClauseAudit, not legal advice. Laws vary by state and change, consult a qualified attorney for your situation. Published 2026-05-01; last reviewed 2026-07-01.