Ranking
The vendor's agreements were benchmarked against thousands of unsigned ndas and are in the top 33% for customer favorability.
50% customer favorability, based on 750 plus contract signals powered by Certify.
Indicates balanced, low-risk terms favorable to the customer.
Top 33% Non-Disclosure Agreement contract. No structural blockers. Procurement-ready.
Risk Summary
A concise snapshot of key risks, their impact, and priority concerns.
Discloser's Assignment Rights
Discloser's assignments
- Discloser is not allowed to assign in the event of a merger or acquisition.
- Discloser is not allowed to assign in the event of a corporate reorganization
Consent requirements
- There are no consent requirements restricting Discloser's ability to assign the contract
Subprocessor notice
- There are no notice requirements restricting Discloser's ability to assign the contract
Discloser's assignment rights
- There are no restrictions or conditions on Discloser's right to assign to a competitor of Receiver
Receiver's Assignment Rights
Receiver's assignments
- Receiver is allowed to assign in the event of a merger or acquisition
- Receiver is allowed to assign in the event of a corporate reorganization
Consent requirements
- There are no consent requirements restricting Receiver's ability to assign the contract
Subprocessor notice
- There are no notice requirements restricting Receiver's ability to assign the contract
Receiver's assignment rights
- There are no restrictions or conditions on Receiver's right to assign to a competitor of Discloser
Summary
Summary
- Restrictive covenants are not addressed in the contract
Return or Destruction Obligations
Return or destruction obligations
- Confidential information must be returned or destroyed upon request
- The contract does not prohibit the retention of confidential information in AI systems beyond the term.
- The contract does not require deletion or suppression of confidential information from models after termination.
- The contract does not acknowledge technical limitations around model unlearning.
- The contract does not define remedies if confidential information is embedded in outputs.
- The contract does not weaken deletion obligations for AI-processed data.
Retention
- A copy of the confidential information may be retained
- Confidential information may be retained as required by law or regulatory authority
- Confidential information may be retained in electronically stored backups/archives
- Confidential information may be retained in compliance with audit or document retention policies (or similar)
Summary
Term
- The term of the contract is > 2 up to 3 years
Protection period
- There is an exception to the end of the non-disclosure obligation for trade secrets
- As it relates to term and/or termination it is not possible to ascertain which party is Receiver and which party is Discloser; therefore, no additional report data is available
- The non-disclosure obligation ends > 2 - 3 years from the date of disclosure
Confidentiality Obligations
Discloser's confidential information
- Receiver explicitly commits to only disclose Discloser's confidential information as necessary for the permitted purpose (or similar)
- Receiver explicitly commits to only use Discloser's confidential information as necessary for the permitted purpose
Protection of confidential information
- Receiver commits to limiting access to only those who are under a legal/contractual obligation to protect confidential information
- Receiver can share confidential information with third parties
- Receiver can share confidential information with its agents and/or advisors (or similar)
- Third party recipients are not required to specifically agree to the terms at least as restrictive as those in the contract
- The contract requires Receiver to assume responsibility for breach by a permitted recipient
- The purpose of the contract is established
- A standard of care is defined for the protection of confidential information
- The standard of care for the protection of confidential information includes the same degree of care Receiver uses for their own confidential information
Residuals clause
- There is no residuals clause
Data breach notification policy
- Receiver commits to notify Discloser in the event of a security incident impacting Discloser's confidential information
Reverse engineering
- Confidential information may not be copied or reverse engineered
Permitted use
- The NDA does not explicitly prohibit use of confidential information for AI training or fine-tuning
- AI training is allowed by default, unless expressly restricted
- The NDA does not distinguish between human review and AI processing of confidential information
- Silence by default does not allow AI use of confidential information
- The NDA does not allow use of confidential information to improve the recipient’s models
General Provisions / Silent Defaults
- Confidentiality obligations are not weaker when AI is involved
Intellectual Property
Assignment of IP
- Discloser does not assign any IP to Receiver
Licenses to IP
- Receiver does not receive a license to Discloser's confidential information beyond what is necessary for the purpose
Indemnification
Summary
- Indemnification is not addressed in the contract
Limitation of Liability
Summary
- Limitation of liability is not addressed in the contract
Warranties
Warranties offered
- Neither party makes any representations or warranties
Defined remedies
- Remedies for AI misuse are not equivalent to remedies for human misuse
- The NDA does not limit liability for AI-related confidentiality failures
- It does not cap damages differently for AI incidents
- Injunctive relief rights are not preserved for AI-related misuse
- The NDA does not shift risk to the disclosing party through “as-is” language
Definition and Ownership
Definition
- What constitutes confidential information is defined
- The definition of confidential information includes trade secrets
- The definition of confidential information includes source code
- There are no specific requirements related to the protection of the regulated data, Personal Identifiable Information (PII), and/or Personal Health Information
- The contract does not include a "reasonable person" standard
- It is unclear whether the contract includes a "reasonable person" standard
- There are no marking requirements for confidential information
- Synthetic data derived from confidential information is not treated as confidential
- The NDA does not include clear definitions of either “derived,” “synthetic,” or “inferred” as they apply in an AI context.
- The NDA does not include provisions stating that AI-generated outputs that contain confidential information are covered under the agreement.
- The contract does not exclude derivative insights from confidentiality protections
Ownership
- Discloser fully retains ownership of their confidential information
Summary
Mutuality
- All commitments concerning confidential information are mutual
- The contract is fully mutual
Exclusions to Confidentiality Obligations
Non-disclosure exclusions
- Information known to the public is excluded from the Receiver's non-disclosure obligations
- Information previously known to the Receiver is excluded from Receiver's non-disclosure obligations
- Information independently developed by the Receiver is excluded from Receiver's non-disclosure obligations
- Information disclosed to the Receiver from some other party that has no duty of confidentiality to the Discloser is excluded from the Receiver's non-disclosure obligations
- Information disclosed by the Receiver with the Discloser's prior written approval is excluded from the Receiver's non-disclosure obligations
- Information disclosed as required by applicable law, a court order, governmental agency, regulatory authority, subpoena, or discovery request is excluded from the Receiver's non-disclosure obligations
- The receiving party does not have to disclose whether AI tools process confidential information
- The receiving party must not identify the categories of AI tools used
- The contract does not require disclosure of third-party AI service providers
- The contract does not require notice before introducing new AI tools into the workflow
- The contract does not require updates if AI usage changes materially
Access the complete methodology and detailed breakdown by
downloading the full report for in depth insights
Why this Matters
See value, risks, and position at a glance for better decisions.
How TrustMark™ Works?
Data Extraction
Scans and converts legal text into structured data.
Objective Scoring
Clauses benchmarked against market data.
Deal Breakers
Risks and non-negotiables flagged early.
Benchmarking
Compares your contract to market standards.
Certification
Contract validated after meeting risk and score thresholds.
Based on 750 plus contract signals benchmarked against market data.
Certified Contract Reports, Explained
Verified™ contract reviews are reviews of contracts that have been carefully checked by contract experts. This review is designed to help users understand the rights and obligations associated with the Mutual Nondisclosure Agreement ("MNDA") for Docusign Inc.. We looked at the issues found in 'Term Sheets' and did not look for any other issues.
For more information on TermScout's contract review process, visit our methodology page.
Not all confidentiality risks are created equal. Even if an NDA includes only a single provision that materially increases risk for either party, the agreement may not merit certification. TermScout evaluates mutual NDAs against objective standards designed to ensure that the agreement imposes fair, reciprocal, and commercially reasonable confidentiality obligations on both parties. Accordingly, TermScout will not certify a mutual NDA if it contains any provision that fails to meet the following standards. Any NDA that includes the opposite of one of these standards will be treated as containing a Deal Breaker:
Residuals clauses allow one party to retain and use information remembered from disclosures, even if that information is confidential. This creates a significant risk that sensitive information could be used without restriction, undermining the entire purpose of the NDA.
When an NDA imposes stronger obligations on one party than the other, it creates an imbalance of risk. Mutual NDAs are intended to protect each party equally, and one-sided obligations expose a party to greater confidentiality, use, or enforcement risk than the counterparty.
Marking requirements can lead to accidental loss of confidentiality protection simply because a party forgets to label a document correctly. Most businesses expect confidentiality protections to apply automatically, and marking requirements place an unreasonable administrative burden on both sides.
Non-solicitation clauses can significantly restrict a company's ability to hire talent or engage with counterparties. These provisions introduce complex compliance challenges that go beyond the purpose of an NDA, which is simply to protect shared confidential information.
Indemnification provisions shift financial and legal risk in ways that are inappropriate for a standalone NDA. Because NDAs should focus narrowly on confidentiality, adding indemnification exposes a party to potentially substantial liability unrelated to misuse of information.
The goal of TermScout's reports is to provide users with the data necessary to make an informed decision about whether they can accept the terms. The data provided in TermScout's reports includes:
- Term Sheet: A full report of the key rights and obligations contained in the agreement.
- Overall Ratings: TermScout's overall impression of the favorability of the contract vis a vis the parties. These ratings are algorithmic approximations of favorability that are based on market data and the subject views of contract experts with experience in the specific type of contract.
- Rare Clause Radar: TermScout identifies and surfaces a list of the most rare and material clauses that favor your counterparty.
- Playbooks: Playbooks are a way of programming into TermScout's software a specific set of acceptance criteria for a contract type. All accounts have access to sample Playbooks for select templates, and Pro accounts have the ability to build custom Playbooks.
- Market Data: Any right or obligation in a contract can be compared to market data for similar contract types, including data from TermScout's Contract Market Database™ of thousands of public contracts and anonymized and aggregated data from hundreds of negotiated contracts.
Please note that this report focuses on the identification of terms from the contract documents listed under 'Scope of Review' and compares them against a defined set of criteria. Certain services may be subject to additional terms not available to TermScout, such as purchase orders and other deal-specific documents. You should always review the terms associated with the specific service you are using and know that TermScout's ratings generally do not cover (a) services purchased through a reseller, (b) offline variants of any of the Agreements, (c) service-specific terms that override any of the terms discussed here, or (d) free services. You also should consult your legal counsel if you have any questions about the meaning, significance or assessment of any agreement or provision.
TermScout prepared this report with an average use-case customer in mind and operated under the assumptions listed below (the "Key Assumptions"). To the extent that provisions in a contract vary based on specific circumstances that differ from the Key Assumptions, TermScout ignores those variations. Additional contract-level assumptions, if any, are disclosed in 'Notes to Customer'.
Key Assumptions
- Customer is an average "end user" of the service (i.e. not a partner, distributor, or developer).
- Customer is not a government entity.
- Customer is a US-based company and is using the service in the US.
- Customer is a paying user (i.e. not a user of free services).
- Customer is not using beta services.
- Unless otherwise noted, service-specific terms that may override or supersede the terms of the Agreement are not reviewed by TermScout.
We reviewed the MNDA for Docusign and any documents specifically listed under 'Scope of Review'. For purposes of this report, "Receiver" means the party contracting with Docusign and "Discloser" means Docusign.
References herein to the "Agreement" are to the following documents:
- The Primary Document: Mutual Nondisclosure Agreement ("MNDA")
TermScout did not review any documents other than those listed above. If other documents form part of this Agreement, the answers provided by TermScout may be incomplete or incorrect. TermScout's accuracy commitments only cover documents specifically identified in this section.
No additional notes to customer for this report.
Frequently Asked Questions
Find quick answers to the most common questions about our platform, process, and agreements.
Procurement and legal teams often escalate legal-tech agreements when ownership language creates ambiguity around uploaded contracts, legal work product, negotiation history, or generated analytical outputs. Delays increase when vendors reserve broad rights over customer-created materials, derived insights, or operational metadata without clearly defined governance boundaries. Enterprise buyers generally expect legal-tech platforms to preserve clear customer ownership of legal content and associated operational intelligence.
Buyers frequently challenge agreements that permit vendors to broadly reuse legal-content data, negotiation patterns, clause analytics, or generated outputs for unrelated commercial or AI-development activities. Additional concern arises when ownership provisions rely on vague “improvement” or “derived data” concepts that could capture strategically sensitive legal information. Enterprise review teams generally favor narrowly scoped vendor rights tied directly to operating and supporting the contracted platform.
Enterprise buyers often interpret ownership language as a signal of the vendor’s governance maturity and operational discipline. Agreements that clearly separate customer-owned legal materials from vendor-owned platform technology generally create more confidence during procurement review. In contrast, heavily vendor-favorable ownership structures may suggest elevated risk around confidentiality, downstream reuse, or long-term control of sensitive legal information and operational insights.
Buyers commonly assess whether ownership terms could affect portability of legal repositories, reuse of privileged content, control over generated analytics, or defensibility of internal legal workflows after deployment. Concern increases when vendors can broadly retain access to customer legal materials or operational outputs following termination. Enterprise teams increasingly evaluate these provisions as indicators of long-term governance stability and information-control risk rather than isolated intellectual-property drafting issues.
Check If Your Contract
Qualifies for Certification
See how your terms compare to market standards and uncover opportunities to build buyer trust and close deals faster.
Get your Certification Score Now