Red Flags to Watch for in a Nda (2026)

What to check in an NDA before you sign A non-disclosure agreement (NDA), also called a confidentiality agreement, is meant to do one simple job: let two parties share confidential information for a defined purpose while keeping it private. Most NDAs are routine, but many contain terms that quietly do far more than protect secrets. They can restrict your business, hand over rights to your ideas, or tie you to obligations you can never actually meet. This checklist walks through the red flags to watch for, whether you are the party disclosing information, the party receiving it, or both. Read the NDA against it before you sign. The goal is not to win every point, but to catch the terms that are doing more than confidentiality and to fix the ones that matter. This article is general guidance, not legal advice. NDA enforceability, and limits on restraints such as non-competes, vary by jurisdiction, so have a qualified professional review anything unusual or high-value. ## The red-flag checklist ### 1. The definition of confidential information - Too broad. If everything the other side ever says is "confidential", the obligation is unmanageable and, in some courts, unenforceable. Look for a sensible definition tied to information that is marked confidential or that a reasonable person would treat as confidential.

• No standard exclusions. A fair NDA excludes information that is already public, that you already knew, that you independently developed, or that you rightfully received from someone else. Missing exclusions is a red flag. ### 2. One-way versus mutual - Check whether the NDA is one-way (only one side is bound) or mutual (both are). If you will also share information, a one-way NDA that binds only you is a red flag. Make it mutual, or at least balanced. ### 3. Duration and survival - Perpetual or very long terms. An obligation that lasts forever is hard to manage and, for ordinary business information, often unreasonable. A defined term (for example, obligations lasting a set number of years after disclosure) is normal. Genuine trade secrets may justify a longer or indefinite term, but that should be deliberate, not accidental. ### 4. Purpose and permitted use - The NDA should define the purpose for which information may be used, and let you actually use it for that purpose. A purpose so narrow that it blocks the very discussion you are having, or so vague that it permits anything, is a problem. ### 5. Residuals clause - A residuals clause lets the receiving party use "residual" information retained in its employees' memories. It favours the receiving party and can gut the protection for the disclosing party. If you are disclosing valuable information, treat a residuals clause as a serious red flag. ### 6. Hidden restraints - Non-compete or non-solicit smuggled in. An NDA is not the place for a non-compete or a ban on hiring staff. If one appears, question it; such restraints face strict limits in many jurisdictions and may be void.
• Exclusivity or standstill. Watch for terms that stop you talking to others or dealing in a party's securities. ### 7. Intellectual property - An NDA should not transfer or license your intellectual property. Watch for wording that assigns ownership of ideas, feedback or improvements to the other side. If there is a feedback clause, make sure it does not hand over rights to your core IP. ### 8. Return or destruction of information - A fair NDA requires information to be returned or destroyed on request or at the end. Watch for an obligation that is impossible to meet, for example deleting data that sits in routine backups. Allow a carve-out for backup copies kept securely and for records the law requires you to keep. ### 9. Remedies, liability and damages - Injunctive relief. It is standard for an NDA to allow the disclosing party to seek an injunction. That is usually fair.
• Indemnities and unlimited liability. Watch for a broad indemnity or uncapped liability for any breach, which can turn a minor slip into a large claim. Consider a liability cap.
• Liquidated damages or penalties. A fixed sum payable on breach may be unenforceable if it is really a penalty rather than a genuine estimate of loss. ### 10. Governing law, jurisdiction and assignment - Inconvenient forum. Check which country's law applies and where disputes are heard. A distant or one-sided forum is a red flag for the party that would have to travel to enforce or defend.
• Assignment. Watch for a right for the other side to assign the NDA freely, so your information could end up with a competitor. ### 11. Carve-out for legally required disclosure - You must be able to disclose information when a court, regulator or law requires it. A good NDA permits this, usually with a duty to notify the other side first where lawful. An NDA with no such carve-out puts you in an impossible position. ## A quick two-column checklist | Watch for | What good looks like | |---|---| | "Everything is confidential" | Clear definition plus standard exclusions | | One-way when you also share | Mutual or balanced obligations | | Perpetual term | Defined term, longer only for true trade secrets | | Residuals clause (if you disclose) | No residuals, or tightly limited | | Non-compete or non-solicit inside the NDA | Removed; kept out of a confidentiality agreement | | IP assignment or broad feedback licence | No transfer of your IP | | "Destroy all copies" with no backup carve-out | Return or destroy, with backup and legal-retention carve-outs | | Uncapped liability or broad indemnity | Reasonable liability cap | | Distant or one-sided forum | A forum both sides can live with | | No carve-out for legally required disclosure | Permitted, with notice where lawful | ## Common mistakes to avoid - Signing a one-way NDA when you will also be sharing information.
• Accepting a definition of confidential information with no exclusions.
• Missing a residuals clause when you are the one disclosing valuable information.
• Letting a non-compete or an IP assignment ride along inside a confidentiality agreement.
• Agreeing to destroy all copies when your backups make that impossible.
• Ignoring the governing law and forum until a dispute actually arises. ## A note on jurisdiction NDAs are generally enforceable, but several limits vary by jurisdiction. Restraints of trade, such as non-competes smuggled into an NDA, face strict limits: in India, section 27 of the Indian Contract Act, 1872 makes agreements in restraint of trade void except in narrow cases, and in England and Wales such restraints are enforceable only so far as they protect a legitimate interest and go no further than necessary. Confidential information may also be protected by separate trade-secrets law, which differs by country. In the United States, the Defend Trade Secrets Act gives certain whistleblower immunity, and an NDA is required to include notice of that immunity to preserve some remedies, so a US-facing NDA that lacks it is a red flag. Liquidated-damages and penalty rules also vary. Treat "varies by jurisdiction" as the safe assumption, especially for restraints and for cross-border NDAs, and get local advice. Last verified October 2026. ## Reviewing NDAs faster without missing the red flags The checklist above is enough to review an NDA well. The practical problem is doing it again and again, quickly, across every NDA your business signs, and keeping track of the terms you agreed, the end dates, and the return-or-destroy obligations once the deal is done. That is the idea behind an AI contract workspace: it can open an NDA and show, clause by clause, which terms are favourable, neutral or unfavourable to your company, flag the red flags this checklist describes, let you edit terms in plain language, and keep key dates and obligations in one live view. Tools such as Adira are built around that single-workspace idea, drafting, reviewing and tracking in one place rather than several. This checklist alone is enough to catch the common red flags in an NDA; a workspace simply makes the same review faster and keeps the obligations visible after signing.