T
Theo Ai
Theo Ai sells predictive litigation intelligence to the defence side. Its published product is a portfolio command centre for enterprise legal departments: it collects case material automatically from the systems a legal team already uses, including Microsoft, Google, Workday and Salesforce, turns the resulting emails, invoices and filings into structured data, and presents a live view of every matter, its cost trajectory and its risk signals in one place.
Over that it runs analytics rather than search: it surfaces patterns across a portfolio rather than a single case, flags matters it judges to be under-reserved, tracks exposure as new facts arrive, summarises each case with attribution back to the underlying source material, and recommends which claims to settle and which to fight. The company describes the intended user as a litigator or in-house legal team drowning in volume, and publishes indicative matter counts by category, from general liability and workers' compensation claims through employment disputes, regulatory matters, customer and vendor disputes and internal investigations.
It markets to five sectors: retail, insurance, chemicals, hospitality and gaming, and pharmaceuticals and medical devices. The company began in 2024 selling case-outcome and settlement prediction to litigation funders, announcing a partnership with Mustang Litigation Funding in March 2025, and has since repositioned around litigation defence for corporate legal departments; the prediction engine remains the core of what it does.
A General Counsel advisory board of sixteen named senior legal figures is published on the site. The product is reached through a web application with password and single sign-on access, and onboarding is currently by invitation only, with a public waitlist. Theo AI, Inc. is based in Palo Alto, California.
Capability grades
All 15 axes, graded from public sources on the date shown. Hover a grade to see what the letter means on that axis.
AI Centrality
How much of the product is actually AI. Whether the machine learning is the mechanism the buyer is paying for or a feature layered onto conventional software, and whether the vendor is specific about which is which.
The artificial intelligence is the product, and there is nothing underneath it to sell, which is the A band. Every function the vendor publishes is model output: synthesising a caseload from documents collected automatically, extracting structure from emails and invoices, recognising patterns across a portfolio, projecting cost trajectories, flagging matters as under-reserved, summarising each case with attribution to source material, and recommending which claims to settle and which to fight.
There is no repository, workflow engine, billing system or document store being sold underneath that a customer would still license if the models were removed; the vendor's own framing is a prediction engine, and its earliest published description was of a proprietary data model and prediction engine rather than of software with intelligence added. The 2024 to 2025 announcements describe the roadmap in the same terms, the funding being applied to expand proprietary data pipelines, enhance the legal corpus and reinforce supervised learning with legal experts.
This grade says nothing about how well the models work or how much is disclosed about them; on that, see the Model Supply Chain and Citation Accuracy rows, both of which sit far lower. Verified 12 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.
Grounding is claimed and nothing is measured on any surface the vendor publishes, which is C. The grounding claim is a single sentence and it is the only one located: every case is summarised with clear attribution to source material. That is a real architectural claim in the product's own idiom, and R40 keeps the D limb from firing because the accuracy content is not a bare assertion that the system does not hallucinate.
Nothing supports it further. No accuracy figure, test set, error rate, evaluation or benchmark appears on any first-party surface, and no failure mode is named. Recorded and deliberately not credited: the chief executive is quoted in a December 2025 interview with a technology publication claiming roughly 85 per cent predictive accuracy against 60 to 65 per cent for human reviewers. That is a third-party publication rather than a vendor disclosure, it names no test set and no method, and it is not what R15 credited on Pre/Dicta, which published its figure, described a test set of more than 50,000 motions across 94 federal district courts and named its own limits.
The contrast is the point: this corpus already holds a litigation prediction product that published its measurement, so the absence here is a choice rather than a feature of the product class. R15 also applies to the citator and authority limbs, which do not bite on a product that predicts outcomes rather than citing law. Verified 12 September 2026.
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.
No oversight structure is published for a system that acts on live client matters, which is the D band. What the product does is published plainly: it recommends which claims to settle versus fight, automatically and in real time, flags matters as under-reserved, and in the vendor's words manages the minutiae. What happens around that decision is published nowhere. No mode structure, no confidence threshold, no escalation path, no review surface, no statement that a lawyer approves an output before it is relied on, and no account of what the system does when the evidence is thin.
The two documents the vendor does publish do not fill the gap: the Terms of Service govern use of the website and never mention output, and the Privacy Policy expressly excludes information processed on behalf of enterprise customers. The nearest thing to a human-in-the-loop statement anywhere on the estate is incidental marketing copy, that the platform lets a team review the portfolio and make decisions with confidence and lets attorneys and paralegals focus on higher-level work.
That positions a human as the reader of an output; it is not an oversight mechanism and it is not offered as one. This grade is a statement about what is published on the date shown, not a finding that no oversight exists in the product. Verified 12 September 2026.
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.
What stands in for deployment evidence is an advisory board and an investor list, and the outcome figures published carry no basis, which is C. The site's principal social proof is a General Counsel Board of sixteen named senior legal figures, one identified on the page as the General Counsel of SmartBiz Bank, alongside a strip of investor logos. An advisory board is not a customer and is recorded here rather than credited; nor are investors.
No customer is named anywhere on the current estate, no case study is published, and no logo wall of users appears. One named deployment does exist and is first-party: the vendor announced a partnership with Mustang Litigation Funding in March 2025, with the counterparty's chief technology officer quoted, but the account is forward-looking rather than measured, projecting that a one per cent annual improvement in case selection would raise returns.
The figures that circulate are all unattributed or third-party: an early claim that review time falls from between seven and thirty days to seconds, an assertion that early users found the platform verified their underwriting teams' conclusions, and the 85 per cent accuracy claim made in an interview. None states a basis. The record would move on a named customer with a figure and a method, which is the ordinary route out of this band. Verified 12 September 2026.
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.
Nothing is published on how client confidences are handled by a product built to ingest them, which is the D band, and the shape of the gap is worth stating precisely because it is not an unread document. Two instruments are published and both were read in full. The Terms of Service, last updated August 2025, govern use of the website at theoai.ai; they contain no confidentiality obligation running to a customer, no security commitment, no data handling terms and no reference to case material.
The Privacy Policy, last updated 6 April 2025, opens by excluding the very thing this axis asks about: it states that it does not apply to information processed on behalf of enterprise customers as a processor or service provider, and that such use is governed by agreements with those customers. Those agreements are not published. So a buyer evaluating this product before signing can read nothing about training on client data, segregation between customers or matters, retention or deletion of case files, or what any model provider may retain.
That matters more here than on most records, because the published product ingests litigation files automatically from a customer's own Microsoft, Google, Workday and Salesforce systems. Recorded and not credited: the application's sign-in page offers single sign-on, which is an access method rather than a confidentiality commitment. Verified 12 September 2026.
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.
Nothing is published on the advice line for a product that produces legal work, which is the D band. The product tells a legal team what a case is likely to be worth and recommends whether to settle it or fight it. No statement was located anywhere on the estate that the vendor is not a law firm, that its output is not legal advice, that a lawyer must exercise independent professional judgement before relying on it, or that the recommendation is a suggestion rather than a conclusion.
The two published documents do not supply it: the Terms of Service disclaim warranties in respect of the website and its content and say nothing about advice, professional responsibility or the practice of law, and the Privacy Policy is a data document that expressly does not reach the product. Nothing addresses who may use the platform, whether a supervising lawyer's competence duties are engaged when a settlement recommendation is acted on, or any jurisdictional limit, and the site is marketed to litigators, paralegals and legal operations staff alike without distinguishing between them.
This grade describes the published record on the date shown; the absence is unusually complete for a product in this category, and it is the row most likely to move if a customer agreement is ever published. Verified 12 September 2026.
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 is published for a system whose output affects legal outcomes, which is the D band. There is no responsible AI page, no set of published principles, no framework such as the NIST AI Risk Management Framework, no certification, no accountable person or function named, no description of what is evaluated before a model change ships, and no statement of any kind about how the system is tested. Neither published document addresses AI: the Terms of Service govern website use and the Privacy Policy excludes enterprise customer processing.
The bias question is live on this product in a way it is not on most of the corpus and its absence is therefore worth naming rather than passing over. A model that predicts settlement values and case outcomes from historical litigation data is learning from a record that reflects who was represented by whom, in which venue, against which counterparty, and what those parties could afford to accept; nothing published addresses whether output varies by claimant characteristics, venue, counsel or claim type, or whether that has been examined at all.
The vendor's own published account of its method, that it reinforces supervised learning with legal experts, is a training-process description rather than a governance disclosure and is recorded on the Model Supply Chain row. Verified 12 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.
Nothing is published on retention, deletion or access for a system that holds client documents, which is the D band, and the absence is established rather than untested. The Privacy Policy carries a retention section, and it is expressly scoped away from the product: the policy states at the outset that it does not apply to information processed on behalf of enterprise customers, so its retention language, which in any event says only that personal information is kept as long as needed or permitted, reaches website visitors rather than case files.
Its security section is a single sentence about reasonable organisational, technical and administrative measures, with no encryption commitment, no access control description and no incident practice. There is no subprocessor list, no security page, no trust centre, no data processing addendum and no statement of where anything is hosted. Deletion is addressed nowhere for customer material. Two observations are recorded rather than credited, so a reader knows what was found: the application sign-in page offers single sign-on alongside password authentication, which is an authentication method and not a stewardship disclosure; and the Terms of Service grant a perpetual, irrevocable, sublicensable licence over user Submissions, which on its own words covers material posted through the website rather than case documents uploaded to the application. Verified 12 September 2026.
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 only through a standard limitation clause that disclaims the exposure the product creates, which is C, and here the clause reaches the product by an indirect route worth setting out. The application's sign-in page states that by signing in the user agrees to the Terms of Service, and those Terms are a website terms of use. Their liability provisions are nonetheless what a user is bound by. Section 14 supplies the site and its contents as is, where is and where available, without warranties of any kind, and disclaims merchantability, fitness for purpose, non-infringement and title.
Section 16 excludes indirect, incidental, consequential, special, exemplary and punitive damages including loss of profits, use and data, makes ceasing to use the site the user's sole and exclusive remedy for dissatisfaction, and caps aggregate liability at the total amount, if any, paid to the company to use the site. Section 17 runs an indemnity the other way, the user defending and indemnifying the company for claims arising out of their use of the site.
Nothing anywhere allocates the loss when a settlement recommendation or an exposure figure is wrong, no indemnity covers output, and no insurance or warranty position is published. Verified 12 September 2026.
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.
Integrations are named in a sentence with no documentation an implementer could use, which is C. Four systems are named and they are the right ones for the workflow: the vendor states that the platform gathers data points automatically from the tools a team uses every day, from Microsoft, Google, Workday and Salesforce, and adds that the emails and invoices held in them become a source of intelligence. That is more than a logo wall and it does describe, at the highest level, what moves.
What is absent is everything below that level. No integration page exists, no connector list, no developer documentation, no API, no authentication or configuration requirement, no statement of direction of flow, no description of what is read as against written back, and nothing about what a customer must do to connect a system. The one technical fact established directly is on the application sign-in page, which supports single sign-on alongside password authentication; the identity provider is not named.
Recorded and not credited because it is third-party: technology press reports that the product is designed to work inside email rather than through a dashboard, which if published first-party would be a material integration fact. Verified 12 September 2026.
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.
Nothing is published on where the software runs or where client data sits, which is the D band. No hosting arrangement, cloud provider, region, data centre, tenancy model or residency option is stated on any surface located. The Terms of Service address jurisdiction only in the sense of governing law and market availability, stating that the site is controlled or operated from the United States, that it is not intended to subject the company to any non-United States jurisdiction, that it may not be appropriate or available in some non-United States jurisdictions, and that the company may limit availability to any person, geographic area or jurisdiction it chooses.
That is a statement about who may use the website, not about where customer data is processed or stored, and it is recorded here so a reader can see that the nearest published geography is not residency. The Privacy Policy would be the ordinary home for a processing-location statement and it expressly excludes enterprise customer information from its scope. The product is delivered as a hosted web application at an app subdomain, which establishes that it is cloud-delivered and nothing more. Verified 12 September 2026.
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 security attestation was located, which is the D band. There is no trust centre, no security page, no compliance page, no certification badge of any kind on any surface read, and no reference anywhere to SOC 2, ISO 27001 or any equivalent standard, whether as held, in progress or available on request. No penetration testing, vulnerability disclosure programme or audit regime is described. There is accordingly no access flow to grade under R5, because there is nothing to request: the estate contains no sales-gated security artifact, not even a contact route for a security review.
The only security statement located anywhere is one sentence in the Privacy Policy, that the company seeks to use reasonable organisational, technical and administrative measures to protect personal information within its organisation, followed by the standard acknowledgement that no system can be guaranteed secure; and that policy states at its outset that it does not apply to information processed on behalf of enterprise customers.
The ordinary reading of this record is early-stage rather than evasive, and the note should be read that way, but the axis grades what a buyer can verify before signing and the answer is nothing. Verified 12 September 2026.
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 vendor refers to proprietary models without identifying what sits underneath, which is C in its plainest form. The first-party language is consistent across the estate and the announcements: a proprietary data model and prediction engine, proprietary data pipelines, an enhanced legal corpus, supervised learning reinforced with legal experts, and firm-specific prediction engines built on a customer's own case history.
Every one of those describes an approach rather than a component. No model is named, no version is given, no third-party provider is identified, no hosting arrangement for inference is stated, and no commitment exists to notify a customer if any of it changes. There is no subprocessor list to fall back on. Recorded and expressly not credited, because it is third-party rather than vendor disclosure: technology press reporting in late 2025 states that the platform draws on multiple large language models from OpenAI, Google and Anthropic and is built primarily on Google's Gemini, fine-tuned for vertical legal tasks.
If the vendor published that itself it would move this row materially, which is exactly the point of the axis. What a customer inherits today is undisclosed, on a product whose whole function is to send case files, and by the vendor's own account medical and insurance records, to a model. Verified 12 September 2026.
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.
No pricing information is published at any level, including the unit of charge, which is the D band. There is no pricing page, no plan or tier name, no band, no minimum, no term, no statement of whether the product is licensed per user, per matter, per portfolio or per prediction, and nothing about what implementation or data onboarding adds. The site's only commercial surfaces are a waitlist form and a calendar link to book a demonstration.
The Terms of Service contain generic transactional boilerplate about products, orders, shipping and credit cards that appears to be unadapted template language rather than a description of how this product is sold, and it is recorded as such rather than read as pricing structure. Under R10's closing discipline a page that only invites a conversation is an absence and belongs in this note alone, so no VendorPricing row is written for this record.
One adjacent fact is recorded because it bears on what a buyer can obtain rather than on what it costs: the site states that onboarding is currently by invitation only, so the commercial route is not merely unpriced but gated. Verified 12 September 2026.
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.
Coverage is described with real substance and the boundaries are left open, which is B, and this is the strongest of the disclosure rows on the record. The buyer is identified precisely rather than broadly: litigation defence teams inside corporate legal departments, with two published solution surfaces, one for the general counsel and one for product liability, and named user roles of attorney, paralegal and legal operations.
Sector coverage is enumerated rather than claimed at large, naming retail, insurance, chemicals, hospitality and gaming including hotels, resorts, casinos and cruise ships, and pharmaceuticals and medical devices, with the explanation that these are the sectors where litigation volume never slows. Matter coverage is the most specific element and is unusual for a vendor this size: a published table sets out six categories the product is built for, general liability claims, workers' compensation and employee claims, employment and human resources disputes, regulatory and compliance matters, customer and vendor disputes, and internal investigations, each with indicative annual matter counts and page volumes.
What is left open holds it off A. No jurisdiction is named anywhere, nothing states which matter types or claim values fall outside the model's competence, and the historical shift in audience, from litigation funders to plaintiff-side selection to defence-side portfolio management, is not reconciled on the current estate. Verified 12 September 2026.
2 public documents
The public pages on file for Theo Ai, with the recorded signals each one supports and the date it was last read. Open any of them and check the reading against the record.
-
theoai.ai6 signals
Ethical Walls and Matter Segregation, Primary Law Corpus Provenance, Good Law Verification and 3 more
Read Sep 12, 2026
-
app.theoai.ai/login5 signals
Client Data in Training, Prompt and Output Retention, Third Party Request and Subpoena Notice and 2 more
Read Sep 12, 2026
Legal Signals
What each signal meansA signal records what public sources say on the date shown. It is not a grade and it is not a recommendation. Where a signal reads Not addressed, it means the index did not locate the material in public sources on that date, which is a statement about disclosure rather than about the product.
Client Data in Training
Can material a lawyer puts into this product be used to train a model?
No customer agreement, terms of service or equivalent contract is published on any surface located, and no policy page states a position on training. Nothing is granted and nothing is withheld, so a client has no term to hold the firm to. Where a policy page does state a position, the row takes the matching policy value instead and the summary records that no agreement exists.
No customer agreement is published and no policy states a position on training, so a client has no term to hold this vendor to. What is published, and both documents were read in full, is a website Terms of Service last updated August 2025 and a Privacy Policy last updated 6 April 2025, reachable as PDFs linked from the application sign-in page rather than from the marketing site, whose own privacy link is a dead anchor.
Neither reaches customer case material. The Terms govern use of the website at theoai.ai and never mention training, models or output. The Privacy Policy states in its second paragraph that it does not apply to information processed on behalf of enterprise customers as a processor or service provider, and that such use is governed by agreements with those customers; those agreements are not published anywhere located.
Two provisions are recorded so a reader can see what was considered and why neither carries the row. The Privacy Policy lists improving and developing products and services among its purposes, including data analysis and developing new services, but only for the website information within its scope. And Terms section 9 grants a perpetual, irrevocable, sublicensable licence to use, analyse and exploit user Submissions for any purpose, which on its own words covers material posted through the website rather than case files uploaded to the application, though the application's sign-in flow binds users to those Terms.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
No located public material states how long prompts and outputs are retained.
No located public material states how long case material, prompts or generated output are retained, and this is an established absence rather than an unfinished search. The Privacy Policy does carry a retention section, and it is scoped away from the product before it begins: the policy applies to information collected through the vendor's websites, social media pages and online communications, and expressly not to information processed on behalf of enterprise customers.
Within that scope it says only that personal information is retained for as long as needed or permitted in light of the purposes for which it was obtained, unless a longer period is required or permitted by law, which is a criterion rather than a period. The Terms of Service address retention nowhere. No data processing addendum, security page, trust centre or subprocessor list exists on any surface located. Nothing states whether a case file uploaded for prediction is held after the prediction is produced, whether a customer can delete it, or what happens to anything at the end of a relationship.
The surfaces read on the date shown were the home page in full, the application sign-in page, and both published documents in full.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
No located public material addresses walls or matter level segregation.
No located public material addresses walls or matter-level segregation. Nothing published describes separation between customers, between matters inside one customer, or between the users of a single deployment, and no permission model, role structure or access group is described anywhere. The one access-related fact established is on the application sign-in page, which supports single sign-on alongside password authentication; that is an authentication method rather than a segregation model and it is recorded rather than credited.
Two features of the published product make the silence worth naming. The vendor states that the platform collects data automatically from the systems a legal team already uses, naming Microsoft, Google, Workday and Salesforce, which means it reaches across a customer's own estate rather than sitting behind a single upload; and the announced roadmap is firm-specific prediction engines that leverage a customer's own case history, which raises directly the question of whether one customer's history can influence another's prediction, addressed nowhere.
The Privacy Policy that would ordinarily carry a processing-boundary statement expressly excludes enterprise customer information from its scope.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
Published terms or policy address disclosure to authorities or in response to legal process, and no commitment or reservation regarding customer notice is located anywhere. The vendor has told the customer that data can leave and has said nothing about whether the customer hears of it.
Disclosure to authorities is addressed and customer notice is absent, which is this value. The Privacy Policy's disclosure table lists authorities and others among the recipients and states that the vendor may disclose information to law enforcement, public, regulatory and government authorities, courts, or other entities obtaining valid subpoenas, where required by law or legal process or where the vendor deems disclosure appropriate for other legal, compliance or fraud-prevention purposes.
That second limb is broader than compulsion and is quoted so a reader sees it. Nothing anywhere commits the vendor to notify a customer of a demand, reserves discretion over whether to notify, promises to seek a protective order or to redirect the requester, or sets any timeframe. No transparency report exists. One scope limit belongs in the reading and does not change the value: the policy states that it does not apply to information processed on behalf of enterprise customers, so what a buyer is being told about here is website and business-contact information rather than the case files the product ingests, and for those the position is not addressed at all because no customer agreement is published.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
No located public material identifies the corpus behind the product’s answers.
No located public material identifies the corpus behind the product's answers, and on this record that is the sharpest of the disclosure gaps, because for a prediction engine the corpus is the product. The vendor refers to it repeatedly without ever identifying it: proprietary data pipelines, an enhanced legal corpus, a proprietary data model, supervised learning reinforced with legal experts, and firm-specific engines leveraging a customer's own case history.
Not one of those names a source, a jurisdiction, a court record set, a date range or a licensing basis, and no coverage statement of any kind appears. Two things a buyer would need to weigh are therefore unavailable. Whether the historical settlement and outcome data behind a prediction was lawfully obtained and on what terms, which matters because settlement figures are typically confidential; and whether a customer's own case history, once ingested to build a firm-specific engine, remains theirs, which is unaddressed because no customer agreement is published.
Recorded and not credited because it is third-party: technology press reporting in late 2025 describes the platform as built on private settlement records obtained through litigation funders. Verified against the home page, the application sign-in page and both published documents on the date shown.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
No located public material addresses whether authority is checked for subsequent history.
No located public material addresses whether authority is checked for subsequent history, and on this product class the question does not arise in its usual form. The product cites no cases, statutes or regulations to a reader. It works on a customer's own matters and on historical outcome data, and what it emits is a prediction, an exposure figure, a reserve flag and a case summary, none of which is a proposition of law that a lawyer would shepardise.
The nearest adjacency is currency of a different kind, whether the historical data behind a prediction is recent enough for the prediction to hold as law and practice shift, and nothing published addresses that either: no update cadence, no data vintage and no statement of when a model was last retrained appears anywhere. Recorded so the row states the position rather than leaving a reader to infer it from a product category. The home page, the application sign-in page and both published documents were read on the date shown.
Refusal and Uncertainty Behaviour
What does the product do when the answer is not in the corpus?
No located public material addresses what the product does when it cannot ground an answer.
No located public material addresses what the product does when it cannot ground an answer. Nothing states that the system declines to predict, marks a prediction as unsupported, reports that a case falls outside the data it holds, or escalates rather than answering, and no evaluation demonstrating any such behaviour is published. One distinction is worth drawing because it could otherwise be mistaken for a confidence signal.
This product's output is itself probabilistic: the vendor describes estimating the odds of success and a range of recovery, and a probability attached to an outcome is a statement about the case, not a statement about how much the model trusts its own reading of the file. Nothing published exposes the second thing. The gap matters on a product that recommends settling or fighting automatically and in real time, because the case where the system has too little to go on is exactly the case a reviewer needs flagged.
The surrounding documents do not fill it: the Terms of Service disclaim warranties as to the website's content, and the Privacy Policy does not reach the product.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
No court order, opinion or disciplinary record addressing fabricated or hallucinated legal citations produced by this product has been located as of the date shown. This is a statement about the public record on that one subject, not a finding about the product, and this signal is not a litigation history.
Searched on 12 September 2026, on both the product name and the company name, against published trackers of decisions on AI-generated fabricated citations including coverage of the Damien Charlotin AI Hallucination Cases database and two independent sanctions trackers, for any court order, opinion or disciplinary record addressing fabricated or hallucinated legal citations produced by this product. None located. This is a statement about the public record on that one subject as of the date shown, and under R119 this signal records fabricated citations and nothing else, so it is not a litigation history.
One note for a future reader: the vendor's name collides with several unrelated products and companies using the word Theo, so any future search needs the corporate qualifier to be meaningful. Note also that this product does not generate citations to authority, so the shape of exposure this signal tracks is not the shape this product presents.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
No located public material engages with bar or ethics guidance.
No located public material engages with bar or ethics guidance. No bar opinion is named, ABA Formal Opinion 512 does not appear, no state guidance on generative AI in legal practice is referenced, and nothing maps the product to any jurisdiction's rules of professional conduct. Nor is professional responsibility referred to in general terms, which is what separates this from the records that take the tier above: neither published document mentions professional obligations, competence, supervision or the practice of law at all.
The Terms of Service, read in full, are a website terms of use running to twenty-three sections and containing no reference to legal advice or to the professional context in which the product is used; the Privacy Policy is a data document that excludes enterprise customer processing from its scope. The absence sits against a product that recommends whether to settle or fight a live matter and is marketed to attorneys, paralegals and legal operations staff.
Recorded as an absence in the published record on the date shown, not as a finding about the vendor's internal practice.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
Public materials claim time savings without addressing billing or disclosure, and the product sits inside a fee relationship between a lawyer and a client where those savings would change the bill.
Time savings are claimed and nothing addresses billing or disclosure, on a product that sits inside a lawyer-client fee relationship for at least part of its published market. The savings claims are the headline of the vendor's own announcements: that the average mid-sized firm reviews roughly 650 cases a year taking between seven and thirty days each, and that with this product the time is compressed into seconds; and on the current site, that legal teams resolve matters faster and do more with the same headcount.
The fee relationship is engaged because law firms are a named buyer in the vendor's own material, the May 2025 announcement describing settlement prediction tools tailored for Big Law firms alongside general counsel, and case assessment is conventionally billable work. Nothing published addresses what happens to the bill when an assessment that took days takes seconds, whether AI-assisted analysis is identified on an invoice, or whether a client is told the tool was used.
Recorded because it complicates the picture rather than changes the value: the product's current positioning is toward in-house departments and, earlier, litigation funders, and for those buyers no client bill is in the loop.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
No located public material supports a client side disclosure obligation.
No located public material supports a client-side disclosure obligation, and none of the three artifacts this signal looks for exists. There is no subprocessor list on any surface. No model provider is named anywhere, so a firm or a company asked by its counterparty which third party sees its case files cannot answer from anything this vendor publishes; the only provider information in circulation is third-party press reporting and is not the vendor's disclosure.
There is no client-facing disclosure material, no data processing addendum, no security exhibit and no consent or notification pack that could be forwarded. The value is not on-request either, because nothing indicates the material exists behind a sales conversation: the estate contains no security or compliance contact route, no trust centre and no request mechanism of any kind, so under the discipline that a value's own words must be true, on-request would assert the existence of something no surface evidences.
What is published instead is a website Terms of Service and a Privacy Policy that expressly excludes enterprise customer processing and routes it to unpublished customer agreements.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
No located public material addresses court disclosure or verification certification.
No located public material addresses court disclosure or verification certification. One element sits close enough to be worth recording and is deliberately not credited: the vendor states that every case is summarised with clear attribution to source material, so a reader of a summary is told where a proposition came from within the customer's own file. That is a usability and trust claim addressed to the person reading the summary, not a record addressed to a court or a certifying lawyer, and it is a single marketing sentence with nothing behind it.
Nothing states that any output identifies which model produced it, and no model is named anywhere in any event; nothing distinguishes machine-generated content from human-edited content in an exportable form; no audit trail, export or per-document record is described; and no disclosure template, certification form or court-facing guidance was located. The question has real weight on this product, because a settlement recommendation or exposure figure informs a decision a party may later have to explain, and because at least one published matter category, regulatory and compliance matters, sits close to proceedings where the basis of an assessment can be probed.