Your software is live, users are signing up, and somewhere in the onboarding flow sits a license agreement you drafted two years ago. Then a dispute arises. A user redistributes your code, scrapes your database, or files a class action claiming your liability cap is void. You pull up your End User License Agreement expecting protection, only to discover a court considers it unenforceable because of how it was presented, not what it said.
This scenario plays out more often than most founders realize. Courts have grown increasingly skeptical of software license agreements that fail basic formation requirements. The Ninth Circuit’s 2025 decision in Chabolla v. ClassPass Inc. made this painfully clear: if users lack reasonably conspicuous notice and their acceptance action does not unambiguously manifest assent, your agreement holds no weight. Understanding the enforceable EULA requirements courts demand is no longer optional for software companies that want their terms to survive judicial scrutiny.
Below is a practical breakdown of what courts actually examine when deciding whether a EULA binds the user, and where software companies consistently fall short.
How Courts Determine Whether a EULA Is Enforceable
A EULA is a contract. For any contract to be valid, courts require mutual assent, consideration, and terms that are not unconscionable. In the software context, this translates into four elements judges evaluate:
- Reasonable notice: The user must have been presented with the terms (or a clear link to them) before or during the acceptance action.
- Affirmative assent: The user must take a deliberate step that indicates agreement, such as clicking “I Agree” or checking a box.
- Opportunity to review: Terms must be accessible and readable before the user commits.
- Consideration: Something of value must be exchanged. Typically, the user receives software access in return for compliance with the license restrictions.
When any of these elements is missing or deficient, the entire agreement can be voided. The question of EULA enforceability is not about the substance of individual clauses. It begins with whether the agreement was properly formed in the first place.
Clickwrap, Browsewrap, and Sign-In Wrap: Why Presentation Method Matters
Courts categorize online agreements by how they are presented to users. The method you choose directly determines your enforceability odds.
Clickwrap Agreements
Clickwrap requires users to take an affirmative action (clicking a button or checking a box) after being shown the terms or a conspicuous link to them. Courts enforce clickwrap agreements at a rate of approximately 70%. The Second Circuit upheld this approach in Meyer v. Uber Technologies (2017), finding that the signup process directed users to terms with sufficient conspicuousness for constructive notice.
Browsewrap Agreements
Browsewrap places a hyperlink to terms somewhere on the page (often the footer) and considers continued use as acceptance. Courts enforce these at roughly 14%. In Specht v. Netscape Communications Corp. (2d Cir., 2002), the court invalidated a license agreement where the link to terms sat below the download button, outside the user’s natural line of sight.
Sign-In Wrap Agreements
Sign-in wrap places a notice near the login or registration button stating that by signing up, the user agrees to terms linked nearby. This hybrid approach has faced increased scrutiny. In Chabolla v. ClassPass (9th Cir., 2025), the court held that a sign-in wrap failed because the advisory text appeared in small gray font outside the user’s natural flow and did not correspond to the action button text.
The takeaway: clickwrap remains the safest formation method. If you are using anything less than an explicit “I Agree” button tied to conspicuous terms, you are taking a calculated risk with enforceability.
Essential Clauses That Must Appear in Every Software EULA
Even a properly formed EULA fails its purpose if it lacks critical provisions. The following clauses form the structural foundation of a well-structured agreement.
License Grant and Scope
Define exactly what the user is receiving. Specify whether the license is non-exclusive, non-transferable, revocable, and limited to specific devices or user counts. Ambiguity here invites disputes over what the user is permitted to do with your software.
Use Restrictions
Prohibit reverse engineering, decompilation, unauthorized copying, redistribution, and sublicensing. Without explicit restrictions, users may argue that any use not specifically forbidden is permitted.
Intellectual Property Ownership
Assert that you retain all ownership rights to the software, code, trademarks, and copyrights. Clarify the ownership status of any content users create within your platform. An experienced terms and conditions lawyer can help distinguish between platform IP and user-generated content rights.
Limitation of Liability
Cap your maximum liability exposure. Common approaches include limiting damages to the amount the user paid in the preceding 12 months or a fixed dollar amount. Be cautious: courts may strike caps that are nominal relative to the potential harm, particularly for consumer-facing software.
Termination Provisions
Specify the conditions under which the license ends (breach, non-payment, at-will termination) and what happens to user data after termination. Include a reasonable data export window if you handle customer information.
Dispute Resolution
Include choice of law, forum selection, and (if applicable) arbitration clauses. However, arbitration provisions must be conspicuous. In Sgouros v. TransUnion Corp. (7th Cir., 2016), the court refused to enforce an arbitration clause because the “I Accept” button did not adequately direct the user’s attention to the arbitration terms buried within the agreement.
Data Handling and Privacy
Address what data you collect through the software, how it is stored, whether third parties access it, and how your practices align with applicable privacy regulations. This clause should reference (or link to) your full privacy policy.
The Unconscionability Trap: When Courts Strike Down One-Sided Terms
Courts apply a two-part unconscionability analysis to determine whether specific EULA provisions are too one-sided to enforce:
- Procedural unconscionability: Was there unequal bargaining power? Was the agreement presented as take-it-or-leave-it with no opportunity for negotiation? Were key terms hidden in dense formatting?
- Substantive unconscionability: Are the terms unreasonably favorable to one party? Examples include unilateral modification clauses, mandatory arbitration in distant venues, overly broad IP licenses over user content, or liability caps set at trivially low amounts.
In Bragg v. Linden Research, Inc. (E.D. Pa., 2007), the court found Second Life’s terms of service both procedurally and substantively unconscionable. The arbitration clause was buried in a dense paragraph under “General Provisions” with no formatting to draw attention, and the costs of arbitration were not disclosed. The court refused to compel arbitration.
The lesson: even if your EULA is properly formed with clickwrap consent, individual clauses can still be severed or voided if they cross the unconscionability threshold.
Auto-Renewal and Subscription Terms Under New State Laws
If your software operates on a subscription model, your EULA must account for California’s updated Automatic Renewal Law (AB 2863), effective July 1, 2025. The requirements are specific:
- Express affirmative consent to auto-renewal terms before the initial charge
- Mandatory retention of consent records for three years (or one year post-termination, whichever is longer)
- 15 to 45 days advance notice before renewal for subscriptions lasting one year or longer
- Cancellation must be available in the same medium as enrollment
- Free-to-paid conversions now fall within the statute’s expanded scope
At the federal level, the FTC continues enforcement under Section 5 authority regarding deceptive subscription practices. While the formal Click-to-Cancel Rule faced procedural challenges in 2025, the underlying enforcement posture remains active. A qualified SaaS agreement lawyer can ensure your renewal provisions satisfy both state and federal requirements simultaneously.
Common Mistakes That Undermine Enforceability
After reviewing hundreds of software license disputes, certain failure patterns repeat across companies of every size:
- Presenting terms after purchase: EULAs shown only after payment carry significantly less weight. Courts expect users to review and accept terms before committing money or accessing the product.
- Excessive length without structure: A 15,000-word agreement with no headings, no formatting, and no summary creates a procedural unconscionability argument. Courts note when terms are designed to discourage reading.
- Stale agreements: Failing to update your EULA as the software evolves or new regulations take effect leaves gaps that users (and their attorneys) will exploit.
- Browsewrap-only presentation: Burying your license link in a page footer without any acceptance mechanism is the single most common enforceability failure.
- Missing data handling provisions: In 2026, a EULA without data processing terms is incomplete. Privacy regulators and courts both expect this coverage.
- Overly restrictive terms: Clauses prohibiting users from posting reviews, taking screenshots, or discussing the software publicly invite unconscionability challenges and regulatory attention.
How to Strengthen Your EULA Formation Process
Beyond the document itself, your implementation process determines enforceability. Consider these practical steps:
- Use clickwrap with a dedicated checkbox or button. The “I Agree” action must be separate from the general signup or purchase action.
- Make terms conspicuous. Use contrasting colors, adequate font size, and placement within the user’s natural visual flow. The Chabolla ruling specifically penalized gray text on a white background.
- Timestamp and log consent. Maintain records showing which version of the EULA each user accepted, when they accepted it, and through what mechanism.
- Version your agreements. When you update terms, notify existing users and obtain fresh consent for material changes. Silent updates to a live agreement weaken your position.
- Provide a downloadable or printable copy. Courts view accessibility favorably. Let users save a copy for their records.
- Separate critical clauses visually. If your agreement includes arbitration, liability caps, or IP assignments, set them apart with bold headings or separate acknowledgment steps.
Frequently Asked Questions
What is the difference between a EULA and Terms of Service?
A EULA specifically governs the use of licensed software, covering installation, copying, and modification rights. Terms of Service are broader agreements that govern access to a website or online platform. Many SaaS companies combine elements of both into a single agreement, but the licensing provisions (IP ownership, use restrictions, reverse engineering prohibitions) are what distinguish a EULA from general website terms.
Can a EULA be enforced if the user did not read it?
Yes, provided the user had reasonable notice and opportunity to read it before taking an affirmative acceptance action. Courts do not require proof that the user actually read every word. They require proof that the terms were conspicuously presented and the user voluntarily clicked “I Agree” or equivalent. This is why clickwrap formation is so important.
Does a EULA need to be signed to be legally binding?
No. Under the Electronic Signatures in Global and National Commerce Act (E-SIGN) and the Uniform Electronic Transactions Act (UETA), clicking an “I Agree” button constitutes a valid electronic signature. Physical signatures are not required for software license agreements.
How often should a company update its EULA?
Review and update your EULA at least annually, or whenever you make significant changes to your software’s functionality, data practices, or pricing model. Regulatory changes (such as new state privacy laws or FTC guidance) also trigger the need for updates. Each update should be accompanied by user notification and fresh consent for material changes.
Can a court strike down only part of a EULA?
Yes. Courts regularly sever unconscionable or illegal provisions while leaving the remainder of the agreement intact. This is why most EULAs include a severability clause stating that if any provision is found unenforceable, the remaining terms survive. Without a severability clause, one bad provision could theoretically void the entire agreement.
Are EULAs enforceable internationally?
Enforceability varies significantly by jurisdiction. While US courts generally enforce properly formed clickwrap EULAs, the European Union imposes additional consumer protection requirements that can override certain clauses (particularly mandatory arbitration and broad liability exclusions). Your choice-of-law and forum selection clauses help determine which jurisdiction’s rules apply, but they cannot override mandatory consumer protections in the user’s home country.
Protect Your Software With a EULA Built to Hold Up
The gap between a EULA that exists and one that actually protects your business is wider than most software companies assume. Formation method, clause structure, regulatory compliance, and presentation design all feed into whether a court will enforce your agreement when it matters. Meeting the enforceable EULA requirements courts and regulators expect takes deliberate legal strategy, not a template downloaded from the internet.
If your current license agreement has not been reviewed against recent case law and state regulatory changes, it may already contain gaps that would surface in a dispute. TOS Lawyer works exclusively with technology companies on software licensing, terms of service agreements, and SaaS contracts. Book a consultation to get a professional assessment of whether your EULA meets current enforceability standards.