Perspective Lens

The same NDA clause can be a green light, a yellow flag, or a critical issue depending on which side the user is on. This reference flips the lens for the perspective-sensitive provisions.

Operating principle

Every NDA provision creates an asymmetry between the parties. Reading the provision through the user's perspective means asking: does this provision expand or contract our exposure, and by how much, given that we are the disclosing / receiving / mutual party?

A common error is to call a provision "balanced" because it reads neutrally on the page. A clause that says "neither party shall disclose..." is mutual on its face but can be deeply asymmetric if one party is sharing far more than the other. The lens corrects for that by asking about exposure, not just language.

Definition of Confidential Information

Discloser lens: wants the broadest possible definition. Any limitation (marking requirements, written-confirmation requirements, narrow categorical list) creates an opening for the recipient to argue specific information was not confidential. Look for: catch-all language ("information that a reasonable person would understand to be confidential"), explicit coverage of oral and visual disclosures, no marking requirement.

Recipient lens: wants the narrowest workable definition. Marking requirements force the discloser to be deliberate, which limits scope to information the discloser actually cares about protecting. Look for: marking required, oral disclosures require written confirmation within a stated period (30 days standard), exclusion of information of a general business nature.

Mutual lens: wants symmetric definitions. Watch for "mutual" NDAs where the definition of Discloser's Confidential Information is broad and the definition of Recipient's is narrow — a common drafting move that produces a one-way agreement labeled "mutual." Definitions should be parallel; if Party A's information has a catch-all, Party B's should too.

Exclusions from Confidential Information

Discloser lens: wants narrow, well-defined exclusions. Concerned about:

• Independent development carveouts that swallow protection (recipient claims any later work was "independent").
• Reverse engineering carveouts in product/technical NDAs (turns the NDA into a green light to copy).
• Disclosures pursuant to legal process without notice (recipient could be subpoenaed and disclose without telling the discloser).

Recipient lens: wants broad, clearly-stated exclusions. Concerned about:

• Missing exclusions entirely (recipient takes on protection obligations for information that becomes public, was already known, or comes from third parties).
• Exclusions conditioned on documentation requirements that are operationally impossible ("recipient must produce contemporaneous written documentation" of independent development).
• "Public domain" exclusion limited to information that was public at the time of disclosure, missing information that becomes public later through no fault of recipient.

Mutual lens: check that exclusion lists run identically on both sides. Asymmetric exclusion lists in nominally-mutual NDAs are a red flag.

Permitted Uses

Discloser lens: wants the narrowest, most specifically-defined Purpose. "Evaluating a potential acquisition of Company X" is far narrower than "exploring a potential business relationship." Wants explicit prohibition on use for any other purpose. Wants prohibition on use for benchmarking, competitive analysis, or product development.

Recipient lens: wants reasonable operational flexibility. Concerned about Purpose definitions so narrow they prevent legitimate evaluation activity (e.g., NDA for a vendor evaluation that prohibits internal demos to the team that will use the product). Wants ability to use for the named Purpose plus reasonable related activities.

Mutual lens: check that Purpose covers both directions of disclosure equally. In a mutual NDA where Party A is evaluating Party B's product and Party B is evaluating Party A's data integration capability, the Purpose definition needs to capture both evaluation directions.

Permitted Disclosures

Discloser lens: wants tight need-to-know on the recipient side. Concerned about:

• Affiliates included without limit (affiliate could be a competitor of the discloser — common in large corporate families).
• Subcontractor disclosure without affirmative obligation that the subcontractor is bound by similar confidentiality.
• "Need to know" not specified or inflated to "any employee."

Recipient lens: must have permitted disclosure to professional advisors. Without this, recipient cannot share with counsel, accountants, or financial advisors during the evaluation — operationally impossible. Critical-issue if missing. Also wants reasonable affiliate disclosure for normal business operations.

Mutual lens: check that the categories of permitted recipients run symmetrically. A common asymmetry: one side gets to disclose to "affiliates and subcontractors," the other only to "employees with need to know."

Term and Duration

Discloser lens: wants long protection, especially for trade secrets. The standard ask is "3 years from disclosure for general confidential information; for as long as the information remains a trade secret for trade secrets specifically." A 1-year term on technical information is short; less than 2 years on any commercial NDA is short.

Recipient lens: wants finite protection. Perpetual obligations create operational burden — the recipient's compliance program must track this information indefinitely. Standard recipient ask: 2–3 years from disclosure, all information treated identically (no special trade-secret extension). For some recipients (large enterprises), even 3 years can be operationally burdensome and 2 years is preferred.

Mutual lens: check that the term provision treats both parties' information identically. Mutual NDAs with asymmetric terms are a red flag.

Critical jurisdictional note: Perpetual confidentiality obligations on non-trade-secret information may be unenforceable in some jurisdictions. If perpetual term appears and governing law is California or another perpetual-skeptical jurisdiction, flag for the user's review of enforceability — but do not give an enforceability opinion, that is the user's call.

Return / Destruction

Discloser lens: wants strong return obligations on request, with certifications. Watch for:

• No return/destruction obligation at all (means recipient can hold confidential information forever after the engagement ends).
• Mandatory destruction with no certification requirement (no way to verify compliance).

Recipient lens: must have destruction-or-return option (not return-only — operationally impossible for digital information). Must have retention exceptions for:

• Legal and compliance archives.
• Standard backup systems (recipient cannot reasonably purge backups).
• Information embedded in deliverables or work product the recipient owns. With continuing confidentiality obligations on retained materials.

Mutual lens: check symmetry. Asymmetric return/destruction clauses in mutual NDAs flag for the disadvantaged side.

Residuals Clause

Discloser lens: every residuals clause is a problem. The least-bad version is limited to "general knowledge, skills, and experience retained in unaided memory" with explicit no-license language. Any residuals clause is at minimum a material issue from discloser perspective.

Recipient lens: a residuals clause is a recipient-favorable provision and the standard recipient ask in technical NDAs. Coupled with no-license, it preserves the recipient's freedom to operate. Recipients with engineers who will see the discloser's information should ask for residuals.

Mutual lens: residuals in a mutual NDA needs careful analysis. If both parties are receiving information of similar sensitivity, residuals symmetrically protects both. If one party is the substantial discloser, residuals primarily benefits the other.

Equitable Remedies / Injunctive Relief

Discloser lens: wants explicit acknowledgment of irreparable harm, explicit right to injunctive relief, and waiver of bond. Without these, the discloser is left with damages-only remedies, which are inadequate for trade-secret breaches.

Recipient lens: equitable remedies provisions are typically acceptable. Watch for:

• One-sided availability in a mutual NDA (only discloser may seek injunctive relief — flag).
• Combined with broad damages provisions or liquidated damages (creates compounding remedy risk).

Governing Law and Venue

Discloser lens: wants a forum where injunctive relief is readily available and a governing law that recognizes strong trade-secret protections.

Recipient lens: wants a forum that is geographically and procedurally workable, and a governing law that does not enforce perpetual confidentiality on non-trade-secret information.

Mutual lens: mutual NDAs typically use a neutral forum (Delaware, New York) or alternate between the parties' home jurisdictions. Asymmetric venue (always discloser's home court) in a mutual NDA is a flag.

Watching for "Mutual Theater"

A persistent pattern in NDAs labeled "mutual": the document uses neutral pronouns ("each party," "the receiving party") throughout, but the substantive asymmetries reveal that one party is the practical discloser and the agreement is structured to favor that side. Indicators:

• Asymmetric definitions or exclusions, even when the language frame is symmetric.
• Different terms for different categories of information (trade secrets vs general) where one party's information falls predominantly into the more-protected category.
• Permitted-disclosure provisions that work better for one party's organizational structure (e.g., narrow advisor disclosure favors the party that does its evaluation in-house).
• Equitable-relief provisions worded mutually but operationally one-sided.

When reviewing a "mutual" NDA from one party's perspective, always conduct an asymmetry check: would the same provisions read differently if the parties' positions were reversed? If yes, the document is not actually mutual, regardless of label.