Vannus / Catalog / Harvey AI

Harvey AI

Vannus records that this vendor routes across several model providers — not captured by one. Every finding below is quoted to the vendor’s own document, or marked not disclosed where the vendor publishes nothing.

Determination
Contracts with Harvey AI Corporation (United States) — within reach of US legal process.
harvey.ai · read 2026-09-20
read from a master agreement
Contracting entity
Harvey AI Corporation
Jurisdiction
United States
Governing law
The law depends on where the customer is. EEA, Swiss and UK customers get the laws of England and Wales. Everyone else gets the laws of the State of California and the United States. Conflict-of-laws rules and the UN Convention on the International Sale of Goods are excluded. Disputes go to binding arbitration: a sole arbitrator in London under ICC Rules for EEA, Swiss and UK customers, and a sole arbitrator in San Francisco under JAMS Streamlined Rules for everyone else. Disputes above $250,000 go to a three-arbitrator panel at the same seat.
US corporate control
The contracting entity is a US entity, so US law may have legal reach over it and the data it controls. the rule
Depends on
The agreement is under a governing law that depends on where the customer is based.

AI assistant for legal research, contract analysis, and due diligence

legal, research, compliance
What the vendor's own documentation says
expanding its platform to incorporate leading foundation models from Anthropic, Google DeepMind, and OpenAI
harvey.ai ↗ Vendor-sourcedQuote last confirmed 14 Sep 2026; the house has paused automated re-reading of its host until it reads its terms or rules, so it is not re-checked
Who controls it
US corporate controlYes — a US parent or US contracting entity is on the public record · clause read 20 Sep 2026; the house has paused automated re-reading of its host until it reads its terms or rules, so it is not re-checked
Contracting entityHarvey AI Corporation
Governing lawThe law depends on where the customer is. EEA, Swiss and UK customers get the laws of England and Wales. Everyone else gets the laws of the State of California and the United States. Conflict-of-laws rules and the UN Convention on the International Sale of Goods are excluded. Disputes go to binding arbitration: a sole arbitrator in London under ICC Rules for EEA, Swiss and UK customers, and a sole arbitrator in San Francisco under JAMS Streamlined Rules for everyone else. Disputes above $250,000 go to a three-arbitrator panel at the same seat.
Trains on your dataNo — on the vendor's default plan

This page gives the finding and links the document it comes from. The AI Subprocessor Jurisdiction Report ($299) quotes the clause this finding rests on, and the clause for each other vendor in your stack where the report can quote one, in one dated document you can hand to an auditor.

Training and retention posture varies by plan. What we publish above describes the vendor’s default plan; enterprise, team and API agreements frequently differ, often materially, and a contract can override the published default entirely. Check your own plan and contract before relying on this row.

On U.S. CLOUD Act reach specifically: the statute reaches a provider subject to U.S. jurisdiction over data in its possession, custody or control. Corporate control is a strong indicator of that and it is what we can evidence from published documents — but it is not the whole test. A company founded outside the U.S. can still contract through a U.S. entity or run substantial U.S. operations. Treat this as a starting point for your own review, not a legal determination, and take advice on anything that matters.

Record history

This is the history of our record of this vendor: when we first recorded it; each time one of these changed: the determination sentence, the contracting entity, its country, the governing law, the US-control finding, what the answer depends on, the note beside the finding, or the cited document; and each time the vendor's document was read again and none of them changed. A change only in capitals, punctuation or spacing is not a line, and neither is a first document title. A line names what changed and does not repeat what those fields said before; the determination above says what they say now. Where the determination sentence itself changed, the line shows the earlier sentence too, marked as before, with why it changed. The automated re-check's latest result is not a line here; it is printed beside the clause above. A change here may be the vendor changing its document or us correcting our reading of it, and a line says which only where the record shows it; otherwise it says the cause is not established. Each line is today's reading of the record as it stood on that date. A reading we later found its citation does not carry was withdrawn, and is not repeated here. This history as data.

Cite this record
Harvey AI: “Contracts with Harvey AI Corporation (United States) — within reach of US legal process.”
Vannus, https://vannus.co/tool/harvey-ai
harvey.ai · read 2026-09-20

How you may reuse this record

How this entry is set

Vannus records, from the vendor's own published documents, the legal entity a customer contracts with, the country that entity sits in, and the governing law of its terms — and whether the vendor runs its own model or resells someone else's. Each finding is quoted to its source and dated, or marked not disclosed where the vendor publishes nothing. No paid placement on a record, in the catalog or in search — affiliate status is walled off from the record, enforced by a test in the build. See the methodology →

Related tools we record
Visit Harvey AI ↗ Check your whole stack →
Vannus (PRAXIS AI LLC) · entry as of the latest catalog build · all 376 tools · MCP for assistants
Work here and think we got something wrong? Corrections and right of reply → — free, no account, and we publish your response next to our entry.