Non-Disclosure Agreements in India: A Practical B2B Guide — With a Free Template

What an NDA Actually Does — and Doesn't Do

A Non-Disclosure Agreement (NDA), sometimes called a Confidentiality Agreement, is a contract under which one or both parties agree not to disclose or misuse information shared with each other for a defined purpose. In a business-to-business (B2B) context, this is usually the first document signed before two companies start talking seriously — before a pitch deck is shared, before a data room is opened, before a product demo reveals how something actually works.

What an NDA does well: it creates a contractual obligation of confidentiality, defines what counts as "confidential," sets out exceptions, and — critically — gives the disclosing party a basis to seek an injunction or damages if the other side misuses or leaks the information.

What an NDA does not do: it does not stop a determined party from disclosing information if they are prepared to face the legal consequences, it does not protect information that was never properly marked or identified as confidential, and on its own, it does not prevent a counterparty from building a competing product, poaching your staff, or going around you to deal directly with a contact you introduced — those require separate clauses (non-compete, non-solicitation, non-circumvention), which we cover later in this article.

When B2B Businesses Need an NDA

In practice, B2B NDAs in India are signed far more often than most founders and business owners realize is necessary — and far less often than is actually advisable. The most common situations include:

• Vendor and supplier discussions — before sharing pricing structures, production processes, client lists, or technical specifications with a potential supplier or service provider.
• Outsourcing and software development — before handing over source code access, business logic, API documentation, or proprietary datasets to an outsourced development team.
• Investment and fundraising conversations — before sharing a data room, cap table, financial projections, or proprietary technology with a potential investor.
• Mergers, acquisitions, and joint ventures — before due diligence begins, when both parties will see deep operational, financial, and strategic information about the other.
• Distribution, franchise, and channel partner discussions — before disclosing pricing models, territory plans, or trade secrets to a prospective distributor or franchisee.
• Strategic partnerships and pilot projects — before two companies run a trial integration, joint pilot, or co-development exercise.

Mutual vs. Unilateral NDAs — Which Do You Need?

The first structural decision in any NDA is whether it is unilateral (one-way) or mutual (two-way, also called bilateral or reciprocal).

In most B2B exploratory discussions — partnerships, JV talks, vendor onboarding where both sides exchange pricing and process information, investment conversations — a mutual NDA is the more balanced and commonly used structure, and it is the structure used in the free template provided with this article. A unilateral NDA is appropriate only where the information flow is genuinely one-directional.

The Clauses That Actually Matter

Many NDAs circulating in Indian business circles are downloaded templates that "look right" but are missing — or get wrong — the clauses that determine whether the agreement actually protects you when it is tested. Here is what a properly drafted B2B NDA should contain.

1. A Clear Definition of "Confidential Information"

This is the foundation of the entire agreement. A vague definition ("any information shared between the parties") is both over-broad and under-protective — it is unenforceable in practice because it covers everything and nothing. A well-drafted definition specifies the categories of information covered (technical data, business plans, financial information, customer lists, pricing, source code, know-how) and, where appropriate, requires that information be marked as "Confidential" or, if disclosed orally, confirmed in writing within a reasonable period.

2. Carve-Outs — What Is Not Confidential

Every NDA must exclude information that: (a) is or becomes publicly available through no fault of the Receiving Party; (b) was already lawfully in the Receiving Party's possession before disclosure; (c) is independently developed without reference to the Confidential Information; or (d) is rightfully received from a third party without restriction. Without these carve-outs, the agreement technically prohibits the Receiving Party from using information they already legitimately had — which is both unfair and, if challenged, makes the entire confidentiality clause look unreasonable to a court.

3. Defined Purpose and Permitted Use

The NDA should state precisely why the information is being shared (the "Purpose") — for example, "evaluating a potential commercial partnership for distribution of [X] in [territory]." The Receiving Party's obligations should be tied to using the information solely for that Purpose. This single clause is what stops a counterparty from taking information shared for one reason and using it to build a competing offering for an entirely different reason.

4. Term and Survival

Two different timeframes matter here: how long the agreement itself runs (commonly one to three years from signing), and how long the confidentiality obligations survive after the agreement ends or after a specific disclosure is made (commonly two to five years, or — for genuine trade secrets — for as long as the information remains confidential). An NDA that simply says "this Agreement shall remain confidential forever" with no other term is both impractical and, in many circumstances, unenforceable as an unreasonable restraint.

5. Return or Destruction of Information

On termination of discussions, the Receiving Party should be required to return or destroy all Confidential Information (including copies, notes, and — where personal data is involved — data held in any system), and to certify that this has been done on request. This clause has become considerably more important since the Digital Personal Data Protection Act, 2023, where any personal data shared during due diligence or vendor evaluation also triggers data-handling obligations independent of the NDA itself.

6. Remedies — Why an Injunction Clause Matters

Confidential business information is, by its nature, difficult to "un-disclose" — once a trade secret is out, monetary damages rarely make the disclosing party whole. A properly drafted NDA explicitly acknowledges that breach would cause irreparable harm for which damages alone would be an inadequate remedy, and that the disclosing party is entitled to seek injunctive relief (in addition to, not instead of, damages) without being required to prove actual loss as a precondition. This clause does not guarantee an injunction will be granted — that remains a matter for the court — but it materially strengthens the disclosing party's position when seeking one.

7. Governing Law, Jurisdiction, and Dispute Resolution

For a domestic Indian B2B NDA, this is usually straightforward — the laws of India, with courts at a specified city having jurisdiction. For cross-border arrangements (an Indian company and an overseas counterparty), this clause needs careful thought: which country's courts will actually hear a dispute, whether arbitration is preferable to litigation, and — if arbitration is chosen — the seat, rules, and language of arbitration. Getting this wrong does not invalidate the NDA, but it can make enforcement slow, expensive, or practically impossible if a dispute actually arises.

Enforceability in India — What the Law Actually Says

India does not have a standalone "NDA Act." Confidentiality agreements are enforced as ordinary contracts under the Indian Contract Act, 1872, supplemented by the equitable doctrine of breach of confidence, and — where personal data is involved — by the Digital Personal Data Protection Act, 2023. This has a few practical implications worth understanding before you sign or rely on one.

For ordinary confidentiality obligations — "do not disclose or misuse the information we share with you for this Purpose" — Indian courts generally have no difficulty enforcing properly drafted NDAs, and will grant interim injunctions to prevent ongoing or threatened misuse of confidential information where the balance of convenience favours the disclosing party. The areas where enforceability becomes genuinely complicated are restrictions that go beyond confidentiality — non-compete and, to a lesser extent, non-solicitation clauses — which brings us to the next section.

Beyond Confidentiality — Non-Circumvention, Non-Compete & Employee NDAs

"NDA" is often used as a catch-all term in Indian business conversation for several distinct types of restriction, each with different drafting requirements and very different enforceability profiles. Understanding the difference matters — because signing (or relying on) the wrong document for the situation can leave you with no real protection at all.

Non-Circumvention Clauses

A non-circumvention clause prevents a party — typically one acting as an introducer, broker, agent, or sourcing partner — from "cutting out" the other party and dealing directly with a supplier, buyer, manufacturer, or client introduced to them during the relationship. These are extremely common in trading, sourcing, real estate brokerage, and agency arrangements, and are frequently bundled into the same document as confidentiality terms (a combined "NDA and Non-Circumvention Agreement," or "NDNC"). Indian courts generally treat reasonable non-circumvention restrictions — limited in scope, duration, and to specifically identified counterparties or introductions — as enforceable contractual obligations, distinct from the broader restraint-of-trade concerns that apply to non-compete clauses.

Non-Compete Clauses

This is the area where Indian law diverges most sharply from what many business owners expect — especially those familiar with non-compete practice in jurisdictions like the US or UK. Section 27 of the Indian Contract Act, 1872 states that "every agreement by which any one is restrained from exercising a lawful profession, trade or business of any kind, is to that extent void" — subject to a narrow statutory exception for the sale of the goodwill of a business.

In practice, this means:

• A clause preventing an employee or consultant from working in a competing business after their employment or engagement ends is generally unenforceable in India, regardless of how it is worded.
• Restrictions that operate during the term of an employment or service relationship (i.e., not moonlighting for a competitor while still engaged) are generally enforceable, since the person is not yet "restrained" from a trade they are free to pursue once the relationship ends.
• In a genuine business-to-business context — such as the sale of a business along with its goodwill, or restrictions between companies in a joint venture or franchise agreement, reasonably limited in scope, geography, and duration — non-compete style restrictions have a materially better (though still not guaranteed) chance of being upheld, because they fall closer to a reasonable commercial restraint between equal parties rather than a restraint on an individual's livelihood.

Employee, Consultant & Freelancer NDAs

A separate but related need is confidentiality with individuals — employees, consultants, freelance developers, interns, or advisors. These should not simply be the B2B mutual NDA with names swapped in. An employee NDA typically:

• Is unilateral (the individual owes confidentiality to the company, not the reverse) and is often embedded within the employment agreement, offer letter, or a standalone confidentiality and IP assignment undertaking rather than a free-standing "NDA."
• Includes an IP assignment clause — confirming that any work product, code, designs, or inventions created during the engagement belong to the company, which a B2B mutual NDA typically does not need to address.
• Addresses confidentiality obligations after the relationship ends in a way that is realistic and survives the Section 27 limitations on post-termination restraint — focused on protecting genuinely confidential information and trade secrets, rather than attempting a broad post-employment non-compete.
• May include reasonable, narrowly scoped non-solicitation of clients or co-employees post-termination, which Indian courts have shown more willingness to enforce than outright non-competes, provided the scope is reasonable.

If you need confidentiality protection for your workforce — whether full-time employees, contractors, or interns — this should be addressed through your employment documentation and HR policy framework, not by adapting the B2B template provided below.

Common Mistakes That Make an NDA Worthless

Free B2B NDA Template — Download & How to Use It

To help businesses get the basics right, LexWin is making available a free, downloadable Mutual Non-Disclosure Agreement template, designed for B2B use — two companies exploring a commercial relationship, partnership, vendor arrangement, or similar business discussion. It includes a confidentiality framework along with a non-solicitation / anti-poaching clause for key personnel, drafted with Indian law in mind.

Before You Use This Template — Read This

How LexWin Can Help

While this free template is a useful starting point for straightforward B2B confidentiality discussions, every commercial relationship has its own risk profile — the value of the information being shared, the relative bargaining position of the parties, whether the counterparty is based in India or overseas, and what happens if the relationship doesn't work out. LexWin works with businesses across these situations:

Quick Checklist Before You Sign Any NDA

• Is the NDA being signed before any sensitive information is shared — not after?
• Is the "Purpose" of the disclosure clearly and accurately described?
• Is "Confidential Information" defined precisely, with standard carve-outs (public domain, prior possession, independent development, lawful third-party receipt)?
• Is the agreement structured correctly — mutual if both sides are sharing information, unilateral if only one side is?
• Are the term and survival period for confidentiality obligations realistic and clearly stated?
• Does the agreement include a return/destruction of information clause?
• Is there a remedies clause acknowledging the inadequacy of damages and the availability of injunctive relief?
• Is governing law and jurisdiction (or arbitration) clearly specified — especially for cross-border deals?
• Are non-compete elements, if any, scoped narrowly enough to have a realistic chance of enforceability under Section 27 of the Contract Act?
• Is the agreement being signed by someone with actual authority to bind their company?
• Has the stamping position for the relevant state been considered for high-value or high-risk agreements?
• If individuals (employees, consultants, freelancers) are involved, is a separate, appropriately structured confidentiality document being used instead of this B2B template?