EULA stands for End User License Agreement. It is the contract between a software maker and the person or business using the software, and it sets out what the user may and may not do with it. The key idea is that the user gets a license to use the software, not ownership of it.
You usually accept a EULA by clicking "I agree" when you install an app or program. Below: what a EULA covers, example clauses, how it differs from terms of service and a privacy policy, whether EULAs are enforceable, and how to write one.
Table of contents
- What is a EULA?
- What a EULA covers
- EULA example clauses
- EULA vs terms of service vs privacy policy
- Do you need a EULA?
- Are EULAs enforceable?
- How to write a EULA
- FAQ
What is a EULA?
When you buy software, you are not buying the code itself. You are buying permission to use a copy of it under certain conditions. The EULA is the document that grants that permission and sets the conditions.
A EULA protects the software maker's intellectual property, limits its liability if something goes wrong, and tells users what they can expect. It is common for desktop programs, mobile apps, games and software installed on devices. For software delivered in a browser, such as most SaaS products, the same terms usually appear in a terms of service or subscription agreement instead.
What a EULA covers
- License grant. What the user may do: install on how many devices, for personal or commercial use, for how long.
- Restrictions. What the user may not do: copy, resell, reverse engineer, modify or remove copyright notices.
- Ownership. A statement that the software maker keeps all intellectual property rights.
- Updates. Whether you provide updates, and whether they install automatically.
- Fees. Any license fee or subscription, if not covered elsewhere.
- Termination. When the license ends and what the user must do, such as uninstalling the software.
- Warranty disclaimer. What you do and do not promise about the software. See our disclaimer examples for wording.
- Limitation of liability. A cap on what you owe if the software causes loss, within what the law allows.
- Data and privacy. A link to your privacy policy if the software collects personal data.
- Third-party and open-source components. Notices required by the licenses of code you include.
- Governing law and disputes. Which country's or state's law applies and where disputes are heard.
EULA example clauses
These short examples show typical wording. Adapt them to your product and have a lawyer review the final agreement.
License grant. Subject to this Agreement, [Company] grants you a limited, non-exclusive, non-transferable, revocable license to install and use [Product] on up to [number] devices that you own or control, for your [personal / internal business] use.
Restrictions. You may not copy, modify, distribute, sell, rent or sublicense [Product], or reverse engineer, decompile or disassemble it, except where applicable law expressly allows this.
Ownership. [Product] is licensed, not sold. [Company] and its licensors keep all rights, title and interest in [Product], including all intellectual property rights.
Termination. This license ends automatically if you breach this Agreement. When it ends, you must stop using and delete all copies of [Product].
Privacy. [Product] collects certain information as described in our Privacy Policy at [link].
EULA vs terms of service vs privacy policy
| EULA | Terms of service | Privacy policy | |
|---|---|---|---|
| Covers | The license to use software | Use of a service, website or platform | How you collect and use personal data |
| Typical for | Installed software, mobile apps, games | SaaS, websites, online platforms | Any business that handles personal data |
| Legally required? | No, but strongly recommended | No, but strongly recommended | Yes, under the GDPR, CCPA and other privacy laws |
| Main purpose | Protect intellectual property and limit liability | Set rules of use and limit liability | Tell people how their data is used and what rights they have |
Many products need more than one. A mobile app with user accounts often has a EULA for the app, terms of service for the account and a privacy policy for the data. See privacy notice vs privacy policy for what a privacy policy must contain.
Do you need a EULA?
No law requires a EULA, but without one you have less control over how your software is used and fewer protections if something goes wrong. You should have one if you:
- Distribute desktop or downloadable software
- Publish a mobile app. Apple's App Store applies its own standard EULA unless you provide a custom one, and Google Play leaves it to developers.
- Sell software installed on hardware devices
- License software to businesses, where a negotiated license agreement often takes the place of a standard EULA
Are EULAs enforceable?
Generally yes, if users had a fair chance to read the terms and clearly agreed to them. How they agree matters:
- Clickwrap, where the user must tick a box or click "I agree" before installing, is usually enforceable.
- Browsewrap, where the terms are only linked somewhere on a page and use implies agreement, is often not. In Specht v. Netscape (2002), a US court refused to enforce terms that users were never prompted to read.
- Shrinkwrap, terms inside the box of physical software, was upheld in ProCD v. Zeidenberg (1996) because buyers could return the product if they did not agree.
Some terms will not hold up whatever users click. In the EU and UK, unfair terms in consumer contracts are not binding, and you cannot remove consumers' statutory rights. The EU Court of Justice also ruled in UsedSoft v Oracle (2012) that a buyer of a permanent software license can resell it, even if the EULA forbids resale. Terms must be clear and in plain language, especially for consumers.
How to write a EULA
- Define the license. Decide exactly what users can do, on how many devices, and for what purpose.
- List the restrictions that protect your product, such as no copying, resale or reverse engineering.
- Cover updates, fees and termination.
- Add warranty and liability terms that are fair and allowed in the countries where you sell.
- Link your privacy policy if the software collects any personal data, including analytics or crash reports.
- Include open-source notices required by the components you use.
- Choose governing law and how disputes are handled.
- Use clickwrap acceptance and keep a record of when each user agreed and to which version.
- Review it regularly and tell users about material changes.
If your software collects personal data, your EULA works alongside your privacy compliance. ComplyDog helps SaaS and software companies handle the privacy side, with a compliance portal for data requests, DPA signing and subprocessor lists. See how it works.
FAQ
What does EULA stand for?
End User License Agreement. It is usually pronounced "YOO-luh".
Is a EULA a legally binding contract?
Yes, when the user clearly agrees to it, for example by clicking "I agree" before installing. Individual terms can still be unenforceable if they are unfair or conflict with consumer law.
Is a EULA the same as terms and conditions?
Not quite. A EULA licenses software. Terms and conditions, or terms of service, govern the use of a service or website. Some companies combine them in one document.
Can I use a EULA template?
A template is a reasonable starting point, but adapt it to how your software actually works, where you sell it and what data it collects, and have a lawyer review it before you rely on it.
