The Confidential Information Definition Clause: What It Means and How to Draft It (2026)

What the Confidential Information definition does In any NDA or confidentiality clause, the definition of Confidential Information is the engine. Every obligation in the clause (do not use it, do not disclose it, protect it, return it) applies only to whatever falls inside that definition. In plain terms, the definition draws the line around what is protected, and everything on the right side of that line is covered while everything on the wrong side is not. Get the definition wrong and the strongest confidentiality obligations in the world protect the wrong things. This is why experienced lawyers spend more time on the definition than on the obligations. Two contracts can have identical confidentiality duties but protect completely different information, because one defines Confidential Information broadly and the other narrowly. The definition is also where the usual exclusions live, the categories of information that are carved out even though they might otherwise look confidential. ## The two drafting approaches There are two main ways to define Confidential Information, and most real clauses blend them. - The broad, catch-all approach. Confidential Information means any information disclosed by one party to the other, in any form, that relates to the disclosing party's business. This protects almost everything, which suits the party doing most of the disclosing, but it can be so wide that it is hard to know what is actually covered, and courts may read it down.

• The marked or identified approach. Confidential Information means information that is marked confidential, or that is identified as confidential at the time of disclosure (and, for oral disclosures, confirmed in writing within a set number of days). This gives certainty about what is covered but puts a burden on the discloser to label things, and anything unmarked slips through. Many well drafted clauses combine the two: a broad description of the kinds of information covered, plus a deeming rule that information a reasonable person would understand to be confidential is included even if unmarked. The right balance depends on which side of the deal you are on. ## A sample Confidential Information definition > Confidential Information means all information disclosed (whether before or after the date of this Agreement, in writing, orally, visually, electronically or in any other form) by or on behalf of the Disclosing Party to the Receiving Party that relates to the Disclosing Party's business, operations, products, customers, finances, technology or affairs, including the terms of this Agreement, and that is either (a) marked or described as confidential or proprietary, (b) identified as confidential at the time of disclosure, or (c) that a reasonable person would understand to be confidential given its nature or the circumstances of its disclosure. Confidential Information does not include information that the Receiving Party can show: (i) is or becomes publicly available other than through its breach; (ii) was lawfully in its possession before disclosure without a duty of confidentiality; (iii) is lawfully received from a third party free to disclose it; or (iv) is independently developed by the Receiving Party without use of the Confidential Information. Treat this as a drafting starting point, not a finished clause. The right definition depends on what is being shared and the governing law, and this page is general information, not legal advice. ## The standard exclusions, and why they matter The carve-outs at the end of the definition are not boilerplate to skim. They are what stops a confidentiality obligation becoming unfair or impossible to live with. The four classic exclusions are: - Public domain: information already public, or that becomes public without the receiver's fault.
• Already known: information the receiver already lawfully held, free of any duty, before it was disclosed.
• Received from a third party: information lawfully obtained from someone else who was free to share it.
• Independently developed: information the receiver created on its own, without using the confidential material. Without these, a receiver could be in breach for using information it knew all along or that everyone can read online. A separate, legally required exclusion usually appears in the obligations rather than the definition: disclosures compelled by law, a court or a regulator, which are permitted provided the receiver gives notice where it can and discloses only what is required. ## How to draft it well Match the breadth to your side of the deal. If you are mostly disclosing, favour a broad definition with a reasonable-person deeming rule. If you are mostly receiving, favour a definition tied to marking or identification, so you know exactly what you must protect. Cover all forms and timing. Include oral, visual and electronic disclosures, and information shared before the contract was signed (during early discussions), so nothing important falls outside by accident. Decide how oral disclosures are captured. If you require marking, add a workable rule for oral or visual disclosures, such as confirming them in writing within a short period, rather than leaving them unprotected. Keep the standard exclusions. Do not delete the four carve-outs to look tough. A definition without them is often unreasonable and may be read down or refused enforcement by a court. Name especially sensitive categories. Where particular information matters (source code, pricing, customer lists, personal data), naming it removes any argument about whether it is covered. Mind the overlap with trade secrets and personal data. Confidential Information is a contract concept and is broader than a trade secret, which has its own legal definition and protections. Where the information includes personal data, confidentiality obligations sit alongside, not instead of, data-protection duties. ## Points worth negotiating The disclosing party wants the definition wide, a deeming rule for unmarked information, and the contract's own terms treated as confidential. The receiving party wants the definition tied to clear identification, the full set of exclusions, a sensible process for oral disclosures, and a time limit after which the duty ends (except for trade secrets, which are often protected for as long as they stay secret). A balanced result is a reasonably broad definition with a reasonable-person deeming rule, all four standard exclusions, a workable oral-disclosure mechanism, and a duration that fits the sensitivity of the information. ## Jurisdiction notes Confidential Information in a contract is defined by the contract itself, so the wording governs in every jurisdiction, but the surrounding law differs. In the United States, trade secrets receive separate statutory protection (for example under the Defend Trade Secrets Act), and that is narrower than contractual confidential information. In the United Kingdom and other common-law systems, there is also an equitable duty of confidence that can protect information even without a contract, which sits behind the clause. In India, confidentiality is protected mainly through contract, since there is no single trade-secret statute, which makes a well drafted definition especially important. Because the backstops differ, do not rely on the law to fill gaps the definition should cover. ## Common mistakes A definition so broad it is unclear what is actually protected, inviting a court to read it down. A definition tied only to marking, so anything unmarked (including valuable oral disclosures) is unprotected. Deleting the standard exclusions, making the clause unfair. Forgetting pre-contract disclosures made during discussions. Ignoring personal data, so confidentiality and data-protection duties are not aligned. Assuming confidential information and trade secrets are the same thing. Copying a definition from an unrelated NDA without checking it fits what is really being shared. ## One workspace to draft, review and track your clauses Most teams do not lose on the theory of confidentiality. They lose because the definition in one NDA is broad, the next is narrow, the template no one updated is still in circulation, and no one can quickly show what any given contract actually protects. The alternative is to keep drafting, review, tracking and governance in one place rather than across five disconnected tools. The idea is simple. You draft from your own clause catalogue and house positions, the system reads any contract and flags positions (including a lopsided confidentiality definition) as favourable, neutral or unfavourable to your company, and because the contract is held as a structured clause tree rather than flat text you can find every Confidential Information definition across a set of agreements and align them in plain English. Adira is one such workspace, built on Anthropic's Claude and tuned to how your company contracts. India is deepest today, with other jurisdictions and a company command centre on the roadmap.