NDA vs Non-Compete: What Indian Startups Actually Need (and What Doesn't Hold Up in Court)

A non-compete clause that tries to stop you from joining a competitor after you resign is very likely unenforceable in India, since Section 27 of the Indian Contract Act, 1872 voids agreements restraining a lawful profession or trade. What actually holds up instead is a confidentiality clause covering trade secrets and client data, plus a reasonably scoped non-solicitation clause.

Why This Confusion Costs Founders Real Money

Every startup founder has, at some point, copy-pasted an NDA template from the internet and slipped in a clause that says something like: "Employee shall not join a competing business for 12 months after leaving." It feels like standard practice. It is standard practice, in the United States. In India, that clause is very likely worthless the moment someone challenges it in court.

Understanding the difference between what protects your startup and what just looks like protection is one of the most practical legal lessons a founder can learn early.

The Law: Section 27 Says No to Post-Employment Non-Competes

Section 27 of the Indian Contract Act, 1872 states that "every agreement by which anyone is restrained from exercising a lawful profession, trade or business of any kind, is to that extent void." Indian courts have consistently read this to mean that once an employee leaves your company, you cannot legally stop them from joining a competitor, starting a rival business, or using the general skills and knowledge they built while working with you.

This is a deliberate policy choice. Indian law prioritises a person's right to earn a livelihood over a former employer's discomfort with competition. Courts have upheld this position repeatedly over the decades, including in cases involving IT companies, sales teams, and senior executives.

There is one narrow, well-established exception: reasonable restrictions during the employment period itself (not after it ends) are generally enforceable, since the person is still bound by their contract while employed.

So Why Do NDAs Still Work?

NDAs and non-compete clauses get lumped together in founder conversations, but they are legally very different animals.

A non-compete tries to stop someone from working somewhere. Courts largely reject this after employment ends.

An NDA (confidentiality clause) tries to stop someone from using or disclosing specific confidential information, your customer lists, source code, pricing strategy, product roadmap, or trade secrets. Courts routinely enforce this, even after the person has left, because protecting confidential business information is not the same as restraining someone's right to work. The person can join a competitor; they just cannot take your trade secrets with them.

This is the single most important distinction for Indian founders to internalise.

What Founders Should Actually Rely On

Instead of pouring energy into a non-compete clause that likely won't survive a court challenge, structure your agreements around what does hold up:

Strong confidentiality clauses. Be specific about what counts as confidential: client data, technical documentation, unreleased features, financial terms, rather than using vague, catch-all language.

Non-solicitation clauses, reasonably scoped. You generally cannot stop a former employee from working for a competitor, but courts have shown more willingness to enforce narrowly drafted clauses that prevent someone from actively poaching your specific clients or specific colleagues for a limited period after they leave. Reasonableness in scope, geography, and duration matters a great deal here.

IP assignment clauses. Make sure your contracts clearly state that any code, designs, content, or inventions created during someone's employment or engagement belong to the company, not the individual. This is one of the most commonly missed clauses in early-stage startup contracts, and it becomes a serious problem during fundraising due diligence or if a co-founder exits.

Employment-period restrictions, if you need them, are on firmer ground than post-employment ones, but even these should be reasonable and specific.

The Practical Takeaway

Don't waste founder time and legal budget drafting an aggressive non-compete that a court will strike down in one hearing. Put that effort into airtight confidentiality language, sensible non-solicitation terms, and clean IP assignment. That's what actually protects a startup when a co-founder, engineer, or early employee walks out the door.

Is a Non-Compete Clause Valid in India After You Resign?

If you are the one resigning, and your employment contract has a clause saying you cannot join a competitor or start a similar business for some period after you leave, the short answer is that clause is very likely unenforceable in India. Section 27 of the Indian Contract Act, 1872 voids any agreement that restrains a person from exercising a lawful profession, trade, or business, and Indian courts have consistently applied this to strike down post-employment non-compete clauses. Once you have resigned, you are free to join a competitor or start your own venture.

What can still bind you after you leave is different from a non-compete: a confidentiality clause preventing you from using or disclosing your former employer's trade secrets or client data, and a reasonably scoped non-solicitation clause stopping you from actively poaching former colleagues or clients for a limited period. Neither of these stops you from working wherever you want; they only restrict what you take with you and who you actively solicit.

Every business has different risk exposure depending on sector, team structure, and what's genuinely at stake if information walks out with an employee. Vaksy can connect you with a verified advocate on the Vaksy platform who can review your specific employment agreements and NDAs, and draft them in your own language, so your contracts hold up when you actually need them to.

Talk to a Vaksy advocate →

New here? See how talking to a lawyer on Vaksy works →