Why nobody reads your Terms of Service (and what to do about it)
Nearly everyone who signs up for an online product clicks past the Terms of Service without reading a word of it. This isn't a secret, and it isn't unique to any one company — it's just how people use the internet. The natural next question for anyone running a small SaaS product or online business is: if nobody reads it, does it even matter what's in there?
Unread doesn't mean unenforceable
A Terms of Service someone never read can still bind them, under the general legal concept of "clickwrap" agreements — where a user actively clicks "I agree" (or an equivalent action) before using a service. Courts have generally enforced these, on the theory that the user had a reasonable opportunity to read the terms and chose to proceed regardless. This is different from "browsewrap," where terms are simply linked somewhere on a site with no explicit acceptance step — courts have been considerably more skeptical of browsewrap enforceability, since there's no clear moment where the user did anything indicating they agreed to anything.
Enforceability specifics vary by jurisdiction and by how a particular court has ruled on a particular presentation, so this isn't a guarantee that any clickwrap flow is automatically bulletproof. But the general pattern holds broadly: a clear, affirmative acceptance step matters more for enforceability than whether the user actually read the text underneath it.
What actually needs to hold up in a small business ToS
Given that almost nobody reads the full document, the handful of clauses that actually get tested — in a dispute, a refund request, or an outage — deserve more attention than the rest combined:
- Limitation of liability — what the business is and isn't responsible for if something goes wrong, and a cap on damages if the worst case happens
- What happens if the service goes down — whether there's any credit, refund, or guarantee tied to uptime, and what counts as the business's responsibility versus a third-party outage outside its control
- How disputes get resolved — whether disagreements go to arbitration, small claims, or standard litigation, and where (which matters a lot if the business and the customer are in different states or countries)
- How the terms themselves can change — most services reserve the right to update their ToS, but how much notice users get, and whether continued use counts as acceptance of the new version, varies a lot between services and matters if a court ever asks whether a change was properly communicated
Everything else — a friendly intro paragraph, a restatement of what the product does, boilerplate definitions — is filler that doesn't do much work in an actual dispute. It's fine to include for clarity, but it's not where the legal weight sits.
Plain language matters more than it sounds like it should
There's a temptation to write a ToS in dense legal language on the theory that it sounds more official or more protective. In practice, courts examining clickwrap enforceability have sometimes scrutinized not just whether a user clicked "agree," but whether the terms were presented in a way a reasonable person could actually notice and understand — tiny font, a link buried at the bottom of an unrelated page, or terms that contradict what the product's marketing plainly claims can all work against a business trying to rely on those terms later. A ToS that's genuinely readable — short sentences, plain words, headers that describe what each section covers — isn't just friendlier to users. It's also harder to argue was hidden or deceptive if it's ever challenged.
What belongs in a ToS vs. a Privacy Policy
Small businesses frequently combine these into one document, or write one and assume it covers both purposes. They answer different questions and often need to be treated separately:
- Terms of Service — the rules for using the product itself: what's allowed, what's prohibited, payment terms, liability limits, termination rights, and how disputes are handled. It's a contract governing the relationship between the business and the user.
- Privacy Policy — what personal data the business collects, why, how it's stored, who it's shared with, and what rights a user has over their own data. In many jurisdictions this is a legal disclosure requirement, not just good practice, separate from any contractual terms about product usage.
A user disputing a refund is a Terms of Service question. A user asking what happens to their email address after they delete their account is a Privacy Policy question. Keeping the two documents distinct — even if they're linked from the same signup page — makes it clearer which rules apply to which kind of issue, for the business and the user alike.
Getting terms actually agreed to
However carefully a ToS is written, it still needs a clean record that a specific version was presented and accepted by a specific user at a specific time — especially if terms change later and a dispute hinges on which version applied. A signed acknowledgment tied to a timestamp and an audit trail gives a business something concrete to point back to, rather than relying on a checkbox log buried in a database that's hard to explain outside an engineering team.
Frequently asked questions
Can I just copy another company's Terms of Service?
It's a common shortcut, but a copied ToS often includes clauses that don't apply to your actual product or business model, and won't reflect your specific liability concerns, refund policy, or dispute process. It's a reasonable starting point for structure, not a substitute for terms written for your own situation.
How often should a Terms of Service be updated?
Whenever the underlying product, pricing, or policies materially change — there's no fixed schedule. What matters more than frequency is having a clear process for notifying users of changes and recording when each version took effect.
Does a ToS need to be reviewed by a lawyer?
For a low-stakes product with minimal liability exposure, a carefully written general-purpose template can be a reasonable starting point. It's worth paying for legal review once real money, sensitive data, or meaningful liability risk is involved — the cost of a bad limitation-of-liability clause tends to far exceed the cost of having it checked.
Is a clickwrap agreement always enforceable?
Not automatically — enforceability depends on the terms being reasonably presented and the acceptance step being clear and unavoidable, and it can still vary by jurisdiction and by the specific facts of a case. It's a meaningfully stronger position than browsewrap, but "always enforceable" overstates it.
Why teams start with Docracy
“Docracy is a great product that I have tested and am using. It is easy to use, has good tools, is always up to date, and implements new features. Highly recommended.”— DACH Advisory
Also: Compare e-sign pricing · Free mutual NDA template
No account required for up to 2 signers.