End-User Software License Agreement B2C Template

In plain language: Identifies the software publisher as licensor and the end user as licensee, states the name and version of the software being licensed, and confirms the agreement governs all use.

Common mistake: Using a brand name instead of the publisher's registered legal entity. If the licensor entity is wrong, enforcing IP ownership or injunctive relief against infringers becomes procedurally complicated.

In plain language: States exactly what the user may do with the software — typically a non-exclusive, non-transferable, personal-use license to install on a defined number of devices.

Common mistake: Omitting a device-count limit. Without it, a single license purchase can be interpreted as unlimited installations, undermining per-seat or per-device revenue models.

In plain language: Prohibits activities that would harm the publisher's rights — copying, sublicensing, reverse engineering, modifying, distributing, or using the software for commercial purposes without authorization.

Common mistake: Failing to explicitly prohibit commercial use when the license is personal only. Absent this language, a user may resell access or use the software in a revenue-generating context and argue the EULA permitted it.

In plain language: Confirms the publisher owns all IP in the software and that the license grants usage rights only — not title, copyright, or any ownership interest.

Common mistake: Using vague language like 'all rights reserved' without explicitly stating what the user receives. Courts have interpreted ambiguous grants more broadly than the publisher intended.

In plain language: States the software is provided 'as is' with no warranties — express or implied — including no guarantee of merchantability, fitness for a particular purpose, or error-free operation.

Common mistake: Failing to use all-caps formatting for warranty disclaimers in US consumer contracts. Several state courts have held that warranty disclaimers buried in normal body text are not conspicuous enough to be enforceable against consumers.

In plain language: Caps the total financial exposure of the publisher to the amount the user paid for the software in the prior 12 months, and excludes consequential, incidental, and punitive damages.

Common mistake: Setting the liability cap to zero or a nominal amount (e.g., $1). Consumer protection statutes in the EU, UK, and several US states prohibit limiting liability for personal injury or death caused by negligence — and courts often void the entire cap if it is set unreasonably low.

In plain language: Discloses that the software may collect usage data, diagnostic information, or personal data, and directs the user to the publisher's Privacy Policy for details.

Common mistake: Omitting this clause entirely. In jurisdictions subject to GDPR, CCPA, or PIPEDA, collecting any user data without a disclosed legal basis and a linked privacy policy exposes the publisher to regulatory fines.

In plain language: Authorizes the publisher to push automatic updates, patches, or version changes to the software and confirms that updated versions remain subject to the same agreement or any superseding terms.

Common mistake: Not addressing what happens when the EULA terms change with an update. Without explicit language, users can argue the original terms remain in force indefinitely regardless of changes to the software.

In plain language: States the license is effective until terminated, describes the events that trigger termination (breach, non-payment, or publisher's discretion for perpetual licenses), and specifies what happens on termination — typically deletion of all copies.

Common mistake: Requiring notarized written certification of deletion. This is unenforceable against consumers and creates unnecessary friction. A simple obligation to delete, without a certification requirement, is both more enforceable and more reasonable.

In plain language: Specifies which jurisdiction's law governs the agreement and how disputes are resolved — arbitration, small claims court, or litigation — along with any class-action waiver.

Common mistake: Including a class-action waiver without checking its enforceability in the governing jurisdiction. Class-action waivers are unenforceable against consumers in the EU and several US states, and an unenforceable clause can taint related arbitration provisions.

A B2C EULA is a legally binding contract between a software publisher and an individual consumer that governs how the consumer may install, use, and copy the software. Unlike a B2B software license — which assumes a sophisticated business counterparty — a B2C EULA must account for mandatory consumer protection rights that cannot be waived by contract, including statutory warranty rights and cooling-off periods in many jurisdictions. It establishes IP ownership, defines permitted use, disclaims warranties, and limits the publisher's liability.

A EULA is generally enforceable when the consumer had a meaningful opportunity to read it and affirmatively agreed — typically through a clickwrap mechanism where the user checks an 'I Agree' box before installation. Courts in the US, UK, and EU have struck down EULAs presented in ways that did not give consumers a fair chance to review the terms. Additionally, clauses that violate mandatory consumer protection laws — such as waivers of statutory warranty rights in the EU — are unenforceable regardless of what the EULA says.

A EULA governs the license to use locally installed software — a desktop app, game client, or downloaded tool. A Terms of Service (ToS) governs the use of a web-based service or online platform accessed through a browser. Many software products have both: a EULA for the installed client and a ToS for the associated online account or cloud features. If your software is entirely cloud-based with no local installation, a ToS or SaaS Subscription Agreement is typically more appropriate than a standalone EULA.

Yes. Apple App Store and Google Play impose their own platform terms, but those terms govern the relationship between the platform and the user — not between you as the publisher and the end user. Without a publisher-specific EULA, you have no contractual basis to restrict reverse engineering, prohibit redistribution, assert IP ownership, or limit your liability to the end user. Both app stores allow — and effectively require — publishers to link to their own EULA within the app listing or at first launch.

Clickwrap acceptance occurs when a user actively checks a box or clicks a button labeled 'I Agree' or 'Accept' before installing or using the software, with the EULA text or a link to it displayed nearby. Courts in the US and EU consistently enforce clickwrap agreements because the user took an affirmative action demonstrating assent. Pre-checked boxes, implicit acceptance by installation alone (shrinkwrap), or acceptance buried in a multi-step flow without a visible link to the EULA are significantly more vulnerable to challenge.

No. Setting a liability cap of zero is likely unenforceable against consumers in most jurisdictions. The EU Unfair Contract Terms Directive, the UK Consumer Rights Act 2015, and several US state consumer protection statutes prohibit liability exclusions that are unconscionable or that deprive consumers of legal remedies for harm caused by a publisher's negligence. A more defensible approach for free software is a nominal cap (e.g., $50 USD) paired with a clear disclaimer that the software is provided without charge.

Yes, if you collect any personal data from users in the EU or UK, GDPR and UK GDPR apply regardless of whether you are based in the EU. The EULA itself should reference your Privacy Policy and obtain consent for data collection where required. The Privacy Policy — linked from the EULA — must identify what data is collected, the legal basis for processing, retention periods, and user rights. Failure to comply can result in fines of up to 4% of global annual turnover under GDPR.

Under most EULAs, continued use of the software after a EULA update constitutes acceptance of the new terms, provided the user received reasonable notice of the changes. Best practice is to notify users in-app and require a fresh clickwrap acceptance for material changes — such as new data collection practices, a new arbitration clause, or changes to permitted use. For EU consumers, certain material changes may require affirmative consent rather than implied acceptance.

A single EULA with a well-drafted global carve-out clause is a practical approach for most independent developers and small publishers. The carve-out should state that mandatory local consumer protection laws apply to consumers in jurisdictions where contractual waiver is prohibited. For publishers with significant user bases in the EU, UK, or Australia, having a qualified attorney review the EULA for compliance with those specific consumer law regimes is worthwhile before launch.