Every NDA answers one structural question before it answers anything else: is only one side sharing confidential information, or are both? A one-way (unilateral) NDA obligates only the party receiving information, and it’s the right choice whenever you’re the only one disclosing anything real. A mutual (bilateral) NDA obligates both sides equally, and it’s the right choice whenever the relationship runs in both directions from the start. Picking the wrong one doesn’t just look sloppy. A one-way NDA in a two-directional relationship leaves your own disclosures unprotected, and a mutual NDA where only one side is actually sharing anything adds obligations and negotiating friction that don’t need to exist.
One-way NDA vs mutual NDA
| One-way NDA | Mutual NDA | |
|---|---|---|
| Who is bound | Only the receiving party | Both parties, symmetrically |
| Typical use | You are the only one disclosing anything | Both sides share their own information |
| Negotiation | Usually straightforward, less pushback | Both sides scrutinize equally |
| Common relationship | Investor pitch, employee, contractor | Founder talks, M&A, vendor evaluation |
What a One-Way NDA Actually Protects
A one-way NDA makes sense whenever the flow of sensitive information is entirely one direction. If you’re pitching a product idea to a potential contractor, sharing a prototype with a manufacturer, or hiring an employee who will see your systems and customer data but isn’t bringing any confidential information of their own to the table, a one-way NDA covers exactly what needs covering without asking the other party to protect information they were never given. It’s also the more common choice in early scoping conversations, quoting a job, evaluating a single vendor’s proposal, where the other side hasn’t shared anything of their own yet.
The failure mode is using a one-way NDA when the conversation turns out to be more two-directional than expected. If a contractor you hired under a one-way NDA starts sharing their own proprietary methodology as part of the engagement, that information is unprotected unless you update the agreement.
What a Mutual NDA Actually Protects
A mutual NDA binds both sides to the same obligations, which matters whenever each party is disclosing something the other needs to protect. Co-founder conversations are the clearest example: each person is describing their own ideas, contacts, or existing work, and neither should have to trust the other’s discretion without a written obligation running back the other way. M&A due diligence works the same way once both companies start exchanging financials, contracts, and internal plans to evaluate a deal. Vendor evaluations where you’re comparing multiple vendors’ proposals often need mutual coverage too, since a serious proposal usually includes the vendor’s own pricing model or process, information you’d want protected as much as they want your requirements protected.
The tradeoff is that a mutual NDA gets scrutinized by both sides during negotiation, since each party is agreeing to restrictions on itself, not just asking the other side to accept them. That’s not a reason to avoid a mutual NDA when the relationship genuinely calls for one, but it does mean mutual NDAs take slightly longer to finalize than a one-way agreement one side simply signs.
Matching the NDA Type to the Relationship
A short list of common relationships and which direction usually fits:
An investor pitch is almost always one-way. You’re disclosing your business, the investor typically isn’t disclosing anything confidential back, though in practice many investors decline to sign any NDA at all given how many pitches they see, worth confirming before you assume one will be signed. A new employee or independent contractor is typically one-way, since they’re being given access to your systems and information, not bringing their own. A co-founder conversation or a genuine partnership discussion is mutual, since both people are describing their own plans. A vendor or supplier evaluation, comparing multiple options before you sign an agreement, is usually mutual, since a real proposal reveals the vendor’s own confidential process. M&A due diligence, on either side of a potential acquisition, is mutual, since both companies open their books to evaluate the deal.
The Cost of Getting It Wrong
The two failure directions aren’t symmetric. Using a one-way NDA when the relationship turns out to be mutual is the more expensive mistake: the other party’s disclosures to you are simply unprotected, and there’s no retroactive fix without both sides signing an amendment. Using a mutual NDA when a one-way agreement would have done leaves you with unnecessary obligations, restrictions on how you can use and disclose information you received, but at least both sides are protected rather than exposed. When you’re not sure which way a relationship will go, particularly early conversations that could turn into something more collaborative, defaulting to mutual is the safer error to make.
Our NDA generator builds either version and asks a short set of questions about who is actually disclosing what, so you’re matching the document to the relationship rather than guessing from a blank template. For the drafting details once you’ve picked a direction, see How to Write an NDA: A Step-by-Step Guide, and if you’re not sure a standalone NDA is even the right document, NDA vs Confidentiality Clause covers when a clause inside a bigger contract covers you instead.
