If you’re sharing ideas, pricing, customer data, product roadmaps or anything “not public” with another business, you’ll usually want an NDA in place first.
A Mutual Non-Disclosure Agreement (Mutual NDA) is one of the most common ways to do that - because it protects both sides. And with how fast businesses collaborate (especially online), having the right NDA up front is still one of the simplest ways to protect your legal foundations from day one.
This 2026 update reflects what we’re seeing in practice: more partnerships, more outsourcing, more cross-border work, and more valuable data moving between businesses. The core concept hasn’t changed, but the risks (and what you should include) are clearer than ever.
What Is A Mutual Non-Disclosure Agreement (Mutual NDA)?
A Mutual Non-Disclosure Agreement is a contract where both parties agree to keep certain information confidential and only use it for an agreed purpose.
In plain terms, it’s the “we’ll both share some sensitive information, and we’ll both protect it” version of an NDA.
Mutual NDAs are common when you’re exploring something together, such as:
- a potential partnership or joint venture
- a co-marketing arrangement
- a software build where each side is contributing IP
- a supplier relationship where you’ll share pricing and forecasts, and they’ll share manufacturing methods
- talks about buying or selling a business (where both sides share financial and operational information)
Unlike a one-way NDA (where only one party is disclosing confidential information), a mutual NDA assumes each party may disclose confidential information and each party needs the other to protect it.
Why Does “Mutual” Matter?
“Mutual” matters because it changes the risk profile and what’s considered fair.
If both parties are sharing information, a mutual NDA helps keep the relationship balanced. It also avoids the awkward scenario where one side is heavily restricted while the other side has no matching obligations.
That said, “mutual” doesn’t automatically mean “equal”. One party might be disclosing far more valuable information, and the NDA can (and often should) reflect that with tailored clauses and tighter protections.
When Should You Use A Mutual NDA (And When Shouldn’t You)?
If you’re about to share non-public business information and you want to reduce the risk of it being leaked, copied, or misused, it’s usually time to consider an NDA.
A mutual NDA is a good fit when both sides are disclosing. Here are some common situations where we see mutual NDAs in New Zealand businesses.
Common Scenarios Where A Mutual NDA Makes Sense
- Partnership discussions: you’re discussing a collaboration and both sides need to share strategy, financials, or customer insights.
- Product or tech development: you’ll share specifications and the developer shares tools, methods, or frameworks.
- Supplier negotiations: you share volumes, pricing expectations, or brand plans; they share production processes or sourcing info.
- Investment conversations: founders share metrics; investors may share internal models or value-add resources.
- Exploring a business sale: information flows both ways during negotiations and due diligence.
If you’re in a business sale context, confidentiality obligations are often part of the overall deal process alongside documents like a Business Sale Agreement, so it’s worth thinking about the bigger picture early.
There are a few situations where a mutual NDA isn’t the best fit (or isn’t enough by itself):
- Only one party is disclosing: a one-way NDA might be cleaner and more appropriate.
- You’re hiring someone to deliver services: you may need a full Service Agreement (with confidentiality, IP, payment terms and deliverables), not just an NDA.
- You’re onboarding an employee: employment confidentiality is usually handled in an Employment Contract (and supporting policies), rather than a standalone NDA.
- You need to share personal information: an NDA doesn’t replace privacy compliance. If personal data is involved, you may also need a Privacy Policy and the right collection/handling steps under the Privacy Act 2020.
In other words: NDAs are great for confidentiality, but they’re not a “one document solves everything” solution. The right approach depends on what you’re doing and what risks you’re actually trying to control.
What Does A Mutual NDA Usually Cover?
A well-drafted mutual NDA sets clear rules about:
- what information is confidential
- how that information can be used
- who it can be shared with
- how long the confidentiality obligations last
- what happens if there’s a breach
Here are the clauses you’ll commonly see (and what they mean in practical terms).
This is the heart of the agreement. It should be wide enough to protect you, but clear enough that it’s enforceable and workable.
Confidential information often includes things like:
- customer lists and supplier details
- pricing, margins, or budgets
- marketing plans and launch timelines
- product designs, formulas, prototypes, or software code
- business processes and “how we do things” internally
- trade secrets and know-how
A common mistake is assuming “everything we talk about is confidential” is enough. It can work, but it can also lead to arguments later about what was actually covered - especially if the information was shared casually over email, Slack, Zoom, or in a pitch deck.
2. Purpose (Permitted Use)
A mutual NDA usually limits use of confidential information to a defined purpose, like:
- evaluating a potential partnership
- negotiating a supply arrangement
- assessing an acquisition
This matters because “don’t disclose” is only half the problem. The other half is “don’t use it to compete with me”. A strong “purpose” clause helps stop the other party from using your information outside the relationship you’re discussing.
This part usually sets rules like:
- only share information with staff/contractors who genuinely need it
- ensure those people are bound by confidentiality obligations too
- take reasonable steps to prevent unauthorised access
If you’re sharing information with a party who uses overseas contractors or external consultants, this is a key risk area. It’s also where confidentiality intersects with privacy and security expectations under the Privacy Act 2020 if personal information is involved.
4. Exclusions (What Is Not Confidential)
Most NDAs exclude information that is:
- already public (not because of a breach)
- already known to the receiving party before disclosure
- independently developed without reference to the confidential info
- required to be disclosed by law (for example, a court order)
These exclusions are normal, but they need careful drafting so they can’t be used as a loophole.
5. Term And Duration
There are usually two timeframes:
- the term of the agreement (how long you’ll be sharing information / negotiating), and
- the confidentiality period (how long the obligation to keep it confidential lasts).
Confidentiality obligations often continue after the relationship ends. The right length depends on what’s being shared (for example, a short-term marketing campaign vs long-term trade secrets).
If talks fall through, you’ll usually want the other party to:
- return documents and materials, or
- confirm deletion/destruction (including digital copies).
In practice, this needs to reflect reality: backups exist, emails get archived, and information can be embedded in notes. A good NDA is realistic but still protective, with clear obligations and written confirmation where appropriate.
7. Remedies If There’s A Breach
A mutual NDA usually sets out what you can do if the other party breaches confidentiality. This can include seeking damages, and (in some cases) urgent court action to stop ongoing disclosure or misuse.
Even if you never end up in a dispute, having these terms clearly written can make it far easier to resolve issues early - and can be a strong deterrent against misuse.
Mutual NDA Vs Unilateral NDA: Which One Do You Need?
This is one of the most common questions we hear: “Do we need a mutual NDA, or just a standard NDA?”
Here’s a practical way to think about it.
Use A Mutual NDA If:
- you expect both sides to share confidential information
- you want the agreement to feel balanced (especially in early negotiations)
- the project involves co-developing a product, campaign, or service
Use A Unilateral (One-Way) NDA If:
- only you are disclosing confidential information (common with pitches, prototypes, investor decks, and early supplier talks)
- the other party will receive your information but won’t be sharing theirs
Sometimes parties start with a mutual NDA “for simplicity”, even though one side is sharing far more. That can still work, but you’ll want to be careful about how the definition of confidential information, permitted use, and protections are drafted.
If the relationship progresses beyond early discussions, it’s also common to move from an NDA into a broader contract that covers the full commercial deal (including payment, deliverables, liability and IP).
Key Risks And Common Mistakes With Mutual NDAs
An NDA is meant to reduce risk - but the wrong NDA (or a rushed template) can create a false sense of security.
Here are some of the most common issues we see with mutual NDAs for NZ businesses.
1. Using A Generic Template That Doesn’t Match The Deal
Not all confidential information is equal, and not all deals are equal.
If your NDA doesn’t match what’s actually happening (for example, you’re sharing customer data, or you’re collaborating on a product), you might find:
- the definition of confidential information is too narrow
- the “purpose” is vague, making misuse harder to prove
- the agreement doesn’t deal with IP created during discussions
- the agreement is silent on security expectations
This is why it’s worth getting the NDA properly drafted or reviewed - especially when the information you’re sharing is commercially valuable.
2. Forgetting About Privacy And Data Handling
A mutual NDA is about confidentiality. It doesn’t automatically make your data-sharing lawful.
If you’re sharing personal information (for example, customer details, employee records, or user data), you need to think about:
- whether you have authority/consent to share it
- what you told people in your privacy statements
- how the receiving party will store and protect it
- whether you need a broader privacy compliance approach
Even where both parties “promise to keep it secret”, you still need to comply with the Privacy Act 2020 and take reasonable steps around data security.
3. Not Aligning The NDA With The Next Contract
An NDA is often the first document signed, but it’s rarely the last.
If the relationship proceeds, you may later sign a service or supply agreement, or even more formal arrangements like a shareholders deal (for example, if the collaboration turns into a joint venture company and you need a Shareholders Agreement).
If those later documents contradict the NDA (even accidentally), it can create confusion about what applies - and when.
4. Assuming “Mutual” Automatically Prevents Competition
A mutual NDA can restrict the use of confidential information, which helps prevent unfair competition.
But if your real concern is that the other party will set up a competing business, you may also need clauses dealing with:
- non-solicitation (not poaching staff/clients)
- restraint / non-compete provisions (where appropriate and enforceable)
- intellectual property ownership and licensing
These issues need careful drafting because restraint clauses can be tricky to enforce if they’re too broad.
5. Not Thinking About IP Ownership Early
Mutual NDAs often come up when you’re sharing ideas. And that’s where misunderstandings can happen.
For example, imagine you and another business brainstorm a new product feature during negotiations. You share technical requirements; they share an implementation approach. The project doesn’t proceed - then six months later you see something similar launched.
An NDA can help, but it may not fully answer:
- who owns pre-existing IP brought into the discussions
- who owns new IP created during the discussions
- whether either party can use “general learnings”
If IP is central to the relationship, it’s usually worth addressing this clearly - either within the NDA or in the follow-on agreement (and making sure it aligns with how your business is structured and documented, including key governance documents like a Company Constitution if relevant).
Key Takeaways
- A Mutual Non-Disclosure Agreement is a contract where both parties agree to keep shared information confidential and only use it for an agreed purpose.
- Mutual NDAs are commonly used for partnership talks, supplier negotiations, product development discussions, investment conversations, and business sale negotiations.
- A solid mutual NDA usually covers the definition of confidential information, permitted purpose, non-disclosure obligations, exclusions, term/duration, return or destruction of information, and remedies for breach.
- Choosing between a mutual NDA and a unilateral NDA depends on whether one or both parties will be disclosing confidential information.
- Common NDA mistakes include relying on templates, using vague “purpose” clauses, overlooking privacy obligations under the Privacy Act 2020, and failing to address IP and follow-on contract alignment.
- If your NDA is part of a bigger deal (like a service arrangement, supply relationship, or business sale), it’s smart to ensure your documents work together rather than contradict each other.
If you’d like help drafting or reviewing a Mutual Non-Disclosure Agreement (or working out what other legal documents you’ll need for your collaboration), you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.
