Spelled-out amount 50,000 does not match numeral 75,000.
Evidence — 1. Confidentiality Obligation, characters 374–407
fifty thousand dollars ($75,000)
When a contract states an amount in words followed by a numeral in parentheses, the two forms must match. Courts in most US jurisdictions resolve a conflict in favor of the spelled-out form, but the inconsistency itself is a drafting error worth catching before signature.
Recommendation: Verify the intended amount with the drafter and correct whichever form is wrong.
No clause was found defining the duration of confidentiality obligations.
Basis — the document contains no matching clause; this finding is about what is absent.
The Uniform Trade Secrets Act does not itself require a term, but courts in some states have declined to enforce a perpetual confidentiality obligation over information that is not a trade secret, and a silent agreement leaves the duration to argument. A stated term — with a longer or perpetual term for trade secrets — is standard practice.
Recommendation: Add a clause stating either a definite term (e.g., 5 years from disclosure) or, preferably, a definite term for confidential information plus a perpetual term for trade secrets.
No defined-term definition for 'Confidential Information' was detected.
Basis — the document contains no matching clause; this finding is about what is absent.
Without an explicit definition, the scope of the obligation is ambiguous and may be construed narrowly against the disclosing party.
Recommendation: Add a 'Definitions' section defining 'Confidential Information' (or 'Proprietary Information') with the scope of marked, oral, and observable information.
Confidential-Information definition lacks the standard 'publicly available' exclusion.
Basis — the document contains no matching clause; this finding is about what is absent.
All four standard NDA exclusions (public domain, prior knowledge, third-party-lawfully, independently developed) should appear. The 'publicly available' exclusion is the most common.
Recommendation: Add: 'Confidential Information does not include information that is or becomes generally available to the public other than as a result of a breach of this Agreement.'
Confidential-Information definition lacks an exclusion for information previously known to the receiving party.
Basis — the document contains no matching clause; this finding is about what is absent.
Without a 'previously known' carve-out, the receiver risks breaching the NDA by using information they already possessed.
Recommendation: Add: 'Confidential Information does not include information already known to Receiving Party prior to disclosure, as evidenced by its written records.'
Confidential-Information definition lacks a 'lawfully obtained from a third party' carve-out.
Basis — the document contains no matching clause; this finding is about what is absent.
Without this exclusion the receiver could be in breach for using identical information obtained legitimately from another source.
Recommendation: Add: 'Confidential Information does not include information received from a third party not under an obligation of confidentiality to Disclosing Party.'
Confidential-Information definition lacks an 'independently developed' carve-out.
Basis — the document contains no matching clause; this finding is about what is absent.
Without this exclusion, ordinary R&D by the receiver may incidentally be captured. Common Paper, ACC, and ABA practice notes all include this carve-out.
Recommendation: Add: 'Confidential Information does not include information independently developed by Receiving Party without use of or reference to Disclosing Party's Confidential Information.'
No clause was found requiring return or destruction of Confidential Information.
Basis — the document contains no matching clause; this finding is about what is absent.
Without this clause the discloser has no contractual hook to recover or wipe disclosed material once the relationship ends.
Recommendation: Add a return-or-destruction clause triggered by termination of the NDA or upon written request by Disclosing Party.
Found 1 placeholder that looks like unfilled template content: "[insert party name]".
Evidence — Mutual Non-Disclosure Agreement, characters 117–136
[insert party name]
A bracketed placeholder, mustache token, or XXX run that survived into the final document is almost always a drafting accident — the contract is meant to be filled in. A placeholder where a counterparty name belongs makes the agreement legally questionable; a placeholder elsewhere makes the agreement embarrassing.
Recommendation: Replace every flagged placeholder with the intended content, or remove the bracket if the content is no longer needed.
The following date does not exist on the calendar: February 30, 2026.
Evidence — Mutual Non-Disclosure Agreement, characters 91–108
February 30, 2026
A date that is not a real calendar date (e.g., February 30) is a drafting error. It usually points to a typo — for example, intending the last day of the month and writing the wrong number.
Recommendation: Confirm the intended date with the drafter and correct each impossible date.
The contract does not allocate ownership of intellectual property.
Basis — the document contains no matching clause; this finding is about what is absent.
Without an IP-ownership clause, default copyright and patent rules apply. A work an employee prepares within the scope of employment is a work made for hire owned by the employer (17 U.S.C. §§ 101, 201(b)); copyright in a contractor's work vests in the contractor unless a written work-for-hire agreement covers an enumerated category, or the rights are assigned in writing.
Recommendation: Add an IP-ownership clause: state who owns what is created under this contract, assign it expressly (a work-made-for-hire recital alone does not carry every category), and carve out each party's pre-existing material with a licence to use it as incorporated.
Reference model clause
IP ownership with pre-existing-IP carve-out — Common Paper
The Common Paper Cloud Service Agreement allocates ownership cleanly: each party keeps its pre-existing intellectual property, the provider owns the service and any improvements, the customer owns its data, and feedback is licensed back on a non-exclusive basis. Ownership is stated rather than left implicit, and the customer-data carve-out is explicit.
Reference only — Vaulytica does not draft. Source: Common Paper Cloud Service Agreement — Proprietary Rights (Common Paper Standard Agreements, CC BY 4.0) [license: CC-BY-4.0]
No clause was found extending the confidentiality obligation for trade secrets beyond the fixed term.
Basis — the document contains no matching clause; this finding is about what is absent.
Some courts treat a fixed confidentiality term as evidence that the owner stopped taking reasonable secrecy measures after it expired, which can defeat trade-secret status; the risk is real but not automatic.
Recommendation: Add: 'With respect to trade secrets, the obligations of confidentiality shall continue for as long as the information qualifies as a trade secret under applicable law.'
No clause was found limiting use of Confidential Information to a defined Purpose.
Basis — the document contains no matching clause; this finding is about what is absent.
A defined Purpose narrows the field of permitted use and creates a contractual basis for objecting to unrelated downstream use.
Recommendation: Define 'Purpose' and require use 'solely for the Purpose.'
Return-or-destruction language was detected but does not require written certification of destruction.
Basis — the document contains no matching clause; this finding is about what is absent.
Without an attestation requirement, the discloser has no proof that destruction actually occurred — a real-world enforcement gap.
Recommendation: Add: 'Receiving Party shall provide a written certification, signed by an officer, attesting to compliance with this Section within thirty (30) days.'
No clause was found acknowledging irreparable harm or entitlement to injunctive relief.
Basis — the document contains no matching clause; this finding is about what is absent.
Courts generally still require a party seeking an injunction to show irreparable harm, and many treat a contractual stipulation as persuasive rather than binding. The clause strengthens an emergency motion after a leak; its absence does not bar equitable relief.
Recommendation: Add: 'The parties agree that monetary damages would be an inadequate remedy for any breach of this Agreement and that the non-breaching party shall be entitled to seek injunctive or other equitable relief, in addition to any other available remedies.'
Injunctive-relief clause does not include a waiver of bond.
Basis — the document contains no matching clause; this finding is about what is absent.
Many courts require a movant to post a bond as a condition of preliminary injunctive relief. A contractual waiver smooths the emergency-motion path.
Recommendation: Add: 'The party seeking injunctive relief shall be entitled to such relief without the need to post a bond or other security.'
No clause was found stating that disclosure does not grant a license or ownership interest.
Basis — the document contains no matching clause; this finding is about what is absent.
Courts rarely find that disclosure under an NDA implies a license, but a receiver can still argue it. A one-line denial removes the argument.
Recommendation: Add: 'No license or other right is granted to Receiving Party in or to the Confidential Information except as expressly set forth in this Agreement.'
No representation of authority or absence of conflicting obligations was found.
Basis — the document contains no matching clause; this finding is about what is absent.
An authority representation is a low-cost addition that closes off a defensive argument later. Common Paper includes it.
Recommendation: Add: 'Each party represents that it has full authority to enter into this Agreement and that doing so does not conflict with any other obligation.'
No successors-and-assigns clause with consent-to-assignment was found.
Basis — the document contains no matching clause; this finding is about what is absent.
Without a consent-to-assignment clause, an acquirer of the receiving party could inherit access to Confidential Information without the discloser's approval.
Recommendation: Add: 'This Agreement shall bind and inure to the benefit of the parties and their successors and permitted assigns. Neither party may assign this Agreement without the prior written consent of the other party.'
Phrase 'liable for all damages, direct, indirect, consequential, special, and punitive, without limitation' appears in the document.
Evidence — 2. Liability, characters 478–576
Recipient shall be liable for all damages, direct, indirect, consequential, special, and punitive, without limitation, arising from any breach of this Agreement.
An uncapped or unlimited liability clause exposes a party to an open-ended financial risk. Even mutually agreed-upon caps usually carve out specific categories (fraud, willful misconduct, IP indemnity); a blanket 'no cap' is unusual outside those carve-outs.
Recommendation: Confirm the scope is intended. If not, add a per-claim and aggregate cap, and enumerate the carve-outs explicitly.
Reference model clause
Mutual limitation of liability with a stated cap and super-cap — Common Paper
The Common Paper Cloud Service Agreement caps each party's aggregate liability at a stated figure tied to fees (commonly 12 months of fees on the cover page) and excludes indirect, incidental, and consequential damages — then carves out a higher 'super cap' (or uncapped exposure) for confidentiality breaches, indemnification, and a party's gross negligence or willful misconduct. The cap is reciprocal rather than one-sided, and the carve-outs are listed explicitly rather than buried.
Reference only — Vaulytica does not draft. Source: Common Paper Cloud Service Agreement — Limitations on Liability (Common Paper Standard Agreements, CC BY 4.0) [license: CC-BY-4.0]
No Effective Date is named, defined, or stated near the top of this document.
Basis — the document contains no matching clause; this finding is about what is absent.
Most contracts identify a starting point that other date references rely on. Without it, relative terms like 'within 30 days after the Effective Date' have no anchor.
Recommendation: Add an Effective Date — either in the preamble ('dated as of [date]'), as a defined term, or as an explicit 'Effective Date: [date]' line.
The following references do not resolve to any section: Section 9.4.
Evidence — 1. Confidentiality Obligation, characters 287–298
Section 9.4
A broken cross-reference can mean the referenced section was renumbered or deleted, or that a section reference was made up. Either way the reader has no way to follow the citation.
Recommendation: Update each broken reference to point to the correct section, or delete it if it is no longer applicable.
The document does not state where disputes must be brought.
Basis — the document contains no matching clause; this finding is about what is absent.
Without a venue clause, default venue rules apply (in federal court, 28 U.S.C. § 1391). A clear forum-selection clause avoids ambiguity.
No clause was found stating that the NDA does not establish precedent for future agreements.
Basis — the document contains no matching clause; this finding is about what is absent.
A no-precedent clause prevents the receiver from arguing that prior NDAs control subsequent commercial-deal drafting. Optional but common.
Recommendation: Add: 'This Agreement is not intended to create, and shall not be construed as creating, a precedent for any future agreement between the parties.'
Neither 'indemnify' nor 'hold harmless' appears in the document.
Basis — the document contains no matching clause; this finding is about what is absent.
Most commercial contracts allocate risk through an indemnification clause. The absence leaves the parties to default tort and contract law for any third-party claims.
Recommendation: Add an indemnity, or say expressly that the parties allocate no risk that way. If you add one, state who indemnifies whom, for which claims, and the procedure — prompt notice, control of the defence, and no settlement imposing a non-monetary obligation without consent.
Reference model clause
Reciprocal indemnification with defined procedure — Common Paper
The Common Paper Cloud Service Agreement provides reciprocal indemnities (the provider indemnifies for third-party IP-infringement claims; the customer indemnifies for misuse claims) and specifies the indemnification procedure: prompt notice, control of defense, and a duty to cooperate. Indemnity obligations sit above the general liability cap, and the IP indemnity includes standard mitigation options (procure a license, modify, or refund).
Reference only — Vaulytica does not draft. Source: Common Paper Cloud Service Agreement — Indemnification (Common Paper Standard Agreements, CC BY 4.0) [license: CC-BY-4.0]
The families below were detected from this document's own VOCABULARY, not confirmed. A document can discuss another instrument's subject matter without being one — an 83(b) election letter names restricted stock and a right of first refusal, and is not a stock purchase agreement. Each family was scanned with its own rule set, and those checks assume the document IS one; where it is not, an absence reported below is a clause the document was never supposed to carry. Read this section as a prompt to confirm the family, not as a verdict. Kept separate from the primary findings above, and outside every result hash.
Unilateral NDA — Deep Analysis (unilateral-nda-deep) — 7 critical, 8 warnings, 1 informational
| Severity | Rule | Finding | Section |
|---|---|---|---|
| CRITICAL | NDA-D-003 | No clause was found defining the duration of confidentiality obligations. | Mutual Non-Disclosure Agreement |
| CRITICAL | NDA-D-005 | No defined-term definition for 'Confidential Information' was detected. | Mutual Non-Disclosure Agreement |
| CRITICAL | NDA-D-006 | Confidential-Information definition lacks the standard 'publicly available' exclusion. | Mutual Non-Disclosure Agreement |
| CRITICAL | NDA-D-007 | Confidential-Information definition lacks an exclusion for information previously known to the receiving party. | Mutual Non-Disclosure Agreement |
| CRITICAL | NDA-D-008 | Confidential-Information definition lacks a 'lawfully obtained from a third party' carve-out. | Mutual Non-Disclosure Agreement |
| CRITICAL | NDA-D-009 | Confidential-Information definition lacks an 'independently developed' carve-out. | Mutual Non-Disclosure Agreement |
| CRITICAL | NDA-D-013 | No clause was found requiring return or destruction of Confidential Information. | Mutual Non-Disclosure Agreement |
| WARNING | NDA-D-004 | No clause was found extending the confidentiality obligation for trade secrets beyond the fixed term. | Mutual Non-Disclosure Agreement |
| WARNING | NDA-D-012 | No clause was found limiting use of Confidential Information to a defined Purpose. | Mutual Non-Disclosure Agreement |
| WARNING | NDA-D-014 | Return-or-destruction language was detected but does not require written certification of destruction. | Mutual Non-Disclosure Agreement |
| WARNING | NDA-D-015 | No clause was found acknowledging irreparable harm or entitlement to injunctive relief. | Mutual Non-Disclosure Agreement |
| WARNING | NDA-D-016 | Injunctive-relief clause does not include a waiver of bond. | Mutual Non-Disclosure Agreement |
| WARNING | NDA-D-021 | No clause was found stating that disclosure does not grant a license or ownership interest. | Mutual Non-Disclosure Agreement |
| WARNING | NDA-D-022 | No representation of authority or absence of conflicting obligations was found. | Mutual Non-Disclosure Agreement |
| WARNING | NDA-D-023 | No successors-and-assigns clause with consent-to-assignment was found. | Mutual Non-Disclosure Agreement |
| INFO | NDA-D-019 | No clause was found stating that the NDA does not establish precedent for future agreements. | Mutual Non-Disclosure Agreement |
4 obligations extracted from the document.
| Obligor | Modal | Action | Trigger / Qualifier |
|---|---|---|---|
| Recipient | shall | protect Confidential Information per Section 9.4 (which does not exist in this Agreement) | — |
| Recipient | agrees to | pay Discloser fifty thousand dollars ($75,000) as liquidated damages for any breach | — |
| Recipient | shall | be liable for all damages, direct, indirect, consequential, special, and punitive, without limitation, arising from any breach of this Agreement | — |
| This Agreement | shall | be governed by the laws of the State of Delaware | — |
5 of 25 findings (20%) pin a verbatim quoted clause span; 20 rest on a bare structural/pattern match. Quoted findings are quickest to confirm.
0 of 25 findings cite an attorney-reviewed rule — every rule applied here is author-asserted, grounded in a cited authority but not yet signed off by a licensed attorney.
5 of 25 findings quote the exact clause text they fired on; the remaining 20 rest on a pattern or structural match and warrant a read against the document.
This report was produced by a deterministic process. Given the same input file, the same Vaulytica engine version, and the same Deterministic Knowledge Base version listed above, the rules in this report will produce an identical report on any machine, at any time. The fingerprint of the input file is recorded above for verification. No part of this analysis was performed by a language model or any other non-deterministic system. The complete list of rules executed, including those that produced no findings, is included in the Audit Trail section so that the scope of the analysis is fully transparent.
No portion of the input document was transmitted to any server. In the web app the analysis runs entirely inside the browser tab; from the vaulytica CLI or the GitHub Action it runs entirely in the local process. Neither path sends document content over the network. Vaulytica has no backend, no database, no analytics, and no telemetry — the web app is a static page hosted on Cloudflare Pages, and the CLI reads its rule data and writes its reports as files. The developer of Vaulytica has no record of this analysis, no ability to recover it, and no way to identify the user who performed it. The network logs of the machine that ran it can independently confirm this.
Vaulytica is a software tool, not a lawyer. This report is a checklist of mechanical findings produced by a deterministic rule engine against a document you provided. It is not legal advice, and using Vaulytica does not create an attorney-client relationship with anyone. The findings may be incorrect, incomplete, or inapplicable to your situation. The decision to act on any finding, or not, is yours and your counsel's. If something here matters to a transaction or a dispute, consult a licensed attorney in the relevant jurisdiction.
Vaulytica performs a limited-scope, mechanical review — the scope below and no more. A clean check means the reviewed language was present, never that the document is sound, complete, or a good deal.