NDA Template In New Zealand: What To Include In A Non-Disclosure Agreement

If you're running a small business, there's a good chance you'll share valuable information with other people at some point - contractors, suppliers, potential investors, collaborators, even new hires.

And in the early days, it's tempting to move fast and "just get started" on the relationship.

That's where a solid NDA (non-disclosure agreement) comes in. Starting with an NDA template can help you protect your confidential information from day one - but only if it actually fits your business, your situation, and New Zealand law.

Below, we'll walk through what a non-disclosure agreement should include, how an NDA template is usually structured, and the common mistakes we see businesses make when they rely on generic documents.

What Is An NDA (And When Should You Use One)?

An NDA (also called a confidentiality agreement) is a legal contract where one or both parties agree to keep certain information confidential and only use it for a permitted purpose.

In plain terms, it's how you say: "I'm going to tell you something sensitive for business reasons - but you can't share it or misuse it."

As a small business owner, you might use an NDA when:

• You're discussing a potential partnership or collaboration.
• You're talking to a manufacturer or supplier about product specs, pricing, or processes.
• You're pitching to an investor or strategic partner.
• You're engaging an external contractor (developer, marketer, designer, consultant).
• You're hiring team members who'll access sensitive systems, customer data, or IP.

While an NDA template can be a helpful starting point, it's worth remembering that NDAs aren't one-size-fits-all. The right agreement depends on what information you're sharing, who you're sharing it with, and what you want to happen if something goes wrong.

If you're engaging a contractor, for example, the NDA might sit alongside (or be built into) a broader Contractor Agreement so the confidentiality obligations line up with deliverables and ownership of work.

Is An NDA Template Legally Binding In New Zealand?

An NDA can be enforceable in New Zealand if it's a properly formed contract and its terms are clear and reasonable in the circumstances.

Generally, that means there needs to be:

• Clear terms (what is confidential, what isn't, what each party must do).
• Agreement between the parties (often shown by signing, but this can depend on the situation).
• Intention to create legal relations (in business contexts, this is usually assumed).

A key issue with using a random NDA template you've found online is that it may be:

• Written for a different country (different legal concepts, remedies, or definitions).
• Too vague to enforce (or so broad that it becomes unreasonable in practice).
• Missing key clauses that matter for your industry (like IP, return/destruction of materials, or permitted disclosures).
• Inconsistent with other documents you use (like your customer contracts, employment agreements, or shareholder documents).

It's also important to be careful with "template stacking" - where you use an NDA template plus another agreement template, and the two contradict each other. If you're working with multiple parties and long-term arrangements, having consistent documentation matters, including things like a Company Constitution and (where relevant) a Shareholders Agreement that deals with confidential company information at an ownership level.

What Should An NDA Template Include? (The Core Clauses)

Most NDAs follow a fairly standard structure, but the details inside each section are what makes the agreement useful (or risky).

Here are the clauses we'd generally expect to see in a well-drafted NDA template for an NZ business.

1) Who The Parties Are (And Who's Covered)

This sounds simple, but it's a common "gotcha" area.

Your NDA should correctly identify:

• The legal name of each party (person or entity).
• Company numbers (where applicable) and registered addresses.
• Who else is bound by the NDA (e.g. employees, contractors, advisors of the receiving party).

If you're dealing with a company, it's often not enough to bind only the company in name - you also want to ensure the confidentiality obligation extends to the individuals who will actually access your confidential information.

2) What "Confidential Information" Means

This is the heart of the NDA.

A good NDA template will define confidential information clearly, usually including things like:

• Pricing and margins
• Business plans and growth strategy
• Supplier details and terms
• Customer lists and customer data
• Marketing plans and analytics
• Technical information, designs, prototypes, source code, formulas, processes
• Trade secrets and know-how

At the same time, it's usually smart to avoid defining confidential information so broadly that it becomes unrealistic. If everything is confidential forever, it can be harder to enforce and may scare off reasonable counterparties.

Many NDAs also cover the existence of the discussions (e.g. you don't want a supplier telling others you're launching a new product).

3) What The Receiving Party Is Allowed To Do With The Information

An NDA doesn't just say "keep it secret". It also needs to say what the receiving party can do with it.

Most agreements include a "permitted purpose" clause, such as:

• "evaluating a potential business relationship"
• "providing services to the disclosing party"
• "assessing a potential investment"

This matters because one of the biggest risks isn't just disclosure - it's misuse. For example, a contractor might not "leak" your information, but they might use your process to build something similar for someone else.

4) The Confidentiality Obligations (Practical Requirements)

Your NDA template should spell out the receiving party's obligations, such as:

• Not disclosing the confidential information to anyone other than approved representatives.
• Keeping it secure and taking reasonable steps to prevent unauthorised access.
• Only copying information where necessary for the permitted purpose.
• Not reverse engineering, decompiling, or deriving competing materials (where relevant).

If the information includes personal data (for example, customer details), you should also think about your obligations under the Privacy Act 2020. In many situations, an NDA alone isn't enough - you may need a more specific privacy/data arrangement depending on what's being shared and why.

For businesses that collect personal information, it's also important that your external-facing documents (like your Privacy Policy) match what you're doing behind the scenes.

5) Carve-Outs: What Is Not Confidential

Most NDAs include standard exclusions, such as information that:

• Is already public (and not because of a breach).
• Was already known to the receiving party before disclosure.
• Was independently developed without using the confidential information.
• Must be disclosed by law (for example, to a regulator or under a court order).

These carve-outs are normal and practical - and they help keep the NDA fair and enforceable.

6) How Long The NDA Lasts (The Term And Survival Period)

Many people assume an NDA automatically lasts forever. In practice, it's usually more nuanced.

An NDA template typically covers:

• Term: how long the agreement is in effect (e.g. 1?3 years, or until the discussions end).
• Confidentiality period: how long the confidentiality obligations continue after the relationship ends (e.g. 2?5 years, sometimes longer for trade secrets).

What's "right" depends on your business. A fast-moving tech startup might need longer protection around source code and product roadmap. A business discussing a one-off supply arrangement might use a shorter timeframe.

7) Return Or Destruction Of Confidential Information

When the relationship ends (or if negotiations fall over), you'll often want the receiving party to:

• Return physical documents and materials, and/or
• Delete electronic copies and confirm deletion.

This clause is particularly useful where you've shared:

• Product designs
• Customer lists
• Internal financial reports
• Strategy documents

It's also common to include a practical exception for routine back-ups (because deletion from back-up systems can be difficult), as long as the information remains protected and isn't accessed.

8) Intellectual Property: What's Shared vs What's Owned

A big misconception is that an NDA automatically deals with ownership of ideas or work product. Often, it doesn't - unless you include clauses that specifically address it.

If you're sharing confidential information that relates to your intellectual property (like product designs, branding, software, or creative assets), you may want your NDA to clearly state that:

• Nothing in the NDA transfers ownership of IP to the receiving party.
• Any pre-existing IP remains owned by the disclosing party.
• Any new materials created (if relevant) should be dealt with in a separate contract.

If you're actually paying someone to create something, the IP ownership is usually better handled in a properly drafted services agreement rather than relying on an NDA alone.

9) What Happens If There's A Breach (Remedies)

An NDA template should cover what you can do if the other party breaches confidentiality.

This might include:

• Injunctive relief: the right to ask a court for orders to stop (or prevent) disclosure or misuse (this can be crucial if money alone won't fix the problem).
• Damages: compensation for losses caused by the breach.
• Indemnities (sometimes): requiring the receiving party to cover certain losses arising from their breach.

This is also where "template" wording can be risky. If the remedies section is copied from another jurisdiction, it may reference concepts that don't translate neatly into NZ practice - or it may be drafted so broadly that it becomes difficult to rely on.

One-Way Vs Mutual NDA: Which One Should Your NDA Template Be?

There are two common structures for an NDA template:

One-Way NDA (Unilateral)

A one-way NDA is where only one party is disclosing confidential information (and the other party must protect it).

This is common when:

• You're hiring a contractor and you're sharing internal systems/processes.
• You're talking to a supplier about your product idea.
• You're sharing your business model with a potential buyer.

Mutual NDA (Bilateral)

A mutual NDA is where both parties may share confidential information, and both must protect it.

This is common when:

• You're exploring a joint venture or collaboration.
• You're negotiating a strategic partnership.
• You're in early-stage discussions where both parties will exchange sensitive information.

If you're not sure which structure fits your situation, it's worth pausing before signing. Using the wrong type of NDA can lead to awkward gaps - like being bound to protect the other party's information, while yours isn't properly covered.

Common Mistakes When Using An NDA Template (And How To Avoid Them)

Templates can be a great tool, but they can also create a false sense of security.

Here are issues we often see when small businesses rely too heavily on an NDA template.

The NDA Doesn't Match The Real-World Relationship

For example, you might be bringing on a contractor to build your website, but the NDA template doesn't address:

• Who owns the deliverables
• Whether they can use your work in their portfolio
• Whether they can reuse underlying materials for other clients

That's why your broader contracting framework matters. Depending on the engagement, you might also need a Service Agreement so confidentiality, IP, and scope all work together.

The Definition Of Confidential Information Is Too Generic

If the template definition is vague (e.g. "all information disclosed by the disclosing party"), you may struggle to prove what was confidential and what wasn't.

On the other hand, if it's so broad that it captures everything forever, the other party may refuse to sign - or it may be challenged as unreasonable in context.

The NDA Doesn't Deal With Sharing Information Internally

If you're disclosing information to a company, you'll usually expect that company's staff and advisors can access it for the permitted purpose.

Your NDA should address:

• Who counts as an "approved representative"
• Whether those representatives must be bound by confidentiality obligations too
• Who is responsible if an employee/contractor of the receiving party leaks the information

The NDA Ignores Privacy And Data Handling

If you're sharing personal information (like customer contact details, health information, or payment-related data), privacy law becomes part of the picture.

An NDA may help, but it's not automatically a full compliance solution under the Privacy Act 2020. You may need additional privacy terms, a clear purpose, and secure handling arrangements.

The NDA Doesn't Say What Happens At The End

Without a return/destruction clause, the other party may keep your information indefinitely - even if they stop working with you.

From a risk-management perspective, it's usually better to have a clear "exit" process in the contract, especially if you're sharing commercially sensitive documents.

Do You Need Anything Else Besides An NDA?

Often, yes.

An NDA is great for protecting confidential information during discussions or early-stage relationships. But depending on what you're doing, it may need to sit alongside other legal documents to properly protect your business.

For example:

• If you're hiring staff, an NDA is often integrated into an Employment Contract (and supported by workplace policies).
• If you're sharing confidential information as part of a broader project, you may need a service or supply agreement with confidentiality clauses (so obligations align with delivery and payment terms).
• If you're building a company with multiple founders or owners, confidentiality and IP protections are often reinforced in a Founders Agreement and shareholder arrangements.

As your business grows, getting your legal foundations right early can save you a lot of stress later - especially when you start dealing with bigger contracts, higher-value partnerships, or business sale discussions.

Key Takeaways

• An NDA (non-disclosure agreement) is a practical way to protect your business's confidential information when you're dealing with contractors, suppliers, collaborators, and potential investors.
• An NDA template can be enforceable in New Zealand, but it needs to be properly drafted and fit your real-world situation to be effective.
• A strong NDA template should clearly define confidential information, set a permitted purpose, include practical confidentiality obligations, and explain what happens when the relationship ends.
• Choosing between a one-way NDA and a mutual NDA matters - the wrong structure can leave gaps in protection or create unnecessary obligations.
• Common template mistakes include vague definitions, missing return/destruction obligations, ignoring privacy considerations, and failing to align the NDA with your other key contracts.
• In many situations, an NDA works best alongside other documents like a service agreement, employment contract, or founder/shareholder documentation.

This article is general information only and not legal advice. If you'd like help preparing an NDA that actually fits your business (or reviewing an NDA template before you sign it), you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.