Your Terms of Service is a contract — treat it like one
A terms of service (ToS) is the contract between your SaaS and everyone who uses it. It defines what you offer, what users can do, what you're liable for, and how disputes get resolved. Without one, you're operating on implied terms — which usually means the most user-friendly interpretation courts can find.
This guide covers every clause a SaaS ToS needs, why it matters, and what to watch out for.
The essential clauses
1. Acceptance of Terms
This establishes that using your product means agreeing to the ToS. Courts generally uphold "clickwrap" agreements (where users actively check a box or click "I agree") more reliably than "browsewrap" (where terms are just posted on the site). Use clickwrap at signup.
Also state: you can change the terms, and continued use after notice means acceptance of the changes.
2. Description of Service
Describe what your product does at a high level. This isn't marketing copy — it's the scope of what you're obligated to provide. Keep it accurate but not overly specific (you'll need to update the ToS every time you add a feature).
3. Eligibility and Account Registration
- Minimum age (18 in most jurisdictions; GDPR requires 16+ for digital services in many EU states)
- Users must provide accurate information
- Users are responsible for their account credentials
- One account per person/entity (if applicable)
- Your right to suspend or terminate accounts
4. Subscription, Pricing, and Payment Terms
If you charge money, this section is critical:
- How billing cycles work (monthly, annual)
- What happens if payment fails
- Price change notice period (30 days is standard)
- Auto-renewal terms (must be clearly disclosed — many jurisdictions require this)
- Whether prices include VAT/GST
EU note: Under the EU Consumer Rights Directive, if you sell to consumers (not just B2B), you must provide clear pre-contractual information about total price, subscription terms, and cancellation rights. Violating this can void the contract.
5. Cancellation and Refund Policy
- How users cancel (self-serve dashboard, email, etc.)
- Whether you offer refunds (pro-rata, none, 30-day money-back)
- What happens to data after cancellation
- EU/UK 14-day cooling-off right for consumers (unless service delivery has started with explicit consent)
6. Acceptable Use Policy (AUP)
This defines what users cannot do with your product. At minimum:
- No illegal activities
- No harassment or abuse
- No reverse engineering or scraping (if applicable)
- No reselling without permission
- No exceeding usage limits / rate limits
- No circumventing security measures
A strong AUP gives you clear grounds to terminate accounts without refund.
7. Intellectual Property
Two separate IP sections you need:
Your IP: Your software, brand, content — you own it. Users get a limited, non-exclusive, non-transferable license to use it.
User content/data: Users own their data. You get a limited license to process it in order to provide the service. This is critical: if your ToS doesn't address this, you may have ambiguous rights to do basic things like run backups.
8. User-Generated Content (if applicable)
If users can post content visible to others:
- Users own their content, grant you a license to display/distribute it as needed for the service
- Users warrant they have rights to post the content
- Your right to remove content that violates AUP
- DMCA safe harbor notice procedure (if you're in the US)
9. Privacy
A simple reference to your Privacy Policy, incorporated by reference. Don't duplicate privacy terms here — keep them in the privacy policy where they're easier to maintain and update independently.
10. Disclaimers and Limitation of Liability
This is usually the most important section for founders:
Disclaimer of warranties: Service provided "as is" and "as available" without warranties of merchantability or fitness for a particular purpose.
Limitation of liability: Cap your total liability at the amount the user paid in the prior 12 months (or some other defined cap). Exclude liability for indirect, consequential, and incidental damages.
EU/consumer caveat: Many of these disclaimers don't fully apply to EU consumers. Courts can strike down unfair contract terms. For B2B SaaS, they're more enforceable. Regardless, include them — partial protection is better than none.
11. Indemnification
Users agree to indemnify you against claims arising from their use of your service or violation of the ToS. Protects you if a user does something illegal using your product and a third party sues you.
12. Governing Law and Dispute Resolution
- Which country's law governs the contract
- Which court has jurisdiction
- Whether you require arbitration before litigation (common in US SaaS, less common in EU)
For EU businesses: For consumer contracts, you generally can't override the consumer's local courts. For B2B, you can set jurisdiction more freely. Estonian SaaS: Harju County Court is the default.
13. Termination
- Under what conditions you can terminate (AUP violation, non-payment, etc.)
- Notice period for termination without cause
- What happens to data and subscriptions upon termination
- Which clauses survive termination (IP, liability, payment obligations)
14. Changes to the Service
You reserve the right to modify, suspend, or discontinue any part of the service. Typically with reasonable notice. Without this clause, changing your product could be breach of contract.
15. Force Majeure
Neither party liable for failures due to circumstances beyond reasonable control (natural disasters, government action, infrastructure failures). Became especially relevant post-2020.
16. Entire Agreement and Severability
This ToS (plus Privacy Policy, AUP, DPA if applicable) constitutes the entire agreement. If any clause is found unenforceable, the rest of the ToS still stands.
Common mistakes SaaS founders make
Copying a competitor's ToS verbatim
Their ToS reflects their business, their jurisdiction, their risks. Copying it exposes you to: mismatched terms (their cancellation policy doesn't apply to your pricing model), possible IP infringement, and governing law clauses that don't favor you.
No explicit subscription auto-renewal disclosure
Multiple US states (California, New York, others) have auto-renewal laws requiring clear disclosure and easy cancellation. EU also has strong consumer protection rules here. Failing to comply can make auto-renewals unenforceable and expose you to class action risk.
Liability cap set too high (or not set at all)
Without a cap, a user could theoretically sue you for unlimited damages. Set a cap equal to fees paid in the prior 12 months or a fixed amount (€500, $1,000). For free tiers, specify that liability is limited to the extent permitted by law.
Not updating the ToS when adding material features
If you add AI processing, third-party integrations, or new data practices, update the ToS (and privacy policy) and notify users. Operating on outdated terms is a liability.
When to get a lawyer to review
Before you launch paid tiers, especially if you're targeting enterprise. The cost of a lawyer to review a template (€500–€1,500) is trivial compared to the risk of an unenforceable contract in your first big deal.
For early-stage SaaS with free users only: a solid generated template is fine to start. Iterate as you grow.
Generate your Terms of Service in 5 minutes
ComplyKit generates a jurisdiction-aware SaaS Terms of Service free. No login required. Covers all the clauses above, customized to your business type, pricing model, and country.
Generate your SaaS Terms of Service free
Free, no signup required. Generated in under 5 minutes.
Generate Terms of Service →