Juro vs Pactolane: how they compare in 2026

J
Juro profile
P
Pactolane profile
Last verifiedNovember 16, 2026
Verdict

Juro and Pactolane both run the whole contract lifecycle for a legal team and the colleagues who create contracts with it, from approved templates through approval, signature and a repository that AI can answer questions about. Juro, founded in London in 2016, is the older platform, with named customers such as Deliveroo, Funnel and Paddle, a SOC 2 Type 2 report and AI terms that set out training and liability. Its AI Review redlines against a playbook inside Microsoft Word, and Claude and Microsoft Copilot reach contracts through MCP. Pactolane, a Lyon company that began development in 2025, aims at small and mid sized companies. PactAI rates each contract from 0 to 100 against the playbook, and contract data stays on Google Cloud in France and Belgium. The clearest difference is buying. Juro quotes on monthly contract volume with unlimited users, while Pactolane publishes plans from €149 a month. Pactolane publishes no terms of service, and its ISO 27001 certification is still in progress.

Which one fits

Choose Juro if

  • Legal wants control while the business drafts. Templates and approval routes set by legal let sales, HR and procurement create agreements on their own.
  • Your reviewers work in Word. AI Review proposes redlines against the playbook inside Word, where each suggestion can be accepted, edited or skipped.
  • Your team already uses Copilot or Claude. Both reach Juro contracts through MCP, and Juro is an exclusive launch partner for Microsoft's legal MCP.
  • Your security review needs a report. Juro holds SOC 2 Type 2 certification and names its platform subprocessors in its privacy policy.
  • Headcount is growing faster than contract volume. Every plan includes unlimited users, and the quote follows contracts per month.

Choose Pactolane if

  • You want a price before a demo. Team costs €149 a month and Growth €499 a month, excluding tax, with free trials of seven and 14 days.
  • You want a French vendor with French hosting. Pactolane is a Lyon company, and contract data sits on Google Cloud in France and Belgium.
  • You want a quick read on each contract. PactAI rates a contract from 0 to 100 against your playbook and lists the clauses to revise before signature.
  • Sales runs on Pipedrive or Zoho. Pactolane imports contacts from Pipedrive and Zoho CRM as well as Salesforce and HubSpot.
  • Your own AI agents should create contracts under supervision. On the Scale plan, agent requests through the MCP server wait for a person to approve them and expire after 24 hours.

At a glance

Category
JuroContract Review & Drafting
PactolaneContract Review & Drafting
Founded
Juro2016
PactolaneNot published
Headquarters
JuroLondon, United Kingdom
PactolaneLyon, France
Last verified
JuroNov 3, 2026
PactolaneNov 16, 2026

All 15 axes, side by side

The same grid applied to every vendor in the index, graded from public sources. Hover a grade to see what the letter means on that axis.

AI Centrality

How much of the product is actually AI. Whether the machine learning is the mechanism the buyer is paying for or a feature layered onto conventional software, and whether the vendor is specific about which is which.

Juro
BB on AI CentralityThe models are the engine of a core capability, layered on a product that would still function without them as a document or workflow system.

Juro manages the complete contract lifecycle, from template creation and approval routing through negotiation, electronic signature, storage and tracking. Its AI Assistant combines AI Review, which redlines third party contracts against a playbook, AI Extract, which captures data from signed agreements, and AI Draft for editing. Juro also describes a review agent that checks incoming contracts against the rules and notifies legal only when terms fall outside them. Operator adds a conversational agent over the repository that answers with source citations and takes actions for users, and MCP connections let Claude and Microsoft Copilot work with the repository. The underlying contract platform also has a distinct function without those AI features, since legal teams control templates and approval processes and native electronic signature completes transactions independently of an AI response. The company began in 2016 and added AI to that established contracting workflow.

Pactolane
BB on AI CentralityThe models are the engine of a core capability, layered on a product that would still function without them as a document or workflow system.

PactAI is the AI layer on a contract lifecycle platform that would still run without it. It scores each contract against the customer's playbook, flags clauses that need revision with recommended changes, extracts commitments for obligation tracking, and answers questions across the portfolio. Underneath sit templates, a clause library, negotiation with comments by clause, approval workflows, native eIDAS signature, a repository and a dashboard, with more than 350 API endpoints, seven user roles and more than 60 permissions behind them.

Citation Accuracy and Hallucination Disclosure

Whether the vendor publishes measured accuracy on citations and assertions, grounds output to primary sources, and says plainly what its system does when it does not know. Legal has a documented public record of fabricated citations reaching filed briefs, so an untested claim of accuracy is not evidence.

Juro
CC on Citation Accuracy and Hallucination DisclosureAccuracy is asserted without measurement, or grounding is claimed while output cites sources the reader cannot open and verify.

Generated output may misstate people, facts or laws, including legal authorities, Juro's AI terms warn. Operator connects repository answers to source citations, while AI playbooks constrain tasks with contract context and customer rules. Prompt shortcuts help users structure instructions consistently. These features provide context and a route back to source material, but no measured hallucination rate, legal accuracy benchmark or test set accompanies them. Juro does not explain the retrieval mechanism behind Operator's citations. Juro treats generative AI as fallible and places responsibility for identifying and correcting errors with the customer before reliance. A source citation therefore provides a review aid, without a separate guarantee that the answer is correct.

Pactolane
CC on Citation Accuracy and Hallucination DisclosureAccuracy is asserted without measurement, or grounding is claimed while output cites sources the reader cannot open and verify.

PactAI's analysis is anchored to the customer's own playbook. In a worked example on the PactAI page, a nondisclosure agreement rates 72 out of 100 against a playbook called NDA Standard. Two clauses are marked for revision and eight as compliant, with 85 attainable if the recommendations are applied. Answers to portfolio questions draw on the customer's own contracts. No accuracy figure, error rate, test set or description of how PactAI retrieves and checks clauses is published, and no failure mode is named.

Autonomy and Oversight Model

What the system decides on its own, what a lawyer must approve, and whether the vendor documents where the review point sits. A tool that drafts under review and a tool that files without one are different products and different risks.

Juro
BB on Autonomy and Oversight ModelA written commitment that the models work alongside a supervising lawyer, with real review surfaces, short of the full control structure: commonly the threshold at which the system stops or what happens after it is wrong.

Human review is required before customers use or rely on AI output, and Juro prohibits presenting generated output as human authored. Inside the product, legal teams establish approval routes and set playbook context and constraints at the template or individual contract level. AI Review explains which playbook rule supports a proposed edit, and reviewers can accept, edit or skip suggestions, with version control across drafts. Juro also describes a review agent that runs autonomously, notifying legal when a contract falls outside the rules and escalating only then. The responsible AI guidance limits recommended use to tasks that the professional could perform and verify independently. These controls put the reviewer between a proposed redline and its acceptance, but no route is described for reversing or auditing an agent action that turns out to be wrong.

Pactolane
BB on Autonomy and Oversight ModelA written commitment that the models work alongside a supervising lawyer, with real review surfaces, short of the full control structure: commonly the threshold at which the system stops or what happens after it is wrong.

PactAI analyzes, extracts and detects, and the user decides, negotiates and validates, in Pactolane's words; the AI does not sign or send. Approval workflows notify each approver in the app and by email, with approval or rejection in one click and a page for every pending task. Actions taken by outside AI agents through the MCP server on the Scale plan are held for a person: an agent's request to create a contract is approved, rejected, or expires if no one decides within 24 hours. What happens after a PactAI rating or recommendation proves wrong is not described.

Operational and Outcome Evidence

Named, dated evidence that the product works in production at real firms or legal departments. Case studies with figures and identified customers count. Unattributed testimonials and launch announcements do not.

Juro
BB on Operational and Outcome EvidenceReal deployment evidence with substance, short of full attribution or measurement: a named customer without figures, or figures without the named customer.

Customer outcomes come attached to named legal and business leaders. Talentful reports an 86 percent reduction in time to sign, Funnel an 88 percent reduction in manual contract reviews and 8,000 manual contract touchpoints removed, and Luno a 91 percent time saving per contract. Paddle attributes three and a half hours saved per contract to the platform, and COOP Careers reports contracting five times faster. Goldin's stated workload is 20,000 contracts annually, while Deliveroo describes eight years of use. Juro says it powers 3 million contracts, a figure given as 2.5 million elsewhere on its site, and reports 95 percent of AI review suggestions accepted. None of these isolates the contribution of an individual AI feature, and the figures lack a measurement method or deployment period.

Pactolane
CC on Operational and Outcome EvidenceCustomer logos and unattributed testimonials stand in for evidence, or results are quoted with no basis stated.

No customer is named and no case study is published. The home page claims 85 percent fewer emails about contracts and a signing cycle cut from 21 days to 6, with no customer, sample or method behind either figure. Development began in 2025, and the platform describes itself as a CLM built for French small and mid sized companies.

Privilege and Confidentiality Posture

How client confidences are handled: attorney client privilege and work product treatment, segregation of one client matter from another, whether client data trains any model, and what the vendor commits to in writing rather than in marketing.

Juro
BB on Privilege and Confidentiality PostureSubstantive published commitments on confidentiality and training use, short of the full picture: commonly silence on segregation between users or matters, or on what the underlying model provider may retain.

Customer data cannot train an AI model serving another customer. Juro's AI terms permit a model used exclusively for the same customer, with deletion of that model within 60 days after termination. Generated output belongs to the customer and is treated as customer data. The privacy policy lists Microsoft Azure and Google Cloud as the generative AI processors, both in the EEA, and the responsible AI guidance describes confidentiality obligations covering Juro and its technology providers. A data processing agreement and named subprocessors support that contractual framework. Repository separation and permission enforcement across legal, sales, HR and procurement are not explained in that material. Professional confidentiality is recognized, but attorney client privilege and work product receive no separate treatment.

Pactolane
BB on Privilege and Confidentiality PostureSubstantive published commitments on confidentiality and training use, short of the full picture: commonly silence on segregation between users or matters, or on what the underlying model provider may retain.

Contracts are never used to train AI, according to Pactolane's security page. Each organization sees only its own data in a multi tenant architecture. Contract data is encrypted at rest with AES-256-GCM and in transit with TLS, third party contact details are encrypted at rest, and an audit trail cannot be altered. Pactolane acts as processor for customer data under the GDPR, following the customer's instructions, and a standard data processing agreement is available on request. The training commitment sits on the security page, not in published terms, privilege and work product are not addressed, and the AI provider behind PactAI is not named.

UPL and Professional Responsibility Posture

Whether the vendor is clear that it supplies a tool rather than legal advice, who its audience is, and how it addresses unauthorized practice of law, competence and supervision duties, and jurisdiction limits. ABA Formal Opinion 512 is the reference point. Where the advice line is not the duty a product raises, the axis is read through the nearest professional duty it does raise: judicial conduct rules and the reviewing duty for products sold only to courts, and the duty to bill for time actually spent for products that draft time entries.

Juro
CC on UPL and Professional Responsibility PostureA boilerplate disclaimer sits in the terms while the marketing describes the product in advice terms, or the intended audience is left ambiguous.

A person must review generated output under Juro's rules, which prohibit passing it off as human authored. Its responsible AI guidance recognizes lawyers' professional confidentiality duties and extends a related concern to HR teams handling employee information. The contracting workflow allows sales, procurement, HR and finance teams to act within legal team templates and approvals. These are operational controls around contract production, rather than a jurisdiction specific professional responsibility framework. The terms and guidance contain no statement that the product does not give legal advice, identify no governing bar opinion and do not map product behavior to ABA Formal Opinion 512. Nor do they restrict which jurisdictions or categories of professional work the AI can support.

Pactolane
DD on UPL and Professional Responsibility PostureNothing published on the advice line for a product that produces legal work, including where it is sold to people who are not lawyers.

No line between PactAI's recommendations and legal advice is drawn on the product, PactAI, security, pricing or legal notice pages, and no terms of service are published. PactAI tells users which clauses are unacceptable under their playbook and what to negotiate, and the product is sold to sales, finance, procurement and HR teams as well as legal. The only disclaimer sits on Pactolane's guide pages, which say they do not apply the law to a reader's case or replace review by a professional.

AI Governance and Bias Disclosure

Published governance over model behavior: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.

Juro
BB on AI Governance and Bias DisclosureA published governance framework with real substance, short of testing results or a named owner.

Privacy, confidentiality and accuracy in contracting are the focus of Juro's responsible AI framework. Customers can obtain a data protection impact assessment template populated for AI Assistant, with separate data protection guides for AI Assistant and AI Extract. AI playbooks let legal teams specify context and constraints, while an EU AI Act guide addresses the regulatory setting. The framework acknowledges bias and intellectual property issues but treats them as less pertinent than its three principal concerns. It does not identify a person accountable for model behavior, a release testing regime or evaluation results. Those omissions leave the operational ownership of model risk and the testing of biased outputs unclear.

Pactolane
DD on AI Governance and Bias DisclosureNo governance position published for a system whose output affects legal outcomes.

No AI governance position is published. Nothing names who inside Pactolane is accountable for PactAI, describes testing before release, or reports uneven output across contract types, languages or jurisdictions. The PactAI page warns that AI without structure, rules and supervision becomes a risk, and answers with playbooks and user validation, which are product controls rather than governance of the model.

AI Safety and Data Stewardship

Retention, deletion, access control, and what happens to prompts and documents after they are processed. Whether the vendor states its subprocessors and its incident practice, or leaves the buyer to assume.

Juro
BB on AI Safety and Data StewardshipSubstantive published policy covering most of the ground, short of the full set: commonly no named subprocessor list or no stated incident practice.

Juro's privacy policy names its platform subprocessors with the data each handles and where, including AWS and MongoDB for storage, Algolia for in-product lookup, Microsoft and Google for generative AI, and Twilio and Intercom for communications. A data processing agreement governs personal data, gives customers deletion through the product during the term and deletes remaining customer data after a recovery period of up to 60 days from termination. Customer data is replicated across geographically diverse data centers. Separate security and resilience guidance accompanies a status page and a 99.9 percent uptime commitment. The AI terms require deletion of customer specific models within 60 days of termination. Juro describes zero retention APIs with its model providers but gives no AI specific incident notification process.

Pactolane
CC on AI Safety and Data StewardshipA generic privacy policy covers the product without addressing what happens to documents and prompts after processing.

Contract data is encrypted at rest with AES-256-GCM and scrypt key derivation and in transit with TLS, OAuth tokens are encrypted in the database, organizations are isolated from each other, requests carry CSRF protection, and an audit trail cannot be altered. Deleting an account anonymizes the data and removes about 60 types of data in one transaction. The privacy policy covers website and marketing data, with retention periods for contact requests and newsletters, and names Brevo for email. No retention period is stated for contracts, prompts or PactAI outputs during a subscription, no subprocessor list for the platform is published, and no breach notice practice is stated.

AI Liability and Recourse

What the vendor stands behind contractually when its output is wrong. Indemnities, caps, carve outs, insurance, and whether any of it is published or only reachable through a negotiated agreement.

Juro
BB on AI Liability and RecourseA real published position on liability, short of the full picture: commonly a stated indemnity without scope or caps.

Juro separates its AI terms from the Master Services Agreements for customers in the United States and elsewhere. Under clause 3.2 of the AI terms, any MSA indemnity for infringement of intellectual property or other third party rights excludes generated AI output. Clause 3.1 assigns the customer the duty to identify and correct output errors before relying on a result. The March 2025 AI terms retain a link to their February predecessor, making the version boundary identifiable. This arrangement defines the treatment of AI output directly, but leaves customers without the MSA's infringement remedy for that output. Human review is the customer's contractual responsibility.

Pactolane
DD on AI Liability and RecourseNothing published on who bears the loss when the system is wrong.

No terms of service, subscription agreement or liability position is published on Pactolane's site. No warranty, limit of liability or indemnity is stated, and nothing says who bears the loss when a PactAI rating or recommendation is wrong. The data processing agreement is available on request only.

Practice Systems Integration Depth

How deeply the product reaches into the systems legal work already lives in: document management such as iManage and NetDocuments, Word and Outlook, contract lifecycle management, matter management, e-billing, and court filing systems.

Juro
BB on Practice Systems Integration DepthReal integrations exist and are documented, short of depth: named connections without a description of what they actually move.

Contract creation and management connect to business systems and Microsoft Word. Word synchronizes edits, comments, redlines and versions with the contract workspace. Salesforce runs a live two way sync that includes custom object fields, with mapping and setup guides, on the Enterprise plan. Slack, email, Google Drive and Word are available across plans. Growth adds HubSpot, Claude, Copilot, DocuSign, Greenhouse, Zapier and Ashby; Enterprise includes Salesforce, REST API access and webhooks. Claude and Microsoft Copilot use MCP to work with the repository, while the ChatGPT connection remains in beta. The pricing FAQ identifies Salesforce, HubSpot and Workday as integrations carrying additional cost. Outside Salesforce and Word, what each connection syncs and in which direction is not set out, and no iManage or NetDocuments connection is identified.

Pactolane
BB on Practice Systems Integration DepthReal integrations exist and are documented, short of depth: named connections without a description of what they actually move.

Integrations are named by category. Salesforce, HubSpot, Pipedrive and Zoho CRM connect by OAuth, with fields mapped by the user, to import accounts and contacts that prefill contracts. Google Drive, OneDrive, Dropbox and Box connect for storage, and DocuSign, Yousign and Dropbox Sign sit beside the native eIDAS signature. The Scale plan adds an MCP server, a REST API and webhooks, so a customer's AI agents can read contracts and request actions under approval. No connection to Microsoft Word, a document management system or an ERP is described, and what each storage connection syncs is not set out.

Deployment Model and Data Residency

Where the software runs and where the data sits. Multi tenant cloud, single tenant, private deployment, on premises, and whether region of residence is a published option or an enterprise conversation.

Juro
BB on Deployment Model and Data ResidencyDeployment model is stated clearly with partial residency detail, or residency is offered without the processing location being addressed, or the tenancy model is stated on its own with no residency detail published.

Juro's privacy policy, updated 29 September 2026, places contract storage on AWS in the EEA, with MongoDB and Algolia also in the EEA. Generative AI runs on Microsoft Azure servers and Google Cloud's generative AI services, both listed in the EEA, while Microsoft Azure Document Intelligence parses PDFs. Customers use the hosted workspace across more than 85 countries. The data processing agreement of 30 September 2026 replicates customer data across geographically diverse data centers and states that customer data may be processed in any country where Juro or its subprocessors maintain facilities. The published locations therefore describe current practice rather than a residency commitment, and no choice of region, single tenant option or private installation is offered. An EU Data Act addendum addresses a separate contractual requirement.

Pactolane
BB on Deployment Model and Data ResidencyDeployment model is stated clearly with partial residency detail, or residency is offered without the processing location being addressed, or the tenancy model is stated on its own with no residency detail published.

Contract data is hosted on Google Cloud Platform in France and Belgium, inside the European Union, and the legal notice names Google Cloud as host with that data region. The platform is multi tenant, with each organization isolated to its own data. No dedicated or on premises option is offered, and where PactAI's model processing runs is not stated.

Security Certifications and Trust Center

Independent attestation a buyer can pull without a sales call: SOC 2, ISO 27001, penetration test summaries, a trust center with current reports and named scope rather than a badge image.

Juro
BB on Security Certifications and Trust CenterCertification is real and stated, short of accessible evidence: a named standard without scope, date, or a way to obtain the report.

Privacy regulations, application security, network infrastructure, resilience, electronic signatures and responsible AI each get a section in Juro's trust center. Its security claims include SOC 2 Type 2, supported by a trust center topic and a certification badge, and its integration pages add IASME Cyber Essentials. The platform also has a status page and a stated 99.9 percent uptime. Access to the explanatory articles does not require a form, email address or confidentiality agreement. The trust center index does not identify the auditor, attestation period, report date or tested scope, nor give a route to the underlying report or details of a penetration test. The security claims are identifiable, while their independent verification details remain incomplete.

Pactolane
DD on Security Certifications and Trust CenterNo independent security attestation located.

ISO 27001 certification is in progress, by Pactolane's own description on its home and security pages, and no SOC 2 or other independent attestation is claimed. A security dossier is offered on request. The security page lists eIDAS simple electronic signature and GDPR alongside the ISO work, and cites an ISO 27001 control for its CSRF protection.

Model Supply Chain Disclosure

Which models sit underneath, whose they are, where they run, and whether the vendor commits to telling customers when that changes. A legal buyer inherits every dependency it cannot see.

Juro
BB on Model Supply Chain DisclosureThe supply chain is partly disclosed: providers named without change notification, or architecture described without the providers.

Juro's privacy policy names Microsoft Azure as the server for its generative AI functionality and Google Cloud's generative AI services for some of its newest features, both in the EEA, and an OpenAI custom GPT extracts smartfield data for the optional AI Managed Service. The responsible AI guidance, dated January 2026, still names only OpenAI's GPT family delivered through Microsoft on Azure. The data processing agreement gives customers at least 30 days' notice of a new subprocessor, 14 days to object and a route to terminate with a pro rata refund. Model versions, the model behind Google's services and which feature runs on which model are not given, and the notice covers new subprocessors rather than model changes within an existing provider. The trust center's own subprocessor list still names only Algolia, AWS and MongoDB.

Pactolane
DD on Model Supply Chain DisclosureNothing published about the model supply chain a customer inherits.

No model, model provider or AI subprocessor is named on the PactAI, security, privacy or legal notice pages. Google Cloud is named as the host, and nothing says whether PactAI runs on a Google model or another provider, where inference happens, or whether customers are told when a model changes.

Commercial Transparency

Whether a buyer can learn what this costs without entering a sales process: published rates, the unit being charged, what sits behind an enterprise tier, and what implementation adds.

Juro
BB on Commercial TransparencyReal pricing is published for part of the range, with enterprise tiers withheld, or the unit and structure are stated without the figure.

Monthly contract volume and integration complexity set the price, with unlimited users, workflows and templates on every plan. Volume bands range from fewer than 20 contracts per month to more than 1,000. Juro names its plans Essentials, Growth and Enterprise, all billed annually, and integration access steps up across them, with Slack, email, Google Drive and Word on every plan, HubSpot, Copilot and DocuSign from Growth, and Salesforce, REST API access and webhooks in Enterprise. The pricing FAQ adds that Salesforce, HubSpot and Workday carry additional cost. Quotes also reflect implementation complexity. Billing can use USD, GBP or EUR, and nonprofit discounts are available. No numeric subscription or implementation price is stated, so the pricing page supplies the drivers of a quote without a per seat rate or a calculable total.

Pactolane
AA on Commercial TransparencyA buyer can learn what this costs without entering a sales process: published rates, the unit being charged, and what implementation adds.

Three plans are priced on the pricing page, excluding tax. Team costs €149 a month for small teams and Growth €499 a month. Scale starts at €2,500 a month with unlimited contracts and users, the MCP server and API, single sign on, an advanced audit trail, dedicated support and legal onboarding. Annual billing saves 17 percent, €298 a year on Team and €998 on Growth. Team has a seven day free trial and Growth a 14 day trial, without commitment, and plans can be changed at any time.

Firm and Practice Coverage

Who the product is actually built for. AmLaw, midlaw, small firm and solo, in house departments, government and courts, and which practice areas are supported rather than merely claimed.

Juro
BB on Firm and Practice CoverageSegment and practice coverage is described with substance, short of the boundaries: what is supported is clear, what is not is left open.

Buyers span legal, HR, procurement, sales and finance teams. Legal establishes templates and workflow controls, allowing other departments to produce agreements within an approved process. Contract types include NDAs, employment agreements, master services agreements, statements of work, order forms, acquisition material and supplier agreements. The company describes customers in more than 85 countries and positions the platform for businesses completing roughly ten or more contracts each month, though AI review currently works only in English. Its industry examples include software, food delivery and marketplaces. The central setting is an in house contract operation. A dedicated law firm, government or court workflow is not identified, and the product does not function as a primary legal research service.

Pactolane
BB on Firm and Practice CoverageSegment and practice coverage is described with substance, short of the boundaries: what is supported is clear, what is not is left open.

Pactolane is built for French small and mid sized companies, with solution pages for legal, legal operations, sales, finance, procurement, HR and IT teams. Template libraries cover commercial, corporate, real estate, IT and software, and employment contracts, and the site runs in French, English, German, Spanish, Italian and Portuguese. Law firms, contract types the AI does not handle, and jurisdictions outside France are not addressed.

The 12 legal signals, side by side

Recorded rather than graded. These are the questions a practitioner has to answer before a tool touches a client matter, and the answers are taken from public material only.

Client Data in Training

Can material a lawyer puts into this product be used to train a model?

Juro
Permitted, in the contract

Juro's AI terms, last updated 11 March 2025, bar training a model for anyone else with customer data but permit training a model used only to provide services to that same customer, which Juro must erase within 60 days after the agreement ends. The privacy policy of 29 September 2026 repeats the exception for models used only by the customer's business, and the responsible AI guidance rejects training foundational models with customer data.

Shared model training is therefore excluded by contract, while a customer specific model trained on that customer's data is expressly permitted, with no opt out offered.

Pactolane
Never, in policy only

Customer contracts are never used to train AI, according to the security page. No published terms carry the commitment, and the AI provider behind PactAI is not named.

Prompt and Output Retention

How long does the product keep what a lawyer typed, and can that be set to zero?

Juro
Customer controlled, no zero option

Juro's data processing agreement of 30 September 2026 lets customers delete customer data through the product during the term, treated as an instruction to remove it as soon as reasonably practicable, and deletes remaining data after a recovery period of up to 60 days from termination. Generated output counts as customer data under the AI terms, which also require erasure of any customer specific model within 60 days.

Juro describes zero retention APIs with its model providers. No default retention period for prompts and outputs during the term, and no zero retention setting inside Juro itself, is stated.

Pactolane
Disclosed without a period

Deleting an account anonymizes the data and removes about 60 types of data in one transaction. No period is stated for keeping contracts, prompts or PactAI outputs during a subscription, and no retention setting is described.

Ethical Walls and Matter Segregation

Does retrieval respect the firm’s ethical walls, or can the model read across them?

Juro
Not addressed

Legal, sales, HR, procurement and finance can work in Juro's contract workspace. The AI terms prevent a customer specific model from serving another customer and distinguish one user's output from similar output produced for others. Those contractual boundaries do not explain permission enforcement within the repository or retrieval across teams. Juro describes no technical separation model and no controls for ethical walls between matters.

Pactolane
Claimed, not documented

Each organization sees only its own data in a multi tenant setup, and the platform counts seven user roles and more than 60 permissions. How roles limit which contracts a user or PactAI can reach inside one organization is not described.

Third Party Request and Subpoena Notice

If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?

Juro
Notice committed

Juro's data processing agreement, updated 30 September 2026, requires notice to the customer of government access requests under Appendix 3, paragraph 4.4(k). The commitment operates through the Standard Contractual Clauses where the corresponding transfer law applies. Notification to individual data subjects remains the customer's responsibility. An equivalent commitment is not identified in the general terms or CCPA appendix.

Requests from a third party claiming to control customer personal data are directed to the customer. No transparency report or request volume accompanies these provisions.

Pactolane
Disclosure addressed, notice absent

The privacy policy lists public authorities as recipients on a legal request or court order, and the legal notice says data may be given to judicial authorities in case of an offense. No commitment to tell the customer first is made, and no transparency report is published.

Primary Law Corpus Provenance

Where does the law in this product come from, and does the vendor have the right to use it?

Juro
Sources named, basis unstated

Operator answers questions from the customer's contract repository and connects responses to its sources. AI Extract captures data from signed agreements in that same customer supplied collection. The underlying model route is identified as Microsoft Azure and Google Cloud generative AI services, with the responsible AI guidance naming OpenAI's GPT family. Juro is not a primary law research corpus. Rights to the foundation models' training material and an update schedule for that material are not established by the repository's customer supplied provenance.

Pactolane
Not addressed

PactAI works on the customer's own contracts and playbooks, and the platform supplies its own contract templates. No outside legal source, publisher or license is named behind its answers.

Good Law Verification

Does the product tell you when the authority it just cited has been overruled?

Juro
Not addressed

Contracts belonging to the customer, rather than a primary law collection, are what Juro works with. It has no identified citator, treatment signal or process for checking the subsequent history of a legal authority. Operator's citations connect repository answers to contract sources, which serves a different purpose from determining whether a case remains good law. The AI terms acknowledge that generated output can misstate laws and legal authorities and require human correction before reliance.

Pactolane
Not addressed

The product manages contracts and does not cite case law or statutes, so no citator is part of it. Nothing describes checking playbook positions against changes in the law, although a sample PactAI answer flags contracts affected by a new law.

Refusal and Uncertainty Behavior

What does the product do when the answer is not in the corpus?

Juro
Not addressed

Juro warns that generative AI can produce errors and requires a person to review results before reliance. Playbooks provide context and constraints for contract tasks, but no defined abstention path or confidence indicator explains how the system responds when an answer lacks support. The responsible AI guidance treats accuracy as an ongoing professional review responsibility. Juro thus pairs a warning with a human control, but does not say when the AI itself declines a request.

Pactolane
Not addressed

PactAI rates each contract from 0 to 100 against the playbook, with bands for unacceptable, acceptable and preferred clauses, which measures conformity rather than the AI's own certainty. No behavior is described for a question the portfolio cannot answer.

Fabricated Citation Record

Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?

Juro
None located

The AI Hallucination Cases database maintained by Damien Charlotin, which held 2,262 cases on 2 November 2026 and records the tool involved where known, has no case naming Juro. Juro primarily supports commercial contracting inside companies, a setting in which output is less likely to become part of a court filing. Having no recorded case is not a measured accuracy result, and fabricated legal assertions remain possible.

Pactolane
None located

No court decision in the AI Hallucination Cases database maintained by Damien Charlotin names Pactolane or PactAI. The product drafts and reviews commercial contracts rather than court filings.

Bar Guidance Alignment

Has the vendor engaged in public with the ethics opinions its buyers are bound by?

Juro
Generic reference

Lawyers must protect professional confidentiality when using AI, Juro recognizes. Its responsible AI guidance connects that duty to restrictions on training with customer data, while making a similar confidentiality point for HR teams. It does not connect these controls to a named ethics opinion or regulator's requirements. ABA Formal Opinion 512, state bar guidance, and Solicitors Regulation Authority or Law Society materials are not identified as the governing framework.

Pactolane
Not addressed

No bar opinion, professional conduct rule or regulator guidance on AI is named on Pactolane's product, security, pricing or legal notice pages. The buyers are company teams rather than regulated practitioners.

Billing and Fee Posture

Does the vendor address what happens to the bill when the work takes an hour instead of six?

Juro
Outside the fee relationship

Reduced contract work, including faster signing, fewer manual reviews and time saved per agreement, runs through the customer examples. The commercial focus is an in house operation where legal and business teams share the platform. Those efficiency claims say nothing about how a law firm should bill a client for AI assisted work. No matter based fee record, disclosure procedure or guidance on passing time savings through to clients accompanies the contracting workflow.

Pactolane
Outside the fee relationship

Companies buy Pactolane to run their own contracts, so no client bill sits in the loop. Its savings claims, 85 percent fewer contract emails and a signing cycle cut from 21 days to 6, aim at the buyer's own time.

Outside Counsel Guideline Readiness

Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?

Juro
Subprocessors listed

Juro's privacy policy, updated 29 September 2026, lists platform subprocessors with the data each handles and its location, including Microsoft Azure and Google Cloud for generative AI in the EEA, alongside AWS, MongoDB and Algolia. Customer initiated integrations, including the Claude, ChatGPT and Copilot connectors, are listed separately. The contractual package includes a data processing agreement with 30 days' notice of new subprocessors, an EU Data Act addendum and separate AI terms, with an impact assessment template available for AI Assistant.

No client consent or notification pack accompanies this material, and the trust center's shorter list still omits the AI processors.

Pactolane
On request only

A standard data processing agreement and a security dossier are available on request. No subprocessor list for the platform or model provider is published; the privacy policy names Brevo for marketing email and the legal notice names Google Cloud as host.

Court Disclosure Support

If a judge’s standing order requires an AI disclosure, can the product produce one?

Juro
Not addressed

Commercial contracts, not court filings, are what Juro manages. Operator provides source citations for repository answers, and the AI terms prohibit representing generated output as human authored. These features support a limited record of sources and a contractual disclosure boundary. They do not create a court certification, standing order workflow or export that records the model's role and a lawyer's verification. A dedicated litigation disclosure process is not identified.

Pactolane
Not addressed

An audit trail that cannot be altered and an eIDAS signature certificate are kept for each signed contract. Nothing records which parts of a contract or analysis PactAI produced, and the product serves contracting rather than litigation.

What neither one publishes

The questions both sides leave open

Derived from the records above rather than written, so it cannot favor either vendor. Take these into both conversations and ask each side the same question.

Signals neither addresses in public material
  • Good Law Verification
  • Refusal and Uncertainty Behavior
  • Court Disclosure Support

In summary

Juro

Juro is a contract lifecycle platform for in house legal teams whose sales, HR, procurement and finance colleagues create agreements from templates that legal controls. AI Review proposes redlines against the team's playbook, including inside Microsoft Word, AI Extract captures data from signed agreements, and Operator answers questions about the repository with citations to its sources. Salesforce syncs both ways, and Claude and Microsoft Copilot reach contracts through MCP, with Juro named an exclusive launch partner for Microsoft's legal MCP. According to the AI Legal Index, Juro's AI terms bar using customer data to train a model for another customer but allow a model used only for that customer. Its infringement indemnity excludes AI output, and a person must review output before anyone relies on it.

Source: AI Legal Index, 2026

Pactolane

Pactolane is a French contract lifecycle platform from Lyon for small and mid sized companies, covering templates and a clause library, negotiation by clause, approval workflows, native eIDAS signature, a repository and obligation tracking. PactAI rates each contract from 0 to 100 against the customer's playbook, flags clauses to revise with recommended changes, and answers questions across the portfolio. Contacts come in from Salesforce, HubSpot, Pipedrive and Zoho CRM, and the Scale plan adds an MCP server, a REST API and webhooks, with agent actions held for a person to approve. According to the AI Legal Index, contract data is hosted on Google Cloud in France and Belgium, and Pactolane's security page says contracts are never used to train AI. No terms of service are published, and ISO 27001 certification is in progress.

Source: AI Legal Index, 2026

Questions buyers ask

How does Juro compare to Pactolane?

Both manage contracts from template to signature and repository for legal teams and their business colleagues. Juro is the older platform, from London, with Operator and AI Review in Word and a quote based on contract volume. Pactolane is a Lyon company for small and mid sized firms, with PactAI ratings against the playbook and published monthly plans. From the AI Legal Index, based on each vendor's own published materials as of November 16, 2026. No vendor pays for placement.

What do Juro and Pactolane cost?

Juro quotes its Essentials, Growth and Enterprise plans on monthly contract volume, integrations and implementation, with unlimited users on each, and bills in USD, GBP or EUR. Pactolane publishes Team at €149 a month, Growth at €499 and Scale from €2,500, excluding tax, with 17 percent off for annual billing. From the AI Legal Index, based on each vendor's own published materials as of November 16, 2026. No vendor pays for placement.

Do Juro and Pactolane train AI on customer contracts?

Juro's AI terms bar training a model for another customer with customer data, but allow a model used only for that customer, deleted within 60 days after the agreement ends. Pactolane's security page says contracts are never used to train AI, a commitment not repeated in published terms, and it does not name its AI provider. From the AI Legal Index, based on each vendor's own published materials as of November 16, 2026. No vendor pays for placement.

Where do Juro and Pactolane store contract data?

Juro stores contracts on AWS in the EEA and runs generative AI on Microsoft Azure and Google Cloud in the EEA. Pactolane hosts contract data on Google Cloud in France and Belgium, encrypted at rest and in transit. From the AI Legal Index, based on each vendor's own published materials as of November 16, 2026. No vendor pays for placement.

Can AI agents work with Juro and Pactolane contracts?

Both offer MCP. Claude and Microsoft Copilot reach Juro contracts through MCP, and a ChatGPT connection is in beta. Pactolane opens an MCP server, a REST API and webhooks on its Scale plan, and holds each agent action for a person to approve within 24 hours. From the AI Legal Index, based on each vendor's own published materials as of November 16, 2026. No vendor pays for placement.

Disclosure

Neither vendor paid for inclusion, placement or a grade, and neither reviewed this page before it published. Everything on it comes from public material on the dates shown. How the index grades.

Neither vendor publishes an accuracy figure or test set for its AI review. Juro's prices require a quote. Pactolane publishes no terms of service or liability position, offers its data processing agreement on request, and has not completed ISO 27001 certification.

Contact

Correct a record, or ask how something was graded

Every grade and every signal on this index is drawn from public sources and dated. If a record is wrong, out of date, or missing an artifact the index did not locate, send the source and it will be reviewed and the record redated. Vendors are welcome to submit documentation. Nothing on this index is for sale, including a listing, a placement, or a grade.

AI Legal Index

The AI Legal Index is an independent index that tracks changes to AI vendors in legal. It holds 535 vendors across 9 categories, each graded on the same 15 capability axes and recorded against 12 legal signals, from public sources. No vendor pays for inclusion, placement, or rating.

Index Status
Last index update
November 19, 2026
The AI Legal Index is an editorial reference. It is not a regulatory body, not a law firm, and nothing published here is legal advice or a recommendation to retain or avoid a vendor. Records are verified against published sources, bar guidance and public court records. Where a record reads not addressed, the material was not located in public sources on the date shown. See the Methodology page for evaluation standards and limitations.
© 2026 AI Legal Index
3801 N Capital of Texas Hwy, Ste E240 · Austin, TX 78746