Is an NDA Enforceable? When Confidentiality Agreements Hold Up (2026)

Is an NDA enforceable? Yes. A non-disclosure agreement (NDA), also called a confidentiality agreement, is usually enforceable, provided it is a valid contract and its restrictions are reasonable. An NDA is a promise not to use or disclose specific information, and courts across common-law systems enforce that promise through injunctions and damages when it is breached. What decides enforceability is not whether it is called an NDA, but whether it meets the ordinary requirements of a contract and whether its scope is reasonable rather than oppressive. In India, an NDA is a contract under the Indian Contract Act, 1872. To be valid it needs the usual ingredients: offer and acceptance, lawful consideration, free consent and a lawful object. A confidentiality obligation is generally treated as enforceable because it restricts the use of information, not a person's right to work, which keeps it clear of the restraint-of-trade problem that sinks many non-compete clauses. This article is general guidance, not legal advice. Enforceability turns on exact wording and on local law, which varies by jurisdiction, so have a qualified professional review an NDA before you rely on it. ## What makes an NDA hold up An NDA is most likely to be enforced when it has these features: - It is a valid contract. There is clear agreement, consideration (which can be the exchange of information itself or the deal it supports), and parties competent to contract.

• "Confidential information" is defined, not boundless. The agreement identifies what is protected rather than trying to cover everything the recipient ever learns. A workable definition lists categories and often requires written material to be marked confidential.
• There are sensible carve-outs. Standard exclusions are information that is already public, already known to the recipient, independently developed, or required to be disclosed by law or a court. Courts expect these; their absence can make a clause look overbroad.
• The purpose and duration are reasonable. The recipient may use the information only for the agreed purpose, and the obligation lasts a defined, reasonable period (often two to five years, sometimes indefinitely for genuine trade secrets).
• Obligations are clear. The recipient must protect the information, limit who sees it, and return or destroy it when the deal ends. ## What makes a court cut an NDA down - It is really a disguised non-compete. If a confidentiality clause is so broad that it stops a person from working or earning a living, courts may refuse to enforce it. In India this is the Section 27 problem: Section 27 of the Indian Contract Act, 1872, voids agreements in restraint of a lawful trade, business or profession. A genuine confidentiality obligation is not a restraint of trade, but one drafted to function as a lifelong bar on using ordinary skill and knowledge can be struck down.
• The scope is oppressive. An indefinite ban on using information that is really general know-how, with no carve-outs, looks punitive and is vulnerable.
• The information is not actually confidential. You cannot protect what is already public or was never secret.
• It is unsigned or vague. Missing signatures, no definition of confidential information, or no term can all undermine it. ## Confidentiality vs non-compete: the key distinction This distinction is the heart of NDA enforceability. A confidentiality clause restricts what someone may do with specific information; it does not stop them working for a competitor. A non-compete restricts the activity itself. Indian courts generally enforce reasonable confidentiality obligations but are sceptical of post-employment non-competes, treating them as void under Section 27 unless narrowly justified. The Supreme Court is commonly cited (for example Niranjan Shankar Golikari v Century Spinning) for upholding in-service restraints and confidentiality while being wary of restraints that bite after employment ends. If you want protection that survives, frame it as confidentiality and trade-secret protection, not as a bar on working. ## Enforcing an NDA in practice - Injunction first. Because money rarely undoes a leak, the usual first remedy is a court order stopping further use or disclosure.
• Damages. Proven loss from a breach can be recovered; agreed (liquidated) damages may help if they are a genuine pre-estimate of loss, not a penalty.
• Evidence matters. You have to show what was confidential, that it was shared under the NDA, and that the recipient used or disclosed it. Marking material confidential and keeping access logs helps. ## A note on jurisdiction NDAs are enforceable across the UK, Ireland, Singapore, Australia, the US and India, but the detail differs. The Section 27 restraint-of-trade analysis above is India-specific. In the US, enforceability interacts with state trade-secret and non-compete law, and some states now restrict non-competes heavily. In the UK and others, confidentiality can also be protected by the equitable duty of confidence even without a contract. Cross-border NDAs should state a governing law and forum. Treat "varies by jurisdiction" as the default. Last verified October 2026. ## Keeping confidentiality obligations alive after signing An NDA is only as good as the discipline behind it. The enforceable version has a defined term, defined carve-outs, return-or-destroy duties and a date when the obligation ends, and those details have to be tracked across every counterparty you sign with. A company that signs dozens of NDAs quickly loses sight of which are mutual, which expire when, and which carry obligations it is quietly breaching. Drafting an NDA, reviewing its confidentiality and term clauses, tracking the carve-outs and expiry dates, and governing a stack of them can all live in one AI workspace tuned to how your company shares information, which can flag unusual or oppressive wording before you sign. Adira is one example of such a workspace. This guide is enough to judge whether a single NDA will hold up; one workspace simply makes managing many of them a connected job.