Before you start
This article is general information, not legal advice. Laws differ by country and by whether the buyer is a consumer or a business. Have a lawyer read the document you publish.
What an EULA does
An end-user license agreement is the contract between you and the person who installs your software. It says that they are buying a license to use the software, not the software itself, and it lists what that license allows and forbids.
It does three jobs for a small seller. It states the scope of use, so you can point to a document when a customer asks “can I install this on my office computers”. It limits what you promise, such as warranties and liability. And it sets the rules for ending the license, such as non-payment or abuse.
It does not stop piracy, replace your privacy policy or settle tax and refund questions. Those belong in other documents. See terms for selling software for the commercial side.
The clauses and what they depend on
| Clause | What to decide | Keep in step with |
|---|---|---|
| Grant | Who may use the software, for what, for how long | The license’s expires_at, perpetual or subscription |
| Device limit | How many machines, and whether a person or a company counts | activation_limit on the product |
| Restrictions | No reverse engineering of the license check, no sharing keys, no resale | Your technical measures |
| Updates | Which versions a license covers, and for how long | Your release and update policy |
| Subscription license | The license ends when the subscription ends | The subscription status in Stripe |
| Termination | What happens on breach, non-payment or a refund | How you disable licenses |
| Transfer | Whether a license can move to another person or machine | The device page and deactivation |
| Warranty and liability | What you promise and what you disclaim | Consumer law in the buyer’s country |
| Third-party software | Notices for open-source components | The licenses of those components |
| Data | What the app sends and where it is described | Your privacy statement |
| Law and disputes | Which country’s law and which courts | Where you are based |
The right-hand column is the point. A clause is only as good as the system that carries it out.
Where the EULA and the license server disagree
These are the mismatches that produce support requests. For each, change the document or the setting, and make them say the same thing.
| The EULA says | The system does | The fix |
|---|---|---|
| “Up to five devices” | The product’s device limit is 3, the default | Set the limit to 5, or change the text |
| “One user, any number of devices” | The limit counts devices | Pick a number and write it down |
| “Perpetual license” | A subscription license expires three days after the paid period ends | Do not call a subscription perpetual |
| “Updates for one year” | The releases endpoint offers the latest release to any valid license | Decide whether an expired license still gets old builds, and enforce it in the app |
| “License ends on refund” | A full refund of a one-time Stripe payment disables the license, but refunding a subscription invoice does not | Say it, and cancel or disable by hand for subscriptions |
| “Works offline” | A signed token is trusted for 14 days before the app should check again | State the offline period you support |
| “Transferable” | A customer frees a device on the device page and activates elsewhere | Describe the steps, not only the right |
Clavem’s device limit defaults to 3 and can be set per product or per license. A subscription license expires at the end of the paid period plus three days of grace.
Sample wording
These are plain-language examples to show the style, not text to paste into a contract.
Grant. “We grant you a non-exclusive, non-transferable license to install and use the software on up to three devices that you own or control, for the license term.”
Device limit. “The license key allows up to three devices to be active at once. You may deactivate a device from the software or from the device page and activate another.”
Subscription. “If you bought a subscription, the license lasts while the subscription is paid. It ends when the subscription ends, and a short grace period may apply after a late renewal.”
Restrictions. “You may not copy, sell or share your license key, or remove or bypass the license check.”
Termination. “We may disable a license that has been refunded, charged back or used against these terms. The software may then stop its paid features.”
Notice that each sentence describes something the license server does. If you cannot point to the mechanism behind a sentence, take the sentence out.
Open-source components
Most apps contain open-source code. The licenses require notices. The MIT license, for instance, says its copyright notice and permission notice “shall be included in all copies or substantial portions of the Software”. Collect the notices for every component into a third-party notices file shipped with the app, and add a line in the EULA that open-source components stay under their own licenses. Build tools can list your dependencies and their licenses, which is better than doing it by memory. If you distribute components under copyleft licenses, read them with a lawyer before you decide what your EULA can restrict.
Showing it and recording acceptance
Ask for agreement where it is easy to prove. Options, from weakest to strongest:
- A link to the EULA on your website. It is easy to miss.
- A line at checkout. With Stripe Checkout you can require a terms checkbox by setting
consent_collection[terms_of_service]=required, and the paid session recordsconsent.terms_of_serviceasaccepted. - An accept button on first launch or in the installer, with the document visible. Store the version and the time of acceptance locally.
Use the second and third together if you can. Version the document, put the version number in the app, and keep old versions so that you know what a customer agreed to. When you change the EULA, tell customers and ask for agreement again if the change matters to them.
Consumer law and what it overrides
Where buyers are consumers, the law of their country may override parts of your document. Disclaimers of warranty and limits on liability are the usual casualties, and some rights cannot be waived at all. In the EU, for example, a consumer buying at a distance generally has 14 days to withdraw, with an exception for digital content that downloads after the consumer expressly agreed to lose that right, as Your Europe explains. A clause that contradicts a mandatory rule is not enforceable, and it can make the rest of the document look careless.
So write the rules you will really apply, keep them short, and let a lawyer fix the rest for the countries where you sell. For business customers, see selling software to businesses, where negotiated agreements often replace a standard EULA.
Doing this with Clavem
Clavem does not write or host your EULA. It gives you the controls the EULA describes: the device limit, expiry, the subscription behavior, deactivation and the disabled state. Decide those settings first, then write the document to match them.
Questions
Do I need an EULA to sell software?
Not by law in most places, but you need something that says what the buyer may do. Without a written license, you rely on default rules that vary by country and are hard to explain to customers. A short, plain agreement is better than none.
Should the EULA repeat the device limit?
Yes, and it must match the limit your license server enforces. A contract that allows five devices while the server allows three produces refund requests and disputes.
Can I copy an EULA from another product?
A template is a starting point, not a finished document. Terms that suit another product's pricing, countries and data practices may not fit yours, and copied text may carry rights you do not hold. Have a lawyer review the final version.