, Nils-Erik Jansson
Claude for Legal compared with Harvey and Legora
Claude for Legal, Harvey and Legora are three AI tools for legal work, each built for a different starting point. Claude for Legal adds legal plugins, artifacts and connectors to Claude. Harvey and Legora are platforms built for legal work. This guide is written for a legal department or law firm outside Sweden and describes each tool from its vendor's own pages, read on 10 November 2026.
Updated by Nils-Erik Jansson
Claude for Legal, Harvey and Legora are each built for a different starting point, and the choice depends on what your organisation wants the tool to be. HOVR Legal offers setup of Claude for Legal. The comparison is based on the vendors' own pages, not on tests.
What each tool is, according to its vendor
Claude for Legal is Anthropic's offering for legal work in Claude, with ready-made legal artifacts for tasks such as tabular review, horizon scanning, intake and playbook review [1]. In May 2026 Anthropic announced twelve practice-area plugins, among them Commercial, Corporate, Employment, Privacy and Litigation, and each starts with a setup interview to learn the team's playbook and risk settings [2]. Named connectors include iManage, NetDocuments, Ironclad, Docusign, Box and Thomson Reuters, and Claude works inside Word, Outlook, Excel and PowerPoint [1] [2]. The legal page names the Team and Enterprise plans [1].
Harvey describes itself as AI software for legal and professional services, built for law firms and corporate legal teams [7]. Its platform includes agents, Vault for storing and analysing documents, Knowledge for legal, regulatory and tax research, and shared workspaces called Spaces, and its apps cover contract intelligence, horizon scanning, intake, and facts and chronologies [7]. A connector library links other tools to Harvey through MCP [7]. Harvey says it uses models from Anthropic, OpenAI and Google, with Mistral also available in the EU [9].
Legora describes itself as collaborative AI that helps lawyers review and research faster, draft smarter and advise with precision, and calls its Legora aOS the agentic operating system for legal work [10]. Its products include an Agent that plans, executes and reviews tasks, Monitors that scan regulation and flag relevant changes, Tabular Review, Workflows, Legal Research, Skills and Intake [10]. It has add-ins for Word and Outlook and a set of integrations [10]. Its EU sub-processor list names Microsoft, AWS, Google and OpenAI as providers of AI models [12].
What the vendors state on data
The table sets out what each vendor's pages state. Where a page does not state something, the cell reads: the page does not state this, so ask the vendor.
| Question | Claude for Legal | Harvey | Legora |
|---|---|---|---|
| Retention | Enterprise owners set an organisation-wide retention period; custom retention is an Enterprise feature [3] [6]. Deleted conversations leave back-end storage within 30 days [5] | Customers set retention policies and can delete data at any time [8] [9]. Harvey requires zero data retention by model providers [8] | Customers set and manage retention periods [11]. Data is permanently deleted after the contract ends, with an export available first [11] |
| Training on customer data | None by default on Team and Enterprise [3] [6] | Inputs, outputs and uploaded documents are not used to train underlying models [8] [9] | Data is not used to train or fine tune any AI models [11] |
| Certifications | SOC 2 Type I and Type II, ISO 27001:2022, ISO/IEC 42001:2023, HIPAA-ready configuration [4] | SOC 2 Type II, ISO 27001, ISO 27701, ISO 42001, AIUC-1 [8] | SOC 2 Type II, ISO 27001, ISO 42001 [11] |
| Data location | On Team and Enterprise, data is stored in the US, and traffic may by default be routed to the US, Europe, Asia and Australia [14]. Regional processing is available through AWS Bedrock, Google Cloud Vertex AI and Microsoft Foundry [13] | In-region in the EU or Switzerland, the US, or Australia [8] [9] | EU sub-processors listed with EU/EEA residency [12]. The security page mentions flexible storage options [11] |
| Price | Team from 20 US dollars per seat per month billed annually; Enterprise 20 US dollars per seat per month plus usage at API rates, minimum 20 seats [3] | Depends on seats, products and contract terms; on average several hundred dollars per user per month [9] | The page does not state this, so ask the vendor |
What you add yourself, whichever tool you choose
This applies equally to Claude for Legal, Harvey and Legora. A vendor delivers the tool and its security commitments. Your organisation still has to decide the rest.
- Your own rules: which matters and which kinds of data stay out of the tool, and who may use it for what.
- A playbook: your positions on the clauses you negotiate most, written so a tool can apply them. See how to write a contract review playbook.
- A data protection assessment: the data processing agreement, the transfer assessment for every sub-processor in the chain, and a DPIA where one is required. See also the transfer impact assessment guide.
- Settings and review: retention periods set to match your policy, and a routine for checking output before it is used.
When each fits
Claude for Legal fits if your organisation wants one general tool for the whole company and wants to add legal plugins, artifacts and connectors to it [1] [2]. It also fits if you are ready to describe your own playbook and risk settings in the plugin setup interview [2].
Harvey fits if your organisation wants a platform built for legal and professional services, with document storage, research and apps for contract and regulatory work [7]. It also fits if you need data kept in-region in the EU, Switzerland, the US or Australia [8].
Legora fits if your organisation wants a platform built for legal work, with an agent, tabular review and monitoring of regulatory change [10]. It also fits if your lawyers work mainly in Word and Outlook and want the tool there [10].
How to choose
Ask the same questions of every vendor, and put the answers in writing: retention, training, certifications, data location, sub-processors and price. Then see each tool work on your own documents. A demo on the vendor's sample material tells you little about your contracts; see a demo on your own contracts.
In a technology selection, every tool is assessed against the same protocol. The protocol is described under technology selection.
How HOVR Legal works with this
If you are choosing between two or more of these tools, HOVR Legal runs it as a technology selection: the questions before the demo, a demo on your own contracts, and a pilot against fixed criteria. If you have chosen Claude, see Claude Team or Enterprise.
Frequently asked questions
- Can a legal department use more than one of these tools?
- Yes. Anthropic lists Harvey among the legal platforms with a connector to Claude [2]. Whether two tools make sense depends on which part of your work is largest and on your budget. Run the same questions and the same demo on your own contracts for each tool you consider.
- Do the vendors train their models on our data?
- All three state that they do not by default. Anthropic states no training by default on Team and Enterprise [3]. Harvey states that it does not use inputs, outputs or uploaded documents to train underlying models [8]. Legora states that it will not use your data to train or fine tune any AI models [11]. Put the commitment in the contract as well.
- Who is responsible for data protection and confidentiality?
- You are, whichever tool you choose. Anthropic's own guidance on legal work says that whether a configuration meets your obligations is a question for your own counsel [6]. The data processing agreement, the transfer assessment and the retention settings are your work; see the data protection checklist.
Statements about Anthropic's terms and products were read on Anthropic's pages on 10 November 2026 and are checked at the start of every engagement.
Sources
- [1]Claude for legal, Anthropic, read 2026-11-10
- [2]Claude for the legal industry, Anthropic, 12 May 2026, read 2026-11-10
- [3]Pricing, Anthropic, read 2026-11-10
- [4]What certifications has Anthropic obtained?, Anthropic Privacy Center, covers commercial products; read 2026-11-10
- [5]How long do you store my organization's data?, Anthropic Privacy Center, read 2026-11-10
- [6]Using Claude for legal work: privilege, confidentiality, and how to think about configuration, Anthropic Help Center, read 2026-11-10
- [7]Harvey, home page, read 2026-11-10
- [8]Security, Harvey, read 2026-11-10
- [9]Harvey FAQs: security, access, pricing and more, Harvey Help Center, read 2026-11-10
- [10]Legora, home page, read 2026-11-10
- [11]Security and compliance, Legora, read 2026-11-10
- [12]Pre-approved sub-processors, EU, Legora, read 2026-11-10
- [13]Regional compliance, Anthropic, read 2026-11-10
- [14]Where are your servers located?, Anthropic Privacy Center, read 2026-11-10
Insights on the topic
Back to Claude for Legal
More under Claude for Legal
- Claude for Legal setup for the in-house legal team
Fixed-scope engagement: plan and contract, data protection, playbook and escalation for Swedish law, connectors, policy, training, follow-up on real matters.
- Law firm package: Claude for Legal for Swedish firms
Claude for Legal for Swedish law firms: data protection documented under the Swedish Bar Association's guidance and an environment set up for client work.
- Claude Team or Enterprise for a legal department
Claude Team or Enterprise for a legal department: retention periods, routing, logs, seat minimum and price, and what five lawyers can buy.
- Putting a contract review playbook into Claude
How a contract review playbook is loaded into Claude for Legal: where it sits, what goes in beside it, the instruction, and what the lawyer still does.
- Claude for Legal compared with Legora, Juno and Lexnova
A comparison for lawyers working in Sweden: what Claude for Legal, Legora, JUNO AI and Blendow's tools are built for, and when each fits.
- Projects, skills, plugins and connectors in Claude
What a project, a skill, a plugin and a connector are in Claude, and what goes where: playbook, templates, rules, systems.
- Contract renewals with AI: tracking without a CLM
How a legal department builds a watch list of renewals and notice periods from its contract archive with an AI tool, and what the list can and cannot do.