← Back to Blog
LegalMay 10, 2026·8 min read

Terms of Service Template 2026: 17-Section Plain English ToS

Most ToS documents read like they were written by lawyers for other lawyers, not for the actual humans signing up. Below is the 17-section structure every SaaS, Shopify store, and mobile app needs, written in plain English, with the 4 sections that actually save you when something goes wrong.

Skip the writing entirely with our free Terms of Service generator, or read on for the manual structure.

The 4 sections that actually save you

Most founders treat ToS as a checkbox formality, copying a template into the footer and forgetting about it. That works until the first time something goes wrong, at which point four specific sections decide whether your business takes the hit or you do.

Limitation of Liability

Caps the maximum a user can claim against you (typically the amount they paid in the last 12 months, or $100, whichever is greater). Without this clause, a user could theoretically sue for any consequential damage. With it, you have a firm ceiling.

Indemnification

Requires users to defend you if their use of your service causes harm to a third party. Critical for any platform with user-generated content, file uploads, or AI outputs the user produces and publishes.

Acceptable Use Policy

Gives you legal grounds to terminate accounts engaging in scraping, abuse, fraud, or violations of platform rules. Without explicit AUP language, terminations can be challenged as breach of contract.

Governing Law and Dispute Resolution

Forces disputes into a jurisdiction and forum favourable to you (usually your home state with mandatory binding arbitration). Without it, users can sue you anywhere they live, which gets expensive fast.

The complete 17-section structure

Every modern ToS covers the same 17 sections in roughly this order. Adding sections rarely helps; cutting standard sections almost always hurts.

  1. Acceptance of Terms. How users agree (continued use, signup checkbox, etc.).
  2. Description of Service. What you actually provide. One paragraph.
  3. Eligibility and User Accounts. Age requirement (typically 13+, or 18+ for paid services), account security, prohibition on sharing credentials.
  4. Acceptable Use. Prohibited activities and content.
  5. User Content and License. What users post, what license they grant you to use it.
  6. Intellectual Property. Your IP, trademarks, copyright notice.
  7. Payment Terms. Billing cycle, auto-renewal, taxes (if you have paid plans).
  8. Cancellation and Refunds. High-level — refer users to a separate Refund Policy.
  9. Third-Party Services and Links. Disclaim responsibility for external sites.
  10. Disclaimers. Service provided “as is”, no warranty of uninterrupted operation.
  11. Limitation of Liability. See above.
  12. Indemnification. See above.
  13. Termination. By user, by you, effect of termination.
  14. Governing Law and Dispute Resolution. Your jurisdiction, mandatory arbitration if you choose.
  15. Changes to Terms. Notice period, deemed acceptance.
  16. Severability and Entire Agreement. Standard boilerplate that prevents one bad clause from invalidating the whole document.
  17. Contact Information. Email + business address.

SaaS-specific considerations

For SaaS businesses, three sections need extra attention beyond the generic template:

  • Service Level Agreement (SLA) language. If you market “99.9% uptime”, the ToS should state what users get if you miss it (typically pro-rated credits, not refunds). Don't make SLA promises you can't back up — disgruntled customers will hold you to them.
  • Data export rights. EU users have a GDPR right to data portability. Spell out the export format and how long users have to retrieve their data after cancellation.
  • API terms. If you have an API, separate API terms (or a clear API section) prevent disputes about rate limiting, scraping, and resale of your data.

Shopify-specific considerations

For Shopify stores, the ToS interlocks with the Privacy Policy and Refund Policy:

  • Order acceptance vs. order placement. The ToS should clarify that placing an order is an offer, not a contract. The contract forms when you accept the order. This prevents disputes about pricing errors.
  • Inventory and pricing errors. Reserve the right to cancel orders if a pricing error or inventory shortage is discovered after order placement.
  • Shipping and risk transfer. Specify when ownership transfers (typically on delivery to the carrier vs. delivery to the customer). Affects who's responsible if a package is lost in transit.

Pair this guide with our Shopify Privacy Policy guide and the Shopify launch checklist for the complete pre-launch document set.

Common ToS mistakes

  • Auto-renewal language buried. Specifically illegal in California (CCPA) and the EU. Auto-renewal must be conspicuous, with a clear cancellation path.
  • Limiting liability for “gross negligence” or “wilful misconduct”. Most jurisdictions don't enforce these limits. Trying to disclaim them often invalidates the entire limitation of liability clause.
  • One-sided modification rights. “We reserve the right to change these terms at any time without notice” — courts increasingly reject this. State a notice period (30 days is standard).
  • Mandatory arbitration without opt-out. Some jurisdictions require an opt-out window (typically 30 days from account creation). Without it, the arbitration clause may be unenforceable.

Frequently asked questions

Is a Terms of Service legally required?

Strictly, no — there's no federal US or UK law that says every website must have one. But almost every payment processor, app store, and platform requires an active ToS URL before they'll process payments or approve listings. Stripe, Shopify, Apple App Store, Google Play, and most B2B partners all check. The practical answer is: yes, you need one before launch.

What's the difference between Terms of Service and Terms and Conditions?

Functionally nothing. 'Terms of Service' is more common for SaaS and digital products; 'Terms and Conditions' is more common for e-commerce and physical goods. Some businesses use both interchangeably. Pick one and use it consistently across your site, footer, and signup forms.

Can I copy another company's Terms of Service?

Bad idea. Different business models trigger different liability profiles, and copying mismatched language can leave you exposed. ToS is also typically copyrighted material — copying verbatim is a legal grey area. The right approach is to use a generator that asks for your specific business model, then have a lawyer review the limitation of liability and dispute resolution sections before publishing.

How long does a typical Terms of Service need to be?

2,000-3,000 words covers the 17 standard sections in plain English. Going shorter (under 1,500 words) usually means cutting sections you actually need (limitation of liability, indemnification). Going longer (over 4,000 words) often signals lawyer-written content that ordinary users won't read, which can be challenged in court as 'unconscionable' if hidden in dense legalese.

Do I need a lawyer to write Terms of Service?

Yes for review, no for first draft. A 30-minute lawyer review (typically $200-500) catches the four risk sections that matter: limitation of liability, indemnification, governing law, and dispute resolution. Generating the first draft yourself with a tool that covers all 17 standard sections then sending it for review is the most cost-efficient path.

Skip the 8 hours of legal writing

Free Terms of Service generator

All 17 sections in plain English. Adapts to SaaS, Shopify, mobile apps. Lawyer review still recommended.

Generate Terms of Service →

More from SwiftCopy

Keep exploring this topic

Keep the session moving with one related guide, one practical tool, and the broader library of workflows built around the same writing jobs.