How to Create an Enforceable Clickwrap Agreement

To create an enforceable clickwrap agreement, you need to give users conspicuous notice that terms exist, require an unmistakable act of acceptance before they can proceed, keep the terms themselves lawful and reasonable, and preserve a record that ties a specific user to a specific version of the terms at a specific moment. Federal law treats that electronic consent the same as a handwritten signature, so the legal foundation is solid.¹ The details of presentation and record-keeping decide whether the agreement holds up or collapses the first time someone challenges it.

The Two-Part Test Courts Actually Apply

Electronic validity is the starting point, not the finish line. The Electronic Signatures in Global and National Commerce Act, together with the Uniform Electronic Transactions Act adopted in 49 states plus the District of Columbia, means an online agreement cannot be denied effect simply because nothing was signed on paper.¹

Beyond that, ordinary contract law applies. Courts ask two questions. Did the user receive reasonably conspicuous notice that terms existed? And did the user clearly manifest agreement to those terms? The Second Circuit has articulated this standard directly: “reasonably conspicuous notice” and “unambiguous manifestation of assent” are both required for an enforceable online agreement. Miss either one and the agreement fails. Every design and drafting choice below exists to satisfy those two elements.

Browsewrap, the approach that buries a hyperlink to terms somewhere on the page and assumes continued use equals acceptance, fails the notice element. The Ninth Circuit struck down Barnes & Noble’s browsewrap even though a hyperlink appeared on every page, holding that a conspicuous hyperlink alone, without prompting any affirmative action from the user, is not enough.² A clickwrap works because it forces the user to do something affirmative first.

Designing the Acceptance Screen

The Second Circuit’s analysis of Uber’s registration screen reads like a design checklist. The court upheld Uber’s agreement because the payment screen was uncluttered, the notice appeared directly below the registration button in dark print against a white background, the hyperlinks to the terms were blue and underlined, and the entire screen was visible without scrolling. The court specifically noted that the notice was both “spatially coupled” with the registration button and “temporally coupled” with enrollment, meaning the user encountered the terms at the exact moment they were creating an account.³

Translate that into concrete rules for your interface:

Place the terms notice immediately adjacent to the action button, within the same visual block. If a user has to scroll past the button to find the terms reference, you have created the same gap that sinks browsewrap.
Make the hyperlinks visually distinct. Blue, underlined text is the web convention and courts look for it. A link that blends into surrounding text will not satisfy the conspicuous notice standard.
Keep the screen uncluttered. Competing graphics and dense marketing copy undermine the argument that a user noticed the terms.
Use explicit acceptance language. “I agree to the Terms of Service” leaves no ambiguity. Vague labels like “Continue” or “Next” do not communicate that a binding agreement is being formed.
Require an unchecked box or a dedicated acceptance button. Pre-checked boxes are risky because they do not demonstrate a deliberate choice, even though at least one court has upheld them in narrow circumstances. An unchecked box the user must actively select is the safer approach by a wide margin.
Make the full terms viewable before acceptance, whether in a scrollable text box on the same page, a pop-up window, or a new tab. The user needs a genuine opportunity to read them.

Timing matters almost as much as placement. Present the agreement at a moment of meaningful commitment: account registration, checkout, or activation of a new feature. Agreements that appear after a user has already begun using the service are harder to enforce because the user arguably never consented before entering the relationship.

Avoiding Dark Patterns

The FTC has made clear that manipulative interface design can violate federal law even when the underlying terms are reasonable, because consent extracted through manipulation is not real consent. The agency requires businesses to disclose all material terms clearly and conspicuously, obtain express informed consent before charging consumers, and provide cancellation mechanisms at least as easy as sign-up.⁴ Practices the FTC has flagged as subverting consumer autonomy include graying out the privacy-protective option so it looks inactive, confusing double negatives like a “Do Not Sell My Information” toggle set to “off,” burying material terms in dense surrounding text, repeatedly prompting users to reconsider a choice they already made, and pre-checking boxes for data collection or marketing.⁵

If your clickwrap governs a subscription or recurring charge, the FTC’s amended Negative Option Rule adds specific requirements. Cancellation must be available through the same medium the customer used to sign up. If someone subscribed online, they must be able to cancel online without being routed to a phone representative. Charge and cancellation information must appear right when and where the customer agrees, not buried in the full terms document.⁶

Drafting Terms That Won’t Be Struck Down

A perfectly designed acceptance screen cannot save terms that courts or regulators will refuse to enforce. Two categories deserve particular attention.

Federally Prohibited Clauses

The Consumer Review Fairness Act makes it illegal to include any provision that restricts a customer’s ability to post honest reviews, imposes a penalty for posting a review, or claims ownership of the intellectual property in a customer’s review content.⁷ These provisions are void from the moment the contract is formed, and even including them in your terms with no intention of enforcing them violates federal law.⁸ If your current terms contain a non-disparagement clause aimed at customers, remove it.

Unconscionable Clauses

Courts analyze unconscionability on two dimensions. Procedural unconscionability looks at the bargaining process, and clickwrap agreements are inherently take-it-or-leave-it, so courts already approach them with some skepticism on that front. That makes the substantive side more important. Patterns courts have struck down include:

One-sided power imbalances, such as letting the business freeze accounts, seize funds, or investigate a user’s financial records without comparable constraints running the other direction.
Silent unilateral modification, meaning the right to change terms at any time without notice simply by posting an updated version.
Prohibitions on combining claims, which block users from aggregating when individual amounts are too small to justify standalone arbitration.
Excessive arbitration costs, where filing fees exceed the amount in dispute, pricing consumers out of their own claims.

Courts look at the practical effect, not the words. A clause that technically permits arbitration but costs more than the claim is worth functions as a ban, and courts treat it that way.

Updating Terms Without Losing Enforceability

Launching a clickwrap is the easy part. Updates are where companies lose. Simply posting revised terms on the website is not enough; the Ninth Circuit has held that parties have no obligation to periodically check whether the other side has changed the terms. Email notice is better but still precarious when the company cannot prove the user opened the email, the revised terms were not presented inside the product, and nothing required affirmative agreement.

The approach that consistently survives judicial scrutiny is an interstitial screen inside your app or website, sometimes called a blocker card, that prevents further use until the user clicks through a fresh acceptance flow. One court upheld a modification using this method after rejecting the company’s email notice, because the in-product screen required the user to click “I agree” and the company could prove the user’s own login credentials were used to accept.

Four conditions make unilateral modifications more defensible:

Your original terms expressly reserve the right to modify with notice.
You give conspicuous advance notice before changes take effect, ideally through multiple channels including an in-product prompt.
Changes apply prospectively, not retroactively. Courts have called retroactive modification clauses “illusory” because they let one party rewrite the deal after the fact.
Users can reject the new terms by discontinuing use, and your notice says so clearly.

For material changes such as adding an arbitration clause or altering liability limitations, the only approach that reliably holds up is requiring every active user to re-accept through a fresh clickwrap flow.

The Acceptance Record You’ll Need in Court

Your agreement is only as strong as your ability to prove a specific user accepted a specific version of the terms at a specific time. In litigation, the opposing side’s first move is almost always to argue they never agreed. Your logging system is what defeats that argument.

Capture at minimum, for every acceptance event:

A user identifier, such as account ID or email address, tied to the accepting user.
The exact timestamp, stored in a consistent time zone format; UTC is standard.
The IP address from which the acceptance originated.
A version identifier that references the exact document the user accepted, not just “Terms of Service” but “Terms of Service v3.2, effective March 15, 2026.”
Device metadata such as browser type, operating system, and screen resolution, which corroborates that a real user interaction occurred.

Version control deserves separate attention. Every iteration of your terms should be stored as a separate, immutable document, with the old versions archived and still linked to the users who accepted them. A cryptographic hash of each version, using a standard algorithm like SHA-256, provides a tamper-proof way to verify that the document you produce in court is identical to what the user originally saw. If opposing counsel argues you altered the terms after the fact, the hash disproves it.

Integrate acceptance logging with your authentication system so every record ties back to a verified account. The FTC’s negative option rule requires at least three years of retention for subscription services, but for general clickwrap records, retaining them for the length of the user relationship plus any applicable statute of limitations is the more prudent standard.⁶

Two Situations a Standard Clickwrap Does Not Cover

If your service collects personal information from children under 13, a clickwrap with the child alone is legally insufficient. The Children’s Online Privacy Protection Act requires verifiable parental consent before collecting, using, or disclosing a child’s personal data, through a method “reasonably designed in light of available technology to ensure that the person giving the consent is the child’s parent.”⁹ A child clicking “I Agree” does not satisfy that standard; a separate parent-directed consent mechanism is required.

Accessibility is the other blind spot. A clickwrap that relies entirely on mouse clicks, visual cues, and small text can be inaccessible to users with visual or motor impairments, and if such a user cannot meaningfully interact with your acceptance flow, arguing they consented becomes difficult. The DOJ’s 2024 web accessibility rule requiring WCAG 2.1 Level AA compliance applies to state and local governments, but whether the ADA reaches private commercial websites remains an active area of litigation, and multiple courts have extended Title III’s public accommodation requirements to them. At minimum, ensure your acceptance mechanism works with keyboard navigation and screen readers, that form fields have proper labels, and that color contrast meets WCAG 2.1 AA. The implementation cost is low and the enforceability payoff is significant.

1
Office of the Law Revision Counsel. 15 USC 7001 – General Rule of Validity
2
U.S. Court of Appeals for the Ninth Circuit. Nguyen v. Barnes and Noble Inc.
3
Justia Law. Meyer v. Uber Technologies Inc., No. 16-2750
4
Federal Trade Commission. FTC to Ramp Up Enforcement Against Illegal Dark Patterns That Trick or Trap Consumers Into Subscriptions
5
Federal Trade Commission. Bringing Dark Patterns to Light – FTC Staff Report
6
Federal Trade Commission. Click to Cancel – The FTC’s Amended Negative Option Rule and What It Means for Your Business
7
Office of the Law Revision Counsel. 15 USC 45b – Consumer Review Protection
8
Federal Trade Commission. Consumer Review Fairness Act – What Businesses Need to Know
9
Federal Trade Commission. Verifiable Parental Consent and the Children’s Online Privacy Rule