End-User License Agreement Template

License your software rather than sell it, with use and restriction terms adapted for the US, UK, and EU.

Terms
Adjust for your territory

Sets a starting point for your main market; serving several, enable extra sections under Customize. These adjustments cover the US, UK, and EU broadly and are not a substitute for advice on your specific country's law.

Scroll for section-by-section legal context. Click any purple chip to fill in that field. Switch to Customize to enable optional clauses.

END-USER LICENSE AGREEMENT

Effective Date: {Effective Date}

Last updated: {Last Updated Date}

1. Acceptance of This Agreement

This End-User License Agreement (the "Agreement" or "EULA") is a binding contract between {Company Name} ("we", "us", or "our") and you ("you" or "your") governing your use of {Application Name} and any related documentation, updates, and components (the "Application"). It applies whether the Application is downloaded, pre-installed, accessed online, or delivered through a third-party store.

By downloading, installing, copying, accessing, or otherwise using the Application, or by clicking "I Agree," you confirm that you have read and understood this Agreement and that you agree to be bound by it. If you do not agree, do not download, install, or use the Application, and delete any copy in your possession.

If you are accepting this Agreement on behalf of a company or other organization, you represent that you are authorized to bind that organization, in which case "you" and "your" refer to that organization.

About this section

What's in this section

Names the parties and pins down the exact acts that count as acceptance, downloading, installing, or clicking 'I Agree', plus the authority needed to accept on behalf of a company.

Why this section is here

Identifies the parties and records that installing, accessing, or clicking 'I Agree' forms a binding contract. This is the consent hook the rest of the license depends on.

Common mistake

Relying on use alone as acceptance. Tie the agreement to a clear affirmative act, and name the entity that can bind a business user.

2. Definitions

For the purposes of this Agreement:

  • "Application" means the software identified as {Application Name} in object-code form, together with its Documentation and any Updates or components we provide under this Agreement.
  • "Documentation" means the user guides, manuals, and technical materials we make available for the Application.
  • "Device" means a computer, phone, tablet, server, or other hardware that you own or control and on which the Application is installed or run.
  • "Update" means a patch, bug fix, enhancement, upgrade, or new version of the Application that we make available.
  • "Consumer" means an individual acting wholly or mainly outside their trade, business, craft, or profession. (The consumer protections in this Agreement apply only to Consumers.)
  • "Intellectual Property Rights" means all patent, copyright, trademark, trade-secret, database, and other intellectual property rights, whether registered or not.
About this section

What's in this section

The shorthand the rest of the license runs on. 'Application', 'Device', 'Update', and 'Consumer' are fixed here once so every later clause stays precise.

Why this section is here

Defined terms keep the license precise and shorten the rest of the document. Defining 'Application', 'Device', and 'Consumer' is what lets the grant, restrictions, and consumer carve-outs apply cleanly.

Common mistake

Leaving 'the software' or 'the product' undefined, then using several different names for the same thing across the agreement.

3. License Grant

Subject to your continued compliance with this Agreement and, where the Application is paid, your payment of all applicable fees, {Company Name} grants you a limited, non-exclusive, non-transferable, non-sublicensable, and revocable license to install and use the Application for your personal or internal business purposes. (Set the scope to match how you sell: per Device, per named user or "seat," per organization, or per site. Narrow it for a single-user app; widen it for an enterprise or site license.)

Permitted users. If you are an organization, you may allow your employees and contractors to use the Application on your behalf, provided you remain responsible for their compliance with this Agreement.

Evaluation and trial licenses. If the Application is provided for trial, evaluation, beta, or demonstration purposes, the license is granted only for the stated period and only to assess the Application, and we may withdraw it at any time. Such versions may have reduced functionality and may be provided without support.

Reservation of rights. The Application is licensed, not sold. We and our licensors retain all right, title, and interest in and to the Application and all Intellectual Property Rights in it. You receive only the rights expressly granted in this Agreement, and all other rights are reserved.

Updates, upgrades, and support. We may, but are not obligated to, provide Updates. Some Updates may be required for the Application to keep functioning or to remain secure, and, where the Application is configured to do so, Updates may download and install automatically; you consent to this automatic delivery. Updates are governed by this Agreement unless we provide separate terms with them. Any support, maintenance, or service levels are provided only if separately described or agreed in writing, and we may change or discontinue support for older versions.

About this section

What's in this section

The core permission: what the user may do with the software, on how many devices or seats, for what purpose, and the reminder that it is licensed, not sold.

Why this section is here

A EULA licenses software rather than selling it, so this clause is the legal basis for everything the user is allowed to do. Limiting the grant by devices, users, and purpose is what makes the later restrictions enforceable.

Common mistake

Granting broad rights here and then trying to claw them back in the restrictions. Scope the grant tightly from the start.

4. License Restrictions

Except to the extent expressly permitted by this Agreement or required by applicable law, you agree not to, and not to allow any third party to:

  • (a) copy, reproduce, distribute, publish, transmit, sell, resell, rent, lease, lend, or sublicense the Application;
  • (b) modify, adapt, translate, or create derivative works based on the Application;
  • (c) reverse engineer, decompile, or disassemble the Application, or otherwise attempt to discover its source code, underlying ideas, or algorithms, except to the extent this restriction is prohibited by applicable law (for example, where the law gives you a non-excludable right to decompile in order to achieve interoperability, and only after you have requested the necessary information from us);
  • (d) remove, alter, or obscure any copyright, trademark, or other proprietary notice in or on the Application;
  • (e) circumvent, disable, or interfere with any security, licensing, digital-rights-management, or access-control feature of the Application;
  • (f) use the Application to develop a product or service that competes with it, or to provide a service bureau, time-sharing, hosting, or similar service to third parties;
  • (g) use the Application to store or transmit infringing, defamatory, or otherwise unlawful material, or any malicious code; or
  • (h) use the Application in violation of any applicable law or regulation, or in breach of any third party's rights.

You are responsible for all use of the Application under your license, account, or Devices.

About this section

What's in this section

The lettered list of prohibited acts, from copying and reselling to reverse engineering and circumventing license controls. This is where you tailor the boundaries to your product.

Why this section is here

Defines the boundaries of the license, so acts taken outside them are infringement or breach. In the EU and UK an absolute ban on reverse engineering cannot override a user's statutory right to decompile for interoperability.

Common mistake

Banning all reverse engineering with no carve-out. Keep the 'except where the law allows' wording so the clause stays valid.

5. Intellectual Property

The Application and all copies of it, including its code, structure, design, "look and feel," interfaces, content, and Documentation, together with all Intellectual Property Rights in them, are owned by {Company Name} or its licensors and are protected by copyright, trademark, and other intellectual property laws. Except for the limited license granted in Section 3, this Agreement does not transfer to you any right, title, or interest in the Application.

Trademarks. "{Company Name}", "{Application Name}", and our related names, logos, and product names are our trademarks. This Agreement does not grant you any right to use them without our prior written consent.

Feedback. If you send us feedback, suggestions, or ideas about the Application, you grant us a perpetual, irrevocable, worldwide, royalty-free, sublicensable license to use and exploit them for any purpose, without any obligation or compensation to you.

Third-party and open-source components. The Application may include third-party or open-source software that is provided under its own license terms. Those terms are incorporated into this Agreement by reference, and to the extent they conflict with this Agreement in respect of the relevant component, the third-party or open-source terms govern that component. A list of these components and their notices is available within the Documentation or from {Company Name} on request. We provide third-party components without warranty, to the extent the relevant license allows.

About this section

What's in this section

Confirms you keep ownership of the code, marks, and look and feel, and takes a license back to any feedback the user sends.

Why this section is here

Confirms ownership stays with you and your licensors and secures a license to use any feedback. Without it, contributions and your marks are left ambiguous.

Common mistake

Forgetting the feedback license, or naming a brand instead of the legal entity that actually owns the IP.

6. Term and Termination

This Agreement takes effect when you first accept it and continues until terminated.

Termination by you. You may terminate this Agreement at any time by ceasing all use of the Application and deleting all copies in your possession or control.

Termination by us. This Agreement and your license terminate automatically if you breach any of its terms, and we may also suspend or terminate the license if we stop providing the Application or are required to by law. Where reasonable and lawful, we will give you notice and an opportunity to cure a breach before terminating.

Effect of termination. On termination, the license granted to you ends immediately, and you must stop using the Application and delete or remove all copies. Termination does not entitle you to any refund except as required by law or expressly stated.

Survival. The sections that by their nature should survive termination, including Definitions, Intellectual Property, Disclaimer of Warranties, Limitation of Liability, Indemnification, and Governing Law and Disputes, survive termination.

About this section

What's in this section

How long the license lasts, how either side ends it, what the user must do afterwards (stop using and delete copies), and which clauses survive.

Why this section is here

Sets when the license ends and obliges the user to stop using and delete the software, which is how you cut off an infringing or non-paying user.

Common mistake

No requirement to delete copies on termination, which leaves the user with fully usable software.

7. Disclaimer of Warranties

The Application is licensed, not sold. To the fullest extent permitted by applicable law, and except as expressly set out in the territory-specific terms below and for any statutory rights you have as a Consumer, the Application and any support are provided on an "as is" and "as available" basis.

United States. To the fullest extent permitted by law, we and our licensors disclaim all warranties, conditions, and representations of any kind, whether express, implied, statutory, or arising from course of dealing or usage of trade, including the implied warranties of merchantability, fitness for a particular purpose, title, accuracy, and non-infringement. We do not warrant that the Application will meet your requirements, be available on an uninterrupted, timely, secure, or error-free basis, or that any defect will be corrected. No advice or information, whether oral or written, creates any warranty. Some jurisdictions do not allow the exclusion of implied warranties, so some of these exclusions may not apply to you, and you may have other rights that vary by jurisdiction. (Some lawyers set this section and the Limitation of Liability below in ALL CAPS so they are "conspicuous" under UCC § 2-316. Bold text like this is increasingly accepted, but consider caps for maximum enforceability with US users.)

About this section

What's in this section

The quality promises you make and the ones you exclude. The wording swaps by territory, because the US, UK, and EU treat warranties very differently.

Why this section is here

Allocates quality risk. US law lets you disclaim implied warranties, but the UK Consumer Rights Act 2015 and the EU Digital Content Directive (2019/770) give consumers non-excludable conformity rights.

Common mistake

Using a blanket US-style 'as is' disclaimer against UK or EU consumers, where it is void.

Consumer quality rights →

8. Limitation of Liability

United States. To the fullest extent permitted by law: (a) in no event will {Company Name} or its licensors be liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for any loss of profits, revenue, data, business, or goodwill, however caused and on any theory of liability, even if advised of the possibility; and (b) the total aggregate liability of {Company Name} for all claims arising out of or relating to the Application or this Agreement will not exceed the greater of the amount you paid for the Application in the twelve (12) months before the event giving rise to the claim or {Liability Cap}. These limitations apply even if a remedy fails of its essential purpose. Some jurisdictions do not allow the exclusion or limitation of certain damages, so some of the above may not apply to you.

About this section

What's in this section

The cap on what you owe if something goes wrong and the categories of loss you exclude. Set the cap to match what the user actually paid.

Why this section is here

Caps financial exposure. Every region forbids excluding liability for death or personal injury caused by negligence and for fraud, and the EU and UK also protect a consumer's foreseeable losses.

Common mistake

A single uncapped or fully-excluding clause that a court will strike down, often taking the rest of the clause with it.

Limits on excluding liability →

9. Indemnification

To the fullest extent permitted by applicable law, you agree to indemnify, defend, and hold harmless {Company Name} and its officers, directors, employees, and agents from and against any third-party claims, damages, liabilities, costs, and expenses (including reasonable legal fees) arising out of or related to (a) your use of the Application in breach of this Agreement, (b) your violation of any applicable law or of any third party's rights, or (c) content or data you process, store, or distribute using the Application. We will notify you of the claim, give you control of its defense and settlement (with counsel reasonably acceptable to us, and provided no settlement imposes any obligation on us without our consent), and reasonably cooperate at your expense. (If your users are Consumers, this section applies only so far as the law allows, since consumer-protection law in many regions restricts indemnities imposed on Consumers.)

About this section

What's in this section

Shifts the cost of third-party claims caused by the user's misuse onto the user, and sets out how such a claim is notified and defended.

Why this section is here

Shifts the cost of third-party claims caused by your misuse onto you, which protects the licensor when a user breaks the rules or infringes someone's rights. It is standard in commercial software licenses.

Common mistake

Imposing a broad indemnity on consumers. EU and UK consumer law restricts indemnities against Consumers, so keep the 'so far as the law allows' carve-out.

10. Privacy and Data

Our collection and use of personal information in connection with the Application is described in our Privacy Policy, which forms part of this Agreement.

Our handling of personal information is also subject to the US privacy laws that apply to you, which may include the California Consumer Privacy Act (as amended by the CPRA) and other state privacy laws. Where we process personal information on your behalf as a service provider, a separate data processing addendum may apply.

About this section

What's in this section

Points to your Privacy Policy for how the Application handles personal data, and flags that UK GDPR or the GDPR also applies for UK and EU users.

Why this section is here

The Application's data handling is governed by your Privacy Policy, and for UK and EU users the UK GDPR and the GDPR apply to that processing.

Common mistake

Burying data practices inside the EULA instead of pointing to a standalone Privacy Policy.

How the GDPR applies →

11. Governing Law and Disputes

Informal resolution. Before bringing a formal claim, you agree to contact us at {Email Address} and give us a reasonable opportunity to resolve the matter informally.

Governing law and courts. This Agreement is governed by the laws of {Governing Law}, without regard to its conflict-of-laws rules. Subject to any arbitration provision below, you and we submit to the exclusive jurisdiction of {Jurisdiction}.

About this section

What's in this section

Chooses the governing law and the courts, and adds an informal-resolution step first. Consumers keep their home-country law and forum whatever you choose.

Why this section is here

Chooses the governing law and forum. For consumers, the UK and EU guarantee the mandatory law and the courts of the user's home country regardless of this choice.

Common mistake

Forcing US arbitration or a distant forum on EU or UK consumers, which is unenforceable against them.

12. Changes to This Agreement

We may update this Agreement from time to time to reflect changes to the Application, our business, or the law. When we make material changes, we will give reasonable notice, such as by updating the "Last updated" date, posting the new version with the Application, or presenting an in-product notice, and where appropriate we will ask you to actively accept the updated Agreement. Changes take effect when posted unless we state otherwise. Your continued use of the Application after the changes take effect constitutes acceptance, except where applicable law requires your active consent. If you do not agree to the updated Agreement, you must stop using the Application, and, if you are a Consumer who is materially disadvantaged by a change, you may end this Agreement.

About this section

What's in this section

How you roll out a new version of the license and when it takes effect, with active re-acceptance kept where the law requires it.

Why this section is here

Software terms change as the product evolves. This sets how you notify users and when changes take effect, and preserves active consent where the law requires it.

Common mistake

Treating silent posting as acceptance for material changes.

13. General

Entire agreement. This Agreement, together with any terms expressly incorporated by reference, is the entire agreement between you and us regarding the Application and supersedes all prior agreements on the same subject.

Severability. If any provision of this Agreement is held to be unenforceable, the remaining provisions remain in full force, and the unenforceable provision will be applied to the maximum extent permitted by law.

No waiver. Our failure to enforce any provision is not a waiver of our right to enforce it later.

Assignment. You may not assign or transfer this Agreement without our prior written consent. We may assign it in connection with a merger, acquisition, reorganization, or sale of assets. This Agreement binds and benefits the parties and their permitted successors and assigns.

Force majeure. Neither party is liable for any delay or failure to perform caused by events beyond its reasonable control.

Notices. We may give you notices by email, through the Application, or by posting them in connection with the Application. You may send us legal notices at {Email Address} or {Mailing Address}.

Governing language. If this Agreement is translated into another language and there is a conflict, the English version governs to the extent permitted by law.

Third-party rights. Except as expressly stated (for example, our licensors and any app-store beneficiaries), no person other than the parties has any right to enforce this Agreement.

Relationship. Nothing in this Agreement creates any partnership, agency, joint venture, or employment relationship between the parties.

Headings. Headings are for convenience only and do not affect interpretation.

About this section

What's in this section

The boilerplate that holds the contract together: entire agreement, severability, assignment, notices, governing language, and third-party rights.

Why this section is here

Boilerplate such as entire agreement, severability, assignment, and force majeure keeps the contract coherent and survivable if one clause fails.

Common mistake

Dropping severability, so one unenforceable clause can sink the whole EULA.

14. Contact Us

If you have any questions about this Agreement, contact us at:

{Company Name}

{Mailing Address}

Email: {Email Address}

About this section

What's in this section

The licensor's legal name and contact details, the address where questions and formal legal notices are sent.

Why this section is here

Consumer and distance-selling rules expect a clear, monitored point of contact, and it is where formal legal notices are delivered.

Common mistake

Listing only a no-reply address that no one monitors.

Got what you need? Copy the template now, or read on for the section-by-section guide to what each clause does and how to adapt it.

What Is an End-User License Agreement (EULA)?

An End-User License Agreement (EULA) is the contract between the company that makes a piece of software and the person who installs or uses it. It does one core job: it grants a limited license to use the software while making clear that the software is licensed, not sold. Around that grant, it sets out what users may and may not do, who owns the software, what happens when something goes wrong, and how the agreement ends.

The shape of the license depends on how the software is sold. It may be perpetual, granting indefinite use of a particular version, or a subscription that lasts only while the user keeps paying, and it can be scoped to a single device, a named user or "seat," an organization, or a whole site. In every case the user receives a right to use the software, not ownership of it: the publisher keeps the intellectual property and every right the agreement does not expressly grant.

Who Needs a EULA?

Any company that distributes software a user installs, downloads, or embeds needs a EULA. It is the document that protects your intellectual property, limits your liability, and sets the rules of use before the software ever runs. The most common cases:

  • Mobile App

    iOS or Android apps distributed through the app stores, which require a license agreement as a condition of listing.

  • Installed Software

    Downloadable desktop or client software that users install and run on their own devices.

  • SaaS with a Client

    Cloud services that ship a downloadable agent, plugin, or SDK alongside the hosted product.

  • Enterprise / On-Prem

    Software licensed to businesses and installed on their own servers or fleet of managed devices.

The common thread is that your code leaves your control and runs on someone else's device, so the license has to travel with it. Free apps need a EULA as much as paid ones, because the value is in controlling use and limiting liability, not only in collecting a fee. A EULA delivered through a clickwrap agreement lets you present the same terms to every user and capture acceptance before installation, without a separate signing step.

How to Make Your EULA Binding

This template is designed for clickwrap acceptance. Presented at download or first launch, an "I Agree" step makes the EULA binding in the same way a signature would. Under the US ESIGN Act and UETA, and under eIDAS in the EU and UK, clicking to accept is legally equivalent to a handwritten signature for software licenses.

Gate the install on acceptance. The user must be able to read the full EULA before they install or first run the software, and the install or first launch should not proceed until they accept. A link next to the "I Agree" control is the minimum; burying it in a help menu or showing it only after installation weakens enforceability.

Require a click, not a launch. Acceptance must be a deliberate act: an unchecked box the user ticks, or a clearly labelled "I Agree" button next to the terms. Treating mere use or launch of the software as acceptance (browsewrap) is materially weaker and has been rejected by courts.

Log the version, device, and user. Record the exact version of the EULA shown, the timestamp, the device or installation identifier, and the user or account that accepted, tied to the license key where you issue one. That lets you prove which build and which terms a given install agreed to.

Force re-acceptance on major updates. When you change the EULA materially, such as a new restriction, a different liability cap, or a new fee, prompt existing users to actively accept the new version at the next update or launch. Continued use under an old version is not a reliable consent signal.

Miss any of these and what you have is a published document, not an enforceable license. Negotiated or enterprise licenses can still be signed in person or through a signing platform; enable the Signature blocks section for those.

Frequently Asked Questions

A EULA licenses a specific piece of software: what you can do with the app, what you cannot, who owns it, and what happens if it breaks. A Terms of Service governs an ongoing relationship with a website or online service, including accounts, payments, and acceptable use. Many products use both: a EULA for the installed or downloaded software, and Terms of Service for the surrounding service. If your product is purely a hosted web service with nothing to install, Terms of Service alone is usually enough.
Yes. A EULA exists to protect your intellectual property and limit your liability, and both concerns apply whether or not you charge. Free and freemium software is copied, modified, and redistributed just like paid software, and a product released with no license terms gives you little basis to restrict misuse, disclaim warranties, or cap liability. For a free product, simply leave the Fees section disabled; the license grant, restrictions, warranty disclaimer, and liability terms still do the real work.
Yes, when it is presented properly. Courts in the US, UK, and EU enforce EULAs accepted by an affirmative act, such as clicking 'I Agree' before installation, provided the terms were reasonably available and the user had a genuine chance to read them. A EULA buried in a help menu or accepted by simply using the software (browsewrap) is far weaker. Capture the acceptance, the version, and the timestamp so you can prove what the user agreed to.
Not entirely, and not everywhere. In the US you can disclaim implied warranties and limit most liability. In the UK and EU you cannot exclude liability for death or personal injury caused by negligence or for fraud, and you cannot remove a consumer's statutory quality and conformity rights. A clause that tries to exclude everything is often unenforceable in full, so keep the carve-outs the law requires.

Not legal advice

This template is provided for informational purposes only and does not constitute legal advice. Review and adapt it to your specific situation, and consult a qualified attorney before relying on it for a real-world filing or transaction.

Make your end-user license agreement enforceable.

ClickTerm captures acceptance of your end-user license agreement with timestamps, version history, and audit-ready records, so the document holds up when it matters.