---
title: "Cicero (Corporate Solutions Group Pty Ltd, trading as Automatise)"
url: "https://ailawframework.com/software/cicero"
type: "software_profile"
site: "AI Law Framework"
id: "cicero"
vendor: "Corporate Solutions Group Pty Ltd, trading as Automatise"
category: "Legal-specific"
segment: "eDiscovery and litigation"
confidence: "high"
last_reviewed: "2026-09-27"
---

# Cicero (Corporate Solutions Group Pty Ltd, trading as Automatise)

> Document-analysis platform for litigation and disputes: maps pleadings to defences, builds chronologies, searches across large document sets, codes defined data points, tests propositions and lists the people appearing…

Canonical page: https://ailawframework.com/software/cicero  
Last reviewed: 2026-09-27

Site index for agents: https://ailawframework.com/llms.txt

Plan covered: Cicero software-as-a-service under the published SaaS Terms plus an Order Form. Covers the six published analysis functions and the Relativity, iManage and local-upload paths. The Order Form and Documentation need separate review.

Document-analysis platform for litigation and disputes: maps pleadings to defences, builds chronologies, searches across large document sets, codes defined data points, tests propositions and lists the people appearing in the documents.

## Capabilities

- eDiscovery document review
- Chronology building
- Document summarisation
- Knowledge search
- Data extraction

## Key facts

| Fact | Value |
| --- | --- |
| Deployment | SaaS, Private cloud |
| Hosting regions | Australia |
| Australian region | Yes |
| Assurance | ISO 27001 (published claim), SOC Type II (as worded on the vendor's home page), ISO 42001 (published claim, announced 22 May 2025) |
| Training on customer content | Unknown |
| Retention | The SaaS Terms require each party to return, or on request destroy or permanently de-identify, all copies of the other party's Confidential Information within 10 business days of expiry or termination; Client Material is the Client's Confidential Information. Retention is permitted where needed to comply with law, for litigation, for internal quality assurance and record-keeping, or to perform the agreement. Separately, Automatise 'may delete or destroy the Client Material 90 days after the termination or expiry of this Agreement'. No in-life retention period is published for Outputs, chronologies, coding decisions or query history. The privacy policy says personal information is retained for the duration of the relationship unless law requires longer. |
| Integrations | Relativity (document import and push-back), iManage (document import and push-back), Local computer upload, Microsoft Word (export), Microsoft Excel (export), NetDocuments (published as on the way), Nuix (published as on the way), Microsoft SharePoint (published as on the way) |
| Legal content coverage | The product analyses the customer's own document set. No primary-law, legislation or case-law library is claimed on any page read. |
| Pricing | Fees are set out in an Order Form, quoted in Australian dollars and exclusive of GST. The SaaS Terms allow Automatise to increase fees by five percent on each anniversary of the commencement date, and charge support, training and other professional services at its professional services rates on quotation. No refunds are offered other than as required by law. No pricing page appeared in a map of the site and no figure is published. |
| Australian presence | Yes. The contracting entity is named in the vendor's own SaaS Terms: 'Corporate Solutions Group Pty Ltd ACN 632 573 105 of Unit 1603, 568 Oxford Street, Bondi Junction NSW 2022 trading as Automatise ABN 48 632 573 105'. The agreement is governed by the laws of New South Wales with non-exclusive New South Wales jurisdiction, business days are defined by Sydney public holidays and fees are quoted in Australian dollars. The same terms state 'Automatise's Cicero servers are located in Australia. Automatise will ensure that any User Content is processed in Australia and will not be transferred to, or be accessible from, any other country.' The privacy policy commits to the Privacy Act 1988 (Cth) and refers complaints to the Office of the Australian Information Commissioner. The three firms listed here are named in dated items in the vendor's own news listing on the pages read; those item bodies render as stubs, so the scope of each engagement could not be read from the vendor's site. A map of the site also returned news-item URLs referring to Meridian Lawyers, Wotton Kearney, Colin Biggers & Paisley and MinterEllison; those item pages were not opened within the evidence budget, so those firms are not recorded as named customers. |
| Website | https://www.cicero.com.ai |

## What the research found

| Topic | Status | Finding | Open question | Sources |
| --- | --- | --- | --- | --- |
| Product and plan covered | Public claim only | The SaaS Terms define Cicero as 'the AI-driven software-as-a-service known as Cicero developed for use with documents in the legal industry, including to search, review, summarise and synthesise information, including all software, applications plugins, mobile applications and other applications and services provided from time to time'. What a particular customer gets is set by the Order Form and the Documentation, and the Order Form ranks above the standard terms where they conflict. No tiers or editions are published. | Which of the six published functions, and which import and export paths, will our Order Form actually cover, and what does the Documentation say the service includes? | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai) |
| Deployment model | Public claim only | The SaaS Terms describe a hosted software-as-a-service accessed with per-user credentials and state that 'Automatise's Cicero servers are located in Australia'. The home page adds 'Cicero is powered exclusively by privately hosted language models. No shared infrastructure.' and, under a GDPR heading, 'Deploy in any jurisdiction using secure private cloud.' Nothing read says whether the environment is multi-tenant or a separate deployment per customer, and no cloud provider is named. | Is our data held in a tenancy shared with other clients or a separate deployment, which cloud provider and Australian region is used, and where do the privately hosted models physically run? | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai) |
| AI features in scope | Public claim only | The vendor publishes six functions: Pleading Analysis, which extracts every allegation from a Statement of Claim and maps each to the response in the Defence as a pleadings matrix; Chronologies and Timelines, filtered for relevance against nominated allegations and exported as schedules of evidence; Investigations, a cross-document query across large sets; Extractions and Coding of customer-defined data points; Evidence Matrices, which test propositions against the document set and mark gaps and contradictions; and Dramatis Personae, listing individuals by role, relationship and relevance. Every function is a model-performed analysis; there is no non-AI product underneath. | Demonstrate each of the six functions on our document set, and state which are generally available today versus in development. | [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai) |
| Jurisdictions and legal content | Public claim only | The product is presented for litigation and disputes and works on the customer's own documents rather than a law library; no primary-law source is claimed. The contracting entity, governing law, business-day definition and currency are Australian. The vendor's news index includes an item on an update to a New South Wales Supreme Court practice note on artificial intelligence, the body of which renders as a stub. | Which Australian court practice notes on AI use has Cicero been assessed against, and what does the product produce to satisfy a disclosure requirement about AI-assisted preparation? | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai); [Cicero Achieves ISO42001 Certification - vendor news item published 22 May 2025, with dated news index](https://www.cicero.com.ai/news/cicero-achieves-iso42001-certification) |
| Licence and pricing unit | Public claim only | The SaaS Terms grant a non-exclusive, royalty-free, non-transferable right for the term for the client and its End Users to access Cicero for the client's internal business purposes. The agreement runs for an Initial Term set in the Order Form and renews automatically for equivalent periods unless either party gives at least 60 days' notice before expiry. Fees may be increased by five percent on each anniversary of the commencement date. Interest on unpaid amounts is the Reserve Bank of Australia cash rate target plus three percent, and access may be suspended on seven days' notice for non-payment. | Provide the Order Form with fee basis, initial term, renewal notice date, the five percent uplift and any volume limits on documents, queries or matters. | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx) |
| Integration with firm systems | Public claim only | The home page states documents are pulled from Relativity, iManage or a local computer and that refined outputs can be pushed back into iManage or Relativity or exported to Word or Excel, with a footnote that 'NetDocuments, Nuix, and SharePoint - are on the way'. The SaaS Terms define Third Party Services as 'any third party services connected to and/or integrated with Cicero' and disclaim liability for interruptions caused by them. | For our stack, which connector is generally available today, what permissions does it need in iManage or Relativity, and what happens to documents pulled into Cicero if the connector is removed? | [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai); [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx) |
| Support and service levels | Public claim only | The Service Level Agreement annexed to the SaaS Terms commits to 99 percent uptime availability during business hours and sets response targets: Priority 1 (critical) one hour initial response, hourly updates and a four hour target resolution; Priority 2 four hours, four hours and two business days; Priority 3 four hours, eight hours and five business days. Scheduled maintenance is notified at least 72 hours in advance. Support, training and other professional services are charged at the vendor's professional services rates. Automatise reserves the right to update the Service Level Agreement from time to time by notice to the client. | What hours count as business hours for the uptime commitment and the response targets, what remedy applies when they are missed, and will you fix the Service Level Agreement for the term rather than reserving a unilateral right to change it? | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx) |
| Published quality evidence | Not confirmed | The home page publishes time comparisons for four tasks - a pleadings matrix '3 days to 45 min', a first-draft chronology '2 weeks to hours', an evidence matrix '4 weeks to 1 day' and document coding 'weeks to hours' - and a customer account of a pilot on a complex international dispute. The SaaS Terms take the opposite position on quality: Output 'is provided on an as is basis', is 'based on content ... the accuracy or reliability of which is not reviewed or verified by Automatise', and 'Automatise does not warrant the accuracy, reliability or completeness of any Output'. No accuracy measurement, recall figure or independent evaluation is published. | Provide any measured recall and precision for allegation mapping, chronology extraction and data coding on a matter like ours, and say what the marketing time comparisons were measured against. | [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai); [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx) |
| Task fit and verification | Not confirmed | The home page describes a three-stage workflow - 'AI First Pass', 'Lawyer Review & Refinement' with 'full source traceability' where 'every output is a starting point, not a final answer', and 'Export & Integrate' - and says outputs are traceable and editable. The SaaS Terms require the client to accept that it 'must not rely on any Output and must undertake its own enquiries in relation to any matters detailed in any Output' and that it 'will not rely on the Outputs as truth or factual information', and the client indemnifies Automatise against third-party reliance on Output. The traceability claim is not repeated in the terms. | For each function, what does the product show as the source of an entry, and how do we evidence to a court that each entry was checked against the source document? | [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai); [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx) |
| Vendor content directing how AI describes the product | Not confirmed | Checked on 27 September 2026. A map of cicero.com.ai returned 26 URLs and none was /llms.txt, /ai-info, /ai or /for-ai. None of the pages read - home page, terms and conditions page, the downloaded SaaS Terms, the privacy policy or the two news items - contains a block addressed to AI models, assistants or crawlers. This is a negative result on the URLs returned and the pages read, not proof that no such page exists elsewhere. | Does Automatise publish any page or block of content that instructs AI models, assistants or crawlers how to describe Cicero? | [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai); [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - Privacy Policy, updated 20 February 2026](https://www.cicero.com.ai/privacy-policy) |
| Client authority and professional use | Not confirmed | The SaaS Terms place the authority burden on the firm: the client must make all disclosures and obtain all consents so that it may lawfully provide Client Personal Information to Automatise and so that Automatise may lawfully handle it, must comply with the Privacy Laws in its use of Cicero, and indemnifies Automatise against third-party claims arising from reliance on Output. Legal professional privilege is not mentioned in the terms or the privacy policy. The privacy policy states 'we will never share your confidential Client Data ... with any third party excepting our cloud service providers'. | What client notice or consent do you expect a firm to obtain before its clients' documents are loaded into Cicero, and do you take any contractual position on preserving legal professional privilege over material processed by the models? | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - Privacy Policy, updated 20 February 2026](https://www.cicero.com.ai/privacy-policy) |
| Foundation-model providers | Not confirmed | The home page states 'Cicero is powered exclusively by privately hosted language models' and goes no further. No model provider, model family, version or hosting arrangement is named on the home page, the terms and conditions page, the SaaS Terms or the privacy policy. The SaaS Terms define Automatise Material to include 'machine learned algorithms generated by Cicero', which are the vendor's property. A cached third-party university publication annotates one Australian deployment with two model vendor names; that is not vendor-published and is deliberately not recorded here. | Name every model used by each Cicero function, its version, who publishes it, where the weights are hosted, and what notice we get before a model is changed. | [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai); [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - Privacy Policy, updated 20 February 2026](https://www.cicero.com.ai/privacy-policy) |
| Subprocessors | Not confirmed | The SaaS Terms allow subcontracting on notice alone: 'Automatise, after notifying the Client in writing, may subcontract the performance of all or any part of its obligations under this Agreement.' They also acknowledge that 'Automatise relies on certain Third Party Services in order to operate Cicero' and disclaim liability for them. The privacy policy says confidential Client Data is never shared with any third party 'excepting our cloud service providers'. No subprocessor register, no cloud provider name and no objection right is published anywhere read. | Provide a dated list of every subcontractor and cloud provider that can touch our documents, in which country each operates, and give us a right to object before a new one is engaged. | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - Privacy Policy, updated 20 February 2026](https://www.cicero.com.ai/privacy-policy) |
| Training on customer content | Not confirmed | The SaaS Terms contain no prohibition on model training. They do contain a right over de-identified data: 'Automatise may collect, copy, transmit, analyse or otherwise use anonymised Client Material (including without limitation, the Client's use of Client Material, information concerning Client Material and data derived therefrom) to maintain and improve Cicero. Once anonymous, such information is Automatise Material (and not Client Material).' The client's licence to Automatise over Client Material is for providing Cicero and includes a right to sublicense. Neither the terms nor the privacy policy says whether improvement includes training or fine-tuning a model. | Does 'maintain and improve Cicero' include training, fine-tuning or evaluating any model on our anonymised matter content, what anonymisation is applied, and will you contract out of that right for our matters? | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - Privacy Policy, updated 20 February 2026](https://www.cicero.com.ai/privacy-policy) |
| Feedback and quality monitoring | Public claim only | The SaaS Terms define Client Feedback broadly as 'any ideas, feedback, suggestions, enhancement, feature requests, usage information insights or other similar information given by the Client Automatise during the use of Cicero by the Client and End Users', excludes it from Client Material, and provide that 'all Intellectual Property Rights in the Client Feedback are owned by, and vest in, Automatise upon creation'. Nothing read says whether in-product corrections to an output are treated as Client Feedback. | When a lawyer edits or reclassifies an output, is that correction captured as Client Feedback, and if so what is retained and what is it used for? | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx) |
| Retention of documents, outputs and query history | Public claim only | The SaaS Terms require each party to return, or on request destroy or permanently de-identify, all copies of the other party's Confidential Information within 10 business days of expiry or termination, subject to carve-outs for legal compliance, litigation, internal quality assurance and record-keeping, and performing the agreement. A separate clause says Automatise 'may delete or destroy the Client Material 90 days after the termination or expiry of this Agreement'. No period is published for how long documents, Outputs, chronologies or query history are held while the agreement runs. The privacy policy keeps personal information only for the duration of the relationship unless law requires longer. | Reconcile the 10 business day return obligation with the 90 day deletion right, and state the in-life retention period for uploaded documents, Outputs and query logs on a closed matter. | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - Privacy Policy, updated 20 February 2026](https://www.cicero.com.ai/privacy-policy) |
| Deletion and certified erasure | Public claim only | Deletion is addressed only through the Confidential Information clause - return, destruction or permanent de-identification within 10 business days of expiry or termination if requested - and the right for Automatise to delete or destroy Client Material 90 days after termination. There is no matter-level deletion function described, no deletion timetable while the agreement is running, and no certified-deletion commitment. The client is separately made responsible for 'securing, protecting and backing up Client accounts and Client Material contained in Cicero ... in a system outside of Cicero such as a document management system or document review platform'. | Can we delete a single matter and its Outputs on demand, what is the elapsed time to permanent deletion including backups, and will you certify deletion in writing? | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx) |
| Vendor and verifier access to content | Public claim only | The SaaS Terms make Client Material the client's Confidential Information, restrict disclosure to Personnel 'who need to know the Confidential Information for the purposes of this Agreement', and require the discloser to ensure those people are bound by substantially similar confidentiality obligations. Client Personal Information must be treated as the client's Confidential Information and handled only as needed to provide Cicero. Nothing read describes an approval process for support staff to open a matter, background screening, or a customer-visible access log. The home page states 'No shared infrastructure.' | Which Automatise personnel can open our matters, under what ticketed approval and screening, and can we obtain a log of vendor access to our documents? | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai) |
| Access control, SSO and audit | Public claim only | The SaaS Terms give each End User a single set of login and password credentials, require that no set is used by more than one individual, require the client to block, disable or change credentials when a person ceases to be an End User, and require immediate notice if credentials are disclosed to anyone else. The client is responsible for all activity under its accounts, authorised or not, and Automatise is not responsible for unauthorised access to the client's account. Multi-factor authentication, single sign-on, SCIM provisioning and audit-log export are not mentioned in anything read. | Is multi-factor authentication mandatory and is single sign-on or SCIM available, and can we export an audit log of who opened which matter and which analyses were run? | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx) |
| Encryption in transit and at rest | Not confirmed | Nothing read states that data is encrypted in transit or at rest. The SaaS Terms contain no security schedule and no encryption obligation. The privacy policy's security section lists 'hosting information your provide us in the same country of residence', physical security of premises and records, access restricted to personnel who need it, and 'having technological measures in place (for example, anti-virus software, fire walls)'. The home page cites an ISO 27001 certification but no encryption detail, and no security or trust-centre page appeared in a map of the site. | Confirm in writing the encryption standards in transit and at rest for documents, Outputs and backups, and the key-management arrangement, and add a security schedule to the agreement. | [Cicero - Privacy Policy, updated 20 February 2026](https://www.cicero.com.ai/privacy-policy); [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai) |
| Independent security assurance | Public claim only | The home page displays four claims: 'ISO 27001 - Certified information security management across all systems and processes', 'SOC Type II - Independent verification of security controls, availability, and confidentiality over time', 'ISO 42001' and 'GDPR Compliant'. A news item dated 22 May 2025 announces that Cicero 'is now among the first solutions worldwide to achieve ISO 42001 certification for AI Systems Management'. No certification body, certificate number, scope statement, audit period or expiry date is published on any page read, and the SaaS Terms contain no obligation to hold or maintain any certification. | Provide the ISO 27001 and ISO 42001 certificates and the SOC report with certification body, scope and dates, and add a contractual obligation to maintain them for the term. | [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai); [Cicero Achieves ISO42001 Certification - vendor news item published 22 May 2025, with dated news index](https://www.cicero.com.ai/news/cicero-achieves-iso42001-certification); [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx) |
| Contract, entity, liability and forum | Public claim only | The SaaS Terms name the contracting entity as 'Corporate Solutions Group Pty Ltd ACN 632 573 105 of Unit 1603, 568 Oxford Street, Bondi Junction NSW 2022 trading as Automatise ABN 48 632 573 105'. The laws of New South Wales govern, with non-exclusive New South Wales jurisdiction. Aggregate liability for all loss is limited to the total fees paid under the agreement, Consequential Loss is excluded, Cicero is supplied 'as is' with all warranties disclaimed to the extent permitted, and the client indemnifies Automatise for third-party reliance on Output. The Order Form ranks above the standard sections, which can otherwise only be varied by written agreement. There is no data processing agreement, and the terms page publishes the SaaS Terms only as a document to download. | Will you sign a data processing agreement and a security schedule alongside the Order Form, and will you lift the liability cap for a breach of confidentiality or a data breach affecting privileged client material? | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - Terms and conditions page, updated 25 March 2026 (publishes the SaaS terms of service as a download)](https://www.cicero.com.ai/terms-and-conditions) |
| Cross-border transfers and APP 8 | Public claim only | The SaaS Terms carry a clause headed 'No offshore transfer': 'Automatise's Cicero servers are located in Australia. Automatise will ensure that any User Content is processed in Australia and will not be transferred to, or be accessible from, any other country.' The privacy policy repeats that 'we will never transfer your confidential Client Data, including any personal information contained in Client Data, overseas' while noting that some third-party service providers handling contact-level personal information may be based outside Australia, including in the United States. The home page adds 'No data leaves your sovereign jurisdiction.' The clause covers processing, which on its face includes model inference, but no region, cloud provider or backup location is named. | Does the no-offshore-transfer clause cover model inference, backups, logs, telemetry and support access without exception, and in which Australian region are the servers and model endpoints? | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - Privacy Policy, updated 20 February 2026](https://www.cicero.com.ai/privacy-policy); [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai) |
| Incident notification and history | Not confirmed | The SaaS Terms contain no data breach notification obligation on Automatise. 'Cyber Attack' is defined only to support Automatise's right to suspend the service, and the notification duties run the other way: the client must notify Automatise immediately if End User credentials are disclosed and as soon as practicable on becoming aware of any breach of the agreement. The privacy policy sets out a complaints process and refers unresolved complaints to the Office of the Australian Information Commissioner but makes no breach-notification commitment. No incident history is published. | What notification period from discovery will you commit to for a data breach affecting our matters, will you support our own notifiable data breach assessment, and have there been any incidents to date? | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - Privacy Policy, updated 20 February 2026](https://www.cicero.com.ai/privacy-policy) |
| Change notice for models, terms and processors | Public claim only | Sections 1 to 17 of the SaaS Terms may only be amended by written agreement between the parties, but Automatise 'reserves the right to update the Service Level Agreement from time to time by notice to the Client'. Documentation is provided 'from time to time', maintenance is applied with reasonable efforts at prior notice except where urgent, and subcontracting requires only written notice. Nothing read gives any notice obligation before a model, model version or analysis method changes, and the terms and conditions page shows the SaaS Terms were updated on 25 March 2026 and the privacy policy on 20 February 2026. | What notice will we receive before a model or analysis method behind a function changes, and can we require re-validation of an output type after such a change? | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - Terms and conditions page, updated 25 March 2026 (publishes the SaaS terms of service as a download)](https://www.cicero.com.ai/terms-and-conditions); [Cicero - Privacy Policy, updated 20 February 2026](https://www.cicero.com.ai/privacy-policy) |
| Export and exit | Public claim only | The agreement renews automatically unless either party gives at least 60 days' notice before the end of the current term, and no refunds are offered other than as required by law. On termination all licences cease immediately, the client must return all Automatise Materials, and Automatise may delete or destroy Client Material after 90 days. The client is made responsible for backing up Client Material outside Cicero. Export while the service runs is a product feature - matrices, chronologies and coding decisions to Word or Excel, or pushed back to iManage or Relativity - but no export obligation appears in the terms. | On exit, in what formats and within what period will documents, chronologies, coding decisions and matrices be handed back, and what happens to work product if we terminate mid-matter? | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai) |
| Connectors and third-party services | Public claim only | The home page publishes imports from Relativity, iManage and a local computer, push-back to iManage and Relativity, and NetDocuments, Nuix and SharePoint as 'on the way'. The SaaS Terms define Third Party Services as 'any third party services connected to and/or integrated with Cicero', state that Automatise 'relies on certain Third Party Services in order to operate Cicero', and disclaim liability for interruptions or failures caused by them, including a Force Majeure Event defined to include 'failure of a third party service provider'. No third party is named. | Name every third-party service Cicero depends on to operate, what our documents pass through, and which of those sit inside the no-offshore-transfer commitment. | [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai); [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx) |
| Open-web search | Not confirmed | Every function described operates on the customer's own document set - the Statement of Claim and Defence, the imported document population, the propositions the customer states. Nothing on the home page, in the SaaS Terms or in the privacy policy says whether Cicero can retrieve anything from the open web, and the no-offshore-transfer clause addresses where User Content is processed rather than what the system may fetch. | Can Cicero retrieve anything from outside our document set, including the open web or any legal database, and if so can that be disabled? | [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai); [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx) |
| Agent actions and confirmation | Public claim only | The published workflow has three stages and puts the action at the end with the user: an automated first pass, a human-in-the-loop stage where 'Your team reviews AI-generated outputs with full source traceability' and can 'Edit chronology entries, reclassify extractions, verify evidence links', then 'Export & Integrate' where refined outputs are pushed back to iManage or Relativity or exported. Nothing read describes any step Cicero takes on its own, and nothing read describes a confirmation control on the push-back to a document management system. | Does the push-back to iManage or Relativity require a user to confirm each write, and can Cicero create, overwrite or delete anything in those systems without a person approving it? | [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai); [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx) |
| Human review before use | Public claim only | The SaaS Terms make review the client's obligation rather than a product control: Output 'is made available to the Client solely for general informational purposes and is provided on an as is basis', 'is not intended as advice and must not be relied upon as such', the client 'must not rely on any Output and must undertake its own enquiries', and the client indemnifies Automatise against third-party reliance on Output. The home page frames the same point as design - 'AI performs the analysis. Your lawyers make the decisions' and 'Cicero does not replace legal judgment'. No product control that forces or records a named reviewer is described. | Does the product record who reviewed and accepted each entry in a chronology or matrix, and can an output be exported before a reviewer signs it off? | [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx); [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai) |

## Notes

Three firecrawl operations were spent on this profile (terms and conditions page, privacy policy, ISO 42001 news item) on top of the pages already cached from the previous phase. The SaaS Terms are published only as a Word document to download, which a scrape does not render, so that file was fetched directly and converted locally at no credit cost; it is cached at .firecrawl/vendors/cicero/saas-terms-of-service.md. That document answered the Australian questions the previous phase left open: the contracting entity and ACN/ABN, New South Wales governing law, Australian servers and Australian processing of User Content. Still unverified: no model provider is named anywhere, so what 'privately hosted language models' means in practice is unknown; there is no encryption statement of any kind; there is no data breach notification obligation; there is no subprocessor register and subcontracting needs only written notice; the four assurance claims carry no certificate number, certification body or scope and the terms contain no obligation to maintain them; and there is no pricing page. The Order Form, the Documentation and the referenced Service Level Agreement updates were not seen. The customers recorded are limited to firms named in dated items visible on the pages read; those item bodies render as stubs, so the scope of each engagement could not be read from the vendor's own site, and further firms appearing only as news-item URLs in a site map are not recorded. A cached third-party university publication names two model vendors against one Australian deployment; that is a secondary source and is deliberately not recorded as a vendor statement. Capability list updated 2026-09-27 when the controlled vocabulary was extended from 19 to 38 values: added data-extraction. Values already present were kept, because they remain true descriptions of what the product does.

## Sources

- [Cicero - home page (functions, how it works, integrations, data privacy, news index)](https://www.cicero.com.ai) (checked 2026-09-27)
- [Cicero - Terms and conditions page, updated 25 March 2026 (publishes the SaaS terms of service as a download)](https://www.cicero.com.ai/terms-and-conditions) (checked 2026-09-27)
- [Automatise SaaS Terms - the terms of service document downloaded from the terms and conditions page](https://framerusercontent.com/assets/yh5XJmMihpE0AtQ4zkFt2yZv6o.docx) (checked 2026-09-27)
- [Cicero - Privacy Policy, updated 20 February 2026](https://www.cicero.com.ai/privacy-policy) (checked 2026-09-27)
- [Cicero Achieves ISO42001 Certification - vendor news item published 22 May 2025, with dated news index](https://www.cicero.com.ai/news/cicero-achieves-iso42001-certification) (checked 2026-09-27)

A product profile is research to support questions. It does not approve a product for any firm. Public product information supports questions; it does not approve a product for your firm. Verify the exact plan, settings and signed terms.