Nondisclosure agreements (NDAs) and confidentiality agreements are part of everyday business in Wisconsin. Whether you are hiring an employee, onboarding a contractor, sharing pricing with a vendor, pitching to an investor, or opening the books in a potential sale, you will likely be asked to sign—or ask someone else to sign—an NDA. These documents are often labeled “standard,” but the details matter. Small wording choices can shift risk, limit your options, or make it harder to enforce your rights later.
This article explains how NDAs work in Wisconsin, what to watch for at the clause level, and when it makes sense to involve an attorney before you sign. Our goal is to help you identify risks early, negotiate practical terms, and avoid disputes that cost far more than preventive review. For related guidance, see Settlement Agreements and Releases in Wisconsin: Legal Review and Drafting Services.
What an NDA Does (and Doesn't) Do in Wisconsin
An NDA is a contract that restricts how confidential information may be used and shared. It is meant to reduce the risk that sensitive information—such as pricing, customer data, source code, product plans, formulas, or deal terms—leaks to competitors or the public. For related guidance, see Do I Need a Contract Attorney in Wisconsin or Can I Use a Template?.
What an NDA typically does
- Defines “Confidential Information”: Sets the categories of information covered and the conditions under which the information is considered confidential.
- Limits use: States that the recipient may use confidential information only for a defined purpose (for example, “to evaluate a potential partnership”).
- Restricts disclosure: Prohibits sharing the information outside approved recipients, such as employees or advisors who need to know and are bound to protect it.
- Requires safeguards: Requires reasonable steps to protect the information from improper access or disclosure.
- Specifies remedies: Addresses what may happen if the agreement is breached, including potential injunctive relief and other contract remedies.
What an NDA does not do
- Create ownership rights: NDAs usually do not transfer ownership of the information or grant licenses unless stated. Be cautious of language that implies a license or joint ownership.
- Prevent all competition: NDAs are not substitutes for noncompete or nonsolicit agreements. They focus on confidentiality and limited use.
- Protect public or independently developed information: Information that becomes public through no fault of the recipient, or that the recipient already knew or developed independently, is generally not covered if the agreement includes proper carve-outs.
Common NDA Types and Use Cases: Employment, Vendors, Investors, and M&A
Employment and contractors
Employers often use NDAs in onboarding packages for employees, freelancers, and consultants. These agreements should be tailored to the role and access level. Broad, boilerplate language can be hard to enforce or can deter talent. Consider:
- Role-based access: Limit confidentiality obligations to what the individual will realistically see and use.
- Post-employment obligations: Reasonable obligations to return or delete company data, and to continue keeping it confidential after employment ends.
- Inventions: Clarify whether work product belongs to the company, particularly for contractors.
Vendors and suppliers
Vendor NDAs protect pricing, supply chain details, product specs, and any shared roadmaps. Watch for reverse-use risks if the vendor serves competitors and may learn from your data. Consider:
- Purpose limits: Tie use strictly to providing the contracted services.
- Subcontractor flow-down: Require the vendor to bind its subcontractors to equal or stronger confidentiality obligations.
- Security standards: Reference clear security expectations for handling your data.
Investors and advisors
Early-stage fundraising often involves sharing decks, models, and demos. Some investors decline to sign NDAs before diligence; others will sign a short mutual NDA. Consider:
- Selective disclosure: Share only what is necessary at each stage; expand disclosures as diligence deepens.
- Mutual vs. one-way: If both sides are sharing, a mutual NDA can simplify the process.
- Advisor coverage: Ensure the NDA covers outside advisors, including accountants and bankers, under the recipient's responsibility.
Mergers, acquisitions, and strategic deals
Buyers and sellers exchange deeply sensitive information, from customer lists to trade secrets. NDAs in this context are often called confidentiality agreements and may include non-solicit provisions or standstill terms. Consider:
- Clean teams: Restrict access by competitors to aggregated or sanitized data, or use third-party “clean teams.”
- Non-solicit: Limit poaching of employees or customers discovered through diligence, where appropriate.
- Return, destruction, and data hygiene: Require orderly disposition of data at the end of talks, with certification of destruction.
Key Clauses to Review Carefully: Definitions, Scope, Term, and Carve-Outs
Definitions: What counts as “Confidential Information”
Overbroad definitions can trap routine business facts. Narrow, clear definitions reduce disputes. Practical points:
- Marking requirements: Some NDAs require “CONFIDENTIAL” labels or a follow-up memo for oral disclosures. If your team shares information quickly, strict marking can be a compliance risk. Consider a balanced approach: marking where feasible, but also protecting information that a reasonable person would understand is confidential.
- Categories vs. examples: Use examples to show the types of data covered (e.g., “customer lists, pricing, source code”), while avoiding vague catch-alls that sweep in everything.
Scope and purpose limitation
Purpose language controls how the recipient may use the information. Examples:
- Narrow purpose: “Recipient may use Discloser's Confidential Information solely to evaluate a potential distribution agreement between the parties.”
- Risky purpose: “Recipient may use the information for any business purpose related to the parties' relationship.” This can blur limits and open the door to internal product development using your data.
Carve-outs: What is not confidential
Typical carve-outs include: information that is or becomes public through no fault of the recipient; was known to the recipient before disclosure; is independently developed; or is rightfully received from another source. Check the burden of proof and documentation requirements so that routine business knowledge does not become a dispute.
Term and survival
Two timelines matter: the period during which disclosures may be made, and the duration of confidentiality obligations. Clauses often run for 2–5 years, but highly sensitive information such as source code or formulas may warrant longer protection. Some NDAs state that trade secret protections continue as long as the information qualifies as a trade secret under applicable law.
Permitted disclosures
Most NDAs allow disclosure to employees, contractors, and advisors who have a need to know and are bound by confidentiality obligations. Validate that “advisors” include your lawyers, accountants, bankers, and potential financing sources. Also look for a safe process to disclose information if legally required by subpoena, court order, or regulators, including notice obligations and cooperation.
Return and destruction
Specify whether electronic backups must be deleted, whether data can be retained for archival or compliance reasons, and how quickly materials must be returned or destroyed at the end of the relationship. Include certification requirements where appropriate.
Remedies and liability limits
Some NDAs acknowledge that monetary damages may be inadequate and allow a party to seek injunctive relief. Others include limits on indirect damages. Review how these provisions interact with your broader business relationship and insurance coverage.
Wisconsin Considerations: Trade Secrets, Employee Restrictions, and Enforcement
Trade secret protection
Wisconsin law protects trade secrets when reasonable steps are taken to keep information confidential and the information derives value from not being generally known. An NDA can be one of those reasonable steps. Make sure your agreement aligns with your actual practices—access controls, need-to-know limits, and employee training. If your operations do not match the promises in your NDA, enforcement can be harder.
Employee-related restrictions
Wisconsin law treats restraints on employees carefully. NDAs focused on confidentiality are different from noncompete or non-solicitation covenants. If your confidentiality agreement includes provisions that function like noncompete or nonsolicit restrictions, the language may face additional scrutiny. Keep confidentiality commitments distinct and reasonably tailored to protect legitimate business interests.
Enforcement and venue
Wisconsin businesses often prefer Wisconsin law and venue. If the other side proposes another state's law or out-of-state courts, you are taking on added uncertainty and cost. Consider whether Wisconsin law and local venue are important for your situation, especially when your operations, employees, or information are centered in Wisconsin.
Public records and government recipients
If you share information with a public agency, separate public-records rules can apply. Tailor your NDA to address how confidential materials will be handled if a records request arises, including prompt notice and permitted redactions where available.
Mid-article next step: If you are preparing to sign or send out an NDA and want a focused legal review, schedule a consultation. Use our contact form or call 414-253-8500 to speak with our firm about representation and next steps.
Red Flags and Negotiation Points Before You Sign
Five red flags
- Unlimited purpose: Purpose language that allows any internal business use can permit reverse engineering of your commercial strategy. Propose a clear, limited purpose tied to the transaction.
- Everything is confidential—forever: Overbroad, perpetual confidentiality for commonplace information invites disputes. Suggest reasonable terms with trade-secret-specific survival.
- No carve-out for independently developed information: Without this, you risk claims over ideas your team developed on its own. Include a standard independent development carve-out.
- One-way disclosures in a mutual setting: If both sides will share information, but the NDA protects only one side, request a mutual form or add reciprocal protections.
- Unrealistic marking or notice rules: Strict “in writing and labeled” requirements can be impractical in meetings and demos. Use a reasonable-person standard or a short follow-up confirmation window.
Negotiation levers that often work
- Tiered access: Limit who can see your most sensitive materials and require heightened protections (e.g., clean rooms, read-only access).
- Data handling standards: Reference practical safeguards like encryption in transit and at rest, least-privilege access, and prompt revocation at offboarding.
- Return and destruction deadlines: Set firm timelines and certification requirements to reduce data lingering in archives.
- Specific exclusions: Carve out named customers, technologies, or vendors from non-solicit or standstill terms in deal NDAs where appropriate.
- Choice of law and forum: Push for Wisconsin law and a Wisconsin forum when your business is here.
Clause-level examples
- Better: “Recipient may disclose Confidential Information to its employees, contractors, and professional advisors who require access for the Purpose and are bound by confidentiality obligations no less protective than those herein.”
- Risky: “Recipient may disclose to any affiliate or representative.” This can allow broad circulation inside a corporate group without controls.
- Better: “Upon request or termination of discussions, Recipient will promptly return or destroy all Confidential Information, including all copies and backups, and certify destruction upon Discloser's request.”
- Risky: “Recipient will return Confidential Information upon request.” No mention of electronic backups or certifications.
When to Involve an Attorney and What Legal Review Typically Covers
Not every NDA needs a multi-round negotiation. That said, targeted legal review is often worthwhile when any of the following is true:
- You plan to disclose trade secrets, proprietary code, or pricing strategies.
- The other party is a competitor or serves your competitors.
- The NDA includes employee-related restrictions, non-solicit terms, or a standstill.
- The agreement selects another state's law or out-of-state courts.
- Your internal practices may not match the NDA's security or data handling promises.
- The relationship could evolve into a major contract, joint venture, or sale.
What legal review typically includes
- Risk mapping: Align the NDA's obligations with the types of information you will actually share and the people who will access it.
- Term and survival calibration: Adjust durations to reflect the sensitivity of what is being disclosed.
- Carve-out tuning: Ensure standard exclusions exist and fit your operations, including independent development and residual knowledge where appropriate.
- Security and compliance: Confirm that stated safeguards are workable and consistent with your policies and systems.
- Remedies and dispute options: Clarify injunctive language, damages limits, venue, and governing law to reduce enforcement uncertainty.
- Practical playbooks: Translate the final NDA into an internal checklist so your team knows how to label, share, store, and later return or delete data.
If you would like counsel to review an NDA, propose revisions, or handle negotiations, we invite you to schedule a consultation to discuss representation. Use our contact form or call 414-253-8500 to talk through next steps.
Next Steps: Preparing Documents and Opening a Confidential Discussion
Before you send or sign
- Inventory what you will disclose: Identify documents, data sets, and discussions planned for the next 60–90 days. Label what is truly sensitive.
- Decide on mutual or one-way: If both sides will share, mutual is often cleaner. If only one side shares, a one-way NDA may be simpler.
- Draft practical purpose language: Tie use to the specific deal or evaluation. Avoid vague “related to” phrases.
- Set a document-handling routine: Determine who can access, how to mark materials, where to store them, and how to remove access when talks end.
- Plan exit logistics: Decide how and when to request return or destruction and who will certify it on each side.
Coordinating with your broader agreements
Your NDA should fit with your employment agreements, independent contractor terms, vendor contracts, privacy policies, and incident response plans. Conflicts between documents create enforcement problems. Standardizing your definitions (e.g., “Confidential Information,” “Trade Secret,” “Purpose”) helps your teams follow consistent rules.
Short Answers to Common Questions
Is a one-way or mutual NDA better for my situation?
If only one party will share confidential information, a one-way NDA is often sufficient and faster to finalize. If both parties will share, a mutual NDA can create balance and reduce negotiation time. The decision usually turns on who is disclosing, what is being shared, and whether information will flow both directions during diligence.
How long should a Wisconsin NDA last?
Common terms range from 2 to 5 years for general business information. For trade secrets and similarly sensitive materials, protection often lasts as long as the information remains a trade secret under applicable law. The right duration depends on the type of information and your industry cycle.
Can an NDA include non-compete or non-solicit terms for employees?
Some NDAs, especially in deal settings, include non-solicit language. These provisions are treated differently from pure confidentiality commitments and may be reviewed closely under Wisconsin law. Keep confidentiality and any employee-related restrictions distinct, and consider tailored language if such restrictions are appropriate for the transaction.
What happens if confidential information becomes public through no fault of mine?
Most NDAs include a carve-out stating that information that becomes public through no fault of the recipient is no longer protected. Ensure the agreement clearly includes this carve-out and defines how it applies.
Do I need a separate agreement for trade secrets beyond an NDA?
Often, a well-drafted NDA combined with sensible internal controls is sufficient. In some situations—such as complex technology development or joint ventures—additional agreements may be appropriate to address ownership, licensing, and specific handling of trade secrets. The decision depends on the scope and sensitivity of what is being shared.
Ready to Review or Negotiate Your NDA?
If you have an NDA in front of you—or you need to send out your own—speak with our firm about representation. We can review the draft, propose practical revisions, or prepare an agreement tailored to your use case. To schedule a consultation, use our contact form or call 414-2538500.
Disclaimer: This article provides general information about Wisconsin nondisclosure and confidentiality agreements and is not legal advice for any specific situation. Reading this page does not create an attorney-client relationship. Laws and outcomes vary based on facts. Consider consulting an attorney for guidance on your circumstances.
Related articles
Attorney advertising. This page is for general informational purposes only and is not legal advice. Reading this page or contacting the firm does not create an attorney-client relationship.