C

CloudLex

Lexee's six AI features drive work a firm would miss, on a case management system that stands without them. They cover voice and chat intake, demand package drafting, medical summaries and chronologies, questions about a matter, a client facing website assistant, and voice to task. The medical chronology and the demand draft are core plaintiff work, and the AI drives both, reading from and writing back to the case file.

Underneath is a complete practice management system: intake, matters, documents, calendaring, client communication, expenses, settlement calculation, analytics, electronic signature and archiving. The agreement treats the AI Tools as one part of the Services, and Lexee is marketed as one of four pillars alongside the platform, paralegal services and publishing.

Grounding is claimed in general terms, the contract is candid about limits, and nothing is measured. Chat answers are described as grounded in the case's documents and notes, and medical summaries are written back into the case file. Nothing says whether a summary or demand paragraph links back to the source record. The agreement states that outputs may not reflect current legal standards, may get people, entities, places or facts wrong, and may not fit the case, and it disclaims accuracy.

No accuracy figure, test set, evaluation or error rate is published on the Lexee AI page, the platform page, the pricing page or either terms of service.

CloudLex publishes its human review as a workflow. Its four step process for medical record summaries ends with Human Review: an attorney or paralegal reviews, edits and approves the output. Demand drafts are described as designed for staff review, and medical summaries as paralegal reviewed. CloudLex's FAQ says human review stays central to every workflow. The agreement requires outputs to be independently reviewed and validated, by a qualified attorney where applicable, before use in proceedings or client communications.

The client facing website assistant verifies a caller's identity before releasing case details, under the firm's control. What is missing is the failure path: no abstention, confidence signal or threshold for declining, and no route to report a wrong output.

Customers are named with their firms and titles: 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, attorneys at Glugeth & Pierguidi and the Law Office of Daniel Horowitz, and a paralegal at Abrams & Associates. The one figure is about migration: a firm moved over 300 cases without issue.

Nothing measures outcomes such as time saved or intake conversion, and no quote is dated. Client Stories and Client Reviews pages are also published.

Confidentiality and training carry substantive commitments from CloudLex. The customer owns its data exclusively, and CloudLex may access it only to provide the service, fix problems, comply with the law, or at the customer's request. Safeguards include preventing access by CloudLex staff outside narrow exceptions. CloudLex will not use customer data for training other than deidentified Aggregated Data, and will not let its vendors or subcontractors do so.

The AI section commits to keeping client data confidential under privacy laws and bar ethics rules. Two points cut against it: the agreement says customer data may travel unencrypted, and nothing describes separation between matters within a firm.

The professional responsibility position is complete, and it reaches the consumer. CloudLex is not a law firm, cannot give legal advice, and its AI creates no attorney client relationship. Use is limited to subscribers based in the United States. Outputs must be independently reviewed and validated, by a qualified attorney where applicable, before use in proceedings or client communications. The firm is responsible for its fiduciary, record keeping and trust accounting duties, competent representation, deadlines, and getting clients' consent to the service.

Users are encouraged to disclose AI use to clients, and the firm is responsible for what the chatbot says to clients and prospects. The separate chatbot terms tell claimants directly that Lexee AI cannot give legal advice. What is missing: no bar authority is named.

Responsible AI principles sit in CloudLex's contract, with nothing published behind them. The agreement's Transparency and Responsible Use section says the AI Tools follow principles of transparency, fairness and human oversight, and encourages users to disclose AI use to clients. Marketing says Lexee is continuously trained to stay reliable and responsible, and is designed to support human judgment. Missing from the Lexee AI page, the platform page and both terms of service: an owner of model behavior, testing before release, any published result, model documentation and bias measurement.

That gap matters because the AI talks directly to injured members of the public through intake and the client assistant.

Deletion deadlines are real, and for the rest CloudLex leans on Azure. After cancellation a customer has 30 days to export data, and a further 30 days on request for a one time migration fee. CloudLex securely overwrites or deletes customer data 90 days after termination. Its access to customer data is limited to four named cases, and safeguards cover access by CloudLex staff. The security page and FAQ describe AES-256 at rest, TLS 1.2 or above in transit, key rotation, multi factor authentication, role based access, backups and monitoring, attributed to Azure's framework.

What is missing: no subprocessor list, and no incident response or breach notice practice. The agreement also says customer data may travel unencrypted across connecting networks and disclaims liability for deleting or failing to store data, and the privacy policy disclaims the unnamed infrastructure provider's failings.

CloudLex disclaims the exposure its AI creates and gives nothing back. Damages for all claims are capped at the lower of the last paid invoice or two thousand five hundred dollars, so a monthly customer is capped near one month's fee. No carve out is named for confidentiality, security breach, gross negligence or willful misconduct. The service is provided as is, with every warranty disclaimed, and AI output carries its own disclaimer with no liability for errors or reliance.

The only indemnity runs from the customer to CloudLex, covering the firm's own negligence, including malpractice, and any client or prospect interaction through the chatbot or other AI Tools. There is no vendor indemnity, insurance position or service credit. Disputes go to AAA arbitration in New York before three arbitrators, with legal fee recovery capped at twenty thousand dollars.

Named connections cover the tools a small firm uses. Microsoft 365 has its own product page, and there is a Word connector and Gmail and Outlook email management that attach correspondence to the matter. A Legal App Integrator, electronic signature, iOS and Android apps and a referral engine for sending cases to other firms are offered. The agreement covers third party modules, each under its own addendum and charged separately.

What is missing: no API or developer documentation is published, and no document management or electronic billing system is named.

Delivery is in the cloud on Microsoft Azure, which CloudLex names on its pricing page, with round the clock monitoring and 256 bit encryption. The agreement limits use to subscribers based in the United States. No region or data center, selectable residency option, tenancy model, or location for AI processing is stated. Two provisions pull the wrong way. The agreement says customer data may travel unencrypted across connecting networks, and the privacy policy says servers sit with an unnamed third party provider whose security CloudLex does not guarantee.

Every certification CloudLex names belongs to Microsoft, and it says so. CloudLex's FAQ says it is built on Azure and inherits Azure's SOC 1, SOC 2 Type II and ISO 27001 certifications and its audited controls, including penetration testing, geo redundant data centers and encryption. The security page adds compliance with HIPAA, IRS and AICPA standards. An infrastructure provider's certification covers the provider's controls, not the application on top.

Nothing published claims CloudLex itself has been audited: no CloudLex SOC report, ISO certificate, auditor, scope, application penetration test, trust portal or route to request a report is published. HIPAA compliance is the one claim made in CloudLex's own name, without an attestation.

Nothing published says what runs the AI. No model, provider, version or inference location is named on the Lexee AI page, its six feature descriptions, the platform page, the pricing page or either terms of service. The agreement defines AI Tools by CloudLex's own branding, and marketing calls Lexee a PI trained AI without saying how. The agreement mentions third party providers in a general integration context, naming Google, Facebook, Apple, Microsoft and Amazon as examples, and its training clause binds unnamed vendors and subcontractors. No notice of model changes is promised.

No price is published at any level, and CloudLex says so. Its pricing page states it does not publish standard per user pricing, that pricing is customized by package, users, intake and case management needs, storage, integrations, AI and optional services, and that third party price figures are estimates only. There is no figure, rate, unit or package structure to price. The agreement gives billing mechanics instead: monthly or yearly billing in advance, automatic renewal at the original price, a ten day window to opt out after a renewal notice, no refunds for partial months or downgrades, a credit card on file, extra charges above subscribed users or matters, and separate charges plus a service fee for third party modules.

CloudLex documents its coverage and states one hard limit. Nine practice areas have their own pages: personal injury, slip and fall, product liability, mass torts, workers' compensation, social security disability, motor vehicle accidents, wrongful death and medical malpractice. It is built only for plaintiff personal injury firms. The agreement limits use to subscribers based in the United States. Paralegal services cover no fault litigation processing, court calendar management and bilingual intake. What is missing: no firm size, matter volume or state level coverage for deadlines and calendaring is stated.