Product and intended use
Define the configuration, people, information and tasks being assessed.
Product and plan covered, and the product name
Public claim only
The AI functions are published as part of Clio Manage and are gated by plan: the pricing table shows the 'Do more with AI' block off at EasyStart and on at Core, Signature and Elite, and the FAQ states AI is included 'on Core and above. AI comes as part of the plan rather than as a separate add-on.' The former marketing name 'Clio Duo' is absent from the body copy of both Australian pages read on 2026-09-27.
Ask: On our Australian order document, which plan tier are we on, and which of the published AI functions does that tier switch on?
AI functions published
Public claim only
The Australian legal-AI page (read 2026-09-27) groups the functions under four headings and attributes each to Clio Manage: extracting deadlines from court documents into calendar events and tasks with a side-by-side view of the source document; generating draft invoices, routing them to approvers, matching receipts and expenses to matters and configuring whole jobs such as end-of-month billing; drafting motions, letters and client updates from matter activity and summarising long documents; and creating tasks, notes, events and expenses on matter set-up, recommending document names and surfacing priorities.
Ask: Demonstrate each published AI function on our own matter data, and confirm which can be disabled per user and per matter type.
Deployment and where the service runs
Public claim only
Clio Manage is cloud software; the Australian application is at au.app.clio.com (terms clause 10.4). The published sub-processor list (20 August 2026) gives Amazon Web Services as the cloud hosting provider for Clio Manage with data locations 'United States, European Union, Canada, Australia'. The list does not state which location holds an Australian firm's tenant, and no on-premises or private-cloud option was found.
Ask: For our tenant, state in writing which region holds the production data, the backups, the AI vector index and the logs.
Jurisdiction configuration
Public claim only
Terms clause 2.15 states: 'Themis uses one code-base for all jurisdictions. Subscriber is required, using settings available within the Service, to configure the Service for its own jurisdiction and to verify that the settings meet the Subscriber's requirements. Themis will highlight known features that may require Subscriber review.' The obligation to verify Australian fitness therefore sits with the firm, by contract.
Ask: Which settings must we configure for Australian practice, and which features has Clio identified as requiring our review under clause 2.15?
Vendor content directing how AI describes the product
Not confirmed
Checked deliberately on 2026-09-27. Neither the Australian legal-AI page, the Australian pricing page, the Australian Terms of Service, the product-specific terms, the sub-processor list nor the data protection addendum contains a block addressed to AI models, assistants or crawlers, and three earlier site-map operations over clio.com and clio.com/au, one of them searched for 'llms.txt', 'information for AI assistants' and 'ai-info', returned no such page. Recorded as not found rather than absent: a search-filtered site map cannot prove a page does not exist.
Ask: Do you publish any page or block of content, including an llms.txt file, that tells AI models or crawlers how to describe Clio?
Data, controls and requirements
Compare the actual configuration with firm, client and jurisdiction requirements, supported by evidence.
Client authority and disclosure to clients
Public claim only
Clause 2.17 requires the subscriber to provide all necessary notices to, and obtain all necessary rights and consents from, all applicable individuals including its own clients, and says 'Subscriber will determine the content of the notices it provides.' Clause 14.4 places sole responsibility on the subscriber for 'appropriate and legally compliant disclosures to its end-users' about the use of AI, the nature and limitations of AI-generated responses, data practices, and any human oversight or review processes. Clause 3.11 repeats the consent warranty for Content.
Ask: What notice do you say an Australian firm must give its clients before matter content is processed by the AI functions, and will you supply model wording?
Foundation-model providers
Public claim only
The sub-processor list (last modified 20 August 2026) has an 'AI Service Providers' table. Applicable to Clio Manage it names Amazon Web Services (AWS Bedrock) as AI processor, data location United States and European Union; Anthropic, Inc, United States; OpenAI, LLC, United States and European Union; Google LLC (Google Vertex AI), United States, European Union, Canada and Australia; Microsoft Corporation (Azure Foundry), United States and European Union; Braintrust Data, Inc for AI analytics, evaluation and testing, United States; and Turbopuffer, Inc as vector database, United States, European Union, Canada and Australia. No model provider is named on either Australian product page.
Ask: Which of these AI processors actually handles each AI function on our tenant, and which model version, and what notice do we get when that changes?
Sub-processor register and objection rights
Public claim only
Exhibit C to the Australian terms is a published sub-processor page, last modified 20 August 2026, split into infrastructure providers, AI service providers, feature-specific providers, payment processors, Clio affiliates and Themis service providers, each with applicable products and data locations. Under the data protection addendum clause 3.2 Themis notifies the subscriber of new sub-processors; a subscriber objecting on data-protection grounds may ask for the data to be moved, and if that is not reasonably possible either party may terminate on 30 days' notice; silence for 30 days is deemed acceptance.
Ask: Does the 30-day notification and objection mechanism in the addendum apply to our Australian subscription, and how will notice reach us?
Training on customer content
Not confirmed
The pricing FAQ (read 2026-09-27) answers 'Is my firm's data used to train AI?' with 'No. Your firm's data stays in Clio and is never used for AI training or any other external purpose.' Terms clause 14.6 says: 'Themis may de-identify and aggregate the Content submitted to, and Output received from, AI Services and use the same in order to improve and ensure the quality of the AI Services. Subscriber's use of AI Services does not grant Themis the right to use any of Subscriber's Confidential Information for the purpose of training generalized LLMs.' The contractual clause therefore permits de-identified aggregated use of matter content and AI output to improve the AI Services while prohibiting only generalised-LLM training; the FAQ states a flat no. Clause 2.14 also permits perpetual publication of aggregate anonymised reports on Content trends and processing of Usage Data.
Ask: Which statement governs our subscription, and will you contract that no de-identified or aggregated matter content or AI output is used for any model training or tuning, including by your AI sub-processors?
Feedback, telemetry and quality monitoring
Public claim only
Clause 14.6 permits de-identified aggregated use of AI inputs and outputs to improve and ensure the quality of the AI Services. Clause 2.14 lets Themis collect Usage Data, defined as technical logs, data and learnings about the subscriber's use of the Services, and 'use, share and otherwise process such Usage Data for its lawful business purposes', provided Themis does not publicly identify the subscriber as the source, and states 'Subscriber will not interfere with the collection of Usage Data.' Section 15 says Themis may use feedback on Beta Services 'without restriction, payment, or attribution'. Braintrust Data, Inc is the published AI analytics, evaluation and testing sub-processor.
Ask: Can we opt out of Usage Data collection and of Braintrust evaluation for AI interactions, and if not, what exactly is sent?
Retention of content, prompts and outputs
Public claim only
Clause 8.1 gives the subscriber 90 days after cancellation or termination to retrieve Content, and clause 10.7 provides that after no less than 90 days all Content associated with the subscription 'will be irrevocably deleted from the Service'. Escrowed Data, where a subscriber has elected escrow under clause 2.13, remains available for six months. No retention period is published for AI prompts, outputs, embeddings held in the Turbopuffer vector database, or Usage Data.
Ask: State the default and configurable retention for AI prompts, outputs, the vector index and AI interaction logs on our tenant, and whether any of them survive matter deletion.
Deletion and certified erasure
Public claim only
Clause 10.7 provides for irrevocable deletion of Content from the Service after no less than 90 days from cancellation or termination. The data protection addendum clause 7.1 gives the subscriber, within 90 days of termination, an election between retrieval followed by deletion of all other copies, or deletion outright; clause 7.2 allows Themis and its sub-processors to retain personal data where applicable law requires, for that purpose only. No certificate of deletion and no deletion commitment binding the named AI sub-processors was found.
Ask: On exit, will you certify in writing the deletion of matter content, AI prompts and outputs, embeddings and backups, including at Anthropic, OpenAI, AWS, Google and Microsoft, and within what period?
Vendor access to content
Public claim only
Clause 21.3 states: 'The Content is stored securely and encrypted. Only Themis, with strict business reasons, may access and transfer the Content and only to provide Subscriber with the Service. Themis will make reasonable efforts to provide notice to Subscriber prior to such access and transfer.' Clause 4.2 binds Themis and its third-party vendors and hosting partners to hold Content in strict confidence. Clause 2.2 says Themis 'does not review or pre-screen the Content'. The published affiliate list places Clio group companies in Canada, the United States, the United Kingdom, Ireland, Australia, Spain, Colombia, Mexico, Brazil, Chile and Peru.
Ask: Who may read our matter content and AI interaction logs, from which countries, under what approval, and will you give us the access log?
Authentication, single sign-on and audit
Public claim only
Clause 3.3 says Themis 'may, at its discretion, require all Authorized Users to use two-factor authentication' and that 'Two-factor authentication may be disabled by the Authorized User through the account settings, subject to any additional security requirements imposed by Themis' — so by contract the second factor is not mandatory for the user. The pricing FAQ nonetheless asserts every plan includes multi-factor authentication. The pricing table publishes SAML-based single sign-on on Signature and Elite only. Clause 5.8 provides that any Clio features restricting a user's access to Content are supplied 'AS IS' and may contain defects, with liability disclaimed. No audit-log export for AI use was described.
Ask: Can we enforce multi-factor authentication so no user can disable it, and can we export a complete audit log of AI prompts, outputs and web-search use?
Encryption in transit and at rest
Public claim only
Clause 21.3 states 'The Content is stored securely and encrypted', and clause 21.3 also asks the subscriber to accept the risk that information transmitted electronically may be intercepted. Clause 5.1(b) requires passwords to be transmitted in an encrypted format and clause 5.4(a) requires information security practices adhering to industry standards for transmitting and storing Content. The pricing FAQ asserts data is 'encrypted in transit and at rest'. No algorithm, TLS version, key-management arrangement or customer-managed key option is published on the documents read.
Ask: Name the encryption algorithms, TLS version and key-management arrangement for our tenant, the AI call path and backups, and say whether customer-managed keys are available.
Independent security assurance
Public claim only
The pricing FAQ states 'Clio is SOC 2 Type II certified and meets GDPR requirements, and backs up your data multiple times a day using mirrored facilities. Independent third parties audit Clio's security and privacy on a regular basis.' That is an answer on a marketing page, not a contractual warranty. The contractual position is narrower: clause 5.4(d) requires Themis, within 30 days of request, to provide a SOC 2 or SOC 3 report or comparable description of security measures 'in respect of the data center facilities used to host the Service and the Content', and states that to obtain the report the subscriber must enter into an agreement with the third-party provider of the report. No certificate, auditor name, report date or ISO certification was found.
Ask: Provide the current SOC 2 Type II report, its auditor, period and exceptions, and confirm whether its scope covers the AI functions and the AI sub-processors rather than only the data centres.
Contracting entity, liability and forum
Public claim only
The Australian terms are made with Themis Solutions (Australia) Pty Ltd, also known as Clio, and incorporate the privacy policy, Exhibit A service level commitments, Exhibit B data protection addendum for GDPR and Exhibit C authorised sub-processors. Clause 21.9 applies the law of New South Wales with disputes resolved by the courts of New South Wales in Sydney. Clause 11.1 excludes liability for loss resulting from the Services except to the extent caused by Themis's fraud, negligence or wilful misconduct, and where liability can be limited it is limited to Themis's choice of re-supplying the services or paying the cost of re-supply. Clause 14.5 adds a subscriber indemnity for claims arising from its deployment or use of the AI Services. No ACN or ABN is published.
Ask: Confirm the contracting entity and its ACN, and whether the liability limit in clause 11.1 and the AI indemnity in clause 14.5 are negotiable for an Australian firm.
Cross-border transfers and Australian Privacy Principle 8
Public claim only
The published sub-processor list gives Australia as one of four data locations for the Clio Manage hosting provider, but for the named AI processors applicable to Clio Manage the data locations are: AWS Bedrock, United States and European Union; Anthropic Inc, United States; OpenAI LLC, United States and European Union; Microsoft Azure Foundry, United States and European Union; Google Vertex AI and Turbopuffer, United States, European Union, Canada and Australia; Braintrust Data, United States. The list therefore does not state that inference for an Australian firm runs in Australia, and for four of the named AI processors no Australian location is published. Terms clause 5.7 says Themis will comply with the Privacy Act 1988 (Cth) and refers international transfer detail to the Australian privacy policy, which returned HTTP 522 from the origin when requested on 2026-09-27. Product-specific terms clause 2.4 warns that sub-processors used for Web Search 'may process data in a location other than your jurisdiction or your selected data processing region'.
Ask: For each AI function, name the country in which inference runs for our tenant, and state whether Australia-only AI processing is available and on what terms.
Incident notification
Public claim only
Clause 5.5 requires Themis to report to the subscriber, with all relevant details except those that could prejudice other customers' data security, any event Themis reasonably believes represents unauthorised access to, disclosure of, use of, or damage to Content, and to do so 'within 72 hours after learning of the Security Breach'. Clause 5.6 sets out cooperation duties on cause, affected Content, prevention of recurrence, litigation and mitigation. The terms do not address notifiable data breach reporting to the Australian Information Commissioner; that is referred to the privacy policy, which could not be retrieved. No incident history was found.
Ask: How does the 72-hour clause work with our own notifiable data breach obligations, and have there been any incidents in the last 24 months affecting Clio Manage or its AI sub-processors?
Change notice for features, models, terms and processors
Public claim only
Clause 2.11 lets Themis modify or discontinue any feature at any time with or without notice, except that 30 days' notice is given of a modification that materially reduces functionality, during which an Administrator may cancel and take a pro-rata refund. Clause 21.7 lets Themis amend the agreement, notifying subscribers of material changes before they take effect. The sub-processor page is dated and prior versions are not published there, while the addendum gives a 30-day objection window for new sub-processors. The pricing FAQ says Clio 'ships product improvements several times a month' and that 'Updates roll out automatically'. No notice period is published for changing the model behind an AI function.
Ask: What written notice will we get before a model or AI sub-processor changes, and can we pin or defer an AI model change?
Export and exit
Public claim only
Clause 8.1 and clause 10.7 give 90 days after cancellation or termination to retrieve Content before irrevocable deletion. Clause 2.13 offers optional replication to an escrow agent under a separate agreement, with Escrowed Data available for six months. Clause 10.4 allows cancellation only by an Administrator through au.app.clio.com/settings/subscription/edit and states that 'For security and compliance reasons, the Administrator must call support to complete the cancellation. Cancellations shall not be accepted by any other means.' The pricing FAQ asserts retrieval of contacts, matters and financial records 'in open, nonproprietary formats'. No export format is published for AI prompts, outputs or interaction logs.
Ask: List the export formats for matters, documents, AI prompts, AI outputs and audit logs, and confirm the export can be run before we give notice.
Third-party services and connectors
Public claim only
Section 18 provides that third-party services accessed through the Service 'are not "Services" under this Agreement and are not subject to any terms related to the Service, including related warranties, indemnities, service commitments or other obligations', are governed by the third party's own terms, and that Themis may replace, disable or restrict access to any of them at any time without notice, disclaiming all liability. Clause 3.9 governs API access and lets Themis suspend API access for excessive use and modify or discontinue API access with or without notice.
Ask: Which third-party services and integrations will be enabled on our tenant, what matter data does each receive, and will you confirm none are enabled without our written approval?
Open-web search
Public claim only
Product-specific terms section 2 publishes a Web Search feature of the AI Services that 'enhances your experience by directly querying publicly available websites to supplement responses drawn from Materials'. It can be disabled at account level by an Administrator and, when active, at individual conversation level by a user. Clause 2.3 states Web Search 'is performed through one or more of Themis' subprocessors (currently, OpenAI)'. Clause 2.4 warns the data may be processed outside the subscriber's jurisdiction or selected data processing region and puts the decision on the subscriber. Clause 2.5 requires Web Search results to be identified as such, and clause 2.7 states quotations may be inaccurate, incomplete or out of context and must be independently verified.
Ask: Is Web Search on or off by default on our tenant, is it reachable from the Clio Manage AI functions as well as Clio Work, and can we lock it off firm-wide?
Agent actions and confirmation
Public claim only
The legal-AI page publishes a configurable job: 'Configure entire jobs—like end-of-month billing—according to your preferences, with built-in checkpoints to monitor and approve its work as needed.' The product-specific terms describe drafting features including 'agentic features that read, analyze, draft, or edit documents and may reference, incorporate, or be informed by Materials'. Terms clause 14.4 states the subscriber 'retains full control over how the AI Services are implemented, configured, presented, and used'. Neither document publishes which actions can execute without a confirmation step, and the checkpoints are described as approved 'as needed' rather than mandatory.
Ask: List every action the AI can take without a person confirming it, and show us the setting that makes a named approver mandatory for billing jobs.
Human review before use
Public claim only
Clause 14.2 requires the subscriber '(a) to only use the AI Services and Output with human oversight, and (b) that Subscriber is responsible for reviewing the Output, including, without limitation, for accuracy, completeness, appropriateness for Subscriber's use case, to ensure Subscriber's compliance with legal, regulatory, and professional organization requirements ... before disclosing or otherwise using the Output.' The same clause confirms Themis does not review Output. The pricing FAQ asserts 'you review and approve everything before it reaches a client or the court', which the terms make the firm's obligation rather than a product control.
Ask: Which product settings enforce the human-oversight obligation in clause 14.2, as opposed to relying on each user, and can a reviewer be made mandatory by role?
