NDAs in NZ: What to Include in Confidentiality Terms

An NDA contract can look simple, but small drafting mistakes can create real commercial risk. Founders often sign a one page confidentiality agreement without checking what counts as confidential information, how long the obligations last, or whether the other side can still use ideas after the discussion ends. Another common problem is relying on broad wording that sounds protective but is too vague to enforce in practice.

If you are sharing a product concept, customer data, pricing model, software roadmap or supplier information, the wording matters before you sign. A good NDA should match the actual deal, identify the information you need protected, and deal with practical issues such as return of documents, permitted disclosures and legal remedies. This guide explains what a New Zealand business should include in an NDA contract, when businesses usually use one, the legal issues to check before you accept the other side's standard terms, and the mistakes that most often cause trouble later.

Overview

An NDA contract is a legally binding agreement that restricts how one or both parties can use and disclose confidential information. In New Zealand, the best confidentiality agreements are specific, commercially realistic and drafted around the actual information being shared.

A useful NDA should make it clear what is protected, who can see it, why it is being disclosed and what happens when the relationship ends. If those points are vague, the agreement may give less protection than you expect.

Define the confidential information clearly, including documents, data, conversations, samples and commercially sensitive know how.
State the purpose of disclosure, so the recipient can only use the information for that agreed purpose.
Set out who can access the information, such as employees, contractors, advisers or related entities on a need to know basis.
Include exclusions, for example information already public, already known to the recipient, or required to be disclosed by law.
Specify how long confidentiality obligations apply, including any survival period after discussions end.
Deal with storage, security, copying, return or destruction of information.
Cover ownership of intellectual property and make it clear that disclosure does not transfer rights.
Include remedies and enforcement wording that fits the commercial risk if the information is misused.

When New Zealand Businesses Use NDAs

New Zealand businesses usually use NDAs before they share information that has real commercial value and cannot easily be taken back once disclosed.

The classic example is a startup discussing a new product with a developer, manufacturer or potential investor. But confidentiality agreements are also common in ordinary SME transactions, especially where one side is handing over pricing models, customer lists, technical processes or business plans.

Early stage fundraising and investment discussions

Some investors will not sign an NDA before an initial pitch, especially if they see many businesses in the same sector. That does not mean NDAs are pointless. It means founders need to be selective about when to insist on one and what information to hold back until later.

Before you sign or send sensitive material, think about the stage of the conversation. A high level deck may not justify an NDA. Detailed financial models, code architecture, customer churn analysis or proprietary product specifications often do.

Supplier, manufacturer and development arrangements

If you are speaking with a contract manufacturer, software developer, designer or consultant, an NDA contract is often one of the first documents to sort out. These relationships usually involve practical disclosure of confidential information long before the main services agreement is finalised.

This is where founders often get caught. They share technical drawings, formulas, product samples or process documents before checking whether the draft only protects written information, or whether contractors engaged by the recipient are covered at all.

Business sale, acquisition and partnership talks

When a business is being bought, sold or merged, the seller commonly discloses financial records, customer information, supplier arrangements and operational data. A buyer may also share strategy documents or integration plans. An NDA helps set boundaries before due diligence starts.

Partnership and joint venture discussions raise the same issue. Each side may be testing a commercial relationship while trying to protect its own know how. A mutual NDA is often more appropriate in that setting than a one way agreement.

Employment and contractor discussions

A standalone NDA can be useful for senior hires, consultants and contractors, but it should line up with the main employment agreement or contractor agreement. If the documents say different things about confidential information, ownership of work product or post engagement restrictions, disputes become more likely.

For many businesses, confidentiality terms are best built into the core contract rather than left in a separate short form NDA that never gets revisited.

Commercial tenders and service proposals

Businesses responding to tenders or sharing detailed proposals often need confidentiality protections on both sides. The client may disclose internal requirements and data. The provider may disclose pricing logic, methodology or system architecture.

Before you rely on a verbal promise that your proposal will be kept private, check whether the tender terms already deal with confidentiality. If they do, a separate NDA contract might duplicate or conflict with those written terms.

Legal Issues To Check Before You Sign

The right NDA contract is not the longest one. It is the one that clearly matches the information, the relationship and the real risk before you sign.

Here are the clauses that deserve careful attention.

What exactly counts as confidential information?

The definition of confidential information is the core of the agreement. If it is too narrow, valuable material may fall outside the contract. If it is too broad, the recipient may push back or ignore obligations that feel unrealistic.

A well drafted definition usually covers multiple forms of information, such as:

written documents and emails
oral discussions and meeting notes
financial data and forecasts
customer and supplier information
source code, technical documents and product designs
business plans, pricing and marketing strategy
samples, prototypes and specifications

Check whether the NDA says information must be marked confidential. That can help with certainty, but it can also create a trap. If your team forgets to mark a document, you may lose protection under the contract. A better approach is often to protect information that is either identified as confidential or would reasonably be understood to be confidential in the circumstances.

What is the permitted purpose?

The agreement should say why the information is being shared and limit use to that purpose. Without that clause, the recipient may be prevented from disclosing information but still have more room than you intended to use it internally.

Examples of permitted purposes include:

evaluating a proposed investment
assessing a supply or manufacturing arrangement
performing services under a draft commercial deal
considering a potential acquisition or partnership

This matters because misuse is not always a public leak. Sometimes the problem is internal use beyond the deal you were discussing.

Who can receive the information?

Most recipients need to share information with certain people, but that access should be controlled. The NDA should identify who can receive confidential information and on what basis.

You will usually want disclosure limited to people who:

need the information for the permitted purpose
are told it is confidential
are bound by confidentiality obligations, either through contract or professional duties

If the recipient can share information with any related company, adviser or subcontractor without conditions, the practical protection drops quickly. Before you accept the provider's standard terms, check whether onward disclosure is too loose.

What information is excluded?

An NDA should carve out information that should not be restricted. These exclusions make the agreement fairer and more realistic, and they also reduce disputes about whether the recipient has breached the contract.

Common exclusions cover information that:

is already public, other than because of a breach
was lawfully known by the recipient before disclosure
is independently developed without use of the confidential information
is received lawfully from a third party without confidentiality obligations
must be disclosed by law, court order or regulatory requirement

Mandatory disclosure clauses should also say what the recipient must do first, such as giving prompt notice where legally permitted and limiting the disclosure to what is required.

How long do the obligations last?

There is no one perfect confidentiality period for every New Zealand business. The right term depends on the type of information and how quickly it loses value.

For some commercial discussions, two to five years may be reasonable. For trade secrets or highly sensitive technical know how, longer protection may be justified. The key point is to avoid arbitrary wording that does not fit the information. A very short term can undermine protection. An unlimited term can be harder to negotiate and may not always be necessary.

Also check whether the NDA ends at a certain date but the confidentiality obligations survive termination for a further period. Those are different issues.

What happens to documents, files and data at the end?

The agreement should say what the recipient must do when discussions end or on request. If this is missing, information can remain scattered across inboxes, shared drives and backups for years.

The contract may require the recipient to:

return physical documents and samples
destroy electronic copies
delete information from active systems where practicable
confirm destruction in writing
keep one archival copy if required for legal or compliance reasons

This clause needs practical wording. A promise to delete every backup instantly may not reflect how business systems actually work.

Does the NDA deal with intellectual property?

An NDA contract protects secrecy, but it does not automatically transfer ownership of ideas, materials or work product. If intellectual property is relevant, the document should state that disclosure does not grant a licence, assign ownership or allow copying beyond the permitted purpose.

If a contractor or developer will create new materials, a separate services agreement or IP assignment clause may still be needed. This is a common point of confusion. Confidentiality and ownership are related, but they are not the same thing.

What remedies apply if there is a breach?

The main risk with confidential information is that money alone may not fix the damage. Once information is leaked, the commercial value may be gone. That is why many NDAs state that the disclosing party may seek urgent court orders, such as injunctive relief, in addition to any claim for loss.

That wording does not guarantee a court outcome, but it helps signal that ordinary damages may not be an adequate remedy. The agreement should also identify the governing law and dispute framework, especially if the other party is overseas.

Common NDA Mistakes

Most NDA problems come from using a generic template without checking whether it fits the actual conversation.

Here are the mistakes that cause the most trouble for startups and SMEs in New Zealand.

Using an NDA when the real issue is the main contract

An NDA is not a substitute for a proper services agreement, manufacturing agreement or employment agreement. If the other side is going to build, supply or advise, the key risks often sit in ownership, payment, liability clauses, deliverables and termination rights, not just confidentiality.

Founders sometimes spend time negotiating a short NDA and then sign the main contract on standard terms without the same care. That can leave major gaps.

If each side is disclosing valuable information, a mutual NDA is often more appropriate. A one way agreement can create imbalance and friction, particularly in partnership or due diligence discussions.

Before you sign, ask whether the information flow is actually one directional. If not, the document should reflect the reality of the discussion.

Defining confidential information too vaguely

Words like “all information relating to the business” may sound wide, but they can create uncertainty. If a dispute arises, the question will be whether the recipient could reasonably identify what was protected.

The safer approach is to combine a clear definition with examples that fit the transaction.

Forgetting oral disclosures

Many useful discussions happen in calls, demos and meetings. If the NDA only covers written material, important disclosures may sit outside the contract.

If oral disclosures are included, the agreement should still set some practical standard for identifying them as confidential, either at the time or within a short follow up period.

Ignoring privacy obligations

If the information includes personal information, confidentiality is only part of the picture. New Zealand privacy law may also apply to collection, use, storage and disclosure of that data.

An NDA does not replace obligations under privacy law or the need for proper data handling terms and data protection measures. This matters in customer database reviews, software integrations and outsourced service arrangements.

Assuming the NDA protects ideas in the abstract

Businesses sometimes think an NDA means no one can ever use anything “similar” to what was discussed. That is usually too broad. A confidentiality agreement restricts use and disclosure of protected information. It does not automatically create monopoly rights over a concept, market category or general business model.

If the real value lies in branding, code, content, designs or inventions, other intellectual property protections may also need attention.

Letting the term expire too early

Some template NDAs end all obligations after 12 months, even though the information may still be sensitive well after talks have ended. That mismatch often goes unnoticed until a problem appears.

Check the duration carefully, especially where disclosure involves product development, strategic planning or long sales cycles.

Not checking overseas enforcement issues

If the recipient is based outside New Zealand, enforcement becomes more complicated. Governing law, jurisdiction, service of notices and practical recoverability all matter more.

A New Zealand law clause can still be useful, but it may not solve every cross border problem. This is worth reviewing before you disclose key material.

FAQs

Is an NDA contract legally enforceable in New Zealand?

Yes, an NDA can be enforceable in New Zealand if it is properly drafted, supported by a valid contractual arrangement and clear enough to identify the obligations. The usual contract principles still apply, so vague or unrealistic terms can weaken enforceability.

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

An NDA is usually a standalone agreement used before or alongside a wider deal. A confidentiality clause is a section inside another contract, such as a services agreement, employment agreement or sale agreement. Either can work, as long as the wording suits the relationship.

Should startups always ask investors to sign an NDA?

No. Many investors will not sign one at the first meeting. Startups often protect themselves by limiting what they disclose early, then using a confidentiality agreement once the discussion becomes more detailed and commercially sensitive.

Can an NDA stop someone from using my idea?

It can restrict use and disclosure of confidential information that falls within the agreement, but it does not automatically give you ownership of a broad idea or market concept. If intellectual property is important, you may need separate clauses or separate legal protection.

How long should a confidentiality agreement last?

It depends on the information. Some business discussions suit a two to five year period. Trade secrets or long term technical know how may justify longer protection. The duration should reflect how long the information is likely to remain commercially sensitive.

Key Takeaways

An NDA contract should clearly define the confidential information, the permitted purpose and who can access the information.
The agreement should include sensible exclusions, a realistic confidentiality period, and practical rules for return, deletion or destruction of materials.
Confidentiality clauses do not automatically deal with intellectual property ownership, privacy obligations or the wider commercial terms of the relationship.
Founders commonly run into trouble when they use a generic template, forget oral disclosures, accept weak recipient rights, or rely on an NDA when the main contract needs attention.
Before you sign a confidentiality agreement, make sure the wording reflects the actual deal, the sensitivity of the information and any cross border enforcement issues.

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

NDAs in New Zealand: What to Include in a Confidentiality Agreement