What an NDA Actually Does
A non-disclosure agreement (NDA) — also called a confidentiality agreement — is a contract that legally obligates one or more parties to keep specified information secret. If the receiving party discloses that information without authorization, you can sue them for breach of contract.
What an NDA does not do is make information unbreachable. It creates legal recourse after a breach — it does not prevent one. Understanding this distinction helps you decide when an NDA is the right tool and when it is overkill.
Situations Where You Should Always Use an NDA
Sharing a Business Idea Before a Partnership
If you are considering going into business with someone and need to share your concept, customer data, financial projections, or technical approach to evaluate the opportunity — get an NDA signed first. Ideas are not protected by copyright, and if the partnership falls through, you have no recourse without a signed agreement.
Hiring Contractors or Freelancers With Access to Sensitive Information
A freelancer building your product will likely see your source code, internal processes, customer lists, or unreleased features. A standard freelance contract should include confidentiality clauses, but a standalone NDA is appropriate when the sensitivity of the information is high enough to warrant extra emphasis.
Discussions With Potential Investors
Due diligence requires sharing financial details, projections, and proprietary business information. Most institutional investors (VCs, angel networks) will refuse to sign NDAs for early-stage conversations — this is standard practice. For individual investors or strategic partners evaluating an acquisition, an NDA is more appropriate.
Sharing Proprietary Technology or Processes
Manufacturing processes, formulas, algorithms, or technical specifications that give you a competitive advantage are prime candidates for NDA protection. If a supplier, manufacturer, or development partner needs to understand your proprietary process to work with you, protect it first.
Employee Onboarding in Sensitive Roles
New hires in roles that expose them to customer data, trade secrets, or competitive strategy should sign NDAs as part of onboarding. Many jurisdictions enforce these when they are reasonable in scope and duration.
When You Probably Do Not Need an NDA
- General business meetings or exploratory calls where no specific confidential information is exchanged
- Pitching to accelerators or competitions — most have their own confidentiality policies and will not sign yours
- Sharing publicly available information or information the other party already knows
- Casual introductory conversations before you have decided whether to work together
Mutual vs. One-Way NDAs
A one-way (unilateral) NDA protects only one party's information — typically the disclosing party. Use this when you are sharing information with someone but they are not sharing anything sensitive back.
A mutual (bilateral) NDA protects both parties equally. Use this when both parties will be sharing confidential information — common in partnerships, joint ventures, or when two companies are evaluating a merger.
What to Include in an NDA
A solid NDA should define:
- Who the parties are
- What counts as confidential information (and what does not — for example, information already in the public domain)
- What the receiving party can and cannot do with the information
- How long the obligation lasts (typically 2–5 years; perpetual is common for trade secrets)
- What happens to the information when the relationship ends (return or destroy)
- Which law governs the agreement and where disputes are resolved
TermsDock's NDA Generator creates a complete, professionally structured non-disclosure agreement in seconds. Enter the parties, purpose, and duration — and download a ready-to-sign document.