EULA enforceability has a fraud ceiling. A limitation of liability protects you against most claims, but not against fraud.
Short answer: whether a third party can use or access your software is up to your agreement, not the customer. One court held that letting a third party use the software, even for the customer’s benefit, breached the license. So decide the rule and write it down. This question comes
Short answer: review your EULA or SaaS contract at least once a year, and any time you change your model or launch an offering. The goal is simple: make sure the paper still matches how you actually sell, and simplify it while you are in there. Adjust your contracts to
Copyright law does not stop your customers from reverse engineering your software, your contract has to, and even then courts have carved out fair-use exceptions for interoperability.
Short answer: in most software EULAs, the customer owes you for licenses it installed, not just the ones it actually uses. A reported case involving the Los Angeles County Sheriff drove the point home, and it is a useful teaching tool when a customer claims it should only pay for
Use a contract when you need a commitment neither side can change unilaterally (caps, indemnities, service levels); use a policy when you need the freedom to change the rules as your business evolves (security practices, support hours, acceptable use).
Short answer: the agreement you send to close a deal telegraphs how serious and sophisticated your company is, before anyone reads a word about your product. A long, confusing one says “amateur”; a short, clear, fair one says “we do this all the time.” When a software, SaaS, or other
If customers reach your software in a browser, you need a SaaS subscription agreement; if they download and install it, you need an EULA. The form follows what you deliver, not what you call your company.
A license is permission, not ownership. How the grant clause and the license metric set its limits, and why your software should enforce what the contract says.
If you want to write better SaaS agreements and EULAs, give whoever drafts them one instruction: simplify.
Short answer: copyright protects your software automatically, but a license agreement (a contract) lets you define and limit exactly how the customer may use it. Smart software companies rely on the right mix of both, not one alone. While this is a complex legal issue, let me try to simplify
Short answer: the end user agreement purpose is broader than most vendors realize. In software and SaaS, an end user agreement does more than allocate risk. Its real job is to explain and support your business model, set expectations, and stay readable, with “what happens if things go wrong” as
Short answer: yes, you can reserve the right to change your software contract, but a clause that lets you change “any term at any time in your sole discretion” can backfire badly. In Harris v. Blockbuster, that exact language made the company’s arbitration clause unenforceable, because a promise you can
Short answer: software license transfer M&A and corporate reorganization scenarios have one controlling question: what does your assignment clause say? Your customer can transfer your software in a reorganization only if your agreement says they can. Transfers on a merger, acquisition, stock sale, asset sale, or internal restructuring are governed
Short answer: a well drafted EULA can end a lawsuit before it ever reaches a jury. In Hayes v. SpectorSoft Corporation (E.D. Tenn., November 3, 2009), the software maker won summary judgment and walked away from the case, and the way the end user agreement was written was a big
Get started with a free initial consultation. Fill out the form below to connect with our experts today!