Claren vs Summize: how they compare in 2026

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, workflow engine, matter system or document management layer that would survive the models being removed. The terms of service describe what is licensed as a software solution using artificial intelligence, and the product page markets an AI editor that goes from upload to redline with no setup and no plugins. Even the tiers follow model use: Pro is capped by chat and file upload volume, and higher tiers add AI playbook generation and custom term extraction. Without the models, an upload form remains.

The product comes in three layers, and only the third is AI. A Knowledge Layer holds playbooks and policies. A Contract Operations Layer runs the lifecycle from first request to signature inside existing tools. The agentic AI layer, SIA, is described as surfacing that knowledge as instant answers. Without SIA, a working contract request, repository and operations system remains, embedded in Outlook, Teams, Slack and Salesforce. Summize presents the layers as distinct, each one powering the next.

Clause 3.4 of the terms says the solution may contain outdated or inaccurate information, is trained on historical data with knowledge cutoff dates, may not reflect recent changes in statute or case law, and may produce errors, omissions or misinterpretations of legal concepts that need correction by qualified professionals. Clause 3.4.3 disclaims any representation as to accuracy, completeness or adequacy. The marketing describes the product as built on trusted legal sources, understanding contracts like a lawyer does, and offering answers with citations. No accuracy figure, test set, evaluation, error rate or retrieval method appears anywhere. The trusted legal sources are never named, so what the citations point to beyond the customer's own uploaded document is not stated.

SIA is described as giving instant, reliable answers grounded in the customer's own knowledge and standards. That identifies the grounding source as the Knowledge Layer of playbooks and policies, but no retrieval method is described behind it. The security page says Summize evaluates the effectiveness, quality and security of its AI models on a consistent basis. No result, test set, cadence or scope is published for those evaluations. Summize publishes no accuracy figure. Its materials do not discuss hallucination or name a failure mode, and the published performance figures all measure speed and volume rather than correctness.

Clause 3.3.1 of the terms says 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. Under clause 3.3.3 the customer acknowledges that Claren has expressly told it so. Clause 5.2.10 goes further for one category, barring submission of Claren generated documents to courts in criminal proceedings without independent attorney review. The product design supports this: the model produces a redline the lawyer accepts, rejects or edits, rather than writing to anything itself. There is no threshold at which the system acts alone, no confidence signal shown against an individual suggested edit, no abstention state, and no description of how a reviewer can tell a confident extraction from a marginal one.

Summize says the business becomes more self sufficient while legal remains in full control. It says questions that used to reach legal's inbox are answered instantly by the people who needed them. Its materials do not say what SIA answers alone and what a lawyer approves, and they state no threshold. The Word review workflow shows failed or missing clauses and lets reviewers accept, modify or reject AI recommendations. That control applies to contract review, while the materials do not explain how a wrong SIA answer is corrected.

Eight customer logos are published and five testimonials carry a full name, role and organization: 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. One quote says the product helps spot what a reviewer might have missed when working at the edge of their knowledge. Another reports a lawyer asking after one week that it never be taken away. No figure attaches to any of them. Nothing is dated, no cycle time, volume or cost is given, and the company's own claims stay with unquantified language about hours saved and backlogs cleared. A case studies section and an ROI calculator are published.

Three named customers give attributed quotes. Steven McGeagh at Huel speaks to ease of adoption, Julia Trius at Edpuzzle to receiving agreements already in the required format, and Derek Ihnen at Boon Edam to reduced review time. Customer logos include Revolut, SeatGeek, Miami Heat, Matillion, Sigma Computing, CodeRabbit, KSE and IPC Systems. Summize cites three times faster contract creation, a 40 percent reduction in deal length, a 50 percent reduction in processing time and six times more contracts reviewed. It puts an NDA at two minutes against two hours. A 4,062 percent ROI is attributed to Nucleus Research, a named analyst firm. None of these figures is tied to a named customer or dated. Huel, Edpuzzle and Boon Edam each also have a case study page.

Training is prohibited in the agreement itself, at clause 4.2.4. Segregation is documented: each user has a private and segregated data store on Neon, authentication and row level security for organization roles run through Clerk, and the security page says there is no cross contamination between client matters or organizations. The model provider question is answered directly, with zero data retention agreements in place with OpenAI and Anthropic and each provider's terms linked. Encryption is AES-256 at rest and TLS 1.2 or higher in transit. Privilege is addressed only as data being treated with attorney client privilege in mind, and work product is never mentioned. The confidentiality obligation at clause 12.1 reaches only information clearly labeled or identified as confidential, a narrower net than uploaded matter material would usually fall into.

Under clause 6.1 of the SaaS terms, Summize may store, transmit and process Customer Data only as needed to provide the services, and gets no other rights in it. Clause 6.2 requires physical, technical and organizational measures in line with good industry practice. Clause 6.5 imposes confidentiality with named exceptions. Clause 6.6 requires daily encrypted backups available to the customer on request, and clause 9.2 requires prompt deletion or return of all Customer Data at the customer's choice on termination. Summize says prompts, completions, embeddings and training data are exclusive to each customer and not available to OpenAI or used to improve OpenAI models. Clause 6.4 reserves the right to use Customer Data in aggregated, anonymized form to improve the software through machine learning, so the agreement permits training. Separation between customers is described as siloed AI, without detail on how it is enforced. Summize's published materials do not address privilege or work product.

Clause 3.1 of the terms says the solution gives general information, is not a substitute for licensed legal counsel, does not provide legal advice, and creates no attorney client relationship. Clause 3.3 covers competence and supervision directly: all outputs must be reviewed by qualified legal counsel before reliance, and the customer acknowledges it was expressly told so. Clause 3.3.2 names the doctrine, cautioning users who are not licensed attorneys that use may amount to unauthorized practice of law if used to advise others. Clause 3.2 excludes a whole category: 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, citing variation between the United States and United Kingdom and among states, territories and localities, and puts compliance responsibility on the user. The product is sold to in house legal teams and has no consumer surface.

Summize markets contract answers to people who are not lawyers, in sales, finance, HR and procurement teams. It says questions that used to reach legal's inbox are taken care of, giving the examples of a salesperson checking renewal terms and a CFO querying payment performance without involving legal. Its materials do not say what the output is and is not, and no disclaimer separates information from legal advice. There is no competence or supervision language, and no jurisdiction limit is stated, although customers are in the UK and the US. The SaaS terms contain warranties, indemnities and liability caps but no provision on legal advice. The website terms of use disclaim only the website. The marketing line that legal remains in full control describes workflow, not advice.

No AI governance position is published. There is no responsible AI page, no principles statement, no named owner accountable for model behavior, no evaluation or testing regime before release, and no red teaming description. Nothing addresses bias, including whether redlining or risk flagging performs evenly across contract types, counterparty positions, languages or jurisdictions, and the product is marketed as working across several languages and jurisdictions. The security page concerns information security only. Clause 3.4 of the terms discloses accuracy limits.

The security page sets out four AI commitments, each in one sentence: siloed AI practices, regular assessments of effectiveness, quality and security, ongoing updates to AI capabilities, and a customer feedback loop. No one at Summize is named as accountable for AI outcomes. No testing regime before release is described, and no assessment result is published. Nothing addresses bias or uneven output across contract types or counterparties. The company's General Counsel has written an explainer on the EU AI Act, which comments on the regulation rather than describing Summize's own governance. ISO 27001 is an information security standard and does not cover AI governance.

Retention and deletion are in the agreement rather than marketing. Clause 11.6 commits to deleting all content of the customer and its users within 30 days of the contract expiring. The security page adds that the terms and pilot agreements give a right to delete data at any time. Access control is described concretely: authentication and user management through Clerk, account specific sessions, authenticated API endpoints, row level security for organization roles, multifactor authentication for administrative access, production access on a need to know basis, background checks for staff with access to sensitive systems, and security training at onboarding and after. Suppliers are named: Neon for data stores, Clerk for authentication, and OpenAI, Anthropic and Google for models. Incident response procedures are said to carry SLA targets for acknowledgment, escalation and resolution, but no target is published and no customer notification commitment or timeframe appears. There is no formal subprocessor register with locations; DPAs are available on request.

On termination, clause 9.2 of the SaaS terms requires Summize to promptly delete or return all Customer Data at the customer's option. Retention after that is allowed only where law requires, and confidentiality obligations continue over anything retained. Clause 6.6 requires backups no less frequently than daily, secure and encrypted, in a commonly used machine readable format and available to the customer on request. Access control rests on ISO 27001, with DevSecOps practices and internal password, equipment and data confidentiality policies described. Clause 3.2 gives an annual audit right over user and password compliance. Summize states that it runs regular third party penetration testing. The agreement sets no retention period for the term itself, only for its end. No subprocessor list is published. Clause 8.4 refers to Appendix 3 as defining Sub-Processors, but the appendix is not included in the published document.

Clause 10.1.2 of the terms, dated 11 April 2026, caps total liability at the higher of 100 pounds or the fees paid in the twelve months before the claim, so for a customer in its first months the ceiling 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 to 10.5 disclaim output directly: outcomes are for general information only, are not meant to meet professional requirements, and carry no warranty that they are accurate, complete or up to date. Claren also has no liability for the accuracy of customer content. Clause 9 runs the indemnity one way, from customer to Claren, and no vendor indemnity appears. Clause 10.2 preserves liability for death, personal injury caused by negligence, and fraud. No insurance position is published.

The SaaS terms give the customer an intellectual property infringement indemnity in clause 7.2, covering claims, liabilities, losses, damages and reasonable costs. Clause 7.3 sets one named carve out, for unapproved combinations. Under clause 7.4, which sets out how claims are handled, Summize may not settle without unconditionally releasing the customer. Each liability cap is the greater of a fixed sum or a multiple of charges, so the fixed sum sets a minimum. Clause 8.3 caps general liability at the greater of £100,000 or 150 percent of total charges. Clause 8.2 sets a separate, higher cap for breach of the security and data protection obligations, at the greater of £500,000 or 500 percent of total charges. Clause 8.1 preserves liability for willful misconduct, and clause 8.4 makes Summize liable for its subcontractors and subprocessors as for itself. Clause 3.6 warrants that the software meets its specification in all material respects and is free of material errors and defects. Clause 3.5 requires reasonable skill and care, clause 3.8 warrants against malicious code, and clause 7.1 warrants that Summize holds the rights to supply the service. The agreement does not disclaim output accuracy, and Summize publishes no insurance position.

Slack and Microsoft Teams are described in the agreement rather than marketing. Clause 2.4 says the solution is designed to fit into an organization's internal communication and workflow system such as Slack or Teams, and that Claren may require the customer to hold an active account with one. It also says Claren may access the customer's Slack or Teams account and the channels it is told to access, and deliver content or outcomes through them. That states the direction of data and the configuration needed. 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, contract lifecycle, matter management or electronic signature product is named. There is no integrations page, API reference or developer documentation in the site navigation.

Summize works inside Outlook, Microsoft Teams, Slack, Gmail, Microsoft Word, Salesforce, HubSpot and Jira. It adds Summize Sign for e signature and a Claude integration, and each integration has its own dedicated page. The examples given are a salesperson checking renewal terms inside Salesforce and a CFO querying payment performance across the supplier base. Contract context and assistance are available in the tool, without a new login to manage. Summize says there is no separate platform to adopt. Implementation runs in sprints of three to four weeks under a methodology Summize calls HERO, with in house implementation staff. A full rollout typically completes within twelve weeks.

The security page says cloud infrastructure is hosted in United States, United Kingdom or European Union data centers, with residency options for enterprise customers, and that all data including read replicas can be stored in a specific region on request. Tenancy is described through the data layer: each user has a private and segregated data store on Neon, with row level security for organization roles, though the platform is never called single tenant or multitenant. Where processing happens, as distinct from where data sits, is not stated. Models are called through the OpenAI, Anthropic and Google APIs and no location is stated for any of them, so nothing published confirms that inference stays in the European Union for a customer choosing residency there.

On its home page Summize says data never leaves the customer's environment, and its FAQ says the platform is built on Azure enterprise infrastructure. That names the infrastructure provider, but no region is given and nothing says where customer contract data is stored. The only published hosting location is in the website terms of use, which say the Website is hosted on servers in the United Kingdom. That covers the marketing site, not the software. Summize does not say whether the platform is single tenant or multitenant. Siloed AI, as Summize describes it, covers how prompts and embeddings are handled rather than a tenancy model.

The security page says Claren is currently pursuing SOC 2 Type II and ISO 27001 certification, expected in Q2 2026, and separately that Claren uses SOC 2 compliant vendors and third party software providers. Both sentences say the same thing: the certifications belong to suppliers and to the future, not to Claren. The home page instead lists SOC 2 compliant among the reasons to choose the product, with no qualification, and the two statements conflict. Q2 2026 has passed with no published update. The supplier certification that is evidenced is Clerk's, with SOC 2 Type II and ISO 27001 and a link to its trust page, but nothing published extends that attestation to Claren's own systems. A trust center is said to be available on request, and no report, auditor, scope or period is published.

ISO 27001 certification is held, with a badge naming ISOQAR as the certification body and UKAS as the accrediting body. No certificate number, scope, statement of applicability, or issue and expiry dates are published, and there is no trust portal or route to a report. Penetration testing is described as regular and third party, with no firm or dates named. A security whitepaper by CTO Richard Somerfield is offered behind a form. Summize does not hold SOC 2. It says it audits infrastructure in line with standards including SOC II and intends to work toward SOC II accreditation.

The security page says Claren uses models from OpenAI, Anthropic and Google through their APIs, and the latest open source models on request. Each provider's own no training position is cited with a link: OpenAI's enterprise privacy policy, Google's Gemini API additional terms and Anthropic's privacy terms. OpenAI's abuse monitoring retention of up to 30 days is disclosed, and Claren says it has zero data retention agreements with OpenAI and Anthropic. No model or version is named, only the provider, so which model performs a redline is not stated. Where inference runs is never stated. No commitment to notify customers if a provider, model or arrangement changes is published, although the open source option is offered on request.

The security page names OpenAI and states that customer prompts, completions, embeddings and training data are not available to OpenAI or used to improve OpenAI models. The FAQ adds that SIA is built on Azure enterprise infrastructure. No specific model or version is named, and Summize publishes no commitment to notify customers when a model or provider changes. No subprocessor register is published. Appendix 3, cited in the agreement as defining Sub-Processors, does not appear in the published text.

Three plans are published with names and contents. Pro carries unlimited chats, 100 chat file uploads, 100 data room uploads, AI redlines, a prompt library tuned for legal work, 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 AI training sessions every two weeks, 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 asks for a demo. A closing note says plans are based on average document usage and that packages and pricing vary by workflow and document volume. So volume drives the bill, and what a unit costs or what is included beyond the upload caps is not stated. An ROI calculator is published.

The pricing structure sits in the published SaaS terms, and the site has no pricing page. The terms define the Order Form as setting out user numbers and the type of software license, so the charge is per user by license type. The initial term renews automatically for twelve month periods unless 90 days' written notice is given. Clause 2.2(b) limits any renewal increase to 10 percent over the previous twelve month term for the same plan, tier and package, unless a higher cap is agreed. Payment is due 30 days from a valid invoice. Fees exclude VAT and sales tax but include other taxes, and expenses need prior written approval. No figure, band, tier name or feature split is published.

Supported work is clear: contract review, redlining, key term extraction and document question and answer for in house legal teams, across several languages and jurisdictions, with named customers in energy, telecommunications, retail, technology and drinks. The exclusions are explicit and come from the agreement. Clause 3.2 puts criminal matters, active court proceedings and any matter where liberty is at stake outside the product entirely. Clause 3.5 says 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. No firm segment or size is stated, law firm use as against in house use is never addressed, government legal work is not mentioned, and no contract type is named as unsuitable.

Five buying teams (Legal, Sales, Finance, HR and Procurement) and eight sectors each have a dedicated page. The sectors are Software, Sports, Finance, Manufacturing, Business Services, Media and Internet, Retail and Telecommunications. Four use cases are published as request, review, repository and analytics. NDAs are named as a specific contract type with a stated handling time. The buyer is a corporate in house function rather than a law firm, and law firms are neither claimed nor excluded. No organization size is stated, and no contract types beyond NDAs are listed as supported. Government use is not addressed, and nothing says where the product stops.