What Is a EULA?
Short answer: it's the agreement someone accepts before installing or using your software, separate from your privacy policy and doing a different job entirely.
Last updated: August 2026
The short answer
EULA stands for End-User License Agreement. It's a legal contract between whoever owns a piece of software and the person using it, setting out what they're allowed to do with it, what they're not, and who owns what if something goes wrong. If you've ever clicked "I Agree" before installing an app or program, you've accepted one, usually without reading it.
What a EULA actually does
Three things, mainly:
- Defines what the user can do. Install it on how many devices, use it for personal or commercial purposes, that kind of thing.
- Sets restrictions. No reverse engineering, no redistributing, no reselling the license to someone else without permission.
- Protects the creator. Keeps the intellectual property yours, and limits your liability if the software causes a problem for the user.
None of this is about data collection. That's what a privacy policy covers. A EULA and a privacy policy solve different problems and most software genuinely needs both.
Clickwrap vs. shrinkwrap
Most EULAs today are "clickwrap," the box or button you click to accept before a program installs or an app unlocks. Older physical software used "shrinkwrap" agreements, where opening the sealed packaging counted as accepting the terms printed inside. Nearly everything distributed digitally now uses clickwrap, since it creates a clearer record that the user actually saw and agreed to the terms.
EULA vs. terms of service
These get confused because they often cover similar ground, rules for using something, limits on liability, but they apply to different kinds of products. A EULA is specifically for licensed software: something installed or run locally, where you're granting a license to use code you still own. Terms of service is broader and fits ongoing services, websites, and platforms where nothing is really "installed" in the same sense. A downloadable desktop app typically wants a EULA. A web-based SaaS platform often uses terms of service instead, or sometimes both, a EULA for the software component and terms of service for the ongoing account and subscription.
Frequently asked questions
Is a EULA legally binding?
Generally yes, provided the user had a real opportunity to review it and took a clear action to accept it, like clicking "I Agree." Courts have sometimes questioned clickwrap agreements that bury the acceptance step or make the terms hard to actually find before installation.
Can someone refuse a EULA?
Yes, and typically that just means they can't use the software. Declining is usually the only alternative to accepting, there's rarely a middle option.
Do I need a EULA for a simple mobile app?
If you're distributing through an app store, it's worth having one even for a simple app, mainly to protect your intellectual property and limit your liability. Apple provides a standard default EULA if you don't supply your own, but writing your own gives you more control over the actual terms.
Want to see one? Try the EULA generator, or start from the free EULA template if you'd rather edit a document yourself.
Sources
- Wikipedia, "End-user license agreement"
- Dartmouth College IT Services, "What Are EULAs and Why Should I Read Them?"
These describe general contract concepts, not a specific jurisdiction's statute, so they've stayed stable over time.