Claren

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.

The artificial intelligence is the product and there is nothing underneath it. Every function Claren sells is a model output: redlining a contract in seconds with wording edited to the team's stated position, extracting key terms, and answering questions about a document with citations. There is no repository, no workflow engine, no matter system and no document management layer that would survive the models being removed; the terms of service describe the thing being licensed as a software solution utilising artificial intelligence, and the product page markets an AI editor that goes from upload to redline with no setup and no plugins. Even the tier structure is model-shaped, with Pro capped by chat and file upload volume and higher tiers adding AI playbook generation and custom term extraction. Remove the models and a buyer is left with an upload form. Reported here with its located evidence per the standing discipline on A rows. Checked 4 September 2026.

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.

Limitations are disclosed with unusual candour and accuracy is never measured. Clause 3.4 of the terms is the most forthcoming accuracy statement located in this pull: the solution may contain outdated or inaccurate information, is trained on historical data with specific knowledge cutoff dates, may not reflect recent legal developments or changes in statute or case law, and its outputs may contain errors, omissions or misinterpretations of legal concepts requiring correction by qualified professionals. Clause 3.4.3 disclaims any representation as to accuracy, completeness or adequacy. Against that, the marketing asserts what the agreement declines to warrant, describing the product as built on trusted legal sources and understanding contracts like a lawyer does, and offering answers with citations. No accuracy figure, test set, evaluation, error rate or retrieval method appears anywhere, and the trusted legal sources are never named, so a reader cannot tell what the citations resolve to beyond the customer's own uploaded document. Grounding is claimed, limitations are published, and nothing is testable.

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.

The requirement for a lawyer to review sits in the contract rather than in a disclaimer, and the control structure around it is not described. Clause 3.3.1 provides that all information, documents, analyses and other outputs must be reviewed by qualified legal counsel before being relied on, implemented or used as the basis for any decision or action, and clause 3.3.3 has the customer acknowledge that Claren has expressly informed it of that requirement. Clause 5.2.10 goes further for one category, prohibiting submission of Claren-generated documents to courts in criminal proceedings without independent attorney review. The product design supports it, with the model producing a redline the lawyer accepts, rejects or edits rather than writing to anything itself. What is absent is the structure: no threshold at which the system acts alone, no confidence or certainty signal surfaced against an individual suggested edit, no abstention state, and no description of what a reviewer sees to distinguish a high-confidence extraction from a marginal one.

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.

Attribution is unusually complete and measurement is entirely absent. Eight customer logos are published and five testimonials carry a full name, a role and an organisation: Alan Owens, Head of Legal at H&M V Engineering; Arvinder Mangat, General Counsel at Encompass; Carl Dunton, General Counsel at Peak Energy; Chantal Schofield, Knowledge Manager at Telecom Infrastructure Partners; and Jamie Todd, Commercial Counsel at ScreenCloud. Three of the five are the senior legal officer of the named company, which is stronger attribution than a logo strip and stronger than most records in this lane. The quotes are also substantive rather than generic, with one describing the product as helping spot what a reviewer might have missed when working at the edge of their knowledge, and another reporting a lawyer asking after one week that it never be taken away. What holds this at B is that not one figure attaches to any of them: nothing is dated, no cycle time, volume or cost is given, and the corporate claims run to unquantified language about hours saved and backlogs cleared. A case studies section and an ROI calculator exist and were not opened.

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.

Most limbs are met and the two that are not are both worth a buyer's attention. Training is prohibited in the agreement itself at clause 4.2.4, which is the strongest form this commitment takes. Segregation is documented rather than asserted: each user has a private and segregated data store on Neon, authentication and row-level security for organisation roles run through Clerk, and the security page states there is no cross-contamination between client matters or organisations. The model provider limb is answered squarely, with zero data retention agreements named as in place with OpenAI and Anthropic and each provider's own terms linked. Encryption is AES-256 at rest and TLS 1.2 or higher in transit. Two things hold it below the top band. Privilege is addressed only as data being treated with attorney-client privilege in mind, which is a posture rather than the express privilege and work product treatment the top band requires, and work product is never mentioned. And the contractual confidentiality obligation at clause 12.1 reaches only information clearly labelled or identified as confidential, which is a narrower net than uploaded matter material would ordinarily fall into.

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.

The most complete professional responsibility treatment located in this pull, and it sits in the agreement rather than a footer. Clause 3.1 states plainly that the solution provides information of a general nature, is not a substitute for licensed legal counsel, does not provide legal advice, and creates no attorney-client relationship. Clause 3.3 supplies the competence and supervision limb directly, requiring that all outputs be reviewed by qualified legal counsel before reliance and having the customer acknowledge it was expressly told so. Clause 3.3.2 does what almost no vendor does and names the doctrine: users who are not licensed attorneys are specifically cautioned that use may constitute unauthorised practice of law if used to provide legal advice to others. Clause 3.2 carves out an entire category, stating the product must not substitute for representation in criminal matters, active court proceedings or any matter where liberty is at stake, and will not draft court filings in criminal proceedings without independent attorney review. Clause 3.5 names jurisdictional limits explicitly, identifying variation between the United States and United Kingdom and among states, territories and localities, and placing compliance responsibility on the user. The product has no consumer-facing surface, being sold to in-house legal teams.

AI Governance and Bias Disclosure

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

No governance position was located for a product whose entire output is model-generated legal work. There is no responsible AI page, no principles statement, no named owner accountable for model behaviour, no pre-release evaluation or testing regime, no red-teaming description and nothing at all on bias, including nothing on whether redlining or risk flagging performs evenly across contract types, counterparty positions, languages or jurisdictions. That last gap has weight because the product is marketed as operating across multiple languages and jurisdictions. The security page is detailed and entirely about information security, which the axis definition treats as a separate subject and which is graded on the stewardship and certification rows rather than counted twice. Clause 3.4 of the terms discloses accuracy limitations frankly, but disclosing that a model may err is a product warning rather than a governance framework, and it is credited on the accuracy row instead. Searched the home page, the security page, the terms of service and the site navigation on 4 September 2026.

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.

Substantive across most of the set, with the specifics thinning at the edges. Retention and deletion are stated in the agreement rather than in marketing: clause 11.6 commits to deleting all content of the customer and its users within 30 days of the contract expiring, and the security page adds that the terms and pilot agreements specify a right to delete data at any time. Access control is described concretely, with authentication and user management through Clerk, account-specific sessions, authenticated API endpoints, row-level security for organisation roles, multi-factor authentication available for administrative access, production access restricted on a need-to-know basis, background checks for staff with access to sensitive systems, and security awareness training at onboarding and ongoing. Suppliers are named rather than gestured at: Neon for data stores, Clerk for authentication, and OpenAI, Anthropic and Google for models. Incident practice exists and is the softest limb, with defined incident response procedures said to carry SLA targets for acknowledgement, escalation and resolution, but no target is published and no customer notification commitment or timeframe appears anywhere. No formal subprocessor register with locations exists; DPAs are available on request.

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.

Liability is addressed through a limitation clause that disclaims precisely the exposure the product creates. Clause 10.1.2 caps total liability at the higher of 100 pounds or the fees paid in the twelve months preceding the claim, and the floor figure is worth naming: for a customer in its first months the ceiling on a claim may be a hundred pounds. Clause 10.1.1 excludes special damage, lost profits, lost savings, lost business opportunity, lost contracts, goodwill, corrupted data and wasted expenditure. Clauses 10.3, 10.4 and 10.5 then address output directly and disclaim it, stating that outcomes are for general information only, are not intended to meet professional requirements, carry no representation or warranty that they are accurate, complete or up to date, and that Claren has no liability for the accuracy of customer content. Clause 9 runs the indemnity one way only, from customer to Claren, and no vendor indemnity of any kind appears. Clause 10.2 preserves liability for death, personal injury caused by negligence and fraud. No insurance position was located. The whole picture is published, dated 11 April 2026 and readable before signing, which is what keeps it off the floor.

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.

Two integrations are named with real contractual detail and the rest is a number. Slack and Microsoft Teams are named and their behaviour described in the agreement rather than in marketing: clause 2.4 states the solution is designed to be integrated into an organisation's internal communication and workflow system such as Slack or Teams, that Claren may require the customer to hold an active account with one, and that Claren may access the customer's Slack or Teams account and the channels it is instructed to access and deliver content or outcomes through those channels. That is direction of travel and required configuration stated plainly. Beyond it the disclosure stops: the Pro plan lists 15 or more data integrations without naming one, enterprise single sign-on and SAML appear at the tier above, and no document management system, contract lifecycle system, matter management platform or e-signature product is identified anywhere. For a contract review product the absence of any named DMS or CLM is the material gap, since that is where the agreements being reviewed already sit. No integrations page, API reference or developer documentation exists in the site navigation.

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.

Region options are published and the processing half is not. The security page states that cloud infrastructure is hosted in United States, United Kingdom or European Union data centres, with data residency options for enterprise customers, and adds that all data including read replicas can be stored in a data centre located in a specific region on request. That is a genuine three-region choice with the tier it attaches to identified, which is more than most records in this lane offer. Tenancy is described functionally through the data layer, with each user given a private and segregated data store on Neon and row-level security for organisation roles, though the platform is never characterised as single or multi-tenant in terms. What is missing is where processing happens as distinct from where data sits: models are called through the OpenAI, Anthropic and Google APIs and no location is stated for any of them, so a customer selecting European Union residency cannot establish from published material that the inference leg stays in region.

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.

No independent attestation is held, and the site contradicts itself about that. The security page states that Claren is currently pursuing SOC 2 Type II and ISO 27001 certification, expected Q2 2026, and separately that Claren uses SOC-2 compliant vendors and third party software providers. Both sentences are careful and both say the same thing: the certifications belong to suppliers and to the future, not to Claren. The home page says something different, listing SOC 2 compliant among the reasons to choose the product with no qualification. Those cannot both be right, and the specific statement governs the general one. Two further facts belong on the record. The expected certification date, Q2 2026, had passed by the date of this check with no published update either way. And the supplier certification that is evidenced is Clerk's, with SOC 2 Type II and ISO 27001 and a link to its trust page; under the standing rule a supplier's attestation does not travel to the vendor without a scope connector, and none exists. A trust centre is said to be available on request and no report, auditor, scope or period is published.

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.

The providers are named, evidenced and linked, and the models are not identified. The security page states that Claren uses OpenAI, Anthropic and Google's models through their APIs, and the latest open source models on request, and it does not stop at naming them: each provider's own no-training position is cited with a link, to OpenAI's enterprise privacy policy, Google's Gemini API additional terms and Anthropic's privacy terms, and OpenAI's abuse-monitoring retention of up to 30 days is disclosed. Claren adds that it has established zero data retention agreements with OpenAI and Anthropic. That is a fuller account of who touches customer content, and on what terms, than most records in this corpus manage. Three limbs fail. No model or version is named, only the provider, so a buyer cannot establish which model performs a redline. Where inference runs is never stated. And no commitment to notify customers if a provider, model or arrangement changes was located, which matters given the open source option is offered on request.

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.

The shape is visible and the number is not. Three plans are published with names and contents: Pro carries unlimited chats, 100 chat file uploads, 100 data room uploads, AI-powered redlines, a legal-tuned prompt library, 15 or more data integrations and a Slack community; Scale-Up adds enterprise single sign-on and SAML, a dedicated support manager, AI playbook generation, custom contract term extraction and data partitions; Enterprise adds biweekly AI training sessions, enterprise permission and access controls, managed onboarding, direct access to the AI team and priority input on the roadmap. No figure appears at any tier and every call to action is a demand for a demo. The unit of charge is gestured at rather than defined, with a closing note that plans are based on average document usage and that final packages and pricing vary by workflow and document volume, which tells a buyer that volume drives the bill without saying what a unit costs or how many are included beyond the upload caps. An ROI calculator is published and was not opened.

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.

The work is described with substance and one boundary is drawn sharply while others are left open. What is supported is clear: contract review, redlining, key term extraction and document question and answer for in-house legal teams, across multiple languages and jurisdictions, with named customers spanning energy, telecommunications, retail, technology and drinks. The exclusions are unusually explicit for this axis and come from the agreement rather than marketing: clause 3.2 places criminal matters, active court proceedings and any matter where liberty is at stake outside the product entirely, and clause 3.5 states that the product may not account for specific jurisdictional requirements or recent changes in local law, naming the United States and United Kingdom and variation among states and localities. What is missing is the rest of the picture. No firm segment or size is stated, law firm use as against in-house is never addressed, government legal is not mentioned, and no contract type is identified as unsuitable, so a buyer knows what the product will not touch in criminal work and not where else it stops.