Chamelio
Chamelio is a legal intelligence platform sold exclusively to in-house legal departments, built around two modules: Negotiate, a Microsoft Word add-in that reviews and redlines contracts against playbooks it can generate from a team's own precedent, and a Knowledge Center that holds contracts, templates and policies as a searchable repository with automatically extracted metadata. Agentic workflows chain multi-step legal work across intake, review, approval and signature, with approval steps and eligible approvers defined per workflow, and an AI agent answers questions from the department's own documents. It integrates with Slack, Salesforce, DocuSign, Google Drive and SharePoint, offers single sign-on through Entra ID and Okta with SCIM provisioning, and publishes a documented REST API with webhooks. The company positions the platform as a replacement for conventional contract lifecycle management systems and publishes a CLM migration tool. Chamelio is operated by Innvo AI Inc., which trades under the Chamelio name.
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 models are the engine of the capabilities the buyer is sold on: AI redlining in Word, a playbook generator that derives standards from a team's own precedent, automatic metadata extraction, agentic workflows and an AI agent answering from the department's documents. Underneath them sits a product that would still function without any of it, which the vendor effectively concedes by pitching itself as a replacement for contract lifecycle management systems and shipping a CLM Migrator. Strip the models out and a contract repository, a Vault, custom metadata columns, reminders, intake forms, task and matter tracking, approval routing, DocuSign orchestration and Insights dashboards remain, and that is a CLM. That combination is the B band rather than the A band, where removing the models would leave nothing to sell. Verified 2 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.
Accuracy is asserted and never measured. The documentation states that models from leading providers are continuously evaluated and that top performers are automatically deployed for specific tasks, under a heading claiming this will guarantee the most accurate and reliable results, but no benchmark, test set, figure or evaluation is published anywhere on the site or in the documentation. The product page states that every AI answer links back to the source document, which is real grounding for a product whose corpus is the customer's own material, and it is what keeps this off D. It falls short of B because no retrieval method is described and there is no accuracy figure an outsider could test. The published percentages, 89 per cent less review time on the home page and a customer's 90 per cent, measure time saved rather than correctness. Verified 2 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.
The review surfaces are documented in unusual detail because the API reference exposes the workflow engine. Tasks move through defined steps; an approval step carries eligible approvers and pending variables that can be retrieved; approval or rejection is submitted per task; a running task can be cancelled; and an activity log records comments, approvals and other actions. Redlining lands in Word as suggestions a lawyer works with rather than as applied changes. That is a real route back to human judgement, published rather than asserted. What is absent is the threshold. The vendor describes agentic workflows executing complex multi-step tasks and a customer describes the system handling a first pass and escalating only what needs legal review, but nothing published states which steps run unattended, what triggers an escalation, or what happens after the system is wrong. That missing limb is what the B band names. Verified 2 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.
Five customers are named with the individual and the title attached: Noa Weyl, General Counsel at Bizzabo; Noa Rosenberg Segalovitz, General Counsel at Lightricks; Aviad Levin, General Counsel at Socure; Maayan Yaakobovich, Senior Legal Counsel at Radware; and Duncan McQueen, Assistant General Counsel at Integrity. Two carry figures attached to the named customer, a reduction in legal review time of 90 per cent at Integrity and a fall in NDA turnaround from 24 hours to under an hour at Lightricks. What holds this below A is that nothing is dated and no measurement basis is given for any figure. A retrieval note belongs here: the home page carries four headline statistics whose values are rendered by script and extracted as zero, so those four numbers were not read and are not relied on. Verified 2 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.
Substantive and in more than one place. The Terms of Service carry an express clause headed No Third Party LLM Model Training, stating that Customer Data sent to third party large language models is not used to train them and that Chamelio has opted out of every available training option for each one; the data licence is confined to providing the service; and the documentation extends the commitment to Chamelio's own models. Segregation is addressed at the level this buyer segment requires, which for an in-house department is tenant separation rather than matter walls: the documentation states that each customer's data is processed in isolated environments and describes role-based access control, user groups, legal entities and SCIM provisioning. Two things keep it off A. Nothing published addresses attorney client privilege or work product treatment directly, which the A band requires as its own limb. Retention is stated only as data being kept as long as necessary for service delivery, with no period. Verified 2 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.
The only located position on the advice line is a liability clause: the Terms of Service state that Chamelio has no responsibility or liability for the accuracy of Customer Data or for the customer's usage of, or reliance on, Outputs. That is a disclaimer of reliance rather than a statement of what the product is and is not, and no page states that output is not legal advice. Meanwhile the marketing describes the product in advice terms. The home page carries a customer line, published by the vendor, describing the platform as providing strategic insight like a seasoned attorney, and the feature list includes risk and decision support, liability ranking and legal research. A boilerplate disclaimer in the terms alongside marketing that describes the product in advice terms is the C band exactly. The audience is not ambiguous, which is the other route into C: the product is sold exclusively to in-house legal teams, and there is no consumer facing surface, so that limb of the A band does not apply here. No bar or ethics guidance is engaged. Verified 2 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.
There is no responsible AI page, no governance framework, no named owner and no certification such as ISO 42001. What exists sits inside the security documentation under AI Model Security: continuous benchmarking of models from leading providers, automatic deployment of the best performer for a given task, controlled deployment and rollback through model versioning, output filtering and prompt injection safeguards. Those are mechanisms rather than principles, which is why this is not a bare principles page, but they are security and performance controls and the axis is explicit that security controls are a different subject. Nothing at all is published about uneven output across matter types, counterparties or populations, and no testing result of any kind is disclosed. Checked the home page, the security page, the full documentation index and the recoverable portions of the Terms of Service on 2 September 2026. Verified 2 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.
Most of the ground is covered with specifics. Encryption is stated as TLS 1.3 in transit and AES-256 at rest with key rotation. Access control is detailed: least privilege, regular user access reviews, restricted production access, multi-factor authentication for administrative access, role-based access control, session timeouts, and single sign-on with SCIM provisioning documented per identity provider. Incident practice is a published six stage process from detection through containment and forensic investigation to post-incident review, with a commitment to notify customers of incidents that affect them and a security contact address. Deletion is real and observable in the product, since the API documents document deletion and fires a webhook when a document is permanently deleted. The gap is the one the B band names: no subprocessor list is published. The documentation refers to AI sub-processors and to vendor security evaluations without naming a single one, and retention is stated only as being as long as necessary. Verified 2 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.
A real published position, read in part. The Terms of Service allocate loss expressly: Chamelio has no responsibility or liability for the accuracy of Customer Data or for the customer's usage of, or reliance on, Outputs, which is a direct disclaimer of the exposure this product creates. Article 10 is a limitation of liability that the parties agree forms an essential basis of the bargain, applies to the maximum extent permissible, and extends to affiliates, licensors and suppliers. Separate articles cover Indemnification at 9 and Warranty Disclaimers at 8.3, both named and both stated to survive termination. What could not be established is their content: the legal hub renders client side and returns no body, and the search index surfaced Articles 1 to 12 in fragments without reaching the indemnity scope, any cap figure or any warranty. This is graded B rather than C because C requires that liability be addressed only through a limitation clause, and that is false of an agreement carrying distinct indemnity and warranty articles. The unread scope is a limit on this reading, not a finding against the vendor. Verified 2 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.
A real documentation property carries a setup guide per integration, and each states what moves and in which direction. Salesforce: install the Chamelio AI package, generate contracts and sync legal data from Opportunities. DocuSign: signed contracts are captured automatically into the repository. Google Drive and SharePoint: documents import through a native file picker. Slack: legal knowledge, answers and workflow triggers surface in channels. Word: an add-in with its own installation guide delivers review and redlining in the drafting environment. Underneath sits a documented REST API with an OpenAPI specification, covering document upload, search, contract data retrieval, workflow initiation, task approval, signature envelopes and file download, plus thirteen webhook events for document and workflow lifecycle changes. Configuration is documented rather than gestured at, including single sign-on through Entra ID by OIDC and SAML, Okta by OIDC, and SCIM provisioning from both. iManage and NetDocuments are absent, but this product is sold exclusively to in-house departments rather than firms, so those are not the systems this buyer's work lives in. Verified 2 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.
Cloud delivery is clear and the specifics are not. The documentation states hosting on AWS and Google Cloud Platform, describes a multi-cloud strategy for redundancy, and names virtual private cloud isolation, web application firewalls, DDoS protection and network segmentation. On the two things this axis asks for, it stops at the level of an offer. Residency appears as options for specific geographic data storage, with cross-border controls and jurisdiction compliance mentioned, but no region is named anywhere and there is no way for a buyer to learn which regions are available without a sales conversation. No tenancy model is stated: the product is not described as multi-tenant, single-tenant or private anywhere on the site or in the documentation. The isolated processing environment the documentation describes is credited on the confidentiality axis, where it answers the segregation question, and is not counted twice here. Checked the home page, security page and full documentation index on 2 September 2026. Verified 2 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.
SOC 2 Type 2 is claimed on both the security page and in the documentation, and the documentation goes further than most by enumerating the scope as all five trust services criteria: security, availability, processing integrity, confidentiality and privacy. Third-party penetration testing by independent security firms is stated. What the A band asks for is missing on every count: no auditor is named, no coverage period or report date is published, no penetration test summary is offered, and no route to obtain the report is described. A trust centre exists at trust.chamelio.ai and is linked from the security page, but it renders client side and returned an empty document on 2 September 2026. That is a retrieval limit under the machine refusal rule and is not graded against the vendor; equally, nothing on it is credited, since its contents were not read. Verified 2 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 architecture is described and the providers are not named, which is the B band's second limb precisely. The documentation states that Chamelio uses the best model for each job rather than a single model, that models from leading providers are continuously benchmarked, that top performers are automatically deployed for specific tasks, and that model versioning gives controlled deployment and rollback. The Terms of Service define Third Party LLM as a defined term, state that a data processing agreement has been executed with each one, and record that Chamelio has opted out of their training options. Not one provider is identified anywhere. AWS and Google Cloud Platform are named, but as hosting, which says where things run rather than whose models they are. Nor is there any commitment to notify customers when the underlying models change, and automatic deployment of new top performers means they change without notice. Verified 2 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. Two independent page inventories were checked on 2 September 2026 and neither contains a pricing surface: the site's own navigation and footer run to Product, Security, Learn, Company, Careers, Partnership and Contact, and the documentation publishes a complete machine readable index of every page, which covers guides, integrations, API reference and webhooks with nothing on cost. The only commercial route offered is Book a demo. Module names are published, Negotiate and Knowledge Center, but a product structure is not a pricing structure: no tier, no seat or volume unit, no term and no figure appears anywhere. Verified 2 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.
The buyer boundary is stated more plainly than most records in this index manage. The documentation header reads that the platform is exclusively for in-house legal teams, a dedicated page answers who it is for, and the marketing is consistent with it throughout, so a law firm reading this site learns quickly that it is not the customer. Named customers bear that out, sitting at technology companies including Bizzabo, Lightricks, Socure, Radware, Integrity and Atera. What is missing is the other half of the A band. No practice areas are enumerated: the material describes document types the platform handles, contracts, templates, policies, compliance documents, corporate records and regulatory filings, which is a document taxonomy rather than a statement of practice coverage. No company size band, no jurisdiction and no geography is published first party, and nothing states which legal work the platform does not support. Verified 2 September 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?
The published terms prohibit training on customer content. Not a policy page, the agreement.
The prohibition is in the agreement under a clause headed No Third Party LLM Model Training, and it adds that Chamelio has opted out of all available training options for each third party model it uses. The data licence is separately confined to providing the service. The security documentation extends the commitment inward, stating that customer data is not used to train Chamelio's own models or those of its AI sub-processors, which is broader than the home page wording, which promises only that data is never used to train external or public AI models. One carve-out belongs on the record: Chamelio may compile and disclose anonymous aggregated statistics, defined as Derived Data, which it owns along with any products incorporating it. That clause names statistics rather than training and so does not reverse the value, but a buyer should read it. The agreement renders client side and this text was recovered through the search index rather than by loading the page.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
Retention is acknowledged in public materials with no stated period.
Retention is acknowledged in the security documentation under a privacy guarantees heading and no period is given, for prompts, outputs or documents. Deletion exists as a product function rather than a published window: the API documents permanent document deletion and fires a core.document.deleted webhook when it happens, so a customer can remove material, but no retention setting is exposed and no zero retention option is stated as available. The termination and deletion provisions of the Terms of Service could not be read, because the legal hub renders client side and the search index did not surface Article 11 beyond its survival clause.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
The product maintains its own permission model, documented, requiring the firm to keep it aligned.
Chamelio operates its own permission model rather than inheriting one. Documents arrive from Google Drive and SharePoint through a native file picker into Chamelio's own repository, so the source system's access model does not travel with them and is not enforced at query time. What Chamelio publishes in its place is documented: role-based access control, user groups for organising access across the organisation, legal entities, per-document access customisation, and SCIM provisioning from Entra ID and Okta so that group membership can be kept in step with the identity provider. The documentation also states that each customer's data is processed in isolated environments. The consequence for the buyer is the one this value describes: the permission model has to be maintained in Chamelio and kept aligned with the source systems by hand.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
No located term or policy addresses third party requests for customer data.
Nothing locatable addresses disclosure to authorities or in response to legal process, and nothing addresses notice to the customer if a demand arrives. The reason is retrieval rather than drafting, and it is stated here so no reader infers that Chamelio has simply not written the term. Terms of service exist and are referred to from the site, but they sit behind a JavaScript-gated hub that returns the page frame and no body. The full escalation ladder was run: both www and non-www forms, the footer and navigation of pages that do render, sitemap and robots paths, and search queries built from distinctive contract language to pull the text out of the search index rather than the page. Two fragments surfaced that way and neither concerns third party requests: one confirming the customer owns all Customer Data and Outputs, and a paired analytics and feedback provision. The operator independently attempted the same retrieval on separate tooling and obtained the same empty frame, which establishes the block as a property of the site rather than of one fetcher. This row is written on the value's own words, which turn on what is located rather than on what the vendor did, and a buyer sitting where this reading sat could not read the term either. Surfaces checked and confirmed on 2 September 2026.
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.
Checked the home page, product page, security page, the complete documentation index and the recoverable portions of the Terms of Service on 2 September 2026. No public material identifies a corpus. The platform's material is chiefly the customer's own contracts, templates, policies and negotiation history, so the coverage risk this signal tracks does not arise in its usual form. It is not entirely absent either: the home page lists legal research among the AI Agent's capabilities, and no source, jurisdiction or licence basis is stated for whatever underlies that feature.
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.
Checked the home page, product page and the complete documentation index on 2 September 2026. No public material addresses subsequent history, treatment flags or citator coverage. The platform is built around the customer's own document corpus rather than primary authority, and no citator function is claimed anywhere, so the honest reading is that the question is not addressed rather than that a weaker form of checking exists. The legal research capability named on the home page is not documented further and nothing states whether any authority it surfaces is checked for currency.
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.
Checked the home page, product page, security page and the complete documentation index on 2 September 2026. Nothing describes what the platform does when it cannot ground an answer. No abstention path, no no-answer behaviour and no confidence or grounding score is documented, so the weaker values are false of this record as well. The nearest published statements run the other way: the security documentation claims the model selection approach will guarantee the most accurate and reliable results, and output filtering and prompt injection protection are described, but those are security controls over what the system emits rather than an account of what it does when it does not know.
Fabricated Citation Record
Does a public court record exist involving output from this product?
No court order, opinion or disciplinary record naming this product has been located as of the date shown. This is a statement about the public record, not a finding about the product.
Searched the AI Hallucination Cases database maintained by Damien Charlotin, and reporting drawing on it, on 2 September 2026 on both the product name Chamelio and the corporate name Innvo AI. No court order, opinion or disciplinary record naming the product was located. This is a statement about the public record rather than a finding about the product, and it is worth noting that the platform is sold to in-house departments for contract work rather than to litigators for filing, so the exposure this signal tracks is structurally lower for this product than for a research tool.
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.
Checked the home page, product page, security page, company page, the complete documentation index and the recoverable portions of the Terms of Service on 2 September 2026. No public material engages with ABA Formal Opinion 512, any state bar opinion, or any other named ethics guidance. Nothing addresses professional responsibility even in general terms, so this is a full absence rather than a generic reference.
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.
Savings claims are made plainly and repeatedly: an 89 per cent reduction in review time on the home page, a customer's 90 per cent reduction in legal review time, and NDA turnaround falling from 24 hours to under an hour. Nothing published addresses billing, fee or disclosure treatment, and no per matter record of AI assisted work was located. One edge is worth recording, because it recurs for in-house products. This signal assumes a vendor selling to a firm that bills a client by the hour, and Chamelio's buyer is the in-house department, which is the client rather than the biller. The compression it markets lands on outside counsel spend and internal capacity rather than on an invoice the platform's buyer issues, so the top values could not apply here on any evidence.
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.
Checked the home page, security page, the complete documentation index and the recoverable portions of the Terms of Service on 2 September 2026. No subprocessor list is published and no model provider is named anywhere. The gap is explicit rather than inferred: the security documentation states that customer data is not used to train the models of Chamelio's AI sub-processors, and the Terms of Service define Third Party LLM and record that a data processing agreement has been executed with each one, so the vendor confirms these parties exist and identifies none of them. AWS and Google Cloud Platform are named, but naming a host says where a model runs rather than whose it is, which does not satisfy this signal. A department asked by a counterparty which providers see its contracts could not answer from anything Chamelio publishes.
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.
Checked the home page, product page, security page and the complete documentation index including the API reference on 2 September 2026. Nothing addresses judicial standing orders, AI use disclosure or verification certification. The platform does emit a task level audit trail: the API retrieves activity log history covering comments, approvals and other actions, and the security documentation states that audit trails are maintained for system access and changes. That records who did what to a task, not which model produced which passage or what it retrieved, so it does not answer the question this signal asks. The product class matters too: this platform is sold to in-house departments for contract and knowledge work rather than for court filing, so the disclosure obligation it tracks would usually fall on outside counsel instead.