---
title: "Juro (Juro Online Limited)"
url: "https://ailawframework.com/software/juro"
type: "software_profile"
site: "AI Law Framework"
id: "juro"
vendor: "Juro Online Limited"
category: "Legal-specific"
segment: "Contract review and CLM"
confidence: "medium"
last_reviewed: "2026-09-21"
---

# Juro (Juro Online Limited)

> UK-based AI-native contract lifecycle platform for in-house teams: templates, AI review/redline, e-sign and repository, with optional MCP connectors to ChatGPT and Claude.

Canonical page: https://ailawframework.com/software/juro  
Last reviewed: 2026-09-21

Site index for agents: https://ailawframework.com/llms.txt

Plan covered: Juro SaaS CLM (create, negotiate, sign, store) under the public DPA plus unpublished MSA. ChatGPT/Claude MCP connectors are optional and in beta. AI Managed Service (OpenAI/Claude extraction) needs separate review.

## Capabilities

- Contract drafting
- Contract review and redlining
- Document automation
- Document summarisation
- Knowledge search
- Agentic workflows

## Key facts

| Fact | Value |
| --- | --- |
| Deployment | SaaS |
| Hosting regions | European Union / EEA |
| Australian region | No |
| Model providers | Google Cloud generative AI, OpenAI (MCP and AI Managed Service), Anthropic (MCP and AI Managed Service) |
| Assurance | SOC 2 Type II, Cyber Essentials |
| Training on customer content | No |
| Retention | DPA: customer can delete in-product during the term; after termination, up to 60 days' recovery period then Juro deletes remaining Customer Data as soon as reasonably practicable unless law requires storage. Privacy does not publish a numbered prompt-retention period. |
| Integrations | Microsoft Word, Slack, Google Drive, HubSpot, Salesforce, DocuSign, ChatGPT (MCP, beta), Claude (MCP), Zapier, Greenhouse, Ashby, REST API |
| Legal content coverage | Customer templates and repository. No licensed Australian primary-law citator described. |
| Pricing | Pricing page is a calculator without a published list. ChatGPT integration page: Slack, Email, Google Drive and Word on all plans; Growth adds HubSpot, Claude, DocuSign, Greenhouse, Zapier, Ashby; Enterprise adds Salesforce, REST API and webhooks. ChatGPT MCP still in beta. |
| Australian presence | Unknown. HQ London; processing facilities also Riga. Platform hosting listed as EEA (AWS, MongoDB). No named Australian customer or AU region found. |
| Website | https://juro.com |

## What the research found

| Topic | Status | Finding | Open question | Sources |
| --- | --- | --- | --- | --- |
| Plan, contracting entity and modules | Public claim only | Contracting entity is Juro Online Limited (London EC1R 0DS; ICO ZB407649). Public DPA incorporates an unpublished MSA. Modules: create/approve/negotiate/sign/store plus AI Assistant, AI Review, AI Extract/Draft (pricing toggles), Operator. Optional MCP to ChatGPT and Claude; optional AI Managed Service using OpenAI custom GPT and/or Claude. | Confirm the MSA version, which AI modules and MCP connectors are on the Order, and whether AI Managed Service is in scope. | [Juro — home](https://juro.com/); [Juro Data Processing Agreement](https://juro.com/terms/dpa); [Juro Privacy Policy (includes subprocessors)](https://juro.com/privacy); [Juro — ChatGPT / MCP integration](https://juro.com/integrations/chatgpt) |
| Deployment model | Public claim only | SaaS web app. Privacy lists AWS and MongoDB as platform hosting in the EEA. Offices in London and Riga. No on-premises option was found. Google authentication region follows the customer's Google account (US or EEA). | Name the AWS and MongoDB regions for our tenancy and whether an Australia or UK-only option exists. | [Juro Privacy Policy (includes subprocessors)](https://juro.com/privacy); [Juro — home](https://juro.com/) |
| Product features in scope | Public claim only | End-to-end CLM: templates, AI intake/review/redline, e-sign, repository Q&A (Operator), Word/Slack/CRM integrations. Homepage demo warns AI may be inaccurate and not to paste confidential info into the public demo. | Which of AI Review, AI Draft, AI Extract, Operator, e-sign and each connector will be enabled on our plan? | [Juro — home](https://juro.com/); [Juro — pricing](https://juro.com/pricing); [Juro — ChatGPT / MCP integration](https://juro.com/integrations/chatgpt) |
| Governing law and Australian coverage | Not confirmed | The public Terms HTML scrape did not yield MSA governing-law text. DPA SCCs: if the Agreement is not EU-member-state law, SCCs are Irish law, or English law if the Agreement is UK law. UK GDPR trust page exists. No Australian law option or named AU customer was found. | Which law and courts apply to our MSA, and will you accept Australian law or at least a non-exclusive Australian forum? | [Juro Data Processing Agreement](https://juro.com/terms/dpa); [Juro Trust Center](https://juro.com/trust); [Juro Terms (page; MSA body not extracted)](https://juro.com/terms) |
| Licence, term and price | Public claim only | Pricing page is an interactive calculator showing $0 until configured; no public list. Integration page describes All / Growth / Enterprise connector bundles. DPA refers to Fees and Initial Term / Renewal Term in the Agreement. | Provide an itemised quote for our user count, AI modules, Growth vs Enterprise connectors, term and renewal. | [Juro — pricing](https://juro.com/pricing); [Juro — ChatGPT / MCP integration](https://juro.com/integrations/chatgpt); [Juro Data Processing Agreement](https://juro.com/terms/dpa) |
| Word, DMS and identity integration | Public claim only | Word, Slack, Email, Google Drive on all plans; Growth/Enterprise add CRM, DocuSign, Zapier, Salesforce, API. ChatGPT and Claude via MCP (ChatGPT still beta). Google SSO; Ory for MCP OAuth. No iManage/NetDocuments connector was found. | Demonstrate Word round-trip, our CRM, SSO/MFA and whether a DMS connector exists on Enterprise. | [Juro — ChatGPT / MCP integration](https://juro.com/integrations/chatgpt); [Juro Privacy Policy (includes subprocessors)](https://juro.com/privacy); [Juro — home](https://juro.com/) |
| Support channels and hours | Public claim only | Privacy: live chat, phone and email for support. London HQ. No public AEST coverage hours. Gong may record sales/customer calls. | State severity definitions, response times in AEST/AEDT, and whether Gong recordings of our calls are optional. | [Juro Privacy Policy (includes subprocessors)](https://juro.com/privacy); [Juro — home](https://juro.com/) |
| Measured quality and hallucination evidence | Public claim only | Homepage: AI may produce inaccurate information. Operator cites sources. No independent hallucination benchmark was found. Marketing claims 2.5 million contracts on the platform. | Share measured redline-acceptance and citation-error rates, including known failure modes. | [Juro — home](https://juro.com/) |
| Task fit for Australian legal work | Public claim only | Fit is in-house commercial contracting (templates, third-party paper review, e-sign, repository). Not a licensed Australian research product. Hosting is EEA, not Australia. | Will our tenancy keep MCP/ChatGPT/Claude off by default, and is the product intended for law-firm client-matter work or only in-house? | [Juro — home](https://juro.com/); [Juro — ChatGPT / MCP integration](https://juro.com/integrations/chatgpt) |
| Who is controller, and client-matter authority | Public claim only | Privacy: Juro is controller of account/usage data and processor of data customers put in (users, counterparties, documents). DPA: Juro processes Customer Data only on Instructions (the Agreement). Customer remains responsible for data-subject rights using in-product tools. | Confirm the DPA is incorporated in our MSA and that we remain controller of contract content. | [Juro Privacy Policy (includes subprocessors)](https://juro.com/privacy); [Juro Data Processing Agreement](https://juro.com/terms/dpa) |
| Foundation-model provider | Public claim only | Privacy: Google Cloud generative AI powers some newest AI features (auth US or EEA by Google account). Optional OpenAI MCP and Anthropic MCP (residency follows the customer's OpenAI/Claude policy). AI Managed Service: OpenAI custom GPT and/or Claude; Anthropic locations include US, UK, EEA plus other countries for safety/support. No customer model picker for the core Assistant was described. | Name every model that will see our contracts on our plan, their regions, and whether MCP and Managed Service are disabled. | [Juro Privacy Policy (includes subprocessors)](https://juro.com/privacy); [Juro — ChatGPT / MCP integration](https://juro.com/integrations/chatgpt) |
| Subprocessors and subprocessors list | Public claim only | Privacy is the DPA-referenced subprocessor list. Platform hosting: AWS and MongoDB in the EEA; Algolia also named on the trust footer. Optional MCP: OpenAI, Anthropic, Ory. DPA: New Subprocessor objection process (30 days then 14 days to terminate for a data-protection-law objection). | Provide the current full customer-data subprocessor table with regions and confirm 30-day objection applies to our Order. | [Juro Privacy Policy (includes subprocessors)](https://juro.com/privacy); [Juro Data Processing Agreement](https://juro.com/terms/dpa) |
| Training and secondary use of customer content | Public claim only | Privacy (Improving Juro): if you use the AI Assistant, Juro does not — and does not allow its AI technology providers to — use your data to train any models, except models used only by your business. That exception is a customer-specific model, not a global training opt-in. MCP and Managed Service send data to OpenAI/Anthropic under those vendors' policies. | Confirm the no-training warranty applies to Operator, AI Review and Google Cloud gen-AI, and that no customer-only fine-tune will be built unless we order it. | [Juro Privacy Policy (includes subprocessors)](https://juro.com/privacy) |
| Feedback and evaluation use | Public claim only | Privacy lists improving Juro via testing, feedback platforms, heat mapping and research, with the AI Assistant no-training carve-out above. Gong records sales/customer calls for training and monitoring. DPA personnel access Customer Data only as necessary to comply with Instructions. | Can product-analytics and Gong recording of our account be contracted off, and is contract text excluded from 'improving Juro' research? | [Juro Privacy Policy (includes subprocessors)](https://juro.com/privacy); [Juro Data Processing Agreement](https://juro.com/terms/dpa) |
| Retention of prompts, documents and logs | Public claim only | DPA Term lasts until Juro deletes all Customer Data. In-term deletion via the product. After termination, up to 60 days' recovery then deletion as soon as reasonably practicable unless law requires storage. No public day-count for AI prompts or backups. | State retention for contracts, AI prompts/outputs, MCP logs, backups and Gong recordings. | [Juro Data Processing Agreement](https://juro.com/terms/dpa) |
| Deletion and certified erasure | Public claim only | In-term: in-product delete is an Instruction; Juro complies as soon as reasonably practicable. End of Term: 60-day recovery then delete remaining copies unless law requires storage. DPA also requires export functionality during the Term. No certificate-of-deletion clause was found. | What is the maximum time to delete including backups, and will you issue a deletion certificate? | [Juro Data Processing Agreement](https://juro.com/terms/dpa) |
| Vendor staff access to matter data | Public claim only | DPA: personnel and subprocessors access Customer Data only as necessary to comply with Instructions; confidentiality obligations; security training. Offices in London and Riga. AI Managed Service uses OpenAI/Claude to extract smartfields at the customer's request. | Is staff access logged, MFA-gated, limited to ticketed support, and available as an audit export? Which Riga roles can see contracts? | [Juro Data Processing Agreement](https://juro.com/terms/dpa); [Juro Privacy Policy (includes subprocessors)](https://juro.com/privacy) |
| SSO, MFA, roles and audit logs | Not confirmed | Google authentication is described. Trust/application-security pages exist but the scrape did not yield SSO/SCIM/MFA detail. DPA mentions Additional Security Controls without naming them in the extracted appendix beyond TLS/AES-256. | Does our plan include Entra/Okta SSO, mandatory MFA, RBAC and exportable audit logs? | [Juro Privacy Policy (includes subprocessors)](https://juro.com/privacy); [Juro Trust Center](https://juro.com/trust); [Juro Data Processing Agreement](https://juro.com/terms/dpa) |
| Encryption in transit and at rest | Public claim only | DPA Appendix 2: TLS for data in transit; AES-256 at rest. | Confirm TLS version in production, key custody in AWS/MongoDB, and whether customer-managed keys are available. | [Juro Data Processing Agreement](https://juro.com/terms/dpa) |
| SOC, ISO and other audits | Public claim only | DPA: Juro will maintain Cyber Essentials certification and an annual SOC 2 Type II report for Audited Services. Trust pages market SOC 2. ISO 27001 was not found in the DPA. Reports were not inspected in this pass. | Provide the current SOC 2 Type II and Cyber Essentials artefacts whose scope includes AI Assistant, Operator and MCP. | [Juro Data Processing Agreement](https://juro.com/terms/dpa); [Juro Trust Center](https://juro.com/trust) |
| Contract, DPA, liability and indemnity | Not confirmed | Public DPA is detailed (Instructions, SCCs, subprocessors via privacy policy, 60-day exit). The MSA/Terms page scrape did not return liability cap, IP indemnity or governing law. Evaluation terms exist separately for trials. | Provide the MSA liability cap, IP indemnity and confirmation the public DPA is incorporated without carve-outs for AI/MCP. | [Juro Data Processing Agreement](https://juro.com/terms/dpa); [Juro Terms (page; MSA body not extracted)](https://juro.com/terms) |
| Cross-border transfers and residency | Public claim only | AWS and MongoDB listed as EEA for contract data. Privacy: some facilities are outside the UK/EEA; SCCs in the DPA. Google gen-AI and Google auth: US or EEA. MCP follows the customer's OpenAI/Claude residency. Anthropic enterprise use lists US, UK, EEA plus other countries for safety/support. No Australian region. | Map every flow of our contract text (AWS region, Google gen-AI, MCP, Managed Service) and confirm APP 8 wording if we proceed from Australia. | [Juro Privacy Policy (includes subprocessors)](https://juro.com/privacy); [Juro Data Processing Agreement](https://juro.com/terms/dpa) |
| Breach notification | Public claim only | DPA 6.2: notify Customer without undue delay after becoming aware of a Data Incident; initial notice plus further detail as available; not an admission of fault. No 72-hour customer-notice number in that clause. | Write a 72-hour (or faster) customer-notice SLA into the Order, including the notification email. | [Juro Data Processing Agreement](https://juro.com/terms/dpa) |
| Unilateral term and product changes | Public claim only | DPA: Security Measures may be updated if not a material reduction. New Subprocessors: objection and possible termination as above. MSA change mechanism was not in the Terms scrape. | Will material AI-provider, MCP, hosting-region or liability changes require 30 days' written notice and a right to terminate without penalty? | [Juro Data Processing Agreement](https://juro.com/terms/dpa) |
| Export, termination and lock-in | Public claim only | DPA: export during the Term; after termination instruct return under the MSA; remaining data deleted after up to 60 days' recovery. Word/PDF originals remain wherever the customer stored them. | On termination, in what formats and within how many days can we export the repository and smartfields, and is deletion certified including backups? | [Juro Data Processing Agreement](https://juro.com/terms/dpa) |
| PMS, DMS and agent connectors | Public claim only | CRM, Slack, Word, Drive, DocuSign, Zapier, API. ChatGPT and Claude MCP let those assistants call Juro data (beta for ChatGPT). Operator takes actions and answers questions in-product. No iManage connector found. | Which connectors are in our Order, is MCP in or out, and which Operator actions are enabled? | [Juro — ChatGPT / MCP integration](https://juro.com/integrations/chatgpt); [Juro — home](https://juro.com/); [Juro Privacy Policy (includes subprocessors)](https://juro.com/privacy) |
| Open-web search and browsing | Not confirmed | No Juro page in this pass described the core Assistant browsing the open web. MCP uses ChatGPT/Claude, which may have their own web tools outside Juro's DPA. | Does Operator or AI Review send matter text to an open-web search index, and can ChatGPT/Claude web search be disabled when MCP is on? | [Juro — home](https://juro.com/); [Juro — ChatGPT / MCP integration](https://juro.com/integrations/chatgpt) |
| What the tool may do without a click | Public claim only | Homepage: Operator 'takes actions for you'. AI agents for review/redline. E-sign sends to counterparties when a user triggers send. MCP lets an external LLM query Juro when the user prompts in ChatGPT/Claude. | Which Operator/MCP actions require in-product confirmation, and is MCP disabled by default? | [Juro — home](https://juro.com/); [Juro — ChatGPT / MCP integration](https://juro.com/integrations/chatgpt) |
| Required lawyer review before client use | Public claim only | Public demo: AI may produce inaccurate information. No MSA clause requiring lawyer review was extracted (MSA unread). DPA does not itself impose human-in-the-loop on AI output. | Will you contract that AI Review/Operator output is not legal advice and must be lawyer-reviewed before counterparties receive a contract? | [Juro — home](https://juro.com/) |

## Notes

MSA/Terms body not extracted (nav-only scrape); SOC 2 and Cyber Essentials unread; no AU region; MCP ChatGPT in beta; Google Cloud gen-AI unnamed model; no named AU customers.

## Sources

- [Juro — home](https://juro.com/) (checked 2026-09-21)
- [Juro Terms (page; MSA body not extracted)](https://juro.com/terms) (checked 2026-09-21)
- [Juro Data Processing Agreement](https://juro.com/terms/dpa) (checked 2026-09-21)
- [Juro Privacy Policy (includes subprocessors)](https://juro.com/privacy) (checked 2026-09-21)
- [Juro — ChatGPT / MCP integration](https://juro.com/integrations/chatgpt) (checked 2026-09-21)
- [Juro — pricing](https://juro.com/pricing) (checked 2026-09-21)
- [Juro Trust Center](https://juro.com/trust) (checked 2026-09-21)

A product profile is research to support questions. It does not approve a product for any firm. Public product information supports questions; it does not approve a product for your firm. Verify the exact plan, settings and signed terms.