CloudLex vs ProPlaintiff: how they compare in 2026

Six AI features drive capabilities a firm would miss, on a case management system that stands entirely without them. Lexee AI covers lead and intake capture by voice and chat, demand package drafting from case facts and records, medical summaries and chronologies built from unstructured records, natural-language querying of a matter, a client-facing website assistant, and voice-to-task conversion. The medical chronology and the demand draft are the two most labour-intensive documents in a plaintiff practice and the models are the mechanism for both. The vendor's own framing is built in, not bolted on, and the AI reads from and writes back into the case file rather than requiring re-entry. Underneath sits a complete practice management system covering intake, matters, documents, calendaring, client communication, expense management, settlement calculation, analytics, e-signature and archiving, none of which needs a model. The agreement treats AI Tools as a defined subset of the Services rather than as the Services themselves, and the ecosystem is marketed as four pillars of which Lexee is one alongside the platform, paralegal services and a publishing arm.

AI native by construction and explicit about the distinction. The vendor states it is built from the ground up as an AI native platform and is not layering AI onto outdated software, and the product surface bears that out: every named feature is generative or analytical rather than a form with a model attached, spanning demand letters, medical chronologies, document generation, summaries, review, media analysis, case analysis and a conversational assistant. The agentic framing is applied to case management itself rather than to a single document type, so the model layer is the operating logic of the system rather than a capability within it. Remove the models and what remains is a file store with a calendar. Sixth consecutive A on this axis in this category, and the pattern is now unbroken across every plaintiff side vendor built. Note the vendor's own framing of the AI as a force multiplier and digital assistant handling repetitive data heavy work, which is a centrality claim and a substitution disclaimer in the same breath.

Grounding is claimed in general terms, the limitations are stated with unusual candour in the contract, and nothing is measured. The product pages describe chat answers as grounded in the case's documents and notes, medical summaries as written back into the case file, and outputs generally as tied to the matter rather than generated in isolation. What is absent is the verification surface: nothing describes whether a generated summary or demand paragraph carries a link, page reference or citation back to the source record a reader could open. The agreement is franker than the marketing and is credited for it, stating that outputs may not always reflect the most current legal standards, may not accurately reflect applicable people, entities, places or other facts, and may not be tailored to specific case circumstances, with all warranties as to accuracy, completeness and suitability disclaimed. Searched the Lexee AI page, the platform page, the pricing page and both terms of service on 31 Aug 2026 and located no accuracy figure, no test set, no evaluation and no error rate. One limb does not apply and is neither credited nor penalised, since a citator is out of scope for a tool reading a matter's own records rather than primary law.

Grounding is claimed clearly and nothing behind it is published. The vendor states that demand letters cite specific medical records, bills and reports automatically, and that smart citations pull directly from the firm's uploaded files, which is the right architecture and describes citation to the case file rather than to invented sources. The vendor also publishes, in its own practitioner guidance, that good platforms log what data was used, what was generated and who approved it, and that this is the firm's defensibility. What is absent is any measurement or any specification of its own implementation: no accuracy figure, no extraction error rate, no evaluation, no description of what smart citations resolve to or how a user verifies one, and no statement of behaviour when records are incomplete or provider names are inconsistent, a failure mode the vendor's own content identifies as where platforms fall apart. Held at C rather than B because the peers graded B in this category publish a citation mechanism a reader can see operating, being page level links, hyperlinked navigation or a table of authorities, and here the mechanism is asserted rather than described. Checked the home page, the demand letters page, the blog library and the G2 listing on 29 Aug 2026.

The clearest human-review architecture in the plaintiff lane, published as a workflow rather than asserted as a value. The vendor sets out a four-step process for medical record summarisation in which step four is Human Review: an attorney or paralegal reviews the output, edits as needed, and approves it for use. The same structure repeats at feature level, with demand drafts described as expert human-reviewed and designed for staff review and refinement, and medical summaries as AI-drafted and paralegal-reviewed. The positioning line is that Lexee supports review, not judgment, and the FAQ states that human review and judgment remain central to every workflow. The agreement makes it binding, requiring that all outputs be independently reviewed and validated, by a qualified attorney where applicable, before being used in legal proceedings or client communications. One product-level control deserves separate credit because its peers lack it: the client-facing website assistant verifies a caller's identity before releasing any case-specific information, under firm-controlled verification. What is missing is the failure path: no abstention behaviour, no confidence or uncertainty signal, no threshold at which a feature declines, and no route to report or correct a wrong output.

The clearest published oversight position in this category, stated as a rule rather than as reassurance. The vendor's own guidance states that attorney oversight is non negotiable, that AI drafts and attorneys approve, and that no compliant workflow skips that step. It further states that the firm owns the output and that a good platform logs what data was used, what was generated and who approved it. Alongside that, the product ships permission management and system activity logs, which are the mechanisms an approval record would run on. Separately the vendor disclaims substitution, framing the AI as a force multiplier freeing paralegals and attorneys for client communication, negotiation and trial preparation. Held at B rather than A because the rule is published as advice to the profession rather than as a specification of this product: nothing states that ProPlaintiff enforces an approval step, whether any generation can be sent without one, what the activity log actually captures, or whether the approval record the vendor says firms need is one this platform produces. A vendor that names the right standard and does not claim to meet it has done half of the work visibly.

Fully attributed customers in quantity, with almost no measurement attached. Six named attorneys appear with their firm and title: a partner at Pollack, Pollack, Issac & DeCiccio; a senior litigation attorney at Mitchell and Danoff; a founding partner at Rasmussen Injury Law; a trial lawyer at Ikhilov & Associates; an attorney at Glugeth & Pierguidi; and an attorney at the Law Office of Daniel Horowitz. A litigation paralegal at Abrams & Associates also appears. That is attribution rather than a logo strip, and the firms are identifiable plaintiff practices. One figure is published and it concerns migration rather than outcome, a firm reporting that it transferred over 300 cases without issue. Nothing else carries a number: no time saved, no settlement or intake conversion figure, and no date on any quote. Dedicated Client Stories and Client Reviews pages exist and were not opened on 31 Aug 2026, and they are the route to moving this row. Checked the Lexee AI page, the platform page and the home page.

Nothing located. No customer or firm is named anywhere in vendor material, no case study, no usage figure, no time saving or outcome claim with or without methodology, no funding announcement, no independent analyst placement and no award. That is unusual for this category rather than typical: every other record built here publishes at least throughput figures, and three name customers or independent recognition. A G2 listing exists and carries vendor supplied product description rather than verified customer outcomes located in this pass. The vendor publishes a substantial practitioner content library and none of it contains a customer result. Checked the home page, the demand letters page, the case management page, the blog library, the G2 listing and the site navigation on 29 Aug 2026. Recorded as a documented absence across those surfaces rather than as a judgement about adoption, which cannot be assessed from public material.

Substantive commitments on both confidentiality and training use, with two disclosures a buyer should weigh. The agreement gives the customer exclusive ownership of Customer Data and limits vendor access to four named circumstances: to provide the Services, to respond to service or technical problems, to comply with the law, or at the customer's request. Commercially reasonable administrative, physical and technical safeguards are undertaken, expressly including measures preventing access, use, modification or disclosure by CloudLex personnel outside three narrow exceptions. The training position is contractual and restrictive, with CloudLex undertaking not to use Customer Data other than Aggregated Data for training and not to allow its vendors or subcontractors to do so, and Aggregated Data defined to omit anything identifying the customer, its clients or any individual or organisation. The AI Tools section commits to maintaining confidentiality and security of client data in compliance with applicable privacy laws and bar ethics rules, and naming bar ethics rules in a customer agreement is rare. Two things cut against and are recorded rather than smoothed: the agreement acknowledges that Customer Data may be transmitted unencrypted, and nothing describes segregation between matters within a firm.

Basic protections are stated with one useful specific, and no privilege position exists. Published: HIPAA compliance with industry standard safeguards, encryption, storage in the United States, and access limited to authorised users at the firm, supported in product by permission management, system activity logs and secure case sharing. Naming United States storage is a concrete locational commitment most peers in this category do not make and it is credited. Against that: no SOC 2 or any independent attestation was located, no business associate agreement is offered despite the vendor's own guidance telling readers to choose HIPAA compliant platforms under a BAA, and no treatment of attorney client privilege or work product appears. Held at C rather than B because the peers at B in this category carry an independent attestation, a BAA, or both, and this record carries a self declared compliance posture with product features supporting it. Checked the home page, the case management page, the compliance and security references, the blog library and the site navigation on 29 Aug 2026.

The most complete professional responsibility treatment located in this pull, and the only one that reaches the consumer. Every limb this axis asks for is published. What the product is and is not: CloudLex is not a law firm and does not and cannot provide legal advice of any kind, outputs are for informational purposes only, and use of the AI Tools creates no attorney-client relationship with CloudLex, its affiliates or its AI systems. Who may use it: subscribers based in the United States and their authorised users, a stated jurisdictional limit few vendors give. Competence and supervision: outputs must be independently reviewed and validated, by a qualified attorney where applicable, before use in legal proceedings or client communications, and the firm is made solely responsible for its fiduciary duty, record-keeping and client trust accounting rules, ethical professional standards, competent representation, timely filings and management of legal deadlines and court dates, and for obtaining its clients' affirmative consent to use of the service. Users are encouraged to disclose AI use to clients. Where a chatbot facilitates exchanges with clients and prospective clients, the firm and not CloudLex is responsible for the content and results. And the consumer-facing surface carries its own disclosure: the separate chatbot terms tell the claimant directly that Lexee AI does not and cannot provide legal advice of any kind. No bar authority is named by title, which is the one softness.

THE BEST POSITION ON THIS AXIS IN THE CATEGORY AND ONE OF THE BEST IN THE PULL. The vendor publishes, in its own practitioner guidance, that ABA Model Rules on competence and supervision apply to AI assisted drafting, that the firm owns the output, that attorney oversight is non negotiable and no compliant workflow skips the approval step, and that firms must verify jurisdictional variation in damages language, statutory references and negligence framing because those differ by state. It separately disclaims substitution, stating the AI does not replace human judgement and frames it as a force multiplier. Naming the specific rules that apply, identifying who carries the professional obligation, and flagging jurisdictional variation as the user's responsibility together constitute a real professional responsibility position rather than a disclaimer. Held at B rather than A because it is published as market education in a blog library rather than as a product commitment or a term: nothing binds the vendor to it, it is not surfaced in the product or in any agreement located, and no named bar authority beyond the ABA Model Rules is engaged. Every other record in this category grades D here.

Principles are stated where they bind and no apparatus stands behind them. The agreement carries a section headed Transparency and Responsible Use providing that the AI Tools are developed and deployed in accordance with principles of responsible AI, including transparency, fairness and human oversight, and encouraging users to disclose AI use to clients. Putting fairness in a customer contract is rare, and only one other vendor in this pull does it. The marketing adds that Lexee is a purpose-built AI initiative undergoing continuous training to keep its capabilities reliable and responsible, and frames the design around complementing rather than replacing human judgement. What is absent is everything that would let a buyer test any of it. Searched the Lexee AI page, the platform page and both terms of service on 31 Aug 2026 and located no accountable owner for model behaviour, no pre-release testing or evaluation regime, no published result, no model documentation, and no measurement or discussion of bias beyond the single word fairness. The gap has an edge here because the AI speaks directly to injured members of the public through the intake capture and client assistant features, where uneven performance across callers would matter and is unexamined.

Nothing published about how the models are governed, evaluated or monitored. No AI policy, no model card, no bias or fairness testing, no evaluation methodology, no accuracy monitoring, no drift statement, no named governance body and no ISO 42001. The vendor's own content acknowledges that AI medical record analysis accuracy has improved for platforms trained specifically on clinical and legal documents, which is an accuracy claim about the field rather than a disclosure about this system. The category risk applies unchanged: the platform generates demand letters anchoring damages including a justified pain and suffering valuation, by the vendor's own description, and any systematic tendency in how that valuation is framed falls on claimants. Sixth consecutive D on this axis in this category. Checked the home page, the product pages, the blog library, the G2 listing and the site navigation on 29 Aug 2026.

Deletion is specified with real deadlines, the infrastructure controls are inherited from Azure, and the data lifecycle in between is thin. What is published: a staged exit in which the customer has 30 days after cancellation to download or export Customer Data, a further 30 days on request against a one-time migration fee, no obligation on CloudLex to maintain data beyond 60 days, and a commitment to securely overwrite or delete Customer Data 90 days following termination. Access is contractually limited to four named circumstances, and safeguards are undertaken on a commercially reasonable basis expressly including measures preventing access, use, modification or disclosure by CloudLex personnel. The security and compliance page and the FAQ, read on 31 Aug 2026, describe encryption at AES-256 at rest and TLS 1.2 or above in transit with automatic key rotation, multi-factor authentication, role-based access control, geo-redundant data centres, disaster recovery, continuous backups and 24/7 monitoring, though the material attributes these to Azure's framework rather than to controls CloudLex operates itself. Against that: no subprocessor list exists anywhere; no incident response or breach notification practice was located; the agreement acknowledges that Customer Data may be transmitted unencrypted across connecting networks, which sits oddly beside the encryption claims; CloudLex disclaims any responsibility or liability for the deletion or failure to store Customer Data while reserving the right to impose storage limits; and the privacy policy disclaims all liability for the acts or failings of its unnamed infrastructure provider.

Protection is stated with a locational specific and use is unaddressed. Published: data is encrypted, stored securely in the United States, accessible only to authorised users at the firm, with HIPAA compliance and industry standard safeguards. United States storage is a real commitment and is the concrete element here. What was not located: any statement on whether uploaded medical records, case files, generated chronologies or demand drafts are used to train or improve models, any retention period, any deletion right at matter close, and any description of what happens to firm saved templates and preferred language, which by the vendor's own description accumulate a firm's drafting patterns over time. Held at C rather than higher because the peers at B publish either an exercisable control such as manual deletion or an independent attestation covering the handling claims, and neither exists here. Checked the home page, the case management page, the compliance references and the site navigation on 29 Aug 2026.

The exposure the AI creates is disclaimed in detail and nothing is allocated back to the buyer. The cap is the harshest formulation located in this pull: maximum compensatory damages for all claims relating to the Services, individually or in aggregate, are the lower of the last paid invoice or two thousand five hundred dollars. Lower of, not greater of, so a firm paying monthly is capped near one month's fee however large the loss. No carve-out is named for confidentiality, security breach, gross negligence or wilful misconduct. Services are provided as is and with all faults with every warranty disclaimed including non-infringement, and outputs carry their own disclaimer of accuracy, completeness and suitability with no liability for errors, omissions or outcomes resulting from reliance on AI-generated content. The only indemnity runs from the customer to CloudLex and reaches unusually far, covering the customer's own negligent or wilful acts including malpractice, and any communications or interactions between the firm and a client, potential client or third party facilitated by the chatbot or other AI Tools. There is no vendor indemnity, no insurance position, and no service level commitment carrying a credit. Disputes go to AAA arbitration in New York before three arbitrators, with recovery of legal fees capped at twenty thousand dollars.

No published position located. Nothing was found on liability for AI output, warranty, service levels or remedy. The vendor's own guidance states that the firm owns the output, which is a clear allocation of responsibility to the customer and is the closest thing to a liability position in public material, and it is advice to the profession rather than a contractual term. Nothing addresses what happens when a generated demand misstates a treatment, when a citation resolves to the wrong record, or when a deadline generated by the AI calendar feature is wrong, which on a case management platform is a malpractice exposure rather than a drafting one. Checked the home page, the product pages, the blog library and the site navigation on 29 Aug 2026.

Named connections into the systems a small firm actually runs on, with the depth undocumented on the surfaces read. Microsoft 365 has its own product page, and CloudLex publishes a Word connector and Gmail and Outlook email management so that correspondence and drafting attach to the matter rather than living outside it. A Legal App Integrator is offered as the general integration surface, alongside e-signature, mobile applications for iOS and Android, and a referral engine that lets a firm send a case to another firm and track it. The agreement adds a formal structure for third-party functionality, defining 3rd Party Modules supplied by Third Party Providers, each governed by its own addendum and charged separately, with Google, Facebook, Apple, Microsoft and Amazon named as examples of providers through which Customer Data may interoperate. What is not established is what any integration moves or how it is configured: the integrations page was not opened on 31 Aug 2026, no application programming interface or developer documentation was located, and nothing names a document management system or an e-billing platform.

Nothing available, and the vendor says so, which is why this is recorded as disclosure rather than silence. Published material describes future API integration, stating the capability as planned rather than delivered, and data migration is offered, which is a one time import path rather than an integration. No case management system, document management system or records retrieval integration is named, and the reason is structural rather than an oversight: this product is itself the case management platform, so it competes with Filevine, Litify, Clio and CasePeer rather than connecting to them. That positioning is coherent and it leaves a firm with no route to move data between this system and anything else on an ongoing basis. Compare Tavrn at B, naming four case management systems plus live API access. Checked the case management page, the home page, the product pages and the site navigation on 29 Aug 2026.

Cloud delivery is explicit, the hosting platform is named in marketing, and the residency question is never reached. The pricing page states that CloudLex is hosted on Microsoft Azure with 24/7/365 active security monitoring, 256-bit encryption and SSL, which establishes the platform if not the geography. The agreement adds one real boundary, restricting use of the service to subscribers based in the United States and their authorised users, which narrows the question without answering it. Searched the Lexee AI page, the platform page, the pricing page and both terms of service on 31 Aug 2026 and located no region or data centre location, no residency option a customer can select, no tenancy model, and no statement distinguishing where matter data is stored from where AI processing runs. Two provisions pull the wrong way and belong on the record: the agreement acknowledges that Customer Data may be transmitted unencrypted across connecting networks, and the privacy policy states that servers are not located at CloudLex but at a third-party infrastructure provider whose security measures CloudLex does not guarantee and for whose failings it accepts no liability, without naming that provider.

A real residency statement with nothing behind it, and a deployment option named without detail. The vendor states that data is stored securely in the United States, which is a jurisdictional commitment rather than a gesture at secure cloud infrastructure and is more than most records in this category publish. Custom deployment is separately named as available for firm wide automation supporting hundreds of attorneys, which implies something beyond standard multi tenant provisioning and is not described. What is absent: no hosting provider named, no region or availability zone detail, no statement of whether custom deployment means dedicated infrastructure, a private instance or configuration, and no data processing description. Credited at C for the United States commitment and held there because a country is the beginning of a residency answer rather than the whole of it. Compare Supio at B, which names data centres in three countries against three matching regulatory regimes.

Every attestation named belongs to Microsoft, and the vendor says so plainly rather than blurring it. The FAQ states that CloudLex is built entirely on Microsoft Azure, inheriting its enterprise-grade security standards including SOC 1, SOC 2 Type II and ISO 27001 certifications, and that every layer of CloudLex's infrastructure is backed by Azure's independently audited compliance framework, which it describes as covering continuous vulnerability assessment and penetration testing, geo-redundant data centres with 24-hour surveillance and physical access controls, encryption at TLS 1.2 or above in transit and AES-256 at rest, and automatic key rotation. The security and compliance page adds 256-bit encryption, SSL, data redundancy, disaster recovery, continuous backups and compliance with HIPAA, IRS and AICPA standards. The distinction matters and is the finding here: an infrastructure provider's certification attests the infrastructure provider's controls, not the application built on top of it, and nothing published claims that CloudLex itself has been audited against any standard. Searched the security page, the FAQ, the pricing page, the platform page and both terms of service on 31 Aug 2026 and located no CloudLex-specific SOC report, no ISO certificate, no named auditor, no scope statement or coverage period for CloudLex's own controls, no penetration test of the application, no trust portal and no route to request any report. HIPAA compliance is asserted directly by CloudLex and is the one claim made in its own name, without an accompanying attestation.

No independent attestation of any kind was located, and the vendor's own guidance shows it knows what the standard is. Located: HIPAA compliance claimed with industry standard safeguards, encryption, United States storage, permission management, system activity logs and a stated secure and HIPAA compliant workflow. Not located: any SOC 2 of either type, any ISO certification, any named auditor, any examination scope or date, any business associate agreement offer, and any trust centre, security page or documentation request route. Under the three tier test the artifact is absent rather than gated. The gap is measured against the vendor's own published advice, which tells readers evaluating platforms to look for SOC 2 Type II, HIPAA compliance and GDPR adherence, and to safeguard privileged communications by choosing HIPAA compliant platforms under a BAA. On its own criteria this record would not clear the bar it sets for others. Fourth instance in the pull of a vendor advising buyers to demand what it does not publish, after LinkSquares, FinregE and DigitalOwl.

Nothing published identifies what runs the AI. Searched the Lexee AI page and all six feature descriptions, the platform page, the pricing page, and both the firm-facing and chatbot terms of service on 31 Aug 2026. No model is named, no provider is named, no distinction is drawn between first-party and third-party models, no version appears, and no inference location is stated. The agreement defines AI Tools as CloudLex's AI-driven features including the Lexee AI Chatbot and other artificial intelligence tools offered by CloudLex, which identifies the vendor's own branding rather than anything underneath it. The closest the material comes is the marketing description of a PI-trained AI, which asserts domain specialisation without disclosing architecture, provider or training corpus. Two adjacent provisions are recorded because they show third parties are involved without saying which: the agreement contemplates Third Party Providers through which Customer Data may interoperate, naming Google, Facebook, Apple, Microsoft and Amazon as examples in a general integration context, and the training clause binds vendors and subcontractors without listing them. No change-notification commitment for models was located.

Nothing located. No foundation model provider, model family or version is named, no distinction is drawn between proprietary and third party models, and no subprocessor list was found. The vendor's own practitioner content discusses general assistants including named commercial models and advises that firms require approved confidentiality controls before those touch case files, which demonstrates awareness that the identity of the model matters and stops short of identifying its own. For a platform processing protected health information under a claimed HIPAA posture, every processor touching that data is a question a firm's diligence asks and none can be answered from public material. Checked the home page, the product pages, the blog library, the G2 listing and the site navigation on 29 Aug 2026.

No price is published at any level, and the vendor is unusually explicit that none exists. A dedicated pricing page states that CloudLex does not publish or authorize standard public per-user pricing, that pricing is customised on the selected package, number of users, intake and case management requirements, storage, integrations, AI capabilities and optional services, and that any pricing shown on third-party websites should be treated as an estimate only and may not reflect current pricing. Disclaiming other people's numbers is rare and is recorded as candour, but it confirms rather than relieves the absence: there is no figure, no tier name with a rate, no unit of charge published, and no published package structure a buyer could price. What the agreement supplies is billing mechanics rather than cost: charging monthly or yearly in advance against an Order Form, automatic renewal at the original signup price unless notified in advance, a ten-day window to give notice of non-renewal after a renewal notification, no refunds for partial months or for downgrades, a valid credit card required on file with authorisation to charge, additional charges for use exceeding subscribed users or matters, and separate charges for third-party modules plus a service fee on payments CloudLex makes to those providers.

No pricing published at any level. No price, no range, no tier structure and no unit of charge, and no indication of how custom deployment for hundreds of attorneys prices relative to a solo practitioner, despite both being named as target buyers, which is a wide span to leave entirely unpriced. No independent estimate was located either, unlike several peers in this category where third party reconstructions exist. The contingency fee point recorded across this category applies: case costs are advanced against a claimant's recovery, so undisclosed cost is undisclosed cost to an injured person. Checked the home page, the product pages, the pricing navigation and the site navigation on 29 Aug 2026.

Coverage is documented with real specificity and one hard boundary is stated in the agreement. Nine practice areas each have a dedicated page: personal injury, slip and fall and premises liability, product liability, mass torts, workers' compensation, social security disability, motor vehicle accidents, wrongful death and medical malpractice. The segment is drawn tightly and deliberately, with the vendor positioning itself as built exclusively for plaintiff personal injury firms rather than as generic legal software adapted to injury work, and contrasting itself with all-in-one tools and with AI point solutions. The stated limit is jurisdictional and contractual: use of CloudLex is limited to subscribers based in the United States and their authorised users. That is a boundary most vendors in this pull leave unstated. Depth of coverage is supported by the surrounding offering, with paralegal services covering no-fault litigation processing, court calendar management and bilingual intake, which implies the operational reach the software assumes. What is still absent is any statement of firm size served, matter volume threshold, or state-level coverage for the deadline and calendaring functions. The individual practice-area pages were not opened on 31 Aug 2026.

Functional breadth is wide, practice scope is narrow and honestly stated, and the coverage that matters for a case management platform is not characterised. Functional coverage is the broadest claimed in this category, running from intake through litigation across case management, calendaring and deadlines, document generation and review, media analysis, chronologies, demands and analytics in one system. Practice scope is plaintiff side personal injury, stated plainly, with solo attorneys, paralegals and firms of hundreds of attorneys all named as buyers. Held at C rather than B because nothing is characterised at the level a buyer checks: no jurisdictional coverage is stated despite the vendor's own guidance warning that damages language, statutory references and negligence framing vary by state, no statement of which record types or formats the medical analysis handles, and no indication of practice sub areas such as mass tort or medical malpractice. For a platform that is the firm's system of record, coverage claims need boundaries and none are given.

The firm-facing agreement restricts training and binds the supply chain, and a second published contract points the other way for a different data flow. The Terms of Service dated 12 Dec 2025 provide that CloudLex will not use Customer Data other than Aggregated Data for training, and will not allow its vendors or subcontractors to do so, absent a separate written agreement. Aggregated Data is defined to omit anything enabling identification of the customer, its clients, or any individual, company or organisation, and CloudLex takes a perpetual royalty-free licence over it, expressly including to train AI models, owning the resulting reports. That is the same shape as the strongest positions in this pull. The divergence a buyer must know about sits in the separate Lexee AI Chatbot Terms, which bind the firm's prospective client rather than the firm: an individual using the chat widget on a firm's website irrevocably grants CloudLex a perpetual, sub-licensable licence over their own submitted data, not limited to aggregated form, expressly including training and improving AI models, and consents to that use. So matter data in the platform is protected by contract while intake conversations captured through the firm's own website are not.

Silent. The quoted phrase is the most specific data statement the vendor publishes and it addresses location, not use. No statement was located in either direction on whether uploaded medical records, case files, generated chronologies or demand drafts are used to train or improve models. One product behaviour makes the silence more consequential than usual: the vendor states that firms save templates, preferred language and common arguments so that junior associates draft like senior partners, which means the system accumulates a firm's drafting patterns over time, and nothing describes whether that accumulation stays inside the firm boundary. Compare Eve, which discloses firm scoped adaptation openly alongside its training commitment. Recorded as silent, not as a negative commitment. Checked the home page, the demand letters page, the case management page and the compliance references on 29 Aug 2026.

The end of the lifecycle is specified with dates; the middle of it is not. On cancellation or discontinuation the customer has 30 days to access the account and download or export Customer Data, after which the account converts to inactive and a further 30-day export window is available on request against a one-time migration fee. CloudLex has no obligation to maintain Customer Data after 60 days and commits to securely overwrite or delete it 90 days following termination. Those are real deadlines a firm can plan a migration around, and few vendors in this pull publish them. What is absent is any retention position during the term, and nothing at all specific to the AI: no period for prompts submitted to the AI Tools, no period for generated outputs, no statement about conversation history in the chat features, and no customer-configurable or zero-retention setting. Two related provisions cut against the customer and are recorded here: CloudLex reserves the right to set storage limits per matter and in aggregate, and disclaims responsibility or liability for the deletion or failure to store any Customer Data. The privacy policy was read only in extract.

Not addressed. No retention period is published for uploaded records, generated demands, chronologies or assistant queries, and no deletion right at matter close is described. The question is broader on this record than on the document tools in this category because the product is the firm's case management system rather than a service it sends files to, so it holds the entire matter file for the life of the case and beyond, and nothing states what happens at closure or on termination. Checked the home page, the case management page, the product pages and the site navigation on 29 Aug 2026.

Nothing published describes separation between matters. Searched the Lexee AI page, the platform page, the pricing page and both terms of service on 31 Aug 2026 and located no ethical wall concept, no matter-level permission model, and no statement about whether the AI features are scoped to a single matter. The structural elements that exist sit at account level and are the customer's responsibility rather than the vendor's design: each user holds a sub-account with a unique username, sub-accounts may not be shared, and the agreement places the firm under an express obligation to ensure that all matters are created in accordance with applicable law and that Customer Data relating to them is made available only to those users and other individuals with the legal right to access it. Role-based access control is claimed in marketing with permissions set by the firm, which is the mechanism a firm would use to build a wall, without the vendor describing one. For a plaintiff practice running adverse matters, or one screening a lateral hire, the answer is not published.

Claimed and not documented, with more product substance behind the claim than most records in this category. Named features: permission management, system activity logs and secure case sharing, alongside a statement that data is accessible only to authorised users at the firm. Naming three distinct mechanisms is a stronger claim than a generic assurance and it is why this records as claimed rather than not addressed. Nothing documents how they work: no permission granularity, no statement of whether access is enforced at matter level, no description of whether the AI layer and the Ask Tiff assistant respect the asking user's permissions when answering across the case estate, and no account of how secure case sharing bounds access for an external recipient. On a platform that is the firm's system of record and answers questions across all of it, the permission behaviour of the assistant is the load bearing question. Checked the G2 listing, the case management page and the home page on 29 Aug 2026.

Legal compulsion is named as an exception and no notice is committed anywhere. The agreement provides that CloudLex will not access the customer's accounts or Customer Data except to provide the Services, to respond to service or technical problems, to comply with the law, or at the customer's request, and separately that safeguards will prevent disclosure by CloudLex personnel except to provide the Services, as compelled by law, or as permitted. Both formulations reserve the right to disclose under legal process without any accompanying undertaking. Searched the firm-facing Terms of Service, the Lexee AI Chatbot Terms and the Lexee AI and platform pages on 31 Aug 2026 and located no commitment to notify the customer that a demand has been received, no opportunity to object or challenge, no undertaking to resist or narrow a demand or to seek a protective order, no minimisation commitment, and no transparency report. The absence carries weight for this buyer segment because the platform holds medical records and settlement information on injured plaintiffs. The privacy policy was read only in extract and is the rebuttal route.

Not addressed. No government or law enforcement request clause, no commitment to notify a customer before producing data, and no transparency report were located. No business associate agreement is offered either, so there is no contractual instrument in public view that would govern permitted disclosures. The vendor holds the complete matter file including claimant medical records for firms using it as their case management system. Checked the home page, the case management page, the compliance references and the site navigation on 29 Aug 2026.

The question does not arise in its usual form and is recorded with the reason stated. The AI reads the firm's own matter file, the medical records and documents uploaded to it, and the case data the firm has already entered, so there is no vendor-assembled corpus of primary law, no third-party content licence and no upstream data supplier to identify. The agreement confirms the direction of ownership, making the customer the exclusive owner of Customer Data and limiting CloudLex to a licence over de-identified Aggregated Data. One adjacent point is worth recording because it is a corpus in substance if not in name: CloudLex takes a perpetual licence to compile Customer Data across its user base into Aggregated Data, expressly including to train AI models and to provide consultative and analytical information to its users generally, and owns the resulting Aggregated Data Reports. Nothing published describes what that pooled corpus contains, how it is governed, or what analyses are derived from it. Searched the Lexee AI page, the platform page and both terms on 31 Aug 2026.

Not addressed, and inapplicable in the usual sense with a live residue. The platform operates on the firm's own uploaded case files and medical records rather than a published law corpus, so there is no external legal source to name, license or date. The residue is twofold and unanswered: what the medical analysis models were trained on, and what supports the statutory and negligence framing in generated demand letters, since the vendor's own guidance states that damages language, statutory references and negligence framing vary by state and must be verified. Nothing published names a legal content source, a research provider or a jurisdictional rules base. Checked the demand letters page, the home page, the blog library and the site navigation on 29 Aug 2026.

Not applicable to this product class, and neither credited nor penalised. Lexee AI reads a matter's own records, medical documents and case data rather than retrieving legal authority, so there is no proposition of law whose continued validity would need checking and no citator is claimed anywhere. Searched the Lexee AI page and its six feature descriptions, the platform page and both terms of service on 31 Aug 2026. The currency question that does bite this product is recorded on the Citation Accuracy axis, where the agreement itself supplies the honest statement: outputs may not always reflect the most current legal standards, may not accurately reflect applicable people, entities, places or other facts, and may not be tailored to specific case circumstances, with the user made solely responsible for reviewing and verifying them.

Not addressed, and applicable rather than a scope fact. The vendor's own guidance states that demand letters carry statutory references and negligence framing that vary by state and that firms must verify their platform accounts for this, which establishes that legal authority reaches the output of products in this class including its own. No citator, research provider or treatment checking step is named anywhere, and nothing states what source supports statutory references in a generated demand or whether a superseded provision would be caught. The vendor identifies the risk in market education and does not state how its product handles it. Checked the demand letters page, the blog library, the home page and the site navigation on 29 Aug 2026.

The limitations are disclosed and the behaviour is not. Searched the Lexee AI page and all six feature descriptions, the platform page and both terms of service on 31 Aug 2026 and located no abstention path, no confidence or uncertainty indicator surfaced to a user, no threshold at which a feature declines to answer, and no statement of what happens when the case file does not support the question asked. The chatbot terms come closest without describing a mechanism, acknowledging to the end user that as an AI-driven chatbot Lexee AI may not be able to handle all inquiries and may not generate accurate responses in all cases. The vendor's answer to uncertainty is architectural rather than signalled and is recorded because it is the substitute: a published four-step workflow ends with a human review step in which an attorney or paralegal reviews, edits and approves output before use, and the agreement requires independent validation by a qualified attorney before output is used in proceedings or client communications.

Not addressed, and the vendor's own content identifies the exact failure case it leaves undescribed. Published guidance warns that a platform impressive in a controlled demo can fall apart on actual messy records with missing bills and inconsistent provider names, and separately that a platform should require organised case data rather than accepting a blob of records and guessing. Both describe behaviour under uncertainty as the thing that separates good products from bad, and nothing states how this product behaves: whether a missing bill is flagged, whether inconsistent provider names are surfaced as a conflict, whether a low confidence extraction is marked, or whether Ask Tiff declines when the file does not support an answer. Naming the failure mode in market education and not answering it for your own product is the pattern this record repeats across several axes. Checked the blog library, the home page, the demand letters page and the G2 listing on 29 Aug 2026.

No court order, opinion or disciplinary record naming this product has been located as of 31 Aug 2026. Instrument searched: the AI Hallucination Cases database maintained by Damien Charlotin, which tracks decisions worldwide where a court addressed hallucinated AI content and records the tool implicated where known, together with several independent 2026 sanctions trackers, searched on the company name and the product name. This is a statement about the public record on the date shown rather than a clearance. The exposure profile is worth stating because it differs from a research tool: Lexee AI drafts demand packages and summarises medical records rather than retrieving legal authority, so a fabricated case citation would more likely enter a filing from elsewhere. The nearer risks on this product are a mis-summarised treatment record or a demand overstating what the records support, neither of which this signal captures and both of which the vendor addresses through its human review step rather than through measurement.

None located, with the instrument named. General web searches combining the vendor and product names with court, order, sanction, fabricated citation and demand letter terms returned nothing on 29 Aug 2026, and no named docket database or court record tracker was searched. Recorded as a statement about what this search found, not as a clearance. The exposure shape covers both a misstated medical fact and a wrong statutory reference, since generated demands are stated to include statutory references and negligence framing, and the vendor names no source for either.

Professional obligations are referenced in the agreement as a category, and no authority is named. The AI Tools section commits CloudLex to maintaining the confidentiality and security of client data in compliance with applicable privacy laws and bar ethics rules, which is the only reference to bar ethics located in any customer agreement in this pull. The same agreement makes the firm solely responsible for satisfying duties owed to its clients, naming record-keeping standards and client trust accounting rules, ethical professional standards set for the profession, competent representation, timely filings and management of legal deadlines and court dates, and requires the firm to obtain its clients' affirmative consent to use of the service. Users are encouraged to disclose the use of AI Tools to clients and retain responsibility for such disclosures where required by law or professional standards. What is absent is any citation: searched both terms of service, the Lexee AI page and the platform page on 31 Aug 2026 and located nothing naming ABA Formal Opinion 512, any state bar guidance, or any specific rule, and nothing mapping a feature to an obligation a supervising lawyer could evidence.

Generic reference, and it breaks a five for five run of not addressed in this category. The vendor publishes that ABA Model Rules on competence and supervision apply to AI assisted drafting, that the firm owns the output, that attorney oversight is non negotiable and no compliant workflow skips the approval step, and that privileged communications must be safeguarded by choosing HIPAA compliant platforms under a BAA. Naming the applicable rules by category and identifying who carries the duty is materially more than the silence recorded on EvenUp, Supio, Eve, Tavrn and DigitalOwl. Held at generic reference rather than a stronger value because no specific opinion is named: ABA Formal Opinion 512 is not cited, no state bar guidance is engaged, no jurisdiction specific analysis appears, and the material is market education in a blog library rather than a product commitment or term. First record in this category above not addressed on this signal.

Efficiency is the pitch and the client's bill is not addressed. The published claims are about speed and repetition rather than cost, describing faster drafting, faster record review and faster access to information, with the ecosystem positioned as removing the need for separate AI vendors and tools. Searched the Lexee AI page and its six feature descriptions, the platform page, the pricing page and both terms of service on 31 Aug 2026 and located no per matter record of AI-assisted work for fee purposes and no guidance on how a firm should treat or disclose AI-assisted work when billing a client or accounting for case costs. The question has particular force for this buyer segment, since a contingency firm recovers case costs from the settlement and an AI-drafted demand package or medical chronology is work that would otherwise be paid for as a disbursement or absorbed. One provision sits adjacent without reaching it: the agreement encourages users to disclose the use of AI Tools to clients, which concerns disclosure of use rather than treatment of the fee.

Not addressed. No time saving figure, efficiency claim or return on investment claim was located in vendor material, which is unusual in this category and means there is not even a savings claim to record. Nothing appears on the claimant's side either: no position on whether platform cost is a case expense or firm overhead in contingency work, no disclosure guidance to clients, and no description of a record a firm could produce showing what portion of a demand was machine generated. That last omission sits oddly beside the vendor's own guidance that good platforms log what data was used, what was generated and who approved it, and that this is the firm's defensibility. Checked the home page, the product pages, the blog library and the site navigation on 29 Aug 2026.

The agreements answer some of what a client would ask and none of the supporting artifacts exists. What a firm could point to is real: a contractual restriction on training to de-identified Aggregated Data that also binds vendors and subcontractors, a four-circumstance limit on vendor access to Customer Data, a commitment to confidentiality in compliance with applicable privacy laws and bar ethics rules, HIPAA compliance, and a staged deletion timetable ending in secure overwriting 90 days after termination. What does not exist anywhere on the property, checked on 31 Aug 2026: no subprocessor or model provider list, no data processing addendum, no security questionnaire response, no trust portal, no audit report or route to request one, and no AI disclosure pack. The footer legal inventory is four documents, being a privacy policy, the firm-facing terms, the chatbot terms and a cookie policy. A firm asked by a client which third parties process its matter data would have no list to give, and the privacy policy expressly declines to name the infrastructure provider that holds it.

Not addressed. No trust centre, security page, subprocessor list, named model provider, independent attestation, business associate agreement or documentation request route was located. A firm has nothing it could forward to a client beyond repeating the vendor's own claim of HIPAA compliance and United States storage. The contrast within this category is stark and is the useful calibration: EvenUp reaches on request through a Trust Center portal, Tavrn through an offered BAA, DigitalOwl through both, and this vendor publishes guidance telling readers to choose HIPAA compliant platforms under a BAA while offering neither a BAA nor a route. Checked the home page, the case management page, the compliance and security references and the site navigation on 29 Aug 2026.

The duty is addressed in the agreement and no record exists to discharge it. CloudLex encourages users to disclose the use of AI Tools to clients, with the user retaining full responsibility for such disclosures where required by law or professional standards, and requires that outputs be independently reviewed and validated by a qualified attorney before being used in legal proceedings or client communications. That is an express contemplation that AI-assisted work will reach a court, and only one other vendor in this pull states it. What is missing is everything that would let a lawyer prove the position. Searched the Lexee AI page and its feature descriptions, the platform page and both terms of service on 31 Aug 2026 and located no model identification or versioning, so which system produced a passage cannot be established; no audit trail or log of AI invocations; no record of who reviewed, edited or approved an output despite human review being a published step in the workflow; and no export, certification template or guidance for a court's standing order on AI use.

Partial record, and the elements are present without being connected. On the source limb: demand letters are stated to cite specific medical records, bills and reports automatically, and smart citations pull directly from the firm's uploaded files, so an assertion can in principle be traced to a document. On the process limb: system activity logs are a named product feature, which is the raw material for an audit trail, and the vendor's own guidance states that a good platform logs what data was used, what was generated and who approved it. What is missing is any statement that this product produces that record: nothing describes what the activity log captures, whether it distinguishes machine generated content from human edits, whether it records an approval, or whether any of it is exportable. The vendor has described the artifact a court would want and has not said it makes one.