The Key Clauses in a Non Disclosure Agreement, Explained

What are the key clauses in an NDA? A non-disclosure agreement (NDA), also called a confidentiality agreement, is built from about ten clauses. A few of them carry almost all the risk, and the rest are standard machinery. If you understand what each clause does and why it is there, you can read any NDA with confidence and spot when one is unfair. Below, each clause is explained in plain English, with what it should say and the common trap to avoid. This is general information, not legal advice. For a specific deal or a cross-border NDA, ask a qualified lawyer in your jurisdiction. ## Parties and recitals The first clause names who is bound. It should use the correct legal names and entity types, and it should say whether the duty runs one way (only one side discloses) or both ways (mutual). Many NDAs also bind "affiliates", "representatives", or "advisers", so check that this group is defined and reasonable. If both sides will actually share information, a one-way NDA is the wrong instrument. The recitals, the "whereas" lines, set out why the parties are talking. They matter more than they look, because they frame the purpose for which information may be used. ## Definition of Confidential Information This is the most important clause. It decides what the NDA actually protects. A good definition covers information that is marked confidential, or that a reasonable person would understand to be confidential, connected to the subject of your discussions. It usually names examples: business plans, financials, customer lists, source code, designs, and so on. The trap is a definition that says "any and all information disclosed" with no limit. That can later be read to cover things you never intended, and it makes the exclusions below even more important. ## Exclusions from confidentiality Every fair NDA carves out information that should not be treated as a secret: - information that is or becomes public through no fault of the receiver,

• information the receiver already knew before it was disclosed,
• information developed independently without using the disclosed material, and
• information lawfully received from a third party who was free to share it. If these exclusions are missing, you could be accused of breaching confidentiality over information you were always free to use. Their absence is a red flag. ## Purpose and permitted use This clause limits what the receiver may do with the information. It should tie use to a named purpose, for example "to evaluate a possible partnership", and nothing more. Watch for "any business purpose", which effectively removes the limit. ## Obligations of the receiving party Here the receiver promises how it will protect the information: usually to use reasonable care, to share only on a need-to-know basis with people who are themselves bound to confidentiality, and not to disclose to outsiders. A reasonable standard of care is "the same care you take with your own confidential information, and no less than reasonable care". Be cautious of an absolute promise to prevent any disclosure, because no one can guarantee that. ## Term and survival Two periods live here and should be read separately: - the term, how long the agreement itself runs, during which new disclosures are covered, and
• the survival, how long the confidentiality duty lasts after the agreement ends. Two to five years of survival is common for ordinary commercial information. Genuine trade secrets may deserve a longer or indefinite duty. A perpetual duty on everything is usually too much and is worth negotiating down. ## Return or destruction of information On request, or when the deal ends, the receiver returns or destroys the confidential material and confirms it in writing. A fair version includes a carve-out: you may keep copies that your own policies or the law require you to retain, and copies in routine system backups, as long as they stay confidential. ## Permitted or compelled disclosure If a court, regulator, or law requires the receiver to disclose the information, this clause allows it, usually on condition that the receiver gives prompt notice to the disclosing party (where lawful) so they can seek protection. Without this carve-out, the receiver could be forced to choose between breaking the law and breaching the NDA. ## No licence or transfer of rights This short clause confirms that sharing information under the NDA does not give the receiver any ownership, licence, or intellectual property rights in it. If it is missing, ownership can become arguable later. ## Remedies Because money often cannot undo a leak, NDAs usually say the disclosing party may seek an injunction (a court order to stop the breach) in addition to damages. That is normal and fair. Treat fixed "penalty per breach" amounts with care, because their enforceability varies: in some systems a pre-set sum is enforceable as liquidated damages, in others it may be struck down as a penalty. This varies by jurisdiction. ## Governing law, jurisdiction, and boilerplate The final clauses decide which country's law applies and which courts hear a dispute. Choose a forum you can realistically use. The remaining boilerplate, assignment, notices, entire agreement, no waiver, and severability, is standard, but read it anyway: NDAs sometimes hide a non-solicit or non-compete rider among the boilerplate, and those are separate, significant commitments whose enforceability also differs by country. ## A quick map of risk | Clause | Risk level | Why | |--------|-----------|-----| | Definition of Confidential Information | High | Sets the whole scope | | Exclusions | High | Protects your freedom to operate | | Term and survival | High | Decides how long you are bound | | Purpose | Medium | Limits use | | Obligations | Medium | Sets your duty of care | | Remedies | Medium | Penalty terms can bite | | Governing law | Medium | Decides where you fight | | Return or destruction | Low to medium | Needs a backup carve-out | | No licence, boilerplate | Low | Standard, but read for hidden riders | ## Where a contract workspace helps Understanding these clauses is one thing; checking them on every NDA that crosses your desk, then remembering the survival date years later, is another. That is the work an AI contract workspace can carry. Instead of re-reading each NDA to find the definition, the missing exclusions, and the term, you see each clause modelled as part of a structured clause tree, with its position marked favourable, neutral, or unfavourable to your company, and you can edit a clause in plain English and track the key dates automatically. Adira is one workspace built around that idea, keeping drafting, per-clause risk, version history, and compliance tracking together and tuned to how your company contracts. The clauses above stay the same; a workspace just makes reading and remembering them far less manual. Keep this explainer next to the next NDA you read, and the document will stop feeling like dense legal text and start reading like a short list of decisions.