Most Minnesota business owners ask the same question after handing me an NDA: will this actually hold up if my former employee or counterparty walks off with confidential information? The honest answer is that NDA enforceability in Minnesota turns mostly on common-law contract construction, not statute. Two statutes matter at the edges: the Minnesota Uniform Trade Secrets Act (“MUTSA”), Minn. Stat. § 325C.01, provides a parallel claim where the protected information qualifies as a trade secret, and Minn. Stat. § 181.988 (the 2023 noncompete ban) sets a hard outer boundary the NDA cannot cross. In my practice, the same drafting traps repeat across employment NDAs and business-to-business NDAs. This article walks through what makes a Minnesota NDA enforceable, where most templates fail, and how the noncompete ban changed the calculus. For related context, see our contracts practice overview.

What does Minnesota law require for an NDA to be enforceable?

Minnesota courts treat a nondisclosure agreement (“NDA”) as a contract. To enforce one, you need the standard contract elements (offer, acceptance, consideration, definite terms) plus a confidentiality restriction that is reasonable in scope, duration, and proportional to the legitimate interest the agreement protects. There is no Minnesota statute that codifies NDA enforceability. Courts apply common-law contract principles, and Minnesota courts resolve contract ambiguity against the drafting party.

That posture matters because the party trying to enforce the NDA almost always wrote it. If the agreement is ambiguous about what is “confidential,” Minnesota courts resolve the ambiguity against the drafting party. The same is true for scope and duration. The practical takeaway: the company that benefits from precise, narrow drafting is the company that wants to enforce later. Templates pulled from the internet rarely meet that bar.

How does Minnesota define “confidential information” under an enforceable NDA?

There is no statutory definition of “confidential information” for NDAs in Minnesota. The contract itself defines the term, and Minnesota courts read that definition against the company seeking enforcement. The closest statutory anchor is the trade-secret definition at Minn. Stat. § 325C.01 subd. 5, which defines a trade secret as “information, including a formula, pattern, compilation, program, device, method, technique, or process, that . . . derives independent economic value, actual or potential, from not being generally known.”

Most NDAs sweep broader than the trade-secret category, and that is permitted. A Minnesota NDA can cover pricing strategy, customer lists, internal processes, financial data, and similar materials that may not qualify as trade secrets. But the definition has to identify what is actually confidential. The most common drafting trap I see is a clause that defines confidential information as “all information disclosed by the Company.” Courts regularly trim that language or refuse to enforce it as overbroad. The drafting fix is to identify categories of confidential information with enough specificity that a reasonable reader knows what is in and what is out.

What counts as adequate consideration for an NDA in Minnesota?

Consideration is the central enforceability question for any restrictive covenant in Minnesota. New-hire NDAs are easy: the offer of employment itself is the consideration, provided the NDA is presented and signed before the employee starts work. Mid-employment NDAs are harder. Continued employment alone is generally not enough; Minnesota courts look for additional consideration like a raise, bonus, promotion, or access to a new category of information that the employee did not previously have.

The cleanest fix when an existing employee needs to sign a new NDA is to pair the agreement with a documented, contemporaneous benefit: a promotion, a discrete bonus tied to the signing, a role change with new information access, or an equity grant. The benefit needs to be real and documented. A nominal payment paired with a heavily restrictive NDA is the pattern most likely to be treated as a sham. A recurring pattern I see in NDA enforceability disputes is mid-employment consideration that was either undocumented or transparently inadequate.

How does Minnesota’s 2023 noncompete ban shape what an NDA can do?

The 2023 noncompete ban at Minn. Stat. § 181.988 does not ban NDAs. The statute defines a “covenant not to compete” as an agreement that restricts the employee, after termination, from performing: (1) work for another employer for a specified period of time; (2) work in a specified geographical area; or (3) work for another employer in a capacity similar to the employee’s work for the employer that is party to the agreement. NDAs and nonsolicitation agreements are expressly carved out. The statute makes any covenant not to compete contained in a contract or agreement void and unenforceable, but that prohibition does not reach a properly drafted NDA.

The boundary is functional, not formal. An NDA written so broadly that it operates as a de facto noncompete is unenforceable. If “confidential information” is defined so expansively that the former employee cannot work in the same industry without breaching, courts are likely to read the agreement as a noncompete in disguise and refuse to enforce it under Minn. Stat. § 181.988. The drafting principle: define confidential information narrowly enough that someone with general industry skills, public knowledge, and prior experience can work elsewhere without using the protected material. An NDA that survives the noncompete ban is one that targets specific information, not the employee’s career path.

Where does a Minnesota NDA overlap with the Minnesota Uniform Trade Secrets Act?

An NDA and MUTSA protect different things and provide different remedies. The NDA protects whatever the contract defines as confidential. MUTSA protects information meeting the statutory trade-secret definition at Minn. Stat. § 325C.01 subd. 5: information that derives independent economic value from not being generally known and is the subject of reasonable secrecy efforts. The two protections overlap where the protected information qualifies as a trade secret and run independently where it does not.

When information is misappropriated, the well-drafted complaint usually pleads breach of contract under the NDA and misappropriation under MUTSA. The contract claim provides money damages for proven loss. The MUTSA claim opens injunctive relief under Minn. Stat. § 325C.02 and damages, including potential exemplary damages for willful and malicious misappropriation, under Minn. Stat. § 325C.03. Where the trade secret is related to a product or service used in, or intended for use in, interstate or foreign commerce, the federal Defend Trade Secrets Act, 18 U.S.C. § 1836, supplies a parallel federal civil claim that runs alongside MUTSA and the contract claim, with its own injunctive and damages remedies and a federal forum. Pleading all three gives you parallel paths to relief and avoids losing the case if the protected material turns out not to qualify as a trade secret under state law. For deeper coverage of the trade-secret overlay, see our overview of MUTSA for business owners and what you can actually recover in a trade-secret case.

What duration is reasonable for a Minnesota NDA?

Minnesota courts evaluate NDA duration against the legitimate interest the agreement protects. There is no fixed maximum in statute. A duration tied to the actual useful life of the protected information is the safer drafting posture. Perpetual NDAs are not categorically void, but courts look skeptically at them outside the trade-secret context.

For trade-secret information, an indefinite duration is defensible because trade-secret protection itself lasts as long as the information remains secret and reasonable secrecy efforts continue. For information with a shorter shelf life (a marketing plan, a sales pipeline snapshot, a pricing decision tied to a particular quarter), courts are less likely to enforce a long restriction. The drafting principle: tie duration to the nature of what you are protecting. A perpetual NDA covering ordinary business information invites a court to read the agreement as overbroad and decline to enforce it. Where mixed information is in scope, consider tiered duration: longer for trade-secret-category material, shorter for time-bounded business information.

What remedies does Minnesota law allow for NDA breach?

An NDA breach claim in Minnesota travels two tracks. The contract claim provides money damages for proven loss caused by the breach. Where the protected information meets the trade-secret definition, the parallel MUTSA claim adds injunctive relief under Minn. Stat. § 325C.02 and statutory damages under Minn. Stat. § 325C.03, including potential exemplary damages of up to twice the compensatory award for willful and malicious misappropriation.

MUTSA’s injunction provision states that “[a]ctual or threatened misappropriation may be enjoined. Upon application to the court, an injunction shall be terminated when the trade secret has ceased to exist, but the injunction may be continued for an additional reasonable period of time in order to eliminate commercial advantage that otherwise would be derived from the misappropriation.” (Minn. Stat. § 325C.02.) In practice, contract damages for NDA breach are often hard to prove. Lost profits require showing what would have happened absent the breach, which is speculative. Injunctive relief under MUTSA is usually the more useful remedy when speed matters. Many well-drafted NDAs also include an attorney-fees clause and a liquidated-damages clause. Minnesota courts generally enforce attorney-fees clauses subject to a reasonableness review. Liquidated-damages clauses are enforced when the actual damages would be difficult to estimate at contract formation AND the stipulated amount is a reasonable forecast of those damages, a two-prong test that fails if the clause is a penalty.

What drafting traps make Minnesota NDAs unenforceable?

The recurring traps in unenforceable Minnesota NDAs are: an overbroad definition of “confidential information” that sweeps in publicly available material; missing or inadequate consideration for mid-employment NDAs; perpetual duration paired with broad scope; and language that functions as a noncompete in disguise. Each is fixable at the drafting stage and harder (sometimes impossible) to fix in litigation.

A short list of common drafting failures:

  • “All information disclosed by the Company” with no carve-outs for information that is public, already known to the recipient, independently developed, or rightfully obtained from a third party.
  • Mid-employment NDA handed to existing employees with no documented raise, bonus, promotion, or new information access tied to the signing.
  • Perpetual restriction paired with a broad confidential-information definition.
  • Restrictions on the employee’s ability to work in the same industry, even if labeled as confidentiality protection.
  • No carve-out for whistleblower disclosures protected by federal law (the Defend Trade Secrets Act notice requirement) or for testimony compelled by subpoena or court order.
  • No specification of who owns information jointly developed or independently created during the engagement.

In my experience, most NDA enforceability disputes reach me because the agreement was pulled from a template without any of these adjustments. For more on how to keep protectable information genuinely protected, see our coverage of reasonable measures to protect trade secrets.

How do employment NDAs differ from business-to-business NDAs in Minnesota?

Employment NDAs and business-to-business (“B2B”) NDAs are construed under the same common-law contract principles, but Minnesota courts apply tighter scrutiny to employment NDAs because the restrained party has less bargaining power and more at stake (the ability to earn a living). B2B NDAs between sophisticated parties are generally enforced more readily, particularly where each side had counsel and the agreement reflects negotiated language.

Practical differences:

  • Consideration. B2B NDAs almost always have clear consideration (the underlying transaction or information exchange). Employment NDAs require careful attention to consideration timing.
  • Scope. B2B NDAs often define confidential information by reference to specific projects or marked materials. Employment NDAs that try the same approach are easier to enforce than blanket-coverage employment NDAs.
  • Noncompete-ban interaction. Minn. Stat. § 181.988 applies to employment NDAs and to NDAs with independent contractors. Functional-noncompete concerns can also surface in B2B settings (a vendor NDA so broad it freezes the vendor out of an entire industry), though § 181.988 does not reach true B2B agreements. Those remain scrutinized under common-law reasonableness, where courts give business-to-business agreements more deference than employment restrictions.
  • Ambiguity construction. The rule that ambiguity is resolved against the drafting party applies in both settings, but courts apply it more aggressively against employers in employment-context disputes.

For more on what survives the 2023 ban and how the trade-secret regime backstops former-employee confidentiality, see our explainer on the noncompete ban and what still protects trade secrets.

Can I require new hires to sign an NDA after the 2023 noncompete ban?

Yes. Minn. Stat. § 181.988 bans noncompetes but expressly carves out nondisclosure and nonsolicitation agreements. The boundary is functional: an NDA written so broadly it operates as a noncompete (preventing the employee from working in the same field) will not be enforced. Define confidential information narrowly enough that someone with general industry skills can still work elsewhere.

Does mid-employment consideration need to be more than nominal?

Generally yes. Continued employment alone is usually not adequate consideration for a new restrictive covenant in Minnesota. Courts look for a meaningful benefit tied to the signing: a raise, bonus, promotion, equity grant, or access to a new category of confidential information. A token payment risks being treated as a sham, especially if the NDA significantly restricts the employee’s options.

Is a perpetual NDA enforceable in Minnesota?

It depends on what the NDA protects. For trade-secret information, an indefinite duration is defensible because trade-secret protection itself runs as long as the information remains secret. For ordinary business information with a shorter useful life, a perpetual restriction is more likely to be read as overbroad. Tie duration to the nature of the information being protected.

Can I enforce an NDA against an independent contractor in Minnesota?

Yes, with the same caveats that apply to employees. Minn. Stat. § 181.988 defines ’employee’ to include independent contractors, so the functional-noncompete limit applies. Consideration is usually built into the underlying contractor agreement. The biggest risk with contractor NDAs is an overbroad definition of confidential information that effectively prevents the contractor from working with similar clients.

What if my NDA also includes a non-solicitation clause?

Non-solicitation clauses (restricting solicitation of customers or employees) are not banned by Minn. Stat. § 181.988. Minnesota courts evaluate them under the same common-law reasonableness analysis used for any restrictive covenant: legitimate interest, reasonable scope, reasonable duration, and adequate consideration. A combined NDA, customer non-solicit, and employee non-solicit agreement is common and enforceable when each piece is drafted within bounds.

Will a Minnesota court rewrite an overbroad NDA, or void it entirely?

Minnesota courts have historically applied equitable modification, rewriting overbroad restrictions to make them reasonable rather than voiding the entire agreement. But equitable modification is discretionary, and Minn. Stat. § 181.988 supersedes it for noncompete restrictions covered by the 2023 ban. An agreement that is overbroad in multiple dimensions (scope, duration, geography, and consideration) is at higher risk of being voided entirely. Drafting within bounds at the outset is the safer posture.

A Minnesota NDA is enforceable when it identifies a legitimate interest, defines confidential information narrowly, rests on adequate consideration, and stays inside the noncompete-ban boundary set by Minn. Stat. § 181.988. The 2023 ban did not weaken NDA protection; it raised the drafting bar by making functional-noncompete language unenforceable. For information that also qualifies as a trade secret, the parallel claim under the Minnesota Uniform Trade Secrets Act is often the stronger litigation path. Most NDA enforceability disputes I see come from templates that were never adjusted to the business they were supposed to protect. If you would like a second set of eyes on the specific terms of an NDA you are using or about to sign, email aaron@aaronhall.com with the agreement and a brief description of the situation. For broader coverage of related contract issues, see our contracts practice overview.