The short version
- Two elements decide it: reasonably conspicuous notice of the terms, and an affirmative act that manifests agreement. Reading is not required and never has been.
- Clickwrap — an unticked box beside a visible link — is routinely enforced. Browsewrap, a footer link with no action, usually is not.
- Sign-in wrap ("by continuing you agree") sits in between and turns entirely on how visible the notice was at the moment of the click.
- Keep a record of which version each user accepted and when. Without it you can prove terms exist but not that this person agreed to these ones.
The test courts actually apply
Online terms are ordinary contracts, and the question is the ordinary contract question: did the parties agree? Courts have converged on two requirements. The user must have had reasonably conspicuous notice that terms existed and applied, and must have taken an affirmative act that unambiguously manifests assent to them.
Neither requirement involves reading. Failing to read a contract you signed has never been a defence, and the online cases follow the paper ones. What has changed is that in an online flow it is genuinely possible for a user never to have been shown that terms existed at all — and that is a defence, because it defeats notice.
How much assent each pattern actually captures
Footer link only
"By continuing you agree"
Unticked box beside a link
Box plus scroll-through and a stored record
Browsewrap: the pattern that mostly fails
Browsewrap makes the terms available through a link — usually in the footer — and asserts that continued use constitutes acceptance. The user does nothing. The argument is that the link was there to be found.
Courts treat this as presumptively unenforceable, because there is no way to establish that the user knew the terms existed. Analyses of the case law put the failure rate for browsewrap arguments somewhere north of eight in ten. The exceptions tend to involve sophisticated commercial parties in a repeated relationship, where actual knowledge can be inferred from the course of dealing — which is not the situation of a consumer signing up once.
Clickwrap: the pattern that works
Clickwrap requires the user to take a distinct, deliberate action indicating agreement — most commonly ticking a box that starts unticked, beside a sentence naming the terms and linking to them. Courts uphold it consistently, because both elements are satisfied and both are provable.
What makes a clickwrap flow hold up
- The checkbox starts unticked. A pre-ticked box is not an affirmative act, and under EU rules it is not consent at all.
- The agreement is named and linked in the sentence beside the box, not somewhere else on the page.
- The link is visually distinguishable — underlined or coloured — and opens the actual current terms.
- The notice sits next to the button the user is about to press, above the fold, not below it.
- The action button is unambiguous. "I agree" is stronger than "Continue".
- You store which version was accepted, by which account, at what timestamp — and you keep the superseded versions.
That last point is the one engineering teams skip. Terms change; disputes concern conduct from two years ago. Being able to produce the exact text a user accepted, and evidence that they accepted it, converts a plausible argument into a straightforward one. It is the same problem as proving an electronic signature, and it has the same answer: keep the record at the moment it is made.
Sign-in wrap, and the grey area most products live in
Sign-in wrap places a notice near the action — "By creating an account you agree to our Terms" — without a separate checkbox. The click on "Sign up" is the affirmative act, and the sentence beside it is the notice. Courts treat it as falling between the other two, and outcomes vary with the specifics.
Five interface details that decide a sign-in wrap case
The signup screen
Sign-in wrap is popular because a checkbox costs conversion. That is a real trade-off, and worth making deliberately rather than by default — the cost of the checkbox is a measurable conversion delta, and the cost of losing your terms is the entire agreement in the one dispute that matters.
Terms of service template
Full text, free to read and copy — acceptance, licence, acceptable use, liability, termination, changes and governing law, with the acceptance clause written to match a clickwrap flow.
Changing terms after people have agreed
A contract cannot usually be altered by one party alone, and "we may modify these terms at any time by posting a revised version" is exactly that. Clauses of this kind have been held illusory in a number of cases, sometimes taking the whole agreement with them.
- 1
Give notice through a channel they will see
Email to the account address, or an in-product message on next login. Publishing a new page and changing the date is notice to nobody.
- 2
Say what changed
A summary of the material changes, not only a new document. This is what makes acceptance meaningful rather than nominal.
- 3
Allow a period before it takes effect
Thirty days is a common and defensible default. Immediate effect on posting is the part that reads as unilateral.
- 4
Re-collect assent for material changes
For anything that changes the bargain — price, arbitration, liability, data use — put the box back and make them tick it again.
- 5
Give an exit
A user who does not accept should be able to stop using the service and, where they have paid, get the unused balance back. This is what makes the change consensual rather than imposed.
The clauses worth getting right
Assuming the terms are enforceable, a small number of clauses carry nearly all of the value. The rest is furniture.
| Clause | What it does | The common mistake |
|---|---|---|
| Limitation of liability | Caps exposure, usually at fees paid, and excludes indirect loss | Omitting the carve-outs that are unenforceable anyway, which can void the whole clause in consumer contracts |
| Licence to user content | Lets you host, display and transmit what users upload | Drafting it so broadly it reads as a rights grab, which generates a public problem rather than a legal one |
| Termination and suspension | Lets you remove abusive accounts without breaching | No stated grounds, no notice, and no way for a user to appeal — the shape regulators dislike |
| Governing law and forum | Decides where a dispute happens | Consumer protection rules in the user's home jurisdiction frequently override it anyway |
| Arbitration and class waiver | Routes disputes out of court | Requires very clear notice to survive, and mass individual arbitration has made it an expensive win in some sectors |
| Changes clause | Sets how the terms can be amended | "At any time, effective on posting" — the clause most likely to be held illusory |
What to do about the terms you already have
- Open your signup flow on a phone and screenshot it. That screenshot is the evidence in any future dispute — decide now whether you would want to produce it.
- Check whether the box, if there is one, starts unticked, and whether the link opens the live terms.
- Find out whether your system records the accepted version per user. If it does not, that is a small piece of work with a large payoff.
- Archive every superseded version with the dates it was live.
- Reread the changes clause. If it says you may amend at any time effective immediately, rewrite it — it is the single most commonly attacked provision in the document.
And if you are on the other side of this — a user, or a business being asked to accept someone else's terms — the same analysis runs backwards. How to read a contract applies without modification; online terms are just a contract you were not invited to negotiate.
Sources
General information, not legal advice. This guide explains how these documents and rules generally work. Law varies by jurisdiction and changes, and none of it is applied to your circumstances here. For anything consequential, consult a licensed attorney where you are.
Frequently asked
Are terms of service enforceable if the user never read them?
Yes, provided they had reasonably conspicuous notice and took an action manifesting agreement. Failure to read a contract has never been a defence. What defeats enforcement is a flow where the user was never meaningfully told the terms existed — which is why presentation, not drafting, decides most of these cases.
Is a pre-ticked checkbox good enough?
No. A pre-ticked box is not an affirmative act, so it fails the assent element, and under EU rules it is expressly not valid consent. It is also one of the clearest signals to a court that the flow was designed to obtain agreement without attention. Start it unticked.
Do I need a separate agreement for paying customers?
Usually yes, or at least a separate layer. Public terms of service handle account access and acceptable use. Payment, service levels, data processing and support commitments belong in a subscription or SaaS agreement with the customer, particularly where the buyer is a business that will want to negotiate.
Can I put the terms in a PDF?
You can, and it weakens you. A PDF adds a step between the notice and the text, renders badly on phones, and makes it harder to show what was live on a given date. Terms should be a normal, indexable web page with a visible last-updated date, with prior versions archived.
What happens if my terms are held unenforceable?
You fall back to whatever the general law provides, which is considerably worse for you. No liability cap, no exclusion of consequential loss, no chosen forum, no arbitration clause, and no express licence to the user content your product depends on displaying. The clauses do not fail individually — they fail together, because the agreement itself was never formed.