How to Draft an NDA in India: Key Clauses, Carve-outs and Enforceability

Pretty much every meaningful business conversation in India eventually runs into a Non-Disclosure Agreement. Founders share product roadmaps with investors. Employers hand financials to senior hires. Vendors exchange source code. Acquirers comb through target company books during diligence. In each of these moments, an NDA is what turns a verbal promise of secrecy into something a court can actually enforce. Legally, the NDA sits inside the Indian Contract Act, 1872, and drafted properly, it converts confidentiality from a handshake into a binding legal obligation. Drafted poorly, and it is simply a document that will not survive the first real dispute.

This guide covers how to draft an NDA in India, including essential clauses, enforceability carve-outs, and how Indian courts assess these agreements when challenged.

The Legal Basis for NDA Enforceability in India

NDAs do not have a distinct, dedicated statute of their own in India and do not require any special government registration to be effective. An NDA’s enforceability flows from the general principles of contract law under the Indian Contract Act, 1872: to be valid, it must have a lawful object, must be supported by lawful consideration, and must be entered into with the free consent of the parties, consistent with Section 10 of the Act.

Indian courts have consistently sustained confidentiality obligations under this general contract law framework, but they examine NDAs closely, looking specifically for provisions that are equivocal, inequitable, or that function as a disguised restraint of trade rather than a genuine confidentiality obligation. Generic NDA templates pulled from the internet rarely survive a genuinely contested dispute, precisely because courts review every concrete element: the underlying facts of the business relationship, each individual provision, and, where relevant, whether the document itself was properly stamped.

The Clauses Every Defensible NDA Needs

A precise, non-vague definition of confidential information

“Everything discussed in this meeting is confidential” sounds protective but is actually weak, because it gives a court very little concrete substance to work with when deciding what was actually supposed to be protected if a dispute arises later. An effective NDA specifies categories of information with enough precision that a court can determine, on the facts, whether a specific piece of disclosed information genuinely falls within the definition: trade secrets, financial data, business strategy documents, client and customer lists, and proprietary source code are commonly named categories rather than left to a single, sweeping, undifferentiated phrase.

Clear identification of the parties and their roles

The agreement should specify who the disclosing party and receiving party are, and where the NDA is mutual (both sides may share confidential information) rather than unilateral (only one side is disclosing), the drafting needs to reflect that structure accurately throughout, rather than using one-directional language in a document intended to bind both parties equally.

The duration of the confidentiality obligation

An NDA needs to state clearly how long the confidentiality obligation lasts, both during the underlying business relationship and, critically, for how long after that relationship ends. Unreasonable durations, whether unreasonably short (undermining the protection’s practical value) or unreasonably long and indefinite (inviting judicial scrutiny as an unfair restraint), are among the most common drafting failures Indian legal practitioners report seeing across hundreds of reviewed NDAs, alongside vague definitions and missing standard boilerplate.

Reasonable steps and treatment as secret

Courts examining an NDA increasingly look for language demonstrating that the disclosing party actually treated the information as secret and took genuine, active steps to protect it. A confidentiality clause that simply labels information as “confidential” without describing any protective measures is generally insufficient on its own; the “reasonable steps” standard is best satisfied through a combination of well-drafted contractual language, actual physical and electronic access controls around the information, and consistent labelling or marking procedures applied in practice, not merely promised on paper.

Exclusions and carve-outs from the definition of confidential information

This is a clause first-time drafters frequently skip, and doing so is a genuine risk to enforceability, not merely an oversight. Standard exclusions typically carve out information that was already known to the receiving party before disclosure, becomes public through no fault of the receiving party, is independently developed by the receiving party without reference to the disclosed confidential information, and is received lawfully from a third party who owed no duty of confidentiality to the original discloser.

Including these specific exclusions, tailored to the actual relationship, reduces the risk of overclaiming, and an NDA that overclaims by treating genuinely non-confidential information as protected tends to weaken the enforceability of the core obligation as a whole, since a court may view the entire definition as unreasonably broad.

Permitted disclosure and consequences of breach

The agreement should specify any circumstances under which disclosure is permitted despite the general confidentiality obligation, such as disclosure required by law or a court order, and should clearly set out the consequences of breach, whether through a specified remedy, a right to injunctive relief, or a liquidated damages provision, so both parties understand what happens if the obligation is violated.

IP assignment where the relationship involves creating new work

Where the NDA governs a relationship involving development work, such as engaging a freelance developer or a vendor building custom code, a clear IP assignment clause matters as much as the confidentiality clause itself. If the receiving party develops something, a code module, a design, a process, using the disclosing party’s trade secrets or confidential information as a foundation, that new work should be explicitly assigned to the disclosing party rather than left ambiguous, since confidentiality alone does not automatically resolve ownership of derivative work product.

Jurisdiction and governing law

The jurisdiction clause should name an Indian court with genuine, practical jurisdiction over the parties and the relationship. Naming a foreign court as the governing jurisdiction forces an additional, often costly enforcement step within India if the NDA is ever breached and needs to be enforced against an Indian party, since a foreign judgment typically requires its own separate recognition and enforcement process under Indian law.

The Trap Most NDAs Fall Into: Section 27 and Restraint of Trade

Under Section 27 of the Indian Contract Act, 1872, any agreement that operates as a restraint on a person’s ability to exercise a lawful trade, profession, or business is void, subject only to a narrow statutory exception for the sale of goodwill. This provision is the single most important legal constraint shaping NDA drafting in India, and it is the ground on which many otherwise well-intentioned NDAs actually fail in court.

Many practitioners draft NDAs that blend post-employment non-compete obligations into what is meant to be a confidentiality agreement, restricting a departing employee’s ability to work in the same field or for a competing employer, framed as though it were simply an extension of confidentiality. This blending is a genuine legal error: courts distinguish sharply between a legitimate obligation not to disclose or misuse specific confidential information (which is enforceable) and a restriction on where or in what field a person can subsequently work (which, as a restraint of trade, is generally void under Section 27, regardless of how the clause is labelled).

Including unenforceable non-compete language inside an NDA does not just fail on that specific clause; it can invite a court to scrutinise the entire document more sceptically as an attempt to disguise a restraint of trade behind confidentiality language.

The practical drafting guidance: keep confidentiality obligations and any separate non-compete or non-solicitation intentions in genuinely distinct provisions, and understand that the non-compete elements, even when kept separate, face their own, considerably higher bar for enforceability in India, particularly once employment has ended.

Types of NDAs Used in India

Unilateral NDA. Only one party discloses confidential information and the other party is bound to protect it, common in vendor, contractor, and investor due diligence contexts where information flows predominantly in one direction.

Mutual NDA. Both parties may disclose confidential information to each other and both are bound by reciprocal obligations, typical in joint venture discussions, M&A negotiations, and partnership evaluations where both sides are sharing sensitive information.

Employee NDA. Governs an employee’s obligation to protect confidential information encountered during employment, and Indian courts examine these particularly closely to rule out clauses that are equivocal, inequitable, or that function as disguised non-compete provisions rather than genuine confidentiality protection. A well-drafted employee NDA is specific to the employee’s actual role and responsibilities, rather than relying on a broad, standard template applied identically across every position in the organisation.

Simplified confidentiality clause within a broader agreement. For short-term, lower-stakes engagements, such as a two-week freelance sprint, a full, lengthy standalone NDA can be genuine overkill and, in practice, often gets signed without being read carefully. A simplified confidentiality clause embedded directly within the underlying service agreement is frequently the more proportionate and, in practice, more effective approach for these shorter, lower-value relationships.

Stamp Duty: A Frequently Overlooked Enforceability Issue

An NDA that is signed but never properly stamped creates a genuine evidentiary problem in India: an insufficiently stamped document faces admissibility restrictions if a dispute later requires the agreement to be produced as evidence in court. Stamp duty rates and requirements vary by state, and enterprises executing NDAs at any volume need a systematic process for ensuring correct stamp duty is applied at the point of execution, rather than discovering the gap only once a dispute has already arisen and the document needs to be relied upon.

Common Drafting Mistakes: How to Draft an NDA in India

Vague, sweeping definitions of confidential information. As covered above, this weakens rather than strengthens protection, since courts need concrete substance to enforce against.

Missing exclusions and carve-outs. An NDA with no carve-outs for public information, prior knowledge, or independent development tends to overclaim, which weakens the enforceability of the entire confidentiality obligation, not just the missing carve-out itself.

Blending non-compete language into confidentiality obligations. This is the Section 27 trap described above, and it is one of the most consistently identified drafting failures across Indian legal practice.

Unreasonable duration terms. Either too short to provide meaningful protection, or indefinite and unreasonably long in a way that invites judicial scrutiny.

Naming a foreign jurisdiction unnecessarily. This creates an avoidable additional enforcement hurdle within India without a corresponding benefit, for NDAs governing genuinely India-based relationships.

Failing to stamp the document correctly. This creates a real admissibility risk that only becomes apparent, often too late to easily fix, once the NDA needs to be produced in a dispute.

Using a one-size-fits-all template regardless of relationship type. A vendor NDA, an investor NDA, and an employee NDA each carry different risk profiles and require different specific provisions; applying an identical generic template across all three misses relationship-specific protections each context actually needs.

Managing NDAs at Enterprise Scale

For enterprises executing NDAs regularly, across vendors, employees, investors, and potential partners, treating each one as an individually drafted, one-off document creates both inconsistency and real operational risk: inconsistent carve-outs across similar relationship types, uneven stamp duty compliance, and no systematic way to track which NDAs are still active, which have expired, and which counterparties are currently bound by an ongoing confidentiality obligation.

Legistify’s contract management platform supports NDA management specifically through a structured clause library covering the standard provisions and India-specific carve-outs described above, automated stamp duty handling at execution, and obligation tracking that flags NDA duration and expiry across the full portfolio, ensuring an enterprise always has visibility into exactly which confidentiality obligations are currently live and with whom.

Conclusion

A well-drafted NDA in India converts a verbal promise of secrecy into a genuinely enforceable legal obligation, but only if it is built around precise definitions, appropriate carve-outs, and a duration that a court would view as reasonable, while carefully avoiding the Section 27 trap of blending confidentiality with an unenforceable restraint of trade. A generic template, downloaded and lightly edited, rarely survives the scrutiny of a genuinely contested dispute, which is precisely why the specific clauses, and the specific exclusions, matter as much as the fact that an NDA exists at all.

Frequently Asked Questions