A Non-Disclosure Agreement, or NDA, is one of the most commonly signed documents in Indian business today. Start-ups sign them before pitching investors, employees sign them on their first day of work, and vendors sign them before a project kicks off. Yet very few people actually read what is inside these documents, and even fewer understand what makes an NDA hold up in an Indian court versus what makes it a piece of paper with no real teeth.

This article breaks down the Indian legal position on NDAs, the clauses that actually matter, and the common mistakes that can make an otherwise well-intentioned agreement unenforceable.

Is an NDA even a valid contract in India?

There is no standalone law called "the NDA Act" in India. An NDA is simply a contract, and like any other contract, it is governed by the Indian Contract Act, 1872. For it to be enforceable, it must satisfy the basic requirements under Section 10 of the Act: a lawful offer and acceptance, free consent of both parties, lawful consideration, and a lawful object. It must also satisfy the requirement of competent parties.

In practice, this means an NDA cannot be used to hide something illegal, and it cannot be signed under coercion, undue influence, or misrepresentation. Beyond that, courts have generally been willing to enforce confidentiality obligations, as long as they are drafted reasonably.

Section 27 and why "confidentiality" is not the same as "non-compete"

This is probably the single most misunderstood part of NDA drafting in India, and it is worth spending real time on. Section 27 of the Indian Contract Act states that every agreement by which anyone is restrained from exercising a lawful profession, trade, or business of any kind is void to that extent. This means any clause that tries to stop a former employee or contractor from working in the same industry after the relationship ends is very likely to be struck down by a court, no matter how it is worded.

A broad non-compete clause covering the same period as an employment agreement is very likely not to be enforced under Section 27. However, this is where a lot of people get confused. A pure confidentiality clause, one that only stops a person from disclosing or misusing specific confidential information, is a different animal altogether. Indian courts have consistently held that while non-compete clauses after employment usually fail, confidentiality clauses remain valid and enforceable.

So, the practical lesson for anyone drafting or reviewing an NDA in India is this: keep the agreement focused on protecting information, not on restraining someone's right to earn a living. The moment an NDA starts reading like a non-compete in disguise (for example, "the receiving party shall not work with any competitor for two years"), it risks being void in its entirety or at least in that clause.

What every NDA should include

1. A clear definition of confidential information

The definition of confidential information should clearly outline what constitutes confidential information to avoid ambiguity. Vague phrases like "any information shared during the discussion" are a common drafting mistake. It is far more effective to give categories and examples: financial data, source code, customer lists, pricing models, business strategy documents, and so on. Ambiguity in contractual terms is the primary obstacle to enforcement, since vague language creates disputes over what the parties actually intended.

2. Identification of parties

Every NDA needs to clearly state who the disclosing party is and who the receiving party is, including full legal names and addresses. If more than two parties are involved, such as a start-up, an investor, and a due diligence consultant, each one should be listed individually rather than referred to loosely.

3. Obligations of the receiving party

Spell out exactly what the receiving party can and cannot do with the information. Can they share it with their own employees on a need-to-know basis? Can they use it to build a competing product? Can they retain copies after the engagement ends? Leaving this section thin is one of the most common reasons NDAs fail to protect anyone in practice.

4. Exclusions from confidentiality

This is a clause that many first-time founders skip, but it is essential for enforceability. Any information that becomes public through no fault of the receiving party should be carved out and excluded from the definition of confidential information. Standard exclusions typically cover information that:

- was already known to the receiving party before disclosure

- becomes public through no fault of the receiving party

- is independently developed without reference to the confidential information

- is received lawfully from a third party who owed no duty of confidentiality

Skipping this clause is a real risk. Without it, the agreement can look one sided and unreasonable, which weakens its standing if a dispute lands in court.

5. Duration of the obligation

An NDA should state clearly how long the confidentiality obligation lasts, both during the relationship and after it ends. A perpetual obligation for ordinary business information is often viewed as excessive, though longer or indefinite terms are more defensible for genuine trade secrets. A reasonable term, often two to five years post termination depending on the nature of the information, tends to hold up better than an open ended one.

 6. Consequences of breach and remedies

The agreement should spell out what happens if it is breached, including the disclosing party's right to seek an injunction to stop further disclosure, and the right to claim damages. Indian courts can and do grant injunctions in confidentiality disputes where monetary compensation alone would not undo the harm of a leak.

On the question of damages, there is a useful drafting distinction. Under Section 74 of the Contract Act, if a specific penalty figure is written into the NDA, courts will only award it if it reflects a genuine, reasonable estimate of likely loss, not an arbitrary number meant to scare the other party. For this reason, many lawyers prefer to leave damages unliquidated (that is, not pre-fixed) and instead rely on the court's assessment based on actual loss, combined with a separate injunction clause.

7. Governing law and jurisdiction

This matters more than people assume, particularly for start-ups dealing with overseas investors or vendors. The NDA should specify that it is governed by Indian law and name a specific city's courts as having exclusive jurisdiction. Without this, a dispute can turn into a costly argument about which country's courts even have the authority to hear the case, before the actual confidentiality issue is ever addressed.

8. Indemnification

Particularly relevant where the receiving party's own employees, contractors, or affiliates might come into contact with the confidential information, an indemnification clause protects the disclosing party against third party claims that arise from a breach caused by the receiving party's side.

9. Return or destruction of information

The NDA should require the receiving party to return or destroy all confidential material, including copies, notes, and any digital records, once the relationship ends or upon request. In practice, many agreements also ask for written confirmation once this is done.

Registration and stamping: a step people often skip

An NDA does not need to be registered under the Registration Act, 1908, and notarisation is not a legal requirement either, though many parties still do it as a matter of practice.

Stamping is a separate issue, and it is one of the most commonly overlooked steps. An unstamped NDA is still a valid contract, but it is not admissible as evidence until the stamp duty, along with any penalty, has been paid. Section 35 of the Indian Stamp Act, 1899 places a duty on courts and officers to impound instruments that are not duly stamped when they are produced as evidence. If the duty was not paid on time, the shortfall can still be cured later, but the penalty for insufficient stamping can go up to ten times the deficient duty.

Stamp duty rates and rules differ by state, since states like Maharashtra, Gujarat, Karnataka, Kerala, and Rajasthan have their own separate Stamp Acts, while several other states continue to follow the central Indian Stamp Act, 1899. The practical takeaway is simple: stamp the NDA at the time of signing rather than waiting until a dispute forces the issue, since curing the defect later costs more in penalty and in time.

Electronic NDAs are not left out of this either. Under Section 10A of the Information Technology Act, 2000, electronic contracts and digital signatures are legally recognised and enforceable in India. Stamp duty still needs to be accounted for separately, and some states, such as Maharashtra, have specifically extended their stamp law definitions to cover electronic records.

What to avoid when drafting or signing an NDA

Avoid disguising a non-compete as a confidentiality clause. As covered above, this is the single biggest legal risk. If a clause effectively stops someone from working in their field, expect it to be challenged and likely struck down under Section 27.

 Avoid vague, catch all definitions of confidential information. "Everything discussed in this meeting is confidential" sounds protective but is actually weak, because it gives a court very little to work with when deciding what was actually supposed to be protected.

Avoid one sided drafting with no exclusions. An NDA with no carve outs for public information, prior knowledge, or independent development tends to look unreasonable to a court and can weaken the disclosing party's position rather than strengthen it.

Avoid unrealistic, indefinite durations for ordinary information. A confidentiality obligation that never ends, applied to routine business information rather than genuine trade secrets, can invite judicial scrutiny.

Avoid skipping the jurisdiction clause in cross-border NDAs. This is especially relevant for Indian start-ups signing NDAs with foreign investors or clients. Leaving this blank, or naming a foreign court by default, can make enforcement in India slower and more expensive.

Avoid copy pasted templates without adapting them to the actual relationship. A template built for a vendor NDA rarely fits an employment relationship, and a one-way NDA (only one party discloses information) is a very different document from a mutual NDA (both parties share confidential information with each other). Using the wrong structure is a common and avoidable mistake.

Avoid leaving the NDA unstamped. Given how inexpensive stamping usually is compared to the cost of an unenforceable dispute later, this is a step that should never be skipped, particularly for high-value business relationships.

Avoid ignoring data protection obligations where personal data is involved. If the confidential information includes personal data of individuals, such as customer or employee data, the NDA should be consistent with India's data protection framework rather than treating confidentiality and data protection as separate, unrelated concerns.

A quick word on unilateral vs mutual NDAs

Before drafting, it helps to be clear on which type of NDA the situation calls for:

- Unilateral NDA: Only one party is disclosing confidential information, such as an employer sharing proprietary processes with a new employee, or a company sharing a business plan with a potential investor.

- Mutual NDA: Both parties are disclosing and receiving confidential information, common in joint ventures, partnership discussions, or two companies exploring a merger.

- Multilateral NDA: More than two parties are involved, and each party's obligations toward every other party need to be spelled out individually rather than assumed.

Picking the wrong structure at the outset often leads to one sided drafting later, which is why this decision should be made before the clauses are even written.

The bottom line

An NDA in India does not need to be twenty pages long to be effective, but it does need to be precise. The agreements that hold up in practice are the ones with a clear definition of confidential information, reasonable and specific obligations, sensible exclusions, a defined duration, a proper governing law and jurisdiction clause, and correct stamping. The ones that fail tend to share the same flaws: vague language, disguised non-compete clauses, missing exclusions, and a template that was never actually adapted to the relationship it was meant to protect.

Given how much rides on the wording, it is always worth having an NDA reviewed by a lawyer familiar with Indian contract law before it is signed, particularly where high-value trade secrets, cross-border parties, or long-term relationships are involved.

This article is for general informational purposes and does not constitute legal advice. For a specific transaction or dispute, please consult a qualified advocate.