Limitation of Liability Clauses in Minnesota

How do Minnesota courts decide whether a liability cap is enforceable?

Between businesses, Minnesota courts enforce limitation-of-liability clauses under common-law contract-construction principles. Consumer services are the exception: Minn. Stat. § 604.055, subd. 1, makes void an agreement “for a consumer service, including a recreational activity, that purports to release, limit, or waive the liability of one party for damage, injuries, or death resulting from conduct that constitutes greater than ordinary negligence.” The starting point is whether the language is clear and unambiguous. If it is, and both sides had a fair chance to read and negotiate, courts usually enforce the cap as written. If the language is ambiguous, the court reads the ambiguity against the drafter, which almost always means against the party trying to enforce the cap. That single rule is why the best limitation clauses are short, direct, and use defined terms rather than generic “any and all” language.

Beyond clarity, courts look at bargaining power, sophistication of the parties, whether the clause is conspicuous (bolded, all-caps, or set off in its own section is good; buried in paragraph 38 is bad), and whether public policy blocks enforcement for the type of harm at issue. A cap written for a software license between two companies will often be enforced; the same words pasted into a consumer-facing home-services contract may not. The legal test is not a checklist. It is a weighing exercise that turns on facts. The general 7 factors that affect contract enforceability apply here too.

What carve-outs should survive a liability cap?

Certain categories of wrongdoing should sit outside the cap, not inside it, because courts may refuse to enforce a contract term that tries to release a party from its own worst conduct. The standard carve-out set in Minnesota business contracts: fraud, willful or intentional misconduct, and gross negligence. Some drafters also carve out breaches of confidentiality, indemnification obligations for third-party IP infringement, and any liability that cannot be limited by law. Carving these out protects the rest of the cap. Leaving them inside can make the cap vulnerable as applied to those claims and can create severability fights when a court has to decide whether to strike the unenforceable portion or the entire clause.

The drafting pattern is straightforward. After stating the cap, add a sentence that begins, “Notwithstanding the foregoing, the cap shall not apply to…” and list the carve-outs. Order matters less than completeness. The carve-outs for fraud and intentional misconduct are the most important because they are the ones a court is most likely to read in anyway; spelling them out just confirms the parties understood the rule. For how similar carve-outs work in the indemnification context, see indemnity carve-outs for gross negligence and fraud.

Are gross negligence and willful misconduct always carved out?

A court is likely to treat willful misconduct as outside the cap even if the contract is silent, but not gross negligence in a contract between businesses. The Minnesota Supreme Court treats an exculpatory clause as unenforceable if it “purports to release the benefited party from liability for intentional, willful or wanton acts” (Yang v. Voyagaire Houseboats, Inc., 701 N.W.2d 783 (Minn. 2005)), so a cap is unlikely to protect a party from its own intentional or willful wrongdoing even when the contract is silent. Gross negligence is treated differently. Minn. Stat. § 604.055 voids a release of liability for conduct “greater than ordinary negligence” only in agreements “for a consumer service,” so in a business-to-business contract no statute supplies a gross-negligence carve-out, and the safer course is to write one in.

Even where a court would imply part of the carve-out, silent-cap clauses get challenged, and challenges are expensive to defend. An express carve-out for fraud, gross negligence, and intentional misconduct resolves the argument on the page, before it ever reaches a motion. A party may try to delete these carve-outs during negotiation to “tighten” the cap. That is almost always the wrong move: the cap may not protect the drafter if a court later refuses to enforce it as applied to fraud or intentional-misconduct claims, and the deletion creates avoidable litigation risk if the relationship breaks. The drafting principles here overlap with liability caps for breach of confidentiality, where the same carve-out logic applies.

What does “not liable for data collection” mean in a contract?

A clause saying a party is “not liable for data collection” disclaims responsibility for harm that comes from gathering, storing, or using information. You usually see it in two places: a vendor’s contract, where the vendor refuses responsibility for data the customer chooses to upload or for data a third-party tool collects, and a website’s terms of use, where the site owner tries to disclaim responsibility for what it gathers from visitors. Read the clause as a risk allocation between the people who signed it. It decides which of the two signers absorbs a data loss as between themselves; it does not bind a consumer who never agreed to it, and it does not bind a regulator.

Minnesota’s consumer data privacy law limits what such a clause can do for a business the law reaches. The Act covers businesses that, among other thresholds, control or process “personal data of 100,000 consumers or more” in a calendar year (Minn. Stat. § 325M.12, subd. 1). It defines processing to include “the collection, use, storage, disclosure, analysis, deletion, or modification of personal data” (Minn. Stat. § 325M.11(q)), so data collection is squarely within the statute. And it says: “In no event shall any contract relieve a controller or a processor from the liabilities imposed on a controller or processor by virtue of the controller’s or processor’s roles in the processing relationship under sections 325M.10 to 325M.21” (Minn. Stat. § 325M.13(f)). A disclaimer in your contract therefore does not remove what the Act itself imposes on you. On a consumer-facing site, the same statute also says that “Acceptance of a general or broad terms of use or similar document that contains descriptions of personal data processing along with other, unrelated information does not constitute consent” (§ 325M.11(f)), so a data disclaimer buried in general terms does not double as the consumer’s consent.

How broadly should a data-breach carve-out be defined?

Customers often ask that liability for a data breach sit outside the cap, or under a separate, larger cap, because a breach can cost far more than the fees paid under the contract. The hard part is defining the exception. Drawn too narrowly, it misses the incident that actually happens; drawn too broadly, it swallows the cap, because nearly every modern service touches data. Weigh three factors when you set the scope:

• How sensitive the data is. Social Security numbers, account numbers, and health information justify broader protection than a marketing email list.
• Who controls the data. A party should carry the uncapped risk for systems it runs and data it decides how to use, not for a breach on the other side’s network. Under Minnesota’s privacy law, whether a business is the “controller” (the one that decides why and how data is processed) or the “processor” (the one handling it on someone else’s behalf) “is a fact-based determination that depends upon the context in which personal data are to be processed” (Minn. Stat. § 325M.13(g)), so the contract’s labels should match what each party actually does.
• What the law already requires of each side. Minnesota’s breach-notice statute requires a business that “maintains data that includes personal information that the person or business does not own” to notify the owner “immediately following discovery” of a breach (Minn. Stat. § 325E.61, subd. 1(b)). A carve-out keyed to a party’s failure to meet a duty like that one is easier to apply than one keyed to any incident involving data.

A practical pattern ties the exception to a defined “Security Incident” caused by the party’s breach of its own security or confidentiality obligations, and then says which costs it covers: notification, credit monitoring, forensic investigation, and third-party claims are the usual list.

Should privacy and data-breach liability sit outside the cap?

There is no single answer; it is one of the most negotiated points in a technology or services contract. The party holding the data usually argues for a “super-cap” (a second, higher limit just for data claims, often sized to its cyber insurance) rather than unlimited exposure. The customer usually argues that a breach involving personal information is the risk it most needs covered, so a fee-based cap leaves it carrying the loss it hired the vendor to prevent. A super-cap is often where the two sides land, because it gives the customer real protection and gives the vendor a number it can insure.

Regulatory exposure belongs in that conversation. Minnesota’s consumer data privacy law, in force since July 31, 2025, makes a controller or processor that violates it “liable for a civil penalty of not more than $7,500 for each violation” (Minn. Stat. § 325M.20(c)). That figure is set by statute and can change, so confirm it against the current section before you price a super-cap around it. Because penalties are counted per violation, a single incident affecting many consumers can produce a number no fee-based cap was built for.

How are regulatory fines, penalties, and third-party claims treated under a cap?

A liability cap governs what one contracting party can recover from the other. It does nothing to a fine a government agency imposes: the agency is not a party to your contract, and the fine is owed regardless of what the cap says. The real question is whether the party that paid the fine can recover it from its counterparty when the counterparty’s breach caused the violation, and whether that recovery counts against the cap.

Answer that question on the page. A well-drafted clause says expressly whether fines, penalties, and sanctions the other party’s breach caused are recoverable at all, and if so whether they sit inside the general cap, under a super-cap, or outside any cap. Silence leaves you to the contract-construction fight described above, where ambiguity runs against the drafter. Third-party claims (lawsuits by customers, consumers, or rights-holders who never signed your contract) are usually handled through the indemnification clause, and the interaction between that clause and the cap is covered in the indemnification section below.

How does bargaining power affect enforceability?

Bargaining power is one of the first things a Minnesota court examines when a liability cap is challenged. Two sophisticated businesses negotiating a commercial contract through counsel sit at one end of the spectrum: the cap almost always sticks. A take-it-or-leave-it contract handed to a consumer with no meaningful opportunity to negotiate sits at the other end, and the cap faces real unconscionability risk. Most contracts live somewhere in between, and the analysis gets fact-intensive fast.

The factors that weigh in: whether the party being capped had counsel, whether the clause was conspicuously drawn to their attention, whether they had a meaningful alternative (another vendor, another deal structure), and whether the price paid reflects the risk allocation. A low price combined with a tight cap can be defensible when both sides understood the trade-off. The same cap paired with a premium price and no discussion of risk allocation looks different. Minnesota’s unconscionability doctrine is described in the MN legal standard for unconscionable contracts. Where the cap is in a consumer-facing form contract, also review the overlap with unconscionable contracts generally.

Does it matter whether the other side is a consumer or another business?

Yes. The contract-construction rules are the same, but a consumer cap has to earn enforcement on the bargaining-power, conspicuousness, and adhesion factors above, while a business-to-business cap with clear language and evidence of negotiation usually survives. Consumer-protection statutes can also blunt caps in specific contexts that go beyond the common-law rules, and those overlays vary by industry. A cap in a home-improvement contract, a healthcare contract, or a clickwrap consumer product contract can hit statutory limits the parties did not anticipate. If your business has both B2B and consumer versions of the same product, the liability clause should almost never be identical in both. For more on consumer-facing risk, see contract clauses violate consumer protection laws and the clickwrap-specific analysis in are clickwrap agreement liability waivers enforceable.

How does a liability cap interact with a consequential-damages waiver?

The liability cap and the consequential-damages waiver do different work and should sit in different sentences. The cap limits the total dollar amount a party can owe. The consequential-damages waiver removes whole categories of damages (lost profits, lost business opportunities, loss of goodwill, downstream losses to the customer’s customers) from the universe of recoverable harms. A contract can have one, both, or neither. The strongest protection uses both, drafted separately, with each clause doing its own job.

Combining them in a single sentence almost always creates ambiguity. A court reading “Supplier’s total liability shall not exceed fees paid, excluding consequential damages” could read that as a cap on direct damages with consequential damages separately barred, or as a cap that somehow includes consequential damages in a way the parties cannot later recover. Minnesota courts apply the contra proferentem rule (ambiguity construed against the drafter), so the less protective reading often wins. The safer pattern is two back-to-back clauses, each in its own numbered section, each with its own carve-outs. For the damages side of that analysis, see consequential vs. direct damages in business contracts and consequential damages in contract breaches.

How does a liability cap interact with an indemnification obligation?

In practice, how the cap interacts with indemnity turns on the contract language; silence produces expensive fights, and the outcome depends on which clause the court reads as controlling. A supplier agrees to indemnify the customer for third-party IP infringement claims, then learns that its indemnity obligation might be capped at the fees the customer paid, which is often far less than the cost of defending the suit. The supplier thought it was giving meaningful protection; the customer thought it was getting meaningful protection; nobody negotiated the interaction.

The fix is an express statement. The contract should say whether the cap applies to indemnified claims, and if so, whether any indemnity obligations sit outside the cap. IP indemnification is frequently carved out of the cap (or given its own separate, larger cap) because IP exposure is often uninsurable and asymmetric. General contract indemnities are more often kept inside the cap. The negotiation point is not which answer is right in the abstract; it is which answer matches the risk the parties actually want to allocate. For the companion concept, see indemnification clauses in Minnesota contracts.

Are there public-policy limits on limitation clauses?

Yes. Besides the intentional-misconduct rule and the consumer-services statute covered in the carve-outs section above, Yang also treats an exculpatory clause as unenforceable if it “contravenes public policy.” Parties also cannot use private contract language to neutralize duties the law imposes on the public interest. That rule reaches beyond the standard carve-out list. For example, certain safety-related obligations, fiduciary duties, and statutory rights cannot be waived by contract, regardless of how clearly the clause is drawn.

The practical consequence is that a liability cap is not a universal shield. It is strongest against ordinary breach and negligence claims between sophisticated parties and weakest against intentional wrongdoing, fiduciary breaches, and statutory violations. A business owner who assumes the cap closes every exposure in the contract can discover after a dispute that the cap did not reach the claim the other side actually brought. The best drafting response is to know which claims the cap actually limits, which it does not, and to size insurance accordingly.

Are carve-outs enforceable in international contracts?

They can be, but this article’s Minnesota analysis applies only when Minnesota law governs the contract. In a cross-border deal, enforceability turns on two choices the contract makes: which country’s or state’s law governs, and where disputes are heard (a named court or an arbitration seat). Another country’s law may treat a cap or a carve-out differently than Minnesota law does, and the tribunal hearing the dispute applies its own procedural and public-policy rules. Decide both questions in the contract rather than leaving them to a later fight, and before you rely on a cap or carve-out under foreign law, have counsel admitted in that country read it.

What are the tax implications of liability cap carve-outs?

The cap and its carve-outs decide how much one party owes the other; the tax code decides how the payment is treated. Federal law allows a deduction for “all the ordinary and necessary expenses paid or incurred during the taxable year in carrying on any trade or business” (26 U.S.C. § 162(a)). It also denies a deduction “for any amount paid or incurred (whether by suit, agreement, or otherwise) to, or at the direction of, a government or governmental entity in relation to the violation of any law,” subject to exceptions for amounts identified as restitution or as paid to come into compliance with the law (§ 162(f)). So a regulatory fine you pay sits under a different tax rule than contract damages you pay to a customer, even when both arrive in the same dispute. How a specific payment is characterized is a question for your tax advisor, and it is worth asking before a settlement agreement labels the payment.

What drafting patterns hold up best?

A few patterns repeatedly survive Minnesota scrutiny. First, the cap sits in its own numbered section with a clear heading (“Limitation of Liability”), not buried inside a larger clause. Second, the cap is in conspicuous type (bolded or all-caps for the key limiting language) so there is no question the other side was on notice. Third, the carve-outs are express: fraud, intentional misconduct, gross negligence, indemnification obligations (if appropriate), and any liability that cannot be limited by law. Fourth, the consequential-damages waiver sits in its own sentence, not folded into the cap. Fifth, the cap amount is tied to something specific and measurable (fees paid in the prior 12 months, insurance proceeds, a stated dollar figure), not zero and not an arbitrary nominal amount.

The structural point is that limitation-of-liability clauses fail more often from sloppy drafting than from hostile law. Minnesota’s common-law rules are more predictable when the clause is clear, conspicuous, and used between sophisticated parties. A careful clause with clear language, conspicuous presentation, and proper carve-outs enforces cleanly most of the time. A clause that tries to do too much, obscures the limitation, or ignores unequal bargaining power invites the challenge and often loses it. For additional drafting context on related clauses, see 5 contract clauses every growing business should understand.

Closing thought

A limitation-of-liability clause is not a boilerplate paragraph. It has to match the contract it lives in, the parties who signed it, and the risks the business actually faces. Minnesota’s common-law approach gives drafters real room to allocate risk, but only if the clause is written with care: clear language, express carve-outs, conspicuous presentation, and a cap tied to something the parties actually bargained for. For a practical read on the specific clause you are about to sign or send, see my Minnesota business contract practice. Email me at aaron@aaronhall.com to start an intake and conflict check before sending confidential documents.