Do I Need An NDA For An App Idea?

Yes, you can ask app developers to sign an NDA before you share the details of your app idea. In many cases, that's a sensible step - especially if you're about to show a prototype, user research, technical notes, pricing strategy or anything else that gives your business an edge.

The slightly more nuanced part is this: an NDA won't magically protect every thought in your head. New Zealand law doesn't usually protect an idea on its own. What you can protect is the confidential information, code, designs, documents and know-how that sit behind the idea.

So, if you're pitching an app to developers or agencies, the goal is to be practical. Share enough for them to quote properly, but put clear rules around what they can do with your information.

Can I Ask Developers To Sign An NDA Before Sharing My App Idea?

Yes, you can ask developers to sign an NDA before you share sensitive product details. An NDA is a contract that sets out what information is confidential and what the developer can and can't do with it.

This is common when you're speaking with:

• freelance app developers
• software agencies
• UX and UI designers
• technical consultants
• potential co-founders or contractors
• investors or advisers who will see your product roadmap

That said, not every first conversation needs a full NDA. If you're just asking whether a developer has experience building marketplace apps, booking tools or fintech dashboards, you may be able to keep things high-level.

For example, you might say you want to build a booking app for independent tradies, without sharing your customer acquisition plan, pricing model, prototype screens or algorithm logic.

An NDA becomes more useful when you're ready to share the detail that makes your product distinctive, such as:

• wireframes, user flows and Figma designs
• technical specifications and architecture diagrams
• source code, API documentation or database structures
• customer lists, supplier relationships or market research
• commercial plans, budgets and launch timelines
• AI prompts, training data, workflows or proprietary methods

If a developer refuses to sign any confidentiality terms before seeing sensitive material, that doesn't always mean they're untrustworthy. Some agencies have their own NDA, and some avoid very broad NDAs because they work with similar clients. The key is whether the terms are fair, specific and workable for both sides.

Does An NDA Protect My App Idea Or My Source Code?

An NDA protects confidential information, not the bare concept of an app idea. In New Zealand, the law is usually much stronger once your idea has been recorded, developed or expressed in a specific way.

Copyright under the Copyright Act 1994 can protect things like software code, written specifications, interface designs, text, graphics and other original works. But copyright doesn't protect the general idea of an app that solves a problem.

For example, the broad idea of a meal-planning app for busy parents isn't protected by copyright. Your actual app name, logo, codebase, screen designs, customer research and written product strategy may be protectable in different ways.

An NDA helps by making the developer promise not to:

• use your confidential information for their own business
• share it with other clients or competitors
• copy your prototype, pitch deck or technical notes
• keep your materials after the discussions end
• reverse engineer or build around your confidential material

It also creates a clearer paper trail. Without a written NDA, you may struggle to show exactly what was shared, when it was shared, and what restrictions applied.

Other protections may sit alongside your NDA. You might register your app name or logo as a trade mark through IPONZ, keep source code in a private repository, or use a software development agreement that assigns intellectual property to your business. If your app involves a genuinely technical invention, you may also need specialist patent advice before public disclosure.

What Should An App Development NDA Cover?

An app development NDA should cover the information you're sharing, the limited purpose for using it, who can see it, and what happens when the discussions end. A generic NDA can miss the details that matter in a software project.

For an app pitch, your NDA should usually deal with:

• The parties: name your company, NZBN if you have one, and the developer or agency signing the agreement.
• Confidential information: include prototypes, source code, wireframes, technical notes, user research, business plans, data, designs and discussions.
• Purpose: say the developer can only use the information to assess, quote for or provide app development services to your business.
• Permitted disclosure: set out who they can share it with, such as employees, contractors or advisers who genuinely need to know.
• Security: require reasonable steps to protect files, logins, repositories, cloud folders and project management tools.
• Return or deletion: say what happens to your materials if you don't proceed.
• Time period: explain how long the confidentiality obligations last.
• Exclusions: carve out information that's public, already known, independently developed or required to be disclosed by law.

You should also think carefully about personal information. If you're sharing user data, test data or customer information, the Privacy Act 2020 may apply. In that case, the NDA should sit alongside privacy and data handling terms that cover storage, access, security, deletion and overseas service providers.

The more technical your pitch is, the more specific the NDA should be. A one-page template might be fine for an early chat, but it may not be enough once you're sharing code repositories, database structures or commercially sensitive product strategy.

How Do I Handle Prototypes, Ownership And Open Source Code?

You should handle prototypes, ownership and open source code in a separate development agreement, not just in the NDA. The NDA protects secrecy, while the development agreement explains who owns what gets built.

This distinction matters because software projects often mix several types of material:

• your pre-existing idea, brand, content and research
• the developer's pre-existing tools, libraries and code snippets
• new code written specifically for your app
• open source components
• third party APIs, plugins, fonts, templates and SaaS tools

Under the Copyright Act 1994, ownership can depend on how the work was created, whether the developer is an employee or contractor, whether you commissioned and paid for the work, and what your contract says. For commissioned computer programs in New Zealand, the commissioner may be the first owner unless there's an agreement to the contrary. Even so, it's risky to rely only on default rules because agency terms often modify ownership, and different parts of the project may be treated differently.

Your development agreement should clearly say:

• whether your business owns the new code once paid for
• whether the developer keeps ownership of their background IP
• what licence you get to use any developer tools or frameworks
• which open source licences can be used and which need approval
• whether the developer can reuse general know-how from the project
• what happens if the project ends before launch, including handover and source code access

If you're engaging an individual developer as a contractor, your contract should also match the real working relationship. The Employment Relations Act 2000 now includes a contractor gateway test introduced by the Employment Relations Amendment Act 2026, which can affect whether an individual is treated as a contractor rather than an employee. The NDA won't fix a poorly structured engagement on its own.

Can Developers Share My App Details With Their Team Or Subcontractors?

Yes, but only if your NDA allows it and puts sensible limits around that sharing. Most developers can't assess or build an app entirely alone, especially if they work through an agency.

In practice, they may need to disclose your information to:

• their internal developers and project managers
• UX designers or QA testers
• subcontractors in New Zealand or overseas
• cloud hosting providers and collaboration tools
• professional advisers, such as accountants or legal advisers

A good NDA doesn't simply ban all disclosure. That can make the project unworkable. Instead, it says disclosure is only allowed where the person genuinely needs the information for the agreed purpose and is bound by confidentiality obligations at least as strict as the NDA.

Say Mia is building a marketplace app for home cleaners. She speaks with four agencies, then chooses one to receive her detailed Figma prototype, pricing model and launch plan. Her NDA lets the agency share the materials with two named developers, one UX designer and its usual cloud hosting provider. It doesn't let the agency show the prototype to another cleaning platform or use Mia's pricing model in a sales pitch.

Mia also asks for all documents to be returned or deleted if she doesn't proceed within 30 days after receiving the quote. That gives the agency enough access to do its job, while keeping the circle of disclosure tight.

If personal information is involved, you should be even more careful. For example, if you're testing with real customer profiles, the developer may need specific privacy and security obligations under the Privacy Act 2020, not just a general promise to keep things secret.

What Should I Put In A Software NDA Template?

A software NDA template should be treated as a starting point, not a finished document. The clauses need to be tailored to your product, the stage of your discussions and the information you're actually sharing.

Here is a practical outline you can use to plan the document before getting it reviewed:

1. Parties: list your business details, the developer or agency details, and any relevant NZBN or company number.
2. Background: explain that you're discussing a possible app development project or technical services arrangement.
3. Definition Of Confidential Information: include app concepts, prototypes, source code, product roadmaps, pricing, customer information, designs, data and conversations.
4. Purpose: limit use to assessing, quoting for, negotiating or delivering the app development project.
5. Confidentiality Obligations: require the recipient to keep the information secret and use reasonable security measures.
6. Permitted Disclosures: allow limited disclosure to team members, subcontractors or advisers who need access and are also bound to confidentiality.
7. Exclusions: carve out public information, information already known, independently developed information and legally required disclosure.
8. Return Or Deletion: state when files, credentials, prototypes and documents must be returned, deleted or destroyed.
9. Ownership: confirm that sharing information doesn't transfer ownership of your IP or grant a licence beyond the agreed purpose.
10. Term: set the confidentiality period, and consider longer protection for trade secrets that remain confidential.
11. Consequences Of Breach: explain that your business may seek legal remedies if the NDA is breached.
12. Governing Law: specify New Zealand law and the forum for any legal process, if appropriate.

A lawyer should tailor this before you use it. For example, a healthtech app sharing patient-related test data needs a tailored privacy policy and different protections from a simple to-do list app with no personal information. A SaaS product with valuable backend processes may also need stronger rules around reverse engineering and access to repositories.

If you're using a free template, check that it actually fits New Zealand law and your software scenario. Many templates are written for a different country, or they focus on general business discussions rather than app development.

What Should I Do Before Pitching My App To Developers?

You should prepare what you'll share, decide when the NDA is needed, and keep a clear record of each conversation. This doesn't have to slow you down, but it can help you stay in control.

A Practical Pitch Process

1. Start with a high-level summary: describe the problem, target users and type of app without giving away your core technical or commercial advantage.
2. Shortlist developers: check experience, portfolio, references and whether they use employees, contractors or overseas teams.
3. Use an NDA before deeper disclosure: put it in place before sharing prototypes, source code, user research, data or business strategy.
4. Share in stages: give enough information for a meaningful quote, then disclose more once you've chosen a preferred developer.
5. Control access: use private folders, repository permissions and time-limited invitations where possible.
6. Keep records: save signed NDAs, meeting notes, files shared, access logs and email trails.
7. Move to a development agreement: before work starts, cover scope, milestones, payment, ownership, testing, support, privacy, app terms and conditions and handover.

For example, Mia has a development budget of $25,000 and wants to compare three agencies. She has a first 20-minute call with each agency without sharing her full prototype. After choosing two serious contenders, she sends them an NDA. Once signed, she shares her Figma file, three user personas, a feature list and her launch plan. She doesn't share admin credentials or source code until she has a signed development agreement with her chosen agency.

That process helps Mia get proper quotes without handing over everything too early.

Key Takeaways

• An NDA can help protect confidential information when you pitch your app to developers, but it won't protect a bare idea by itself.
• Your NDA should be specific to software development, including prototypes, source code, designs, data, permitted disclosures and return or deletion of materials.
• Use a development agreement as well as an NDA if someone is actually building the app, especially for IP ownership, open source code, payment and handover.
• If you're sharing user data or test data, think about your obligations under the Privacy Act 2020.
• Trade marks, copyright, contracts and good access controls all work together to protect your app as it grows.

If you'd like help with your app confidentiality agreement, software development contract, IP ownership clauses or privacy terms, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.