Can I prohibit reverse engineering?

Generally yes, but with limits. The EULA can prohibit reverse engineering except where required by applicable law. The Software Interoperability Exception (17 USC §1201(f)) and analogous provisions in EU (Software Directive 2009/24), France, Australia allow reverse engineering for interoperability with other software. Some states (e.g., California Civil Code §1670) limit unconscionable license terms. The "except as required by law" carve-out is essential.

How much liability cap should I use?

Industry conventions for B2B software: cap at fees paid in the prior 12 months. For low-cost or free products, cap at $100 or amount paid. Some jurisdictions don't enforce caps below a reasonable amount; some consumer-protection statutes invalidate caps entirely (Massachusetts G.L. c. 93A). For SaaS with significant data-processing obligations, separate uncapped liability for data breaches and IP infringement may be expected by enterprise customers.

What about open-source libraries in my software?

Disclose them. Modern software almost always uses open-source dependencies (MIT, Apache, BSD are permissive and easy; GPL/AGPL/MPL have copyleft obligations that can require open-sourcing your code). Maintain a NOTICES.txt or third-party-licenses file with each component's license. For GPL-licensed code, ensure your software's licensing allows compliance — sometimes you must re-architect to keep proprietary code separate.

Do I need a separate Privacy Policy / DPA?

For any software that processes personal data: yes. The EULA can reference an external Privacy Policy (typically posted on the publisher's website) and, for B2B SaaS, a Data Processing Agreement (DPA) that specifies the publisher's role as a "processor" under GDPR Article 28 or "service provider" under CCPA. Standard Contractual Clauses (SCCs) for cross-border data transfers are also typically attached for EU customers. Skipping this layer risks GDPR/CCPA liability.

Software EULA Template (End User License Agreement)

End-user license for software products — installation, use, restrictions, warranty, liability, and termination.

Customise

Effective date

Software publisher — name

Publisher address

Software product name

Version

License type

License scope per seat/install

Permitted use cases

Prohibited activities

Updates / upgrades policy

Support / maintenance

Data and privacy policy

State (governing law)

Live preview

END USER LICENSE AGREEMENT

Apexa Warehouse OS v3.4.0
Effective: May 11, 2026

PUBLISHER:
Apexa Software, Inc.
1209 Orange Street, Wilmington, DE 19801

═══════════════════════════════════════════════════════════════════════
IMPORTANT — READ BEFORE INSTALLING
═══════════════════════════════════════════════════════════════════════

THIS END USER LICENSE AGREEMENT (THIS "EULA") IS A LEGAL CONTRACT BETWEEN YOU (EITHER AN INDIVIDUAL OR A LEGAL ENTITY, "LICENSEE") AND APEXA SOFTWARE, INC. ("PUBLISHER"). BY INSTALLING, COPYING, OR USING THE SOFTWARE, YOU AGREE TO BE BOUND BY THE TERMS OF THIS EULA. IF YOU DO NOT AGREE, DO NOT INSTALL OR USE THE SOFTWARE; CONTACT PUBLISHER FOR A REFUND IF AVAILABLE.

═══════════════════════════════════════════════════════════════════════
1. LICENSE GRANT
═══════════════════════════════════════════════════════════════════════

Subject to Licensee's compliance with this EULA and (if applicable) payment of the license fee, Publisher grants Licensee a perpetual, non-exclusive, non-transferable license to install and use the Software for Licensee's internal business purposes, in accordance with the terms hereof.

License scope: one (1) license per individual end user — one user, one or more devices used by that individual.

═══════════════════════════════════════════════════════════════════════
2. PERMITTED USES
═══════════════════════════════════════════════════════════════════════

Licensee may use the Software as follows:

Internal business operations of Licensee organization, including: warehouse and inventory management; integration with existing ERP systems via documented APIs; reporting and analytics on Licensee's own data; training of Licensee personnel; backup and disaster-recovery copies (one additional install for backup purposes).

═══════════════════════════════════════════════════════════════════════
3. PROHIBITED USES (RESTRICTIONS)
═══════════════════════════════════════════════════════════════════════

Licensee shall not, and shall not permit any third party to:

Reverse engineering, decompilation, or disassembly of the Software (except as expressly required by applicable law).
Redistribution, resale, or sublicensing of the Software.
Use for the benefit of third parties (e.g., service-bureau or hosting for non-Licensee organizations) without separate written agreement.
Removal, alteration, or obscuring of copyright, trademark, or other proprietary notices.
Use in violation of applicable export-control laws (US EAR, OFAC sanctions).
Use to develop a competing product.

═══════════════════════════════════════════════════════════════════════
4. OWNERSHIP
═══════════════════════════════════════════════════════════════════════

The Software is licensed, not sold. Publisher retains all right, title, and interest in and to the Software, including all intellectual property rights (copyright, patent, trademark, trade secret). This EULA does not transfer any ownership rights to Licensee.

═══════════════════════════════════════════════════════════════════════
5. UPDATES AND UPGRADES
═══════════════════════════════════════════════════════════════════════

Publisher provides minor version updates (e.g., 3.4.x) at no additional charge during the License Term.
Major version upgrades (e.g., 3.x to 4.0) are not included; Licensee may purchase upgrades at then-current pricing or under existing maintenance agreement.
Updates may be delivered via in-application update mechanism, downloadable installer, or remote installation by Publisher with Licensee consent.

═══════════════════════════════════════════════════════════════════════
6. SUPPORT
═══════════════════════════════════════════════════════════════════════

Publisher provides standard support: email-based technical support during business hours (Monday-Friday, 9 AM - 5 PM Pacific Time, excluding Publisher holidays), with target response within 1 business day.

═══════════════════════════════════════════════════════════════════════
7. DATA AND PRIVACY
═══════════════════════════════════════════════════════════════════════

Software does not transmit Licensee data to Publisher except: (a) anonymized usage telemetry for product improvement (Licensee may opt out in settings); (b) error reports submitted with Licensee consent; (c) license-validation pings as needed for authentication.
Licensee data and customer data processed by the Software remain Licensee's property; Publisher acts as a data processor under applicable privacy law (GDPR, CCPA).
Publisher's detailed Privacy Policy: see [URL]

═══════════════════════════════════════════════════════════════════════
8. WARRANTY DISCLAIMER
═══════════════════════════════════════════════════════════════════════

EXCEPT AS EXPRESSLY STATED IN A SEPARATE WRITTEN AGREEMENT, THE SOFTWARE IS PROVIDED "AS IS" AND "AS AVAILABLE." PUBLISHER MAKES NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, ACCURACY, OR UNINTERRUPTED OPERATION.

PUBLISHER DOES NOT WARRANT THAT THE SOFTWARE WILL BE FREE FROM DEFECTS, ERRORS, OR SECURITY VULNERABILITIES, OR THAT IT WILL OPERATE IN ALL HARDWARE/SOFTWARE COMBINATIONS LICENSEE MAY USE. SOME JURISDICTIONS DO NOT ALLOW DISCLAIMER OF IMPLIED WARRANTIES; IN SUCH JURISDICTIONS, IMPLIED WARRANTIES ARE LIMITED TO THE SHORTEST PERIOD ALLOWED BY LAW.

═══════════════════════════════════════════════════════════════════════
9. LIMITATION OF LIABILITY
═══════════════════════════════════════════════════════════════════════

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL PUBLISHER BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, INCLUDING WITHOUT LIMITATION LOST PROFITS, LOST DATA, OR BUSINESS INTERRUPTION, ARISING OUT OF OR RELATED TO THIS EULA OR THE SOFTWARE, EVEN IF PUBLISHER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

PUBLISHER'S TOTAL AGGREGATE LIABILITY UNDER THIS EULA SHALL NOT EXCEED THE GREATER OF (a) THE AMOUNT PAID BY LICENSEE TO PUBLISHER IN THE TWELVE (12) MONTHS PRECEDING THE CLAIM, OR (b) ONE HUNDRED US DOLLARS ($100). SOME JURISDICTIONS DO NOT ALLOW LIMITATION OR EXCLUSION OF CONSEQUENTIAL OR INCIDENTAL DAMAGES; IN SUCH JURISDICTIONS, PUBLISHER'S LIABILITY IS LIMITED TO THE MAXIMUM EXTENT PERMITTED.

═══════════════════════════════════════════════════════════════════════
10. INDEMNIFICATION
═══════════════════════════════════════════════════════════════════════

Licensee shall indemnify, defend, and hold harmless Publisher from any claim arising from: (a) Licensee's use of the Software in violation of this EULA; (b) data Licensee processes through the Software; (c) Licensee's combination of the Software with third-party products not authorized by Publisher.

═══════════════════════════════════════════════════════════════════════
11. EXPORT CONTROL
═══════════════════════════════════════════════════════════════════════

The Software may be subject to US export control laws (Export Administration Regulations, 15 CFR Parts 730-774; Office of Foreign Assets Control sanctions, 31 CFR Parts 500-598). Licensee shall not export, re-export, or transfer the Software to any country, individual, or entity in violation of such laws.

═══════════════════════════════════════════════════════════════════════
12. TERMINATION
═══════════════════════════════════════════════════════════════════════

12.1 By Licensee. Licensee may terminate at any time by uninstalling the Software and deleting all copies.

12.2 By Publisher. Publisher may terminate this EULA immediately for material breach (e.g., violation of restrictions, unauthorized redistribution, failure to pay).

12.3 Effect of Termination. Upon termination, Licensee shall immediately cease all use of the Software and destroy all copies. Sections 4 (ownership), 8 (warranty disclaimer), 9 (liability limitation), 10 (indemnification), and 13 (governing law) survive.

═══════════════════════════════════════════════════════════════════════
13. GOVERNING LAW; DISPUTE RESOLUTION
═══════════════════════════════════════════════════════════════════════

This EULA is governed by the laws of the State of Delaware, excluding its conflict-of-laws principles, and federal copyright law. Disputes shall be resolved by binding arbitration administered by the American Arbitration Association under its Commercial Arbitration Rules, in Delaware, except that either party may seek injunctive relief in court for IP infringement.

═══════════════════════════════════════════════════════════════════════
14. ENTIRE AGREEMENT; AMENDMENT
═══════════════════════════════════════════════════════════════════════

This EULA constitutes the entire agreement between the parties regarding the Software and supersedes all prior agreements. Publisher may modify this EULA by posting a revised version; continued use after notice constitutes acceptance.

═══════════════════════════════════════════════════════════════════════
15. SEVERABILITY; ASSIGNMENT
═══════════════════════════════════════════════════════════════════════

If any provision is held unenforceable, the remainder remains in effect. Licensee may not assign this EULA. Publisher may assign freely.

═══════════════════════════════════════════════════════════════════════
ACCEPTANCE
═══════════════════════════════════════════════════════════════════════

BY INSTALLING OR USING THE SOFTWARE, LICENSEE ACKNOWLEDGES READING AND AGREEING TO THIS EULA.

About this template

A software EULA (End User License Agreement) is the foundational legal document for any commercial software product. Three structural questions drive EULA design: (1) is the license PERPETUAL (one-time purchase) or SUBSCRIPTION (recurring); (2) is it PER-USER, PER-DEVICE, PER-SEAT, SITE, or ENTERPRISE; (3) is it B2C (consumer-facing, click-through) or B2B (negotiated, signed)? This template targets a B2B perpetual or subscription license — adjust for consumer-facing products. Federal and state law considerations: (1) UCITA — the Uniform Computer Information Transactions Act was proposed in 1999 to standardize software licensing but has been adopted only in Maryland and Virginia. Most states use general contract law and Article 2 of the UCC by analogy, plus federal copyright law. (2) Click-wrap and browse-wrap — the question of whether users actually agreed to the EULA. Click-wrap (user clicks "I Agree") is generally enforceable; browse-wrap (terms posted on website without explicit acceptance) faces judicial skepticism. The Specht v. Netscape (2nd Cir. 2002) case established the modern framework. Best practice: always require affirmative click-through during installation. (3) DMCA Section 1201 (17 USC §1201) prohibits circumvention of technological access controls. The Software Interoperability Exception (17 USC §1201(f)) allows reverse engineering for interoperability — but the EULA can prohibit it for OTHER purposes. The "except as expressly required by applicable law" carve-out in this template (Section 3) is essential to avoid over-broad reverse-engineering prohibitions that fail in some jurisdictions (e.g., EU Software Directive, France, Australia have stronger protected-reverse-engineering rights). (4) Implied warranties — UCC §2-314 (merchantability) and §2-315 (fitness for particular purpose) apply to "goods" but software status under UCC has been disputed. Most courts treat packaged software as a good and SaaS as a service. The "AS IS" disclaimer (Section 8) is essential to limit warranty exposure. (5) Limitation of liability — most jurisdictions enforce caps but with limits: gross negligence and intentional misconduct cannot be disclaimed; consumer-protection laws may override (e.g., Massachusetts G.L. c. 93A bars unfair-business-practice exclusions; California Civil Code §1668 limits liability waivers for fraud). (6) Auto-update consent — many EULAs reserve the right to push updates. Recent case law (Apple v. Pepper, 2019) and increasing privacy regulation make explicit consent for telemetry and updates more important. (7) Data privacy — GDPR (EU), CCPA/CPRA (California), and similar regimes treat customer data flowing through SaaS products as Licensee's data, with the Publisher acting as a "processor" under GDPR Article 28. The EULA should reference (or incorporate by attachment) a Data Processing Agreement (DPA) for B2B SaaS. (8) Export control — software is subject to the Export Administration Regulations (15 CFR Parts 730-774) administered by the Bureau of Industry and Security (BIS), and OFAC sanctions (31 CFR Parts 500-598). Encryption-using software requires special considerations under EAR Category 5 Part 2. Embargo-country prohibitions (Cuba, Iran, North Korea, Syria, Russia post-2022) are strict-liability — even an inadvertent download from a sanctioned country can trigger civil penalties. (9) Open-source components — most modern software incorporates open-source libraries (MIT, Apache, BSD, GPL, AGPL, MPL). The EULA should disclose this and refer Licensee to a separate notices file. GPL/AGPL combination with proprietary code can trigger viral licensing obligations — compliance review is critical before shipping. (10) Termination — typical scope: immediate for breach, with notice for non-payment. Post-termination: Licensee must uninstall and certify destruction. For SaaS, also include data-export rights for a transition period. State considerations: California, Delaware, and New York are the standard governing-law choices for B2B software. California has strict consumer-protection laws that affect even B2B EULAs distributed in California; many publishers carve out California for some provisions. New York has well-developed tech-transfer case law. Delaware is preferred when the software is sold to enterprise customers. Use this template for: SaaS B2B products, on-premises enterprise software, developer tools, embedded software. For consumer-facing products (mobile apps, desktop apps), use a more accessible click-wrap structure with prominent acceptance, plain-language summary, and platform-specific terms (Apple App Store, Google Play, Microsoft Store have additional requirements). For high-value enterprise sales (>$100K ACV), the EULA is often replaced or supplemented with a negotiated Master Software License Agreement (MSLA) with custom terms.

When to use it

Releasing a B2B software product (perpetual or subscription).
Releasing developer tools or APIs that require accepted terms before access.
Embedded software that ships with hardware products.
On-premises enterprise software installed on customer infrastructure.
SaaS products (paired with a separate Terms of Service and Data Processing Agreement).

What to include

License grant with type (perpetual / subscription / trial / freemium).
License scope (per-user / per-device / per-seat / site / enterprise).
Permitted use cases (positive scope).
Prohibited activities (reverse-engineering, redistribution, etc.).
Ownership clarity (license, not sale).
Updates and upgrades policy.
Support tier.
Data and privacy (with DPA reference for B2B SaaS).
Warranty disclaimer (AS IS).
Limitation of liability with cap.
Indemnification (Licensee to Publisher).
Export control (EAR / OFAC).
Termination and survival.
Governing law and dispute resolution (often arbitration).

Frequently asked

Yes — generally. Click-through (user clicks "I Agree" before access) is enforceable in nearly every US jurisdiction. Browse-wrap (terms linked at the bottom of a website with no explicit acceptance) faces more judicial skepticism (Specht v. Netscape, 2nd Cir. 2002). Best practice: require affirmative click-through during installation, with the EULA scrollable in a clear window before the "I Agree" button is enabled.

⚠ Legal disclaimer. Software EULAs are governed by federal copyright law (17 USC), federal export-control law (Export Administration Regulations 15 CFR Parts 730-774; OFAC sanctions 31 CFR Parts 500-598), and state contract law. UCITA has been adopted only in Maryland and Virginia; other states use general contract law and UCC by analogy. Click-through enforceability requires explicit acceptance (Specht v. Netscape, 2nd Cir. 2002). Reverse-engineering prohibitions are subject to interoperability exceptions (17 USC §1201(f)). Liability caps are subject to state consumer-protection law (e.g., Massachusetts G.L. c. 93A, California Civil Code §1668). For data-processing software, separate Privacy Policy and Data Processing Agreement (GDPR Article 28) are typically required. Open-source compliance requires careful management. For enterprise sales, use a negotiated Master Software License Agreement. Not legal advice.

Jurisdiction: United States — federal Copyright Act 17 USC §101 et seq. (software as literary work); DMCA 17 USC §1201 (anti-circumvention); UCC §2-316 warranty disclaimers + §2-719(3) limitation of consequential damages; state UCITA where adopted (MD + VA only); Cal. CCPA / CPRA Civ. Code §1798.100 et seq. + state-equivalents (CO CPA, CT CTDPA, VA VCDPA, UT UCPA, TX DPSA); ProCD v. Zeidenberg, 86 F.3d 1447 (7th Cir. 1996) (shrinkwrap + clickwrap enforceability).

Last reviewed: 2026-05

Reviewed by ScoutMyTool — consult a licensed attorney for binding use.