<\!DOCTYPE html> SaaS Terms of Service Requirements: What to Include | DocSnappy

SaaS Terms of Service: What You Must Include

A practical guide to drafting SaaS Terms of Service for US businesses. Covers subscription terms, acceptable use, liability limits, data handling, and DMCA compliance.

Why SaaS ToS differ from standard website terms

A standard website terms of service governs how visitors use your site. A SaaS terms of service governs an ongoing contractual relationship — subscription billing, access to a software product, user data, uptime expectations, and support obligations. The stakes are higher and the terms need to be more detailed.

Getting your SaaS ToS wrong exposes you to: chargebacks and subscription disputes, liability for data breaches, copyright infringement claims, inability to enforce payment or terminate abusive users, and regulatory action in states with consumer protection laws.

1. Grant of license and subscription terms

Clearly state what the user is getting: a limited, non-exclusive, non-transferable license to use the software during their subscription period. Specify:

  • What tier or plan they're on and what it includes
  • Number of seats or users permitted
  • Geographic restrictions (if any)
  • Whether the license is for personal or commercial use

2. Subscription billing, auto-renewal, and refunds

This is one of the most legally fraught sections. FTC regulations and state consumer protection laws (particularly in California under APC §17601) require clear disclosure of:

  • The price of the subscription and billing frequency
  • That the subscription will auto-renew unless cancelled
  • How to cancel, and the cancellation deadline
  • Your refund policy (even if it's 'no refunds after 7 days' — just say so clearly)
  • What happens to data on cancellation or non-payment

3. Acceptable Use Policy (AUP)

Your AUP defines what users can and cannot do with your software. At minimum, prohibit:

  • Reverse engineering, decompiling, or scraping your software
  • Using the service to transmit spam, malware, or illegal content
  • Attempting to gain unauthorized access to other users' accounts or your infrastructure
  • Sharing login credentials or exceeding seat limits
  • Using the service in ways that violate applicable law

4. Data ownership, processing, and privacy

For SaaS, your ToS must address who owns the data users put into your system. The answer is almost always: the user owns their data; you have a license to process it to provide the service. Also specify:

  • That you will handle their data per your Privacy Policy (link to it)
  • How long you retain data after account deletion
  • Whether you use aggregated or anonymized data for analytics or product improvement
  • If you process personal data of EU residents, note that you have a DPA (Data Processing Agreement) available

5. Limitation of liability and warranty disclaimer

This is your most important protective clause. In plain English, it says: 'if our software has a bug and causes you losses, we aren't liable beyond the amount you paid us in the last 12 months.'

Courts generally uphold limitation of liability clauses in B2B SaaS agreements. For B2C, consumer protection laws in some states limit how much you can disclaim — you can rarely fully exclude liability for gross negligence or intentional misconduct. Make sure your limitation of liability clause is prominently displayed (often required to be in all-caps to be enforceable in some states).

6. Termination rights

Specify clearly: who can terminate, on what grounds, with how much notice, and what happens to the user's data on termination. Include your right to suspend or terminate immediately for AUP violations.

Also cover what happens to prepaid subscription fees: do you prorate and refund, or is no refund given? This must match your billing and refund policy section.

7. DMCA compliance

If your platform allows any user-generated content (even file uploads or form data), you should include a DMCA safe harbor clause. To qualify for safe harbor protection under the Digital Millennium Copyright Act:

  • Register a DMCA agent with the US Copyright Office
  • Publish a DMCA takedown contact email in your ToS
  • Implement a repeat infringer policy
  • Describe the takedown process for copyright holders

Generate your legal document in 2 minutes

DocSnappy's free generators produce complete, formatted documents you can use immediately.

Browse all US documents →

Frequently Asked Questions

Do I need a lawyer to write SaaS terms of service?

For early-stage products with low revenue, a well-drafted template covers the essentials. As you scale — particularly if you handle sensitive data, serve enterprise clients, or process payments above $10K/month — legal review is worth the investment. A one-time review by a SaaS-experienced attorney typically costs $500–$2,000 and can save multiples of that in avoided disputes.

Can I copy another company's terms of service?

Legally you can (terms of service are not copyrightable in the US), but it's a bad idea practically. Another company's ToS is tailored to their product, business model, and risk profile — not yours. Blindly copying can leave gaps, create contradictions, or include provisions that don't apply to your product and confuse your users.

How often should I update my SaaS ToS?

At minimum, review your ToS annually and whenever: you add a significant new feature, change your pricing or billing model, enter a new geographic market, or a relevant new law passes (e.g., a new state privacy law). Always notify users before terms changes take effect and document the version history.