An NDA isn’t a magic spell. It’s a contract, and like every contract, it’s only as strong as the clarity of its terms and the will to enforce it.
What an NDA actually does
It creates a contractual obligation of confidentiality, defines what counts as “confidential information,” and gives you a civil remedy (damages, injunction) when the other party leaks.
What it doesn’t do
- Doesn’t prevent independent invention.
- Doesn’t cover information that was already public, independently developed, or properly received from a third party.
- Doesn’t override a court subpoena or statutory disclosure.
- Doesn’t criminalise a breach — it’s civil law, not criminal.
The five terms that matter most
- Definition of confidential information: overly narrow definitions miss what you actually want protected; overly broad ones may be unenforceable.
- Permitted use: the receiver can use the info only for the specific purpose stated.
- Term: 2–5 years for ordinary trade secrets; perpetual for things like algorithms or customer lists.
- Return / destruction: what happens to the materials at the end of the engagement.
- Remedies clause: injunction without proof of irreparable harm (very useful in India where damages are hard to quantify).
Mutual vs. one-way
Default to mutual (both parties bound) when both sides will share confidential information. One-way (only the receiver is bound) is appropriate for things like investor pitches.
When to involve a lawyer
Always for any NDA involving IP, source code, or customer data. For routine vendor NDAs — a well-vetted template is fine, but have a lawyer review it before you use it the first time.