Software License Agreement Template (Free Sample)
A license agreement is a contract in which the owner of software or other intellectual property (the licensor) gives someone else (the licensee) permission to use it on stated terms, while keeping ownership. A software license agreement or end user license agreement (EULA) grants a right to install and use a copy of software; it does not sell the software. Below: how a EULA differs from a business software license agreement, SaaS terms of service and an IP or trademark licensing agreement, the clauses to include, when online "click to accept" terms are enforceable, and a free sample software license agreement you can copy into Word.
Drafting a license agreement in Word? LexDraft drafts a first version from your plain-English description and reviews it with tracked-change redlines.Free plan: 5,000 generated words a month, no credit card.
Install free in WordLast checked: 23 October 2026. This page is general information about United States law and practice, not legal advice. Contract and intellectual property law varies by state and by country, and the rules for online terms continue to develop in the courts. Have qualified counsel review a license agreement before it is used.
What is a license agreement?
A license is permission. Without it, copying, installing or using someone else's copyrighted software, patented invention or trademark can infringe the owner's rights. A license agreement sets the limits of that permission: what may be used, by whom, for what purpose, where, for how long and for what fee. Everything the license does not grant stays with the licensor.
Most license agreements also contain ordinary contract terms: payment, warranties, limits on liability, indemnities, confidentiality, termination and governing law. Those terms decide who bears the risk if the software fails, infringes a third party's rights, or is used outside the license.
EULA vs software license agreement vs SaaS terms vs IP licensing agreement
These documents overlap, and what matters legally is what the document says, not its title. In general US usage:
| Document | What is licensed | Who it is for | How it is usually accepted | Typical content |
|---|---|---|---|---|
| End user license agreement (EULA) | A right to install and use a copy of software or an app. | Individual users or businesses, often on standard terms nobody negotiates. | Clicking "I agree" on installation, sign-up or first launch. | Limited grant, use restrictions, no reverse engineering, warranty disclaimer, liability cap, termination. |
| Software license agreement (B2B) | Installed or on-premises software, often with support and maintenance. | A business customer; often negotiated. | Signed by both parties, sometimes with an order form. | Grant scope (users, devices, sites), fees, delivery, acceptance, warranty, IP indemnity, audit, liability cap, termination. |
| SaaS terms of service | Access to software the provider hosts; the customer usually gets no copy to install. | Subscribers, from individuals to enterprises. | Clickwrap for standard plans; a signed SaaS agreement or MSA for larger customers. | Subscription and access rights, acceptable use, service levels, data protection, customer data ownership, fees, suspension, termination. |
| IP or trademark licensing agreement | Patents, copyrights, trademarks, brands or know-how, often to make or sell products. | Manufacturers, brand owners, franchisors, universities and inventors. | Signed by both parties after negotiation. | Field of use, territory, exclusivity, royalties and reports, quality control (for trademarks), improvements, enforcement, sublicensing. |
If you are reviewing a license someone else drafted, see the license agreement review guide or the software license agreement review guide. For hosted software, see the SaaS agreement review guide.
What to include in a license agreement: checklist
- Grant and scope. What is licensed (name the software, version and documentation, or the patents and marks), and exactly what the licensee may do: install, use, copy, modify, distribute or sublicense. Limit it by number of users, devices, sites or instances, and by purpose, such as "internal business purposes".
- Exclusive or non-exclusive. Most software licenses are non-exclusive. An exclusive license should say whether the licensor itself may still use or license the IP, and in what field or territory exclusivity applies.
- Territory. Where the licensee may use the software or sell licensed products. Worldwide is common for software; IP and brand licenses are often limited by country or region.
- Term. Perpetual, a fixed term, or a subscription that renews. Say how renewal works and how either side stops it.
- Fees or royalties. One-time license fee, annual fee, subscription or a royalty on sales. Set payment dates, invoicing, taxes, late charges and, for royalties, the royalty base, reports and records.
- Restrictions. No reverse engineering (to the extent applicable law allows the restriction), no sublicensing, renting or sharing access, no use to build a competing product, and no removal of proprietary notices.
- IP ownership. The licensor keeps all rights not expressly granted. State who owns modifications, improvements, feedback and anything the licensee creates using the software.
- Warranties and disclaimer. Any limited warranty (for example, that the software will substantially conform to its documentation for a set period), the remedy if it does not, and a disclaimer of other warranties.
- Limitation of liability. A cap on damages (often the fees paid in a set period), an exclusion of indirect and consequential damages, and any carve-outs from the cap, such as indemnity obligations or breach of confidentiality. For a perpetual license paid upfront, a rolling 12-month fee cap can eventually fall to zero; decide whether to include the original license fee or a negotiated minimum instead.
- Indemnity. Usually the licensor defends the licensee against claims that the software infringes third-party IP, with remedies such as modifying the software, obtaining a license or refunding fees. The licensee may indemnify for misuse.
- Termination. Termination for breach after a cure period, for insolvency where enforceable, and for convenience if agreed. Say what happens on termination: stop using the software, delete copies, certify deletion, pay amounts owed.
- Audit and compliance. The licensor's right to check use against the license, with reasonable notice, frequency limits, confidentiality and who pays if an audit finds underpayment.
- Export controls and sanctions. Software with encryption or other controlled technology may be subject to US export rules (the Export Administration Regulations) and US sanctions. A clause commits the licensee not to export or use the software in breach of them.
- Governing law and disputes. Which state's or country's law applies, which courts have jurisdiction, and any arbitration clause.
- Third-party and open source components. Components licensed under their own terms, which govern those components.
- General terms. Assignment and change of control, confidentiality, notices, entire agreement, order of precedence with order forms, and any terms that survive termination.
License, not sale: ownership and first sale
Software licenses usually state that the software is "licensed, not sold". The wording matters because of the first sale doctrine in US copyright law (17 U.S.C. 109): the owner of a lawfully made copy can generally resell or give away that copy without the copyright owner's permission. A licensee who is not the owner of the copy does not get that right.
The label alone is not always decisive. In Vernor v. Autodesk, 621 F.3d 1102 (9th Cir. 2010), the Ninth Circuit held that a software user is a licensee rather than an owner of a copy where the copyright owner specifies that the user is granted a license, significantly restricts the user's ability to transfer the software, and imposes notable use restrictions. Other courts have taken different approaches, so a license agreement should not rely on the label alone: it should also contain the transfer and use restrictions that reflect a license.
Clickwrap vs browsewrap: are online license terms enforceable?
A EULA or terms of service is often accepted online rather than signed. US courts generally ask whether the user had reasonable notice of the terms and clearly showed agreement to them. Results depend on the facts and the court, but some patterns are well established:
- Clickwrap (the user must click "I agree" or tick a box next to the terms before continuing) is generally enforced, especially when the terms are presented or linked right next to the button.
- Browsewrap (the terms are only available through a link, often at the bottom of a page, and the user is never asked to agree) is often not enforced. In Specht v. Netscape Communications Corp., 306 F.3d 17 (2d Cir. 2002), users who downloaded free software were not bound by license terms that were visible only by scrolling below the download button. In Nguyen v. Barnes & Noble Inc., 763 F.3d 1171 (9th Cir. 2014), a website's terms linked at the bottom of each page did not bind a user who had no actual knowledge of them.
- Sign-in wrap (a notice such as "By creating an account, you agree to the Terms" next to a button) falls in between. Courts have enforced it where the notice and link were reasonably conspicuous, as in Meyer v. Uber Technologies, Inc., 868 F.3d 66 (2d Cir. 2017), and have refused to where the notice was inconspicuous and did not make clear that clicking the button signified agreement, as in Berman v. Freedom Financial Network, LLC, 30 F.4th 849 (9th Cir. 2022).
- Shrinkwrap (terms inside the box, accepted by using the software) was enforced in ProCD, Inc. v. Zeidenberg, 86 F.3d 1447 (7th Cir. 1996), where the buyer could return the software if it did not accept the terms.
In practice: present the terms before the user agrees, put an "I agree" checkbox or button next to a clear link, do not pre-tick the box, keep a record of which version each user accepted and when, and give notice and a new acceptance when terms change materially. Consumer protection laws can also make particular terms unenforceable against consumers whatever the method of acceptance.
Free software license agreement template (sample text)
Copy the text below into Word and fill in the brackets. It is an original, general US sample of a non-exclusive software license agreement between two businesses for installed (on-premises) software, with a perpetual or fixed-term license and an annual support option. It is a starting point, not a finished agreement: it is not tailored to any state, industry or product, it is not a consumer EULA, and it does not cover hosted SaaS, source code licensing, or patent and trademark licensing. Have qualified counsel review it before use.
Sample: software license agreement (fill-in template)
SOFTWARE LICENSE AGREEMENT
This Software License Agreement (this "Agreement") is made as of [date] (the "Effective Date") between [Licensor legal name], a [State] [entity type] ("Licensor"), and [Licensee legal name], a [State] [entity type] ("Licensee").
1. Definitions. "Software" means Licensor's [product name] software, version [number], in object code form, and any updates Licensor provides under Section 5. "Documentation" means Licensor's user guides and specifications for the Software as provided to Licensee. "Authorized Users" means Licensee's employees and individual contractors who use the Software for Licensee's benefit, up to the number stated in Schedule A. "Schedule A" means the schedule attached to this Agreement stating the license scope, fees and term.
2. License Grant. Subject to Licensee's compliance with this Agreement and payment of the fees, Licensor grants Licensee a non-exclusive, non-transferable (except under Section 15(a)), non-sublicensable license during the License Term to install and use the Software and Documentation, solely for Licensee's internal business purposes, by Authorized Users, on up to [number] [devices / servers / instances], in [the United States / worldwide] (the "Territory"). Licensee may make a reasonable number of copies of the Software for backup and archival purposes, each of which must include Licensor's proprietary notices.
3. Restrictions. Except as expressly permitted by this Agreement, Licensee will not, and will not allow anyone else to: (a) copy, modify or create derivative works of the Software; (b) reverse engineer, decompile or disassemble the Software, except to the extent applicable law permits this despite this restriction; (c) sell, rent, lease, lend, sublicense, distribute or provide the Software to any third party, or use it to provide services to third parties; (d) remove or alter any proprietary notices; (e) use the Software to build a competing product; or (f) use the Software in violation of applicable law or outside the Territory.
4. Ownership; License, Not Sale. The Software is licensed, not sold. Licensor and its licensors own and retain all right, title and interest, including all intellectual property rights, in the Software, the Documentation and all copies, updates and modifications of them. All rights not expressly granted in this Agreement are reserved. If Licensee gives Licensor suggestions or feedback about the Software, Licensor may use them without restriction or payment.
5. Delivery, Support and Updates. Licensor will make the Software available for download within [number] days after the Effective Date. [If Licensee pays the annual support fee in Schedule A, Licensor will provide the support and updates described in Schedule A during each paid support year.] Updates are part of the Software and are subject to this Agreement.
6. Fees and Payment. Licensee will pay the fees in Schedule A within [30] days after the date of each invoice. Fees are stated in US dollars and do not include sales, use, value-added or similar taxes, which Licensee will pay (other than taxes on Licensor's income). Overdue amounts bear interest at the lesser of [1]% per month and the highest rate permitted by law. Except as stated in Sections 9 and 11, fees are non-refundable.
7. Confidentiality. Each party will use the other party's non-public information that is marked or reasonably understood to be confidential, including the Software and the terms of this Agreement, only to perform this Agreement, and will not disclose it except to its employees, contractors and advisers who need to know it and are bound by confidentiality obligations at least as protective. This Section does not apply to information that is or becomes public through no fault of the receiving party, was known to it without restriction, is independently developed, or is rightfully received from a third party without restriction. A party may disclose confidential information when required by law, after giving the other party prompt notice where legally permitted.
8. Audit. On at least [30] days' written notice, and no more than once in any 12-month period, Licensor or an independent auditor bound by confidentiality obligations may verify Licensee's use of the Software during normal business hours in a manner that does not unreasonably interfere with Licensee's business. If an audit shows use beyond the license scope, Licensee will pay the applicable fees for the excess use, and if the underpayment exceeds [5]% of the fees due for the audited period, Licensee will also reimburse the reasonable cost of the audit.
9. Limited Warranty and Disclaimer. Licensor warrants that, for [90] days after delivery, the Software will perform substantially in accordance with the Documentation when used as permitted by this Agreement. If Licensee reports a breach of this warranty during that period, Licensor will, at its option, repair or replace the Software or terminate the license for the affected Software and refund the license fee paid for it. This is Licensee's sole remedy for breach of this warranty. EXCEPT AS EXPRESSLY STATED IN THIS SECTION 9, THE SOFTWARE AND DOCUMENTATION ARE PROVIDED "AS IS", AND LICENSOR DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. LICENSOR DOES NOT WARRANT THAT THE SOFTWARE WILL BE ERROR-FREE OR OPERATE WITHOUT INTERRUPTION.
10. Limitation of Liability. EXCEPT FOR EXCLUDED CLAIMS, (a) NEITHER PARTY WILL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, REVENUE OR DATA, EVEN IF ADVISED OF THEIR POSSIBILITY; AND (b) EACH PARTY'S TOTAL LIABILITY ARISING OUT OF OR RELATING TO THIS AGREEMENT WILL NOT EXCEED THE FEES PAID AND PAYABLE BY LICENSEE UNDER THIS AGREEMENT IN THE [12] MONTHS BEFORE THE EVENT GIVING RISE TO THE LIABILITY. "EXCLUDED CLAIMS" MEANS A PARTY'S OBLIGATIONS UNDER SECTION 11, A BREACH OF SECTION 7, LICENSEE'S BREACH OF SECTION 2 OR 3, AND LICENSEE'S OBLIGATION TO PAY FEES.
11. Infringement Indemnity. (a) Licensor will defend Licensee against any third-party claim alleging that the Software, as delivered and used in accordance with this Agreement, infringes a United States patent, copyright or trademark or misappropriates a trade secret, and will pay the damages and costs finally awarded or agreed in settlement. (b) If the Software is, or in Licensor's opinion is likely to be, subject to such a claim, Licensor may at its option obtain the right for Licensee to continue using it, modify it to be non-infringing without materially reducing its functionality, or terminate the license for the affected Software. On that termination, Licensor will refund, for a perpetual license paid by a one-time fee, the license fee paid for the affected Software less straight-line amortization over [five] years from initial delivery, with the refund never less than zero. For a fixed-term or annually paid license, Licensor will instead refund the prepaid license fees attributable to the unused portion of the period those fees cover. License fees solely attributable to periods after termination of the affected license will no longer be payable. (c) Licensor has no obligation for claims arising from modifications not made by Licensor, combination with items not provided by Licensor, use other than as permitted by this Agreement, or use of a superseded version after Licensor provided a non-infringing update. (d) Licensee must notify Licensor promptly of the claim, give Licensor sole control of the defense and settlement (but Licensor may not settle in a way that admits fault by or imposes obligations on Licensee without Licensee's consent), and provide reasonable cooperation at Licensor's expense. This Section 11 states Licensor's entire liability, and Licensee's exclusive remedy, for infringement claims.
12. Term and Termination. (a) This Agreement starts on the Effective Date and continues for the license term stated in Schedule A [perpetual / [number] years, renewing for successive one-year terms unless either party gives notice of non-renewal at least [60] days before the end of the then-current term] (the "License Term"), unless terminated earlier under this Section 12. Licenses for affected Software may also be terminated under Sections 9 and 11. (b) Either party may terminate this Agreement by written notice if the other party materially breaches it and does not cure the breach within [30] days after receiving written notice describing it. (c) On termination or expiry of this Agreement, all licenses under it end. On termination of a license for affected Software under Section 9 or 11, only that license ends and this Agreement continues for any remaining Software. For each license that ends, Licensee will stop using the affected Software and Documentation, delete or destroy all copies of them in its possession or control, and certify this in writing on request. Licensee will pay fees accrued before the license ends, subject to any refund or cancellation of fees required by Sections 9 and 11. (d) Sections 3, 4, 6 (for amounts owed), 7, 8 (for [12] months after termination or expiry), 9 (disclaimer and any remedy for a warranty breach reported during the warranty period), 10, 11, 12(c) and 13 through 15 survive termination or expiry of this Agreement or an affected license.
13. Export Controls and Sanctions. Licensee will comply with all applicable export control and sanctions laws, including the US Export Administration Regulations and sanctions administered by the US Department of the Treasury's Office of Foreign Assets Control, and will not export, re-export, transfer or provide access to the Software in violation of them.
14. Third-Party Components. The Software may include third-party and open source components listed in the Documentation. Those components are licensed under their own license terms, which govern Licensee's use of them to the extent required by those terms.
15. General. (a) Assignment. Neither party may assign this Agreement without the other party's prior written consent, except that either party may assign it without consent to a successor to all or substantially all of its business or assets to which this Agreement relates, on written notice. (b) Governing law. This Agreement is governed by the laws of the State of [State], without regard to its conflict of laws rules, and the parties submit to the exclusive jurisdiction of the state and federal courts located in [county, State]. (c) Notices. Notices must be in writing and sent to the addresses in Schedule A. (d) Independent parties. The parties are independent contractors. (e) Severability and waiver. If any provision is held unenforceable, the rest of this Agreement remains in effect, and a failure to enforce a provision is not a waiver. (f) Entire agreement. This Agreement, including Schedule A, is the entire agreement between the parties about its subject matter and supersedes all prior agreements and understandings about it. Terms in any Licensee purchase order do not apply. Any amendment must be in writing and signed by both parties. (g) Counterparts. This Agreement may be signed in counterparts and electronically.
Schedule A. Software and version: [__________]. Authorized Users: [number]. Devices / servers / instances: [number]. Territory: [__________]. License Term: [perpetual / [number] years]. License fee: $[amount] [one-time / per year]. Annual support fee (optional): $[amount], covering [support hours, response times and updates]. Notice addresses: [Licensor] / [Licensee].
[LICENSOR LEGAL NAME] By: ______________________________ Name: [__________] Title: [__________] Date: [______]
[LICENSEE LEGAL NAME] By: ______________________________ Name: [__________] Title: [__________] Date: [______]
Not legal advice. This sample is not tailored to any state, industry or product. A consumer EULA needs different terms, and consumer protection laws limit warranty disclaimers and liability caps against consumers in some states. A hosted service needs SaaS terms (access, service levels, data protection), and patent, trademark or brand licensing needs terms such as royalties, reports and quality control. Have qualified counsel review the agreement before use.
Licensing patents, trademarks and other IP
An IP licensing agreement uses the same structure as a software license, with some terms that matter more:
- Field of use and exclusivity. A license can be exclusive in one field (for example, veterinary uses) and non-exclusive or unavailable in others. Say whether an exclusive licensee can sue infringers.
- Royalties and reports. Define the royalty base (for example, net sales and what is deducted), the rate, minimum royalties, reporting periods and record-keeping, and tie them to an audit right. For patents, the US Supreme Court reaffirmed in Kimble v. Marvel Entertainment, LLC, 576 U.S. 446 (2015), that a patent holder cannot collect royalties for use of a patented invention after the patent expires, so royalty terms that run past expiry need careful drafting.
- Quality control for trademarks. A trademark owner that licenses its mark without controlling the quality of the licensee's goods or services risks a finding that it has abandoned the mark ("naked licensing"). Trademark licenses usually include quality standards, approval rights and inspection.
- Improvements. Who owns improvements each party makes, and whether the other side gets a license to them.
Common mistakes in license agreements
- A vague grant. "Use the software" without limits on users, devices, purpose or territory invites disputes about what the licensee paid for.
- No "licensed, not sold" language or transfer limits. Without them, a licensee may argue it owns its copy and can resell it.
- Browsewrap acceptance for a EULA. Terms reachable only through a footer link, with no "I agree" step, may not bind anyone.
- Disclaimers that are not conspicuous. Courts differ on whether UCC Article 2 applies to software licenses. Where it applies, the general rule is that a merchantability disclaimer must mention merchantability and, if written, be conspicuous; a disclaimer of the implied warranty of fitness must be written and conspicuous. There are exceptions, including qualifying "as is" language. Capitals can help draw attention, but formatting alone does not ensure enforceability. Check the applicable state's law and the agreement's presentation.
- A liability cap with unclear carve-outs. If the cap does not say whether it covers indemnity, confidentiality and unpaid fees, each side will read it differently.
- Ignoring open source components. Open source licenses attach their own conditions. The license agreement should not promise rights in those components that the open source license does not give.
- No exit plan. No statement of what happens to copies, data and payments when the license ends.
How to draft or review a license agreement in Word with LexDraft
LexDraft is a Word add-in from Microsoft AppSource. It opens as a side panel in Word 365 (Windows and Mac), Word 2021 and Word on the web, so the license agreement stays in the document you are already editing.
Describe the agreement
Open LexDraft in Word and describe the license in plain English: the licensor and licensee, what is licensed, the users, devices and territory, the term, the fees, and the governing law. LexDraft asks a few clarifying questions, then writes a first draft into your document as editable Word text.
Review it against the governing law
To review a license agreement you drafted, or one you were given, pick the governing state and run a review. LexDraft has four built-in playbooks (NDA, SaaS MSA, DPA and services agreement) and no dedicated license agreement playbook, so an installed-software or IP license runs as a general review; if the deal is really a hosted subscription, use the SaaS MSA playbook. Findings are graded Critical, High, Medium or Low, and LexDraft flags standard terms that are missing.
Check and accept the redlines
Run the defined-term and cross-reference checks, which are rule-based and run without AI. Accept or reject each proposed redline; accepted changes land as native Word tracked changes. Nothing changes in your document until you accept a redline.
For a quick read of a single clause, such as a limitation of liability or indemnity clause, paste it into the free clause risk checker.
What LexDraft does not do: it does not give legal advice, search patents or trademarks, check chain of title, scan code or check open source compliance, or decide whether online terms are enforceable. You check every output before the agreement is signed or published.
Frequently Asked Questions About License Agreements
What is a license agreement?
A license agreement is a contract in which the owner of software or other intellectual property (the licensor) gives another party (the licensee) permission to use it on stated terms, such as which users, for what purpose, where, for how long and for what fee. The licensor keeps ownership, and every right the agreement does not grant stays with the licensor.
What is the difference between a EULA and a software license agreement?
A EULA (end user license agreement) is usually a standard, non-negotiated license that each user accepts by clicking "I agree" when installing or signing up. A business software license agreement is usually signed by both parties, can be negotiated, and covers more commercial terms, such as the number of users and devices, fees, support, audit rights and an infringement indemnity.
Is a EULA legally binding?
Often, but it depends on how it is presented. US courts generally enforce clickwrap terms, where the user must click "I agree" next to the terms, because the user had notice and showed agreement. Browsewrap terms, available only through a link the user is never asked to agree to, are often not enforced, as in Specht v. Netscape (2d Cir. 2002). Consumer protection laws can also make particular terms unenforceable.
Do you own software you buy?
Usually you own a license to use it, not the software. Software licenses commonly say the software is "licensed, not sold" and restrict transfer and use. In Vernor v. Autodesk (9th Cir. 2010), the Ninth Circuit held that a user who received software under that kind of license was a licensee, not the owner of the copy, so the first sale doctrine did not let the user resell it. Other courts have taken different approaches.
What is the difference between an exclusive and a non-exclusive license?
Under a non-exclusive license, the licensor can license the same rights to others and use them itself. Under an exclusive license, the licensor promises not to license those rights to anyone else in the defined field and territory, and depending on the wording may not use them itself. Most software licenses are non-exclusive; exclusive licenses are more common for patents, brands and content.
What should a licensing agreement include?
At a minimum: what is licensed and the scope of the grant (users, devices, purpose), whether it is exclusive, the territory and term, fees or royalties, restrictions, who owns the IP and any improvements, warranties and disclaimers, a limitation of liability, an infringement indemnity, termination and what happens after it, audit rights, export compliance and governing law.
Is a SaaS agreement a license agreement?
Not exactly. With SaaS the provider hosts the software and the customer gets a right to access and use the service, usually without receiving a copy to install. SaaS terms therefore focus on access, service levels, data protection, customer data and suspension, while an installed-software license focuses on copies, installation, transfer and deletion. Many SaaS agreements still use license language for the access right.
Can I use this template as a EULA for an app or for consumers?
Not as written. The sample on this page is a business-to-business license for installed software. For a consumer EULA or app terms, use an acceptance process that gives users clear notice of the terms and obtains their agreement; a clear clickwrap flow is a practical choice. The terms should follow applicable app store requirements and must comply with consumer protection laws, which in some states limit warranty disclaimers and liability limits against consumers. Have counsel adapt it.
Reviewing a license agreement someone else drafted?
Draft and review a license agreement in Word
Describe the agreement, get a first draft in your document, then review it with tracked-change redlines. You stay in Word, and you decide what changes.
Install LexDraft for WordThis page is general information, not legal advice. LexDraft does not give legal advice; have qualified counsel check every license agreement against the law that governs it. Spotted something out of date? Email support@lexdraft.ai and we will fix it.