NDAs and Confidentiality Agreements in New Zealand

If you are about to share a business idea, financial model, customer list or product plan, an NDA can feel like the obvious first step. But many founders sign the wrong version, rely on a template that does not fit the deal, or assume an NDA will protect every conversation automatically. Those mistakes can leave gaps right when sensitive information matters most.

A non-disclosure agreement, often called an NDA or confidentiality agreement, is a contract that sets rules about how confidential information can be used, shared and protected. In practice, the real questions are usually more specific: what counts as confidential, who can see it, how long the obligation lasts, and what happens if the information is misused.

This guide answers those points for New Zealand businesses. It explains what an NDA is, when businesses usually use one, the legal issues to check before you sign, and the common drafting problems that cause disputes later.

Overview

An NDA is a contract used to protect confidential business information when you need to disclose it to someone else. For New Zealand businesses, it is often used before investment talks, supplier discussions, contractor engagement, product development, due diligence, or early-stage commercial negotiations.

A good NDA does not just say “keep this secret”. It defines the information covered, limits how the recipient can use it, sets practical exceptions, and gives both sides a clearer basis for dealing with a breach.

• Identify exactly what information is meant to be confidential.
• Check whether the NDA is one-way or mutual.
• Confirm why the information can be used, and what uses are banned.
• Review carve-outs, such as information already public or already known.
• Check who can receive the information internally, such as employees, advisers or contractors.
• Look at the confidentiality period and whether it is realistic for the information involved.
• See what happens to documents, files and data after the discussions end.
• Review the remedies clause, especially before you rely on a verbal promise or sign the other side’s standard terms.

When New Zealand Businesses Use NDAs

New Zealand businesses usually use NDAs when one side needs to share commercially sensitive information before a broader agreement is signed. The main purpose is to make those early discussions safer and more predictable.

Investment and capital raising discussions

Founders sometimes want an NDA in place before sharing forecasts, pitch materials, product roadmaps or customer traction data with a potential investor. Whether an investor will sign one depends on the situation. Many professional investors are cautious about signing NDAs at the first meeting, especially if they review lots of similar businesses.

Even so, an NDA may still be appropriate in some fundraising contexts, particularly where the information goes beyond a standard pitch and includes genuinely sensitive technical, financial or strategic material. Before you send a data room or detailed internal assumptions, it is worth checking whether the confidentiality terms actually match the sensitivity of the information.

Supplier, distributor and service provider negotiations

An NDA is common before you disclose margins, pricing models, operational processes, manufacturing methods or customer requirements to a potential supplier or commercial partner. This often comes up before you sign a contract, or before you accept the provider's standard terms without much room to renegotiate.

For example, a food business speaking with a co-manufacturer might need to share recipes, production forecasts and packaging plans. A software company discussing a white-label arrangement might need to disclose platform architecture, client requirements and future features. In both cases, the NDA helps set limits before detailed conversations begin.

Contractor and consultant engagements

Businesses often share sensitive information with developers, designers, marketers, virtual assistants and specialist consultants before a full service agreement is finalised. An NDA can be useful where the person needs access to your customer data, internal systems, launch strategy, pricing or product specifications.

That said, confidentiality should usually sit inside the main services contract as well. A standalone NDA may help at the start, but it should not be the only document covering confidentiality if the relationship becomes ongoing.

Due diligence and business sale discussions

Confidentiality agreements are standard in due diligence. If you are buying, selling or investing in a business, one side may need access to financial records, contracts, client details, supplier terms, intellectual property information, or internal policies.

This is where founders often get caught. They hand over a large volume of information quickly, but the NDA does not say enough about who can access it, whether copies can be made, or what happens after the deal falls over. The more sensitive the due diligence materials, the more carefully the NDA should be drafted.

Employment and internal business contexts

Employers also use confidentiality terms when senior staff, key employees or contractors handle trade secrets, strategic plans or proprietary information. In many cases, these obligations are built into employment agreements, contractor agreements or shareholder agreements rather than handled through a separate NDA.

If the issue relates to business ownership, governance or internal know-how, a broader contract may be more effective than a short standalone confidentiality deed. The key is to make sure the confidentiality obligations fit the actual relationship.

Legal Issues To Check Before You Sign

The legal value of an NDA depends on the wording, not the title. Before you sign, check whether the document clearly covers the information, people and risks that matter in the real commercial discussion.

What counts as confidential information?

The definition of confidential information is one of the most important parts of the agreement. If it is too narrow, important information may fall outside the NDA. If it is too broad, the recipient may be taking on obligations that are unrealistic or unclear.

A well-drafted definition usually covers information disclosed in writing, verbally, visually or electronically, and may include related notes, analyses and summaries created by the recipient. It should also reflect the actual deal.

Depending on the context, confidential information may include:

• business plans and growth strategy
• pricing and margin information
• customer and supplier lists
• software code or technical specifications
• product formulas, prototypes or manufacturing methods
• financial records and forecasts
• marketing plans and campaign data
• non-public contract terms

If you are the disclosing party, avoid assuming that everything you say will automatically be protected. Some NDAs only cover documents marked confidential, or only cover written information confirmed in writing after a meeting.

Is it one-way or mutual?

A one-way NDA protects information disclosed by only one side. A mutual NDA protects both parties. The right structure depends on the deal.

If you are pitching a business to a potential distributor and only you are sharing sensitive information, a one-way NDA may be enough. If both sides are exchanging internal material during a joint venture or partnership discussion, a mutual NDA is usually more appropriate.

This matters because a mutual NDA can look balanced while still favouring one side in the detail. Check whether the obligations really operate the same way for both parties.

What can the recipient use the information for?

An NDA should limit use of the information to a defined purpose. Without that, the recipient may be restricted from doing very little beyond not disclosing it publicly.

The purpose clause should be specific enough to stop misuse, while still allowing the recipient to assess the opportunity. For example, the purpose might be evaluating a supply arrangement, reviewing a possible acquisition, or discussing a proposed services engagement.

If the purpose is drafted too widely, confidential information may end up being used to compete, negotiate with others, or shape the recipient’s own offering. Before you sign, check that the use restriction matches the commercial discussion you are actually having.

What are the standard exceptions?

Most NDAs exclude certain information from confidentiality obligations. These exceptions are normal and often necessary. They usually cover information that:

• is already public, other than through a breach
• was already known to the recipient before disclosure
• is received lawfully from another source
• must be disclosed by law, court order or regulatory requirement

The drafting still matters. An exception should not be so broad that it lets the recipient sidestep the confidentiality obligation too easily. If compulsory disclosure is allowed, the NDA should ideally require notice to the disclosing party where legally permitted.

Who can the information be shared with?

Most recipients need to share confidential information with a limited group of people, such as employees, directors, lawyers, accountants, financiers or specialist advisers. The NDA should say who is allowed to receive the information, and on what basis.

This is especially important where the recipient uses contractors, offshore support teams or related entities. If those people are not clearly covered, enforcement becomes harder and the practical risk increases.

It is common to require permitted recipients to be told the information is confidential and to be bound by similar confidentiality obligations. That helps close a gap that many template NDAs leave open.

How long do the obligations last?

An NDA should state how long confidentiality obligations apply. Some agreements use a fixed term, such as two to five years. Others require ongoing confidentiality for trade secrets or highly sensitive technical information.

There is no single perfect timeframe. A short period may be enough for a limited commercial discussion. A longer period may make sense where the information would retain value for years.

Before you sign, think about the commercial shelf life of the information. Customer pricing for a one-off proposal may age quickly. Source code, formulas, or acquisition plans may need longer protection.

What happens to the information when talks end?

The NDA should deal with return, deletion or destruction of confidential materials if negotiations stop. This issue matters more than many founders expect, especially where information has been circulated internally, saved into systems, or shared through a data room.

Look for clauses covering:

• return of physical documents
• deletion of electronic files
• destruction of copies, extracts and summaries
• retention of records needed for legal or compliance purposes
• whether backup systems are excluded or treated separately

If you are disclosing information, make sure the clause is realistic enough to enforce. If you are receiving information, make sure it works with your actual systems and record-keeping obligations.

What remedies are available if there is a breach?

An NDA often states that damages may not be enough and that the disclosing party may seek urgent court orders to stop further misuse. That can be useful, especially if confidential information could be spread quickly.

Still, a remedies clause is not a magic fix. Enforcement depends on the facts, the wording of the contract, and what evidence exists of the breach. If the business risk is significant, getting legal advice or a contract review before you sign is usually far cheaper than trying to repair the damage later.

Common NDA Mistakes

The most common NDA mistakes happen when businesses treat confidentiality as a formality. A short document can still create real risk if the wording is vague, one-sided or inconsistent with the deal.

Using a generic template without tailoring it

Many businesses download a template and send it out unchanged. The problem is that templates often miss the commercial details that matter most, such as whether the information will be shared verbally, whether group companies are involved, or whether technical materials need stronger protection.

A template can be a starting point, but it should be checked against the actual transaction. Before you rely on a verbal promise or a recycled precedent, compare the document to the information you are really planning to disclose.

Assuming the NDA protects intellectual property ownership

An NDA protects confidentiality. It does not automatically transfer or confirm ownership of intellectual property. If a consultant creates work for your business, or if a developer contributes code during a project, you may need separate clauses dealing with ownership, assignment and licence rights.

This is a major issue for product businesses, software companies and creative agencies. If your concern is not just secrecy but ownership of outputs, an NDA alone is usually not enough.

Defining confidential information too loosely

If the definition is too vague, a dispute may arise over whether the information was covered at all. If the definition is too broad, the recipient may push back or ignore practical compliance because the obligations do not feel workable.

The better approach is to describe the categories of information clearly and match the wording to the deal. Precision helps both sides understand what is protected before they exchange material.

Failing to align the NDA with later contracts

An NDA is often signed first, then followed by a services agreement, supply agreement, heads of agreement or sale and purchase documentation. Problems arise when the later contract uses different confidentiality terms, different definitions, or different rules about permitted use.

That inconsistency can create confusion about which document governs. If the relationship moves forward, review the whole contract set together rather than treating the NDA as a standalone issue.

Forgetting privacy and data issues

Some businesses use NDAs when sharing customer or user information. An NDA may help with confidentiality, but it does not replace privacy compliance. If personal information is being disclosed, the Privacy Act 2020 may also need to be considered, including whether the sharing is authorised, necessary and properly handled under your privacy notice and data protection processes.

That is particularly relevant in due diligence, outsourced service arrangements, and data-heavy tech businesses. Confidential does not always mean legally shareable.

Signing the other side’s standard form without checking the practical burden

Large businesses often send their own NDA and expect it to be signed quickly. The main risk is not always the confidentiality promise itself. It can be the extra obligations hidden around non-solicitation, ownership of feedback, return of information, broad warranties, or restrictive dispute clauses.

Before you sign, check whether the NDA goes beyond confidentiality and whether those extra obligations are reasonable for the discussion. This is where founders often get caught because the document looks standard and low-risk.

FAQs

Is an NDA legally enforceable in New Zealand?

Yes, an NDA can be legally enforceable in New Zealand if it is properly drafted as a valid contract and its terms are clear and reasonable. Enforceability still depends on the wording, the facts, and whether you can show a breach.

What is the difference between an NDA and a confidentiality agreement?

In most business contexts, there is little practical difference. “NDA” and “confidentiality agreement” are often used interchangeably to describe a contract that restricts disclosure and use of confidential information.

Can an NDA cover verbal discussions?

Yes, but only if the wording allows for it. Some NDAs cover verbal disclosures automatically, while others require the information to be confirmed in writing within a set timeframe.

Do I need a mutual NDA?

Only if both sides will disclose sensitive information. If just one business is sharing confidential material, a one-way NDA may be enough, but the detail should still be checked carefully before you sign.

Does an NDA stop someone from competing with my business?

Not usually. An NDA mainly protects confidential information. If you need restrictions on competition, solicitation, or use of intellectual property, those points usually need separate clauses and should be assessed carefully under New Zealand law.

Key Takeaways

• An NDA is a contract that protects confidential information by setting rules about use, disclosure and handling.
• New Zealand businesses often use NDAs before investment talks, due diligence, supplier negotiations, contractor engagement and other early commercial discussions.
• The key clauses to review are the definition of confidential information, permitted purpose, exceptions, permitted recipients, duration, return or deletion obligations, and remedies for breach.
• A one-way NDA and a mutual NDA serve different purposes, so the structure should reflect who is actually sharing sensitive material.
• An NDA does not automatically deal with intellectual property ownership, privacy compliance, or all risks in a broader commercial relationship.
• Generic templates and unreviewed standard form NDAs often create problems because they do not match the actual deal or contain extra obligations.
• Before you sign, it is worth checking that the confidentiality terms align with any later services, supply, employment or transaction documents.

If you want help with confidentiality clauses, permitted use restrictions, intellectual property terms, or privacy issues, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.