NDA Analyzer — the five clauses that hide in every non-disclosure agreement
Non-disclosure agreements are signed faster than almost any other legal document. A vendor sends one before the first meeting, an investor sends one before the first pitch, an employee signs one on day one — sometimes after a 30-second skim. The friction with that pattern is that NDAs frequently contain clauses that have nothing to do with non-disclosure: embedded non-competes, IP assignment, exclusive jurisdiction in distant cities, even employment-style restrictions. Here is what the NDA analyzer surfaces, the five most common hidden clauses, and the redline approach that lets a non-lawyer push back confidently.
What the analyzer actually checks
The tool reads the full NDA text, then runs an AI audit pass that compares each clause against a checklist of NDA best-practices and known trap clauses. Output is a risk-flagged clause-by-clause analysis: each finding includes a severity rating (high / medium / low), the verbatim quote of the offending text, an explanation of why it's flagged, and a suggested redline. Plus a missing-clauses section that surfaces standard NDA carveouts (residual knowledge, publicly-known information, government-required disclosure) that should be present but aren't.
The output is structured for action. You can take the redlines directly into a negotiation with the counterparty, or pass them to your lawyer for review. The verbatim quotes mean you can verify every flag — the AI isn't asking you to trust its summary; it's pointing at the actual text in the document.
Five clauses that hide in every NDA
The patterns the analyzer catches most often:
- Embedded non-competes. An NDA shouldn't restrict where you work next. Many do, with 12-24 month post-engagement non-competes buried in the obligations section. In India specifically, Section 27 of the Indian Contract Act makes most post-employment non-competes unenforceable, but having them in writing still chills you. Always flagged high-severity.
- IP assignment. An NDA shouldn't include IP assignment language (that belongs in an employment / consulting / IP agreement). When found in NDAs, it often gives the counterparty rights to derivatives and improvements — much broader than the disclosure context warrants. Common in founder-investor NDAs as a hidden trap. High severity.
- Mutual vs unilateral mismatch. Mutual NDAs protect both parties' confidential information; unilateral NDAs only protect one side. The analyzer surfaces which direction the document actually flows. Surprisingly often, a document labeled 'Mutual NDA' has unilateral restrictions buried in the substantive clauses.
- Missing standard carveouts. Every reasonable NDA carves out: information already publicly known, information independently developed, information required to be disclosed by law, residual knowledge in the recipient's head. Carveouts left out turn an NDA into a perpetual gag. The analyzer flags each missing carveout explicitly.
- Exclusive jurisdiction in distant cities. An NDA between two parties based in Bangalore shouldn't have exclusive jurisdiction in Delhi or Mumbai (let alone Singapore or Delaware). Distant-jurisdiction clauses make any dispute economically prohibitive — usually the point. Flagged medium-severity with context.
The redline approach for non-lawyers
Each flag in the output comes with a suggested replacement that a non-lawyer can confidently propose to the counterparty:
- Quote what's flagged. 'I noticed this clause: [verbatim quote]. This typically belongs in an employment agreement, not an NDA. Could we remove it from the NDA and address IP separately if needed later?'
- Suggest the replacement. 'I'd propose: [replacement language from the analyzer's output].' Pre-built language is much easier to push than vague objections.
- Reference the standard. 'Standard NDAs typically include carveouts for [list]. Could we add those?' Naming the omitted carveouts directly shifts the conversation from 'you're being difficult' to 'we're aligning to standard practice.'
When to use this tool vs go straight to a lawyer
Three signals that the analyzer is sufficient:
- Low-stakes mutual NDA between equal counterparties. Vendor-prospect, founder-advisor, exploratory partnership talks. The analyzer's audit usually suffices.
- Standard form NDA from a Fortune 500. Big-company NDAs are usually variations on a well-known template. The analyzer's pattern-match catches deviations.
- Pre-meeting NDA before a first conversation. Often signed to enable a 30-minute discovery call. The analyzer's 15-credit cost is dramatically cheaper than a lawyer's review for routine documents.
When you should escalate to counsel
Three signals that suggest a lawyer is worth the cost:
- M&A or acquisition discussions. Pre-deal NDAs often carry standstill provisions, no-shop language, or specific-performance remedies that should be vetted by deal counsel.
- Large vendor or supply-chain relationships. NDAs governing relationships worth significant revenue should be reviewed in the context of the broader commercial deal — a lawyer doing both at once finds inconsistencies the analyzer alone cannot.
- IP licensing context. If the NDA is the first step in an IP licensing discussion, the IP assignment + non-compete provisions deserve careful expert review.
Limits and pricing
NDA Analyzer charges 15 credits per analysis. The tool handles PDFs up to 25 MB. Processing runs on our servers; the document is in memory only during analysis and is never persisted. Output is the structured risk-flag list plus suggested redlines.
Important: This is not legal advice. The tool is an audit aid. For NDAs in any of the three escalation categories above, consult an employment / commercial / IP lawyer as appropriate.