Free contract review in seconds.
Every finding cited. No AI. Nothing uploaded.

Drop an NDA, MSA, lease, DPA or employment contract and see what is missing, what is one-sided, and what is due when — each finding quoted from your document and tied to the rule and the statute or practice source behind it. It is a deterministic rule engine, so the same file always gives the same report; it never leaves your browser; and it is free forever under MIT. No account needed.

Drop a PDF, DOCX or text file — up to four at once.
Read locally in this tab — nothing is uploaded. Drop a pair and they are also checked against each other.

Multiple files? Drop a folder or No file?

What you get back.

Not a chatbot summary — a short list of what to raise, each item showing its evidence. See a real sample →

A page that says what to raise and why

Each item opens to the clause it is about, the reason it matters, the rule's suggested change and its source. Nothing to download first.

Your draft back with comments

Drop a .docx and get it back with each item as a Word comment on its clause. Your text is unchanged.

Everything else, if you want it

A Word report, dates for your calendar, spreadsheets of obligations and fixes, and a verification certificate. Drop related documents together and conflicts between them are listed too.

Free reviews by document.

What Vaulytica checks, and why it matters, for the documents people sign most.

Comparing AI tools? How deterministic review differs from AI contract review.

What it reviews.

286 document types, each with its own playbook. The checks that run are the ones that belong to the document in front of you, so a plain NDA is never flagged for missing GDPR clauses — and a document matching none of them is reported as unmatched rather than given a confidently wrong verdict.

Browse every document type and exactly what is checked in it →

See every document type

Details.

Everything below is here because an attorney evaluating this tool will want it — and folded away because nobody should have to scroll past it to use the thing.

What it checks in every document

131 rules at launch across twelve categories — 220 more in v3, 771 more in v4, 621 more in v5, 92 more in v6, 111 more in v7 (1,946 in total). Every finding cites the rule by id; legal assertions cite a statute or regulator by URL, drafting-practice findings cite their practice source.

Structural & formal

Party blocks, signatures, defined terms, cross-references, numbering, template placeholders.

STRUCT-001STRUCT-003STRUCT-005STRUCT-007STRUCT-009STRUCT-011

Financial terms

Word/numeral mismatches, currency consistency, usury, payment terms, MFN, caps.

FIN-001FIN-002FIN-003FIN-004FIN-005FIN-007

Temporal

Impossible dates, auto-renewal notice windows, survival, cure periods, post-expiry references.

TEMP-001TEMP-004TEMP-005TEMP-006TEMP-008TEMP-010

Risk allocation

Indemnity presence + mutuality + caps, LoL with exceptions, consequential waivers, insurance.

RISK-001RISK-002RISK-004RISK-005RISK-009RISK-013

Choice & venue

Governing law, forum, foreign-venue enforceability, arbitration, class waivers, jury waivers.

CHOICE-001CHOICE-004CHOICE-005CHOICE-006CHOICE-007CHOICE-008

Dark patterns

Unilateral modification rights, buried auto-renewal notices, asymmetric fee-shifting, forced arbitration.

DARK-001DARK-002DARK-003DARK-004

Before you send it

What the file carries besides its words: tracked changes, comments, hidden text, names in its properties, account and ID numbers, and redactions that can be lifted (a box drawn over PDF text, text colored to match its background, a redaction mark never applied). Each is reported by where it is; the covered words are never shown.

HANDOFF-001HANDOFF-005HANDOFF-006HANDOFF-007

How it works

Your file goes in on the left, runs through a deterministic rule engine fed by the Knowledge Base, comes back out on the right as a Word document. Nothing else moves.

Why there is no AI in it

Every other contract tool leans on a language model: paste your contract, the AI summarizes, the AI flags risk, the AI suggests redlines. The output is fluent, confident, and different every time you run it. A junior associate can use that for research. A senior partner cannot sign off on it, an auditor cannot trace it, and a client cannot reproduce it. It is, by construction, uncitable.

Vaulytica does the work those tools cannot: the same cited checks, run the same way every time. The professional failure mode in contract review is not "I did not understand the indemnity clause." It is "I read eighty pages at midnight and missed that the auto-renewal triggers sixty days before expiry rather than thirty." A deterministic checklist runner applies the same checks at midnight as at noon, and the report lists every one it ran.

What it does not do

  • It does not give legal advice. It is a software tool. If something here matters, hire a lawyer.
  • It does not claim an accuracy it has not measured. There is no precision or recall figure on real contracts. Where it is known to be wrong is published.
  • It does not replace your judgment. It finds mechanical things consistently. The hard calls are still yours.
  • It does not use AI. Not a model, not a copilot, not "powered by." A probabilistic answer cannot be cited. The whole point of this is the opposite.
  • It does not draft for you. Where a rule has an attributed public model clause, the report shows that clause as a reference — never a generated redline.
  • It does not see your data. There is no server. Your contract never leaves the tab.

Your privacy, and how to verify it

Vaulytica runs entirely in your browser. There is no server to send your file to, because there is no server. The site is a static page on Cloudflare Pages, the code is on GitHub under MIT, and there is no analytics, no telemetry, no error reporting, and no fonts from CDNs. Every byte your browser fetches comes from vaulytica.com.

Verify it in about thirty seconds:

  1. Open this page in Chrome, Firefox, or Safari.
  2. Press F12 (or ⌥⌘I on macOS) to open DevTools.
  3. Click the Network tab and check "Disable cache."
  4. Reload once to capture the initial asset loads, then click Clear.
  5. Drop a contract and watch the tab during analysis. You may see the app fetch its own rule data and playbooks from this same origin — every request is a GET with no body, and nothing from your document appears in any of them.

For court and ethics compliance

Courts increasingly regulate generative-AI use in filings: the Ropes & Gray AI Court Order Tracker lists 300+ judge- and court-level directives, and the Legal AI Governance tracker counts roughly 113 orders that bind attorney filings — most requiring disclosure of AI use, verification of AI output, or a certification that neither occurred (New York's court-system-wide 22 NYCRR Part 161 took effect June 1, 2026). Privilege case law on consumer AI tools is diverging, not settled — compare United States v. Heppner (S.D.N.Y. 2026, no privilege for material run through a public generative-AI tool) with Warner v. Gilbarco (E.D. Mich. 2026, no waiver) — and ABA Formal Opinion 512 puts the verification duty on the lawyer.

Vaulytica can make the no-generative-AI certification provable rather than asserted: every report can ship with a one-page verification certificate (Word + JSON) stating the engine and knowledge-base versions, the input's SHA-256, the result hash, and that the analysis was a deterministic rule evaluation with no generative-AI, machine-learning, or probabilistic component — performed locally, with no document content transmitted. The certificate carries its own tamper-evident hash, and anyone can re-run vaulytica verify <report> <file> to reproduce the analysis exactly. It certifies what this tool did — never your overall compliance; the reviewing attorney remains responsible for verifying findings and meeting the applicable orders and professional-conduct rules.

Where the rules come from

Every rule cites at least one of these. Every source is free and public. A citation is not the same as a lawyer vouching for the rule: separately, a legal-basis ledger records which rules a licensed attorney has independently signed off on — 0 so far. That is the honest starting point, published so you can watch the number climb rather than take a marketing claim on faith.

SEC EDGAR public domain

Real-world clause corpus sampled from EX-10 attachments to 10-K, 10-Q, 8-K, and S-1 filings.

efts.sec.gov

Cornell LII free use

Cross-references between the UCC and each state's enacted version, and state-code lookups.

law.cornell.edu

Common Paper CC BY 4.0

Canonical balanced-default reference clauses for NDA, SaaS, MSA, SOW, DPA, and more.

commonpaper.com

CUAD CC BY 4.0

510 contracts, 13,000+ expert annotations, 41 clause categories. Trains the deterministic classifier.

atticusprojectai.org

LEDGAR CC BY 4.0

80,000+ provisions across 100 clause categories. Broader training set for the classifier.

huggingface.co/lex_glue

US Code (LRC) public domain

Official US Code in USLM XML: Titles 9, 11, 15, 17, 18, 28, 35, and 41.

uscode.house.gov

eCFR public domain

Electronic Code of Federal Regulations: FTC (16), CFTC (17), IRS (26), Labor (29), HIPAA (45).

ecfr.gov

govinfo public domain

Bulk Federal Register, CFR, Public Laws, and Statute Compilations in XML.

govinfo.gov

Uniform Law Commission free use

UETA, UCC, UTSA, RUFADAA, and other uniform-act citations.

uniformlaws.org

awesome-legal CC0

Curated set of public legal templates: GitHub's BEIPA, Cooley offer letters, YC SAFEs.

github.com/ankane/awesome-legal

Atticus Project CC BY 4.0

Clause-type definitions and the broader Open Contract Dataset.

atticusprojectai.org

Open-Agreements MIT + CC BY

Fillable DOCX builds of Common Paper, Bonterms, and OpenAgreements templates.

github.com/open-agreements

Questions

Is this legal advice?

No. Vaulytica is a software tool. It is not a lawyer, it does not give legal advice, and using it does not create an attorney-client relationship with anyone. If something here matters, hire a lawyer.

Can I trust the report?

The report is the output of a deterministic rule engine, not a model. Given the same input file, the same engine version, and the same Deterministic Knowledge Base version, you will get the same report. Every finding quotes the clause it fired on, names the rule by id and version, and cites its source; findings that assert what the law is cite a statute or regulator by URL, and drafting-practice findings cite their practice source instead. The audit trail at the end of every report names every rule that ran, including the silent ones.

Do you train models on my data?

There is no server. Your contract never leaves the tab. Nothing is logged, nothing is uploaded, nothing is retained.

What document types are supported?

286, listed in full under "What it reviews" above — NDAs, MSAs and SOWs, SaaS agreements, DPAs and SCCs, HIPAA BAAs, employment agreements, commercial and residential leases, M&A documents, equity and financing instruments, wills and trusts, court filings, and compliance policies. The structural and financial rules run against any agreement.

How is the data kept current?

The Deterministic Knowledge Base is rebuilt weekly via a public GitHub Action that fetches from SEC EDGAR, the US Code, the eCFR, govinfo, Common Paper, CUAD, LEDGAR, and other free public sources. Every entry records its source URL, retrieval date, and license. The current version is stamped on every report.

Can I use my firm's own standard?

Yes. Load a custom playbook and its rules run alongside the catalog; findings from your standard are marked as yours in the report, so "our standard flagged this" is never confused with "Vaulytica's catalog flagged this."

Can I add a rule?

Yes. See docs/adding-a-rule.md in the repository. Every new rule must cite at least one Knowledge Base entry by id, include a positive and negative test fixture, and pass the deterministic regression check.

What if I find a bug?

Open an issue on GitHub. The repository is public and MIT-licensed. Reproducible bugs with a redacted fixture contract are fixed fast.

Why MIT license?

MIT is the most permissive license most attorneys recognize on sight, and it removes any friction for someone who wants to fork the project, run it internally at a firm, or build a paid wrapper around it. The license invites that.

What about other languages?

English today. Legal language is jurisdiction-specific and "just translate it" is wrong. A future contributor with the right expertise can add another jurisdiction-language pair as a complete unit.

Stop hoping the checklist got run.
Show that it did.