A clickwrap agreement is any contract a user accepts by clicking “I agree”: the checkbox on signup, the button before install, or the prompt before checkout. It sounds like a formality. In court, it isn’t. How you present that click decides whether the agreement holds up at all.
In litigation tracked through 2020, clickwrap agreements won enforcement 70% of the time. Sign-in-wrap came in at 64%. Browsewrap, where terms are linked in a footer with no click required, won only 14%. That gap is the whole argument for building your acceptance flow correctly the first time.
Key Takeaways
-
Clickwrap wins in court roughly five times more often than browsewrap.
-
Courts test two things: did the user get reasonable notice, and did they take an unambiguous action to agree?
-
A EULA, a SaaS agreement, or a Terms of Service can all be presented as clickwrap. The format is independent of the document type.
-
The most common enforceability failure isn’t bad legal language. It’s a weak or missing acceptance flow.
What Makes an Agreement “Clickwrap”
The user sees the terms, or a clear link to them, and has to take a specific action such as checking a box or clicking “I agree” before moving forward. If they decline, they can’t continue. That’s the whole mechanism.
Contrast that with a browsewrap agreement: terms sit behind a footer link, and using the site is treated as agreement, with no click required. A sign-in-wrap agreement places the terms near a signup or login button, but the user isn’t forced to interact with them directly before proceeding.
Courts don’t treat these as interchangeable. They ask two questions: did the user get reasonable notice of the terms, and did they take an unambiguous action showing they agreed? Clickwrap answers both clearly. Browsewrap answers neither because nobody had to see the terms, let alone act on them.
Why Browsewrap Keeps Losing in Court
A browsewrap agreement assumes a user read something they were never asked to look at. That assumption is exactly what falls apart in litigation. A defendant can credibly argue they never saw the terms at all, and there’s no click, checkbox, or timestamp proving otherwise.
Clickwrap removes that argument entirely. The user’s click is a timestamped, logged action tied to a specific version of the terms. That evidence trail is why clickwrap holds up far more consistently. It isn’t that judges favor the format on principle; clickwrap actually satisfies the notice-and-assent test that browsewrap was never built to pass.
Building an Acceptance Flow That Holds Up
A checkbox alone doesn’t guarantee enforceability. Courts have struck down clickwrap flows too, usually for the same handful of reasons:
-
The terms link wasn’t visible before the click. If the user has to scroll or hunt to find what they’re agreeing to, notice is weak.
-
The checkbox was pre-checked. Pre-checked boxes don’t demonstrate an affirmative choice. Courts can read that as no real assent at all.
-
The language buried what was being agreed to. “By continuing, you agree to updates to our terms” is vaguer than a direct “I agree to the Terms of Service.”
-
There’s no record of which version was accepted. If your terms change later, you need to prove which version this specific user agreed to and when.
The fix for all four is procedural, not legal: show the terms or a clear link directly above the action, require an active click, leave nothing pre-checked, and log the timestamp and version.
Where This Applies: EULAs, ToS, and SaaS Agreements
Clickwrap isn’t a document type. It’s a delivery method. A EULA can be clickwrap. A SaaS subscription agreement can be clickwrap. Terms of Service almost always is. The document defines what’s being agreed to; the acceptance flow determines whether that agreement is enforceable if it’s ever challenged.
That’s the connective thread across a EULA, a SaaS agreement, and clickwrap mechanics: get the document type right, and it still won’t protect you if the acceptance flow doesn’t hold up. Get the acceptance flow right, and a poorly drafted document still won’t protect you either. Both pieces have to work together.
Structuring both the document and the acceptance flow so they actually hold up in a dispute is what our SaaS & Tech Product Legal practice handles for clients directly.
Frequently Asked Questions
-
Is a checkbox enough, or does it need a separate “Submit” click?
A checkbox alone can work if it’s clearly tied to the terms and not pre-checked. Many companies pair it with a separate confirmation step for higher-value agreements, such as enterprise contracts or paid subscriptions, to strengthen the evidence trail.
-
Do I need users to re-accept terms after an update?
For material changes, yes. Courts have repeatedly found that continuing to use a service isn’t the same as agreeing to new terms unless the user affirmatively re-accepted them.
-
Is browsewrap ever acceptable?
Rarely as the sole method. Some companies use it for low-stakes policies, such as a general site disclaimer, but rely on clickwrap for anything that actually needs to be enforced, including a EULA, a subscription agreement, or a Terms of Service.
Conclusion
The document matters, but the click matters just as much. A well-drafted EULA or SaaS agreement can still fail in court if nobody can prove the user actually agreed to it. Build the acceptance flow with the same care as the document itself: visible terms, an active click, no pre-checked boxes, and a logged version and timestamp.
