Confidentiality Clauses and NDAs Explained (India)

A confidentiality clause, or a standalone NDA, is a promise that information one side shares with the other will not be used or passed on outside an agreed purpose. In India this promise is almost entirely a creature of contract. There is no standalone trade secrets statute here, unlike the US Defend Trade Secrets Act or the EU Trade Secrets Directive. What you have instead is contract law plus an older equitable idea called "breach of confidence," and a practical trap: an unstamped NDA can be thrown out of evidence in an Indian court, no matter how well it is drafted. The one thing most people get wrong: they think signing an NDA is the protection. Signing is only step one. What actually protects you is a tight definition of what counts as confidential, honest carve-outs, and a document stamped correctly enough to be usable if you ever need to enforce it. This guide (published by Adira, which makes contract review and CLM software, so we have a commercial stake in you understanding contracts well, but this explainer stands on its own) walks through what the clause does, what Indian law says, and what to check before you sign or send one.

Plain meaning

A confidentiality clause does three things: defines "Confidential Information" (usually broadly, sometimes so broadly it becomes meaningless), restricts what the receiving party can do with it (no use outside an agreed purpose, no disclosure beyond people who genuinely need it, no reverse engineering in many tech deals), and sets a time limit, or claims not to.

A standalone NDA is the same three ideas in a document of their own, usually signed before a deal is discussed at all, so the exploratory conversation itself, term sheets, financials, roadmaps, is protected even if no deal happens. A confidentiality clause inside a bigger contract does the same job for information exchanged during that contract's life, often for years after it ends. Neither is self-enforcing. An NDA that says "all information exchanged is confidential forever" sounds strong on paper and is often weaker in practice, because it is unworkable to police and courts are wary of enforcing promises that make no commercial sense over time.

Who it protects and what triggers it

The party disclosing sensitive information, a startup pitching an investor, a vendor sharing pricing with a client, an employer briefing a new hire on roadmaps, is the one the clause protects. The trigger is any use or disclosure of the defined "Confidential Information" outside what the clause permits: an employee leaves and takes know-how to a competitor, a party being evaluated for a deal that falls through keeps using what it learned during diligence, or a partner's staff discuss your numbers with people who had no reason to know them. None of these need a formal "leak" to count as breach; using the information for a purpose the clause did not authorise is usually enough.

What to look for

Four mechanics decide whether a confidentiality clause actually holds up when you need it, none visible if you only read the opening promise:

1. How "Confidential Information" is defined. A tight definition (marked confidential, or reasonably understood as such from its nature and context) is usable. An unlimited one ("any information disclosed by either party") is hard to police, because almost nothing falls outside it, which paradoxically weakens the whole clause.
2. What is carved out. A competent clause excludes information already public, already known to the receiving party, independently developed, or later received lawfully from someone else. Missing these, the clause technically covers information the receiving party could never realistically avoid using.
3. The term, and what survives. Does the obligation end with the contract, or survive a stated period, often two to five years, sometimes indefinitely for trade secrets? Silence on survival usually means it dies with the contract, rarely what the disclosing party intended.
4. Compelled disclosure. Can the receiving party disclose when a court or regulator requires it, with a duty to notify the disclosing party first? No such carve-out puts the receiving party in an impossible spot: breach the NDA, or defy a court order.

The Indian position: no standalone statute, contract plus equity

India has no dedicated trade secrets or confidential information statute, unlike the US, UK, or EU. Confidentiality protection here rests on two legs. The first is ordinary contract law: a confidentiality clause or NDA is enforced like any other contractual promise under the Indian Contract Act, 1872, through damages (Sections 73 and 74) or an injunction under the Specific Relief Act, 1963.

The second leg matters even when there is no enforceable contract, or the contract is silent or defective: the equitable doctrine of "breach of confidence." This is not a statute, it is a principle Indian courts inherited from English common law, and it does not depend on a valid contract being in place. As Lord Denning put it in Seager v Copydex, a formulation Indian courts have expressly adopted: the law on this subject "does not depend on any implied contract. It depends on the broad principle of equity that he who has received information in confidence shall not take unfair advantage of it." Practically, this means even a defectively signed NDA, or a relationship where confidential material was shared with no NDA at all, can still support a claim, because equity looks at whether information was received under a stated or obvious limited purpose, not only at whether a contract was validly formed.

A named Indian case: John Richard Brady v Chemical Process Equipments

In John Richard Brady and Others v Chemical Process Equipments P. Ltd. and Another (Delhi High Court, AIR 1987 Delhi 372), the plaintiffs had shared confidential drawings, know-how and specifications for a Fodder Production Unit with the defendants, entrusted for a limited purpose. The defendants used that information, and access gained to the plaintiffs' facility, as what the court called a "spring-board" to build and sell their own competing machines.

The Delhi High Court restrained the defendants, applying the equitable breach-of-confidence principle from the English case Saltman Engineering v Campbell Engineering and expressly endorsing Lord Denning's formulation that confidentiality protection does not depend on an implied contract. The full judgment is on Indian Kanoon. Why this matters: even where your NDA turns out poorly drafted, unsigned by the right person, or arguably not a binding contract at all, Indian courts have been willing to restrain misuse of confidential information on equitable grounds alone, if you can show it was shared for a limited, understood purpose and then misused. This is a real backstop, but harder to win than a straightforward contract claim, and it depends heavily on the facts.

The stamping trap: Section 35, Indian Stamp Act, 1899

Almost nobody checks this, and it can quietly gut an otherwise well-drafted NDA. Under Section 35 of the Indian Stamp Act, 1899:

"No instrument chargeable with duty shall be admitted in evidence for any purpose by any person having by law or consent of parties authority to receive evidence... or shall be acted upon, registered or authenticated by any such person or by any public officer, unless such instrument is duly stamped." Source: Section 35, Indian Stamp Act, 1899

Plainly: if a document requires stamp duty (a state subject, so rates and coverage for NDAs vary by state) and it was not stamped, or under-stamped, a court can refuse to admit it as evidence at all, until the deficient duty and a penalty are paid. You are not permanently barred; Section 35's proviso lets you cure the defect by paying up at the time you try to rely on the document. But that means the delay and penalty land exactly when you can least afford them, mid-dispute, while trying to get an urgent injunction against someone misusing your confidential information. The fix is cheap: confirm the correct stamp duty for the state of execution, and get it stamped properly at signing, not after a dispute starts.

Red flags

Normal	Red flag	Why it matters
Obligation survives a stated period after termination, commonly 2-5 years	No survival clause, or silence on what happens after termination	May be read as ending with the contract, leaving shared information unprotected right when a relationship sours
Clear carve-outs: public domain, independently developed, already known, lawfully received from a third party	No carve-outs at all	Turns an ordinary business relationship into a technical breach risk, since almost nothing avoids overlapping with public or prior knowledge
Reasonable, time-bound confidentiality matched to what is genuinely sensitive	Perpetual confidentiality applied to everything disclosed, no distinction by sensitivity	Unworkable and often unenforceable in spirit; also makes it hard to safely hire from or work with anyone else in the sector
A residuals clause for information in employees' unaided memory	No residuals clause at all	Ordinary professional experience can technically be read as a breach the moment someone changes jobs
Compelled-disclosure carve-out, with notice to the other party first	No compelled-disclosure exception	Direct conflict between an NDA and a court or regulator's order, with no lawful way out
Confidentiality tied to a legitimate purpose (trade secrets, client data, deal terms)	Used broadly to stop an employee discussing working conditions, pay, or wrongdoing witnessed	A red flag on intent, not just drafting, and increasingly scrutinised
Document properly stamped for the state of execution, at signing	Stamping never checked, or a token unstamped "quick NDA"	Inadmissible in evidence under Section 35 of the Stamp Act until cured, exactly when you need it fastest

Bad clause → better clause

Bad: "All information disclosed by either party shall be kept strictly confidential by the receiving party forever and shall not be disclosed to any person under any circumstances."

What is wrong: no definition of what counts as confidential, no carve-outs, no compelled-disclosure exception, and an unworkable "forever, no circumstances" promise a court is unlikely to enforce literally.

Better: "'Confidential Information' means information disclosed by one party (Discloser) to the other (Recipient) that is marked confidential, or that a reasonable person would understand to be confidential given its nature and the circumstances of disclosure. It does not include information that (a) is or becomes public through no fault of Recipient, (b) was already lawfully known to Recipient, (c) is independently developed without reference to Discloser's Confidential Information, or (d) is lawfully received from a third party without an obligation of confidentiality. Recipient shall use it only for the Permitted Purpose and disclose it only to those who need to know it and are bound by confidentiality obligations at least as protective as this clause. Recipient may disclose it if legally compelled, provided it gives Discloser prompt written notice, where lawfully possible, to allow Discloser to seek a protective order. These obligations survive for 3 years after termination, except for information that qualifies as a trade secret, for which they survive as long as the information remains secret."

What changed and why: the definition is objective and checkable, the four standard carve-outs are present, there is a working compelled-disclosure exception, and the survival period is stated explicitly instead of left open to argument.

How it interacts with related clauses

Confidentiality does not sit in isolation. Three clauses shape how much it actually protects you:

• IP assignment and ownership. A confidentiality clause stops misuse of information; it does not decide who owns work product created using it. If technical know-how feeds into new inventions or code, check the IP assignment clause separately.
• Indemnity and limitation of liability. If a breach causes real financial loss, whether and how much you can recover depends on whether confidentiality breaches are carved out of the liability cap or covered by a specific indemnity. Teeth in the clause but no matching indemnity can mean a technical win and a capped, disappointing recovery.
• Non-compete and non-solicit. Often confused with confidentiality, but a different job. Confidentiality restricts use of specific information; a non-compete restricts working for a competitor at all, and is treated far more skeptically under Indian law (Section 27 of the Contract Act voids most non-competes after employment ends). A strong confidentiality clause does not also give you an enforceable non-compete.

You can mark up how these clauses interact directly in a document, for free, using Weave, which lets you flag and comment on clauses like this before you send a contract back for negotiation.

US and global contrast

The US has the Defend Trade Secrets Act, 2016, a federal statute giving trade secret owners a direct federal cause of action, alongside state-level statutes (most states have adopted a version of the Uniform Trade Secrets Act) that exist independently of any contract. So in the US, even with no NDA at all, misappropriating a genuine trade secret can be pursued as a distinct statutory claim, with remedies that in some cases include exemplary damages and attorney's fees. India has nothing equivalent. Protection here has to come from the contract itself, or from the older, harder-to-predict equitable route through breach of confidence. Do not assume Indian confidentiality protection matches US "trade secret" protection in strength or predictability. Draft the NDA carefully in India; you cannot fall back on a statute the way you might in Delaware or California.

FAQ

Does India have a trade secrets law like the US? No. India has no standalone trade secrets statute. Protection comes from contract law (the confidentiality clause or NDA, enforced under the Indian Contract Act and Specific Relief Act) and from the equitable common-law doctrine of breach of confidence, which courts apply even where a contract is weak or absent, as in John Richard Brady v Chemical Process Equipments (Delhi HC, AIR 1987 Delhi 372).

Can I enforce an NDA that turns out to be technically invalid or unsigned by the right person? Possibly, through the equitable breach-of-confidence route rather than a straight contract claim. Following the principle in John Richard Brady, Indian courts have restrained misuse of confidential information on equitable grounds where it was shared for a clear, limited purpose, even without a fully valid contract. This is a real but harder-to-win backstop, and it depends heavily on the specific facts.

What happens if my NDA was never stamped? Under Section 35 of the Indian Stamp Act, 1899, an unstamped or under-stamped document that requires duty can be refused as evidence in any Indian court, for any purpose, until the deficient duty and any penalty are paid. It is usually curable by paying up at the time you seek to rely on it, but that delay and cost typically hit at the worst possible moment, mid-dispute.

Should confidentiality obligations really last forever? Rarely, and drafting it that way is a red flag, not a strength. Most clauses state a survival period, commonly 2 to 5 years after the contract ends, with an exception for genuine trade secrets, which may need to survive as long as the information stays secret. A blanket "forever" clause applied to everything disclosed is often unenforceable in spirit.

What is a residuals clause and why does it matter? It permits the receiving party to use general knowledge and know-how retained in employees' unaided memory, so ordinary career mobility is not read as a technical breach every time someone who worked on a project later works elsewhere in the industry. Its absence is a common red flag in employment and consulting NDAs.

Can a company use confidentiality clauses to stop employees discussing pay or reporting wrongdoing? That is a red flag use of confidentiality, not its intended purpose. It is meant to protect genuinely sensitive business information, not to silence employees on working conditions, compensation, or good-faith reports of wrongdoing. Courts and regulators increasingly scrutinise clauses drafted or used that way.

This guide gets you to understanding what a confidentiality clause or NDA does under Indian law, and what to check before you sign or rely on one. It does not tell you whether a specific clause is enforceable, adequately stamped for your state, or advisable for your situation, that depends on facts and jurisdiction, and is not legal advice. Talk to a lawyer before you rely on, or walk away from, a confidentiality obligation in a live negotiation or dispute.