Mutual NDA vs One-Way NDA in India: Which One Should You Use?

Two companies sit down to explore a distribution arrangement. Each will hand over customer lists, pricing models and a roadmap. One party's lawyer sends across a one-way confidentiality agreement that only binds the other side. The other party's lawyer sends back a mutual NDA. Three weeks pass in redlines while the actual commercial discussion stalls, and the deal dies without anyone ever signing anything. The document that was meant to protect the conversation became the reason it never happened.

The choice between a mutual NDA and a one-way NDA is not a matter of taste or of who has the stronger template. It turns on a single question: whose information is actually being exposed, and in which direction. Get that wrong and you either over-protect a conversation that only flows one way, or you leave one party's trade secrets unprotected while everyone assumes the document covers both sides. This guide explains how the mutual NDA vs one-way NDA decision should be made in the Indian context, what each format does at the clause level, and where the practical risks sit.

The mutual NDA vs one-way NDA distinction, stated plainly

A mutual NDA — also called a bilateral NDA or reciprocal confidentiality agreement — imposes confidentiality obligations on both parties at the same time. Each side is simultaneously a disclosing party and a receiving party. If you share your supplier cost sheet with a prospective manufacturer and they share their factory audit report with you, both of those pieces of information sit under the same set of obligations. A breach by either side triggers the same remedies.

A one-way NDA, sometimes called a unilateral NDA, binds only one party. One side discloses and the other receives. The discloser takes on no obligations regarding anything the receiver happens to say. This is the correct instrument when the information genuinely flows in a single direction — an employee receiving internal documents, a contractor being given access to a client's systems, a vendor quoting against a detailed specification.

The confusion arises because most real commercial conversations are lopsided rather than purely one-directional. A startup pitching to an investor discloses far more than it receives, but the investor will still share portfolio data, diligence findings and sometimes term sheet thinking. That asymmetry is what makes the choice consequential: a one-way NDA leaves the investor's disclosures unprotected, while a mutual NDA imposes duties on a startup that may have nothing meaningful to protect.

When a one-way NDA is the right instrument

Unilateral confidentiality is appropriate whenever the relationship is structurally hierarchical or the disclosure is genuinely one-sided. The clearest examples in Indian practice are employment and contracting. An employee joining a company receives access to client databases, source code, internal pricing and strategy documents. The company discloses nothing of comparable sensitivity to the employee. A one-way NDA signed at joining, usually paired with an IP assignment, is the standard and correct approach.

The same logic applies to freelancers and consultants who are given access to a client's systems, marketing data or product plans. A software vendor integrating with a bank's core systems receives far more confidential material than it gives. A one-way NDA from the bank to the vendor is proportionate; a mutual NDA in that situation often creates a false symmetry that the vendor's legal team will resist because it implies the vendor is also exposing trade secrets of equal value.

There is a second, less discussed case: preliminary conversations where one party is clearly the buyer or evaluator. A strategic acquirer conducting diligence on a target will typically insist on a one-way NDA that binds the target and its advisers, because the acquirer's own information exposure is minimal and its internal deal data is already ring-fenced. Targets should push back here — diligence inevitably involves the acquirer sharing integration plans, financing structure and personnel intentions, and those deserve protection too.

Clauses that change between the two formats

The core confidentiality obligations look similar in both documents. What changes is the architecture around them — who is bound, how long, and what happens when only one side breaches. These are the clauses where a template copied from the wrong format causes real problems.

Definitions of disclosing and receiving party

In a mutual NDA, the drafting has to work in both directions without becoming unreadable. The usual technique is to define "Disclosing Party" and "Receiving Party" so that each party occupies both roles depending on who is sharing. A well-drafted mutual NDA will say that the obligations apply "as though each party were the Receiving Party in respect of Confidential Information disclosed to it by the other". A poorly drafted one simply swaps names in a unilateral template and ends up with clauses that only make sense from one side — for instance, an indemnity that runs only from the receiver to the discloser, when both are receivers at different moments.

One-way NDAs avoid this problem entirely because the roles are fixed. The discloser is named, the receiver is named, and every obligation, indemnity and remedy runs in one direction. That clarity is the format's main drafting advantage.

Duration and survival periods

Confidentiality periods are usually expressed as a term running from the date of disclosure or from the date of the agreement, with a survival clause extending obligations after termination. In mutual NDAs, the trap is asymmetric survival: a draft that gives one party five years of protection and the other two years, often hidden in separate schedules. Indian courts will enforce whatever the parties agreed, so an uneven survival period is not automatically void — but it is a signal that the document was assembled from mismatched templates and should be read line by line before signature.

For trade secrets, which have no statutory expiry in India, a fixed period is a commercial choice rather than a legal requirement. Many practitioners use three to five years for general business information and indefinite or until-publicly-available obligations for source code, algorithms and formulations. A one-way NDA given to an employee often pairs a short confidentiality tail with a longer non-solicit period, and the two should not be conflated.

Indemnity and remedy symmetry

This is where the mutual format earns its keep. In a one-way NDA, only the receiver indemnifies the discloser. In a mutual NDA, each party should indemnify the other for losses caused by its own breach. Drafters frequently forget the second half, leaving a document titled "mutual" that only provides a remedy in one direction. The fix is straightforward: an indemnity clause that runs from "each party" to "the other party" in respect of that party's breach, with the same caps, exclusions and notice mechanics applying to both.

Injunctive relief deserves the same treatment. Indian practice relies on the Specific Relief Act, 1963 for interim and permanent injunctions, and confidentiality obligations are among the categories where courts have historically been willing to grant relief because damages are hard to quantify. A mutual NDA should make that remedy available to both sides on equal terms rather than reserving it for the discloser.

Why the format matters under Indian law

Confidentiality agreements in India rest primarily on contract. The Indian Contract Act, 1872 governs formation, consideration and enforceability. A mutual NDA is a contract supported by mutual promises: each party's promise to keep the other's information confidential is consideration for the reciprocal promise. That structure is legally comfortable. A one-way NDA signed at the start of employment or engagement also has consideration, usually the appointment itself or the access granted, though a document signed after the relationship has begun benefits from reciting fresh consideration to avoid an argument that past consideration is no consideration.

Section 27 of the Contract Act voids agreements in restraint of trade, and this is the provision that most often collides with confidentiality drafting. Confidentiality obligations that are reasonable and limited to protecting legitimate proprietary information have generally been treated as outside the mischief of Section 27, because they restrain misuse of information rather than the freedom to carry on a trade. Non-compete clauses that prevent a person from working for a competitor are treated far more strictly. Drafters who bundle a one-way NDA with a broad non-compete should expect the non-compete to be tested and the confidentiality obligation to survive independently.

The other statutory layer is data protection. The Digital Personal Data Protection Act, 2023 imposes obligations on entities processing personal data, and a confidentiality agreement that covers customer databases or employee records should acknowledge those obligations rather than pretend they do not exist. An NDA does not by itself make processing lawful; it sits alongside the consent and notice requirements the DPDP Act creates. For cross-border disclosures, the Information Technology Act, 2000 and the rules framed under it are also relevant where data is stored or transferred outside India.

Stamp duty and registration in practice

An NDA is not a document that requires compulsory registration under the Registration Act, 1908. It creates contractual rights rather than transferring or declaring an interest in immovable property, so the registration provisions that apply to sale deeds, leases and mortgages do not apply to it. Parties sometimes choose to register an NDA anyway, usually because a counterparty insists, but that is a commercial preference rather than a legal requirement.

Stamp duty is a different matter. Stamp duty on an agreement is a state subject, and the rate depends on the state where the instrument is executed and on how the agreement is characterised. Some states levy a fixed nominal duty on agreements generally; others apply a percentage of the contract value or of the consideration. Maharashtra, Karnataka, Delhi and Tamil Nadu each treat commercial agreements differently. It is not possible to state a single figure that applies across India, and any template that quotes one should be treated with suspicion. Confirm the current rate with the sub-registrar's office in the state of execution before signing, and if the agreement is signed in one state and performed in another, take advice on which stamping regime applies.

An unstamped or under-stamped agreement is not automatically void, but it becomes inadmissible in evidence until the deficit duty and penalty are paid. In a dispute over a breached NDA, that procedural problem can delay an injunction application at exactly the moment speed matters. Paying the correct duty at execution is cheap insurance.

Side-by-side comparison

The table below sets out the practical differences that matter when you are choosing between the two formats. It assumes a standard commercial context, not employment, where the one-way format is almost always correct.

Clause checklist before you sign either format

Whichever format you choose, these are the provisions that determine whether the document is usable when something goes wrong. A confidentiality agreement that omits them is a comfort blanket rather than a remedy.

• A precise definition of Confidential Information. It should name categories — technical data, financial information, customer lists, source code, pricing, business plans — and state that information is covered whether disclosed orally, in writing or by inspection, provided oral disclosures are confirmed in writing within a set period.
• Standard carve-outs. Information already public, independently developed, lawfully received from a third party without duty, or required to be disclosed by law or a regulator. The last carve-out should require notice to the discloser where legally possible.
• Permitted recipients and the duty to bind them. Employees, advisers and affiliates who need to know should be listed, and the receiver should be obligated to bind them to equivalent confidentiality. Vicarious liability for a leaking adviser is otherwise easy to deny.
• Purpose limitation. The information may be used only for the stated purpose — evaluating a distribution deal, assessing an investment, performing services. Without this, a receiver can argue that using the information for a different project was never prohibited.
• Return or destruction on termination. With a realistic exception for archival backups required by law or internal compliance, and a certification obligation.
• Duration and survival. A defined term plus a survival period that matches the sensitivity of the information.
• Remedies clause. Acknowledgment that breach causes irreparable harm, that injunctive relief is available, and that remedies are cumulative.
• Governing law and dispute resolution. Indian law, a named seat of arbitration or a named court, and a clear statement on jurisdiction. An NDA with no dispute resolution clause is an NDA you will litigate about before you litigate under it.

Common mistakes that weaken an NDA

The most frequent error is format mismatch — using a one-way NDA in a conversation where both parties disclose, then discovering during a dispute that the other side's disclosures were never protected. This is common when a business development team downloads a template without legal review and sends it to a counterparty whose information is equally sensitive.

The second is a definition so broad that it becomes meaningless. Clauses covering "all information relating to the business" invite a challenge that the obligation is unenforceable for uncertainty and, more practically, make it impossible to prove what was actually confidential. Indian courts are more willing to grant relief when the confidential information is identified with specificity, either in the definition or in a schedule listing the documents disclosed.

Third is the missing purpose limitation. A receiver who is told only to "keep information confidential" may still argue that using it to build a competing product was not prohibited. The purpose clause closes that argument.

Fourth is signing after the disclosure. Founders routinely share a pitch deck, a customer list or a pricing sheet before the NDA is executed, then sign a document that covers only future disclosures. Confidentiality obligations cannot operate retrospectively over information already disclosed unless the agreement says so explicitly — and even then, proving the pre-signature disclosure is difficult.

Fifth is ignoring the stamp duty question entirely. An agreement that cannot be produced in evidence without paying deficit duty and penalty is a weak instrument in an urgent injunction application.

Sixth is treating the NDA as a substitute for actual security. An NDA does not stop a determined recipient from copying a database. Access controls, need-to-know permissions and audit logs do more to prevent loss than any clause. The agreement determines what you can do after the loss; it does not prevent the loss.

Frequently asked questions

Is a mutual NDA legally required for a joint venture in India?

No statute requires one, but a joint venture without a confidentiality agreement is unusual because both parties will exchange commercially sensitive material during negotiation and operation. The agreement is a contractual protection rather than a statutory formality. If the joint venture is structured through a company or LLP, confidentiality obligations are often also written into the shareholders' agreement or LLP agreement, and the standalone NDA may be superseded once that document is signed.

Can a one-way NDA be converted into a mutual NDA later?

Yes, by signing an amendment or a fresh mutual agreement. The practical issue is timing: if information was already disclosed under the one-way NDA, the amendment should expressly extend reciprocal obligations to that earlier information, or the parties should sign a new agreement with a clause covering past disclosures. Simply replacing the document without addressing prior disclosures leaves a gap.

Does an NDA need to be stamped in every state where it is used?

Stamp duty is generally payable in the state where the instrument is executed or first received, depending on that state's stamp legislation. An agreement executed in Karnataka and performed in Maharashtra does not normally need to be stamped twice, but the position varies and an agreement that is not stamped in the state where it is tendered in evidence can face an objection. Confirm the requirement in the state of execution before signing.

What happens if the receiver leaks information but the NDA has no indemnity clause?

The discloser can still sue for breach of contract and claim damages that are proved, and can seek an injunction under the Specific Relief Act, 1963. What is missing is a contractual mechanism for quantifying loss and recovering legal costs. In practice, proving the exact loss from a leak is difficult, which is why indemnity and liquidated damages clauses are common even where they are not strictly necessary.

Is a verbal confidentiality promise enforceable in India?

A verbal agreement can be a valid contract if the essential elements are present, but proving its terms is the obstacle. Without a written record of what was defined as confidential, the purpose, and the duration, a claim is difficult to sustain. For any information that matters commercially, put the obligation in writing and keep a copy of what was disclosed and when.

Drafting Support

Our drafting team prepares mutual and one-way NDAs tailored to the direction of disclosure in your specific transaction, with state-appropriate stamping guidance and dispute resolution clauses that hold up. If you are unsure which format fits your conversation, send us the outline of what each side will share and we will advise on the structure before drafting.