This page is general information, not legal advice. A lawyer who knows your market should review any contract you publish.
How it works
Software is almost always licensed, not sold. The buyer gets a right to use a copy under conditions, and the publisher keeps the rights in the code. The EULA writes those conditions down. The buyer accepts it before use: by clicking “I agree” in the installer or on first launch, or by ticking a box at checkout. Whether a particular way of accepting binds a particular buyer depends on the country, which is a question for your lawyer.
Apple’s standard EULA for App Store apps is a good public example of the structure. Its opening line says apps “are licensed, not sold” to the user, and the licence is subject to the user’s acceptance of either Apple’s standard text or a custom EULA from the publisher. The standard text then covers scope of license, consent to data use, termination, external services, no warranty, limitation of liability and more.
Clauses worth having
| Clause | What it settles |
|---|---|
| Grant | Who gets the license, for which product and version, personal or commercial use |
| Devices | How many computers or users one license covers |
| Restrictions | No resale, sharing of keys, or removing license checks |
| Updates | Whether updates are included and for how long |
| Termination | When the license ends, for example after a refund or a breach |
| Warranty and liability | What you promise, and the cap on what you owe |
| Governing law | Which country’s courts decide disputes |
Lining the text up with the technology
The strongest EULAs match what the software actually enforces. A worked case: the text says “One license covers up to three personal devices.” The product’s device limit is set to 3. When a fourth device tries to activate, the licensing service refuses, and the buyer already knows why because the contract says so.
Likewise for termination. If the EULA says a license ends when the payment is refunded in full, the licensing system should revoke the key at that moment. If the text and the system disagree, you will argue with a customer about a promise you made and did not keep. Choosing the number of devices is covered in device limit, and ending a key early in license revocation.
EULA versus open source license
An open source license gives everyone broad rights to copy and change the code. An EULA does the opposite for compiled commercial software: it grants a narrow right to use, and withholds the rest. A product can ship both when it bundles open source components, which is why Apple’s text carves out their licensing terms.
How Clavem handles it
Clavem does not draft, display or record acceptance of an EULA. Your app or your installer shows it. What Clavem enforces are the numbers an EULA usually mentions: the device limit (default 3, adjustable per product and per license), the validity (perpetual, a fixed number of days, or following the Stripe subscription), and the disabled state after a full refund. The order page shows activation instructions you write, which is a good place to link the EULA. For drafting help see writing an EULA and terms for selling software.
Questions
Is an EULA the same as terms of service?
Not exactly. An EULA governs the right to use installed software. Terms of service usually govern an online service or a store. A paid app with an account often needs both, and a privacy policy as a third document.
Do I need an EULA if I sell through Stripe?
Nothing about Stripe requires one, but without one the buyer has only what the law gives them by default. An EULA lets you state the device limit, the update terms and what happens on refund. Have a lawyer in your country review it.