Product and intended use
Define the configuration, people, information and tasks being assessed.
What is covered and how it is subscribed
Public claim only
GTC clause 3.5 treats Argument Analyser as a separately subscribed service: 'For Customers subscribing to Argument Analyser, the following additional terms apply: (a) In order to access and use Argument Analyser, you must maintain, at a minimum, a current subscription to the CaseBase Service and Unreported Judgments.' The Lexis+ product page lists Argument Analyser as one of four Lexis+ platform tools, and GTC 3.7 sets its own separate prerequisites for Lexis+ without stating that a Lexis+ subscription includes Argument Analyser. Read 2026-09-27.
Ask: Does our order form license Argument Analyser as a separate line item, and do our existing CaseBase and Unreported Judgments subscriptions satisfy clause 3.5 for every user who needs it?
Deployment and hosting region
Not confirmed
The product is a browser-delivered dashboard that takes an uploaded Word or PDF file or pasted text; no on-premises or private-cloud option is described. No page read states a hosting region for Argument Analyser. GTC 3.9 fixes Australia as the primary hosting location for the Lexis+ AI Service only, and the subprocessor list dated 17 September 2026 has no Argument Analyser entry. Checked 2026-09-27.
Ask: In which country are Argument Analyser uploads stored, indexed and processed, is an Australia-only configuration available, and does any failover move that processing offshore?
Named functions
Public claim only
The product FAQ names four outputs: relevant case recommendations linked to the uploaded document; citation analysis showing how cases interrelate and where citations support or contradict arguments; legal issue extraction identifying core issues and gaps in reasoning; and a dashboard with downloadable links to cited authorities. The page states CaseBase is used to check each cited case 'right down to the paragraph', and that external documents including opposing submissions can be processed. Word and PDF are named; size and usage limits are said to depend on subscription type. Checked 2026-09-27.
Ask: Which of the four outputs are generated by a language model and which are drawn from the CaseBase editorial citator, and what are our document size and monthly usage limits in writing?
Australian content coverage
Public claim only
The FAQ states the product 'is built specifically for Australian legal practice', is 'powered by LexisNexis' comprehensive Australian case law databases' and 'covers decisions from federal and state courts across all major jurisdictions'. GTC 3.5 makes CaseBase and Unreported Judgments required subscriptions. No court-by-court coverage table or currency date is published. Checked 2026-09-27.
Ask: Provide the court-by-court coverage list and the currency lag for each series, and say whether tribunals and intermediate appellate decisions are inside the corpus Argument Analyser searches.
Vendor content addressed to AI systems
Public claim only
A deliberate check for content directing how AI systems should describe the product found none on the Argument Analyser product page or the Australian products index, read in full on 2026-09-27. A file does exist at lexisnexis.com/llms.txt, but it is a crawler-access directive rather than descriptive instruction: it allows named search and assistant agents ('User-agent: OAI-SearchBot / Allow: /', 'User-agent: ClaudeBot / Allow: /') and disallows others ('User-agent: GPTBot / Disallow: /', 'User-agent: PerplexityBot / Disallow: /'). No block telling AI models what to say about the product was found.
Ask: Does LexisNexis publish or supply any guidance to AI systems, crawlers or assistants about how its products should be described, and if so where?
Data, controls and requirements
Compare the actual configuration with firm, client and jurisdiction requirements, supported by evidence.
Professional responsibility and client authority
Public claim only
GTC 4.4 states 'We are not a law firm; we do not represent or advise clients in any matter and are not bound by the professional responsibilities and duties of a practising lawyer', and that nothing in the Services creates a solicitor-client relationship or provides legal advice. GTC 4.3(d) states the Services and Materials are not a substitute for professional advice or judgement. Read 2026-09-27.
Ask: What client notice or consent do you expect a firm to obtain before uploading privileged material, and can named matters be excluded from Argument Analyser at tenancy level?
Foundation-model providers
Not confirmed
No model, model provider or technique is published for Argument Analyser on the product page or the Australian products index. The subprocessor list dated 17 September 2026 names AI providers service by service — for example Anthropic PBC, OpenAI LLC, Microsoft Corporation, Mistral AI and Google LLC against Lexis+ AI and Lexis+ with Protégé — but contains no entry for Argument Analyser. Checked 2026-09-27.
Ask: Name every model and provider used by Argument Analyser, the legal entity and endpoint country for each, and which subprocessor-list entry covers this product.
Subprocessors
Public claim only
A dated subprocessor list is published and contractually anchored: DPA clause 3.1 gives general authorisation to engage processors from the list at lexisnexis.com/global/privacy/subprocessors.page, requires the list to be updated at least 14 days in advance of any change, and gives a 14-day objection right. The list, last updated 17 September 2026, itemises services individually and has no entry for Lexis Argument Analyser; it names RELX Trading Australia Pty Ltd among the affiliates providing data centre operations and support. Checked 2026-09-27.
Ask: Which subprocessor-list entry governs Argument Analyser, and will you add a named entry with processing locations so our 14-day objection right under DPA 3.1 is usable?
Training on customer content
Public claim only
GTC 4.8 defines Customer Information as Prompts and Customer Documents together, and states that LexisNexis will, and will ensure its third-party technology suppliers are obliged to, ensure that Customer Information remains within the controlled environment, is not made public or provided to any other user except the originating Authorised User, and 'is not used by LexisNexis to train any AI Technology'. GTC 4.7 defines Customer Documents as files uploaded to the Services, which is what Argument Analyser takes. The Trust Center states 'We pride ourselves on never using customer data to train our models.' Read 2026-09-27.
Ask: Confirm in writing that clause 4.8 covers Argument Analyser uploads, extracted text, embeddings and derived indexes, and that the no-training obligation binds each named model provider.
Feedback, ratings and service improvement
Not confirmed
Neither the GTCs, the DPA nor the product page describes in-product feedback or ratings for Argument Analyser, or whether such signals are used to improve models or rankings. GTC 4.8 addresses Prompts and Customer Documents but is silent on ratings and telemetry. Checked 2026-09-27.
Ask: If a user rates an Argument Analyser result, what is stored, who sees it, and is it used to tune the retrieval or reranking that other customers receive?
Retention of uploads and prompts
Public claim only
GTC 4.7 states Customer Documents 'will be processed in a non-persistent state', are 'purged automatically at the end of a user session or a period of inactivity, whichever occurs first', and that 'retention of Prompt history and its deletion is within the control of the Authorised User'. GTC 4.8 adds that LexisNexis is not obliged to store, maintain, back up, retrieve or restore any Customer Information. No retention period is published for logs, dashboards or derived indexes. Read 2026-09-27.
Ask: State the inactivity period that triggers purge, and the retention of Argument Analyser dashboards, extracted issue lists, system logs and backups on the Australian account.
Deletion and certified erasure
Public claim only
GTC 4.7 purges uploaded documents automatically at session end or after inactivity. DPA clause 2.3(g) requires LexisNexis, at the customer's choice, to delete or return all personal data after the end of the provision of services and delete existing copies unless law requires storage. Neither document offers certified erasure or a deletion deadline, and GTC 4.8 disclaims any obligation to retrieve Customer Information. Read 2026-09-27.
Ask: Will you certify deletion in writing after termination, covering Argument Analyser uploads, logs and any copies held by your AI subprocessors, and within how many days?
Vendor and provider access to content
Public claim only
GTC 3.6 warrants that Folders are under the exclusive control of Authorised Users and that LexisNexis 'will not access or otherwise review the content of Folders without your authorisation', while reserving access or disclosure 'to the extent necessary to facilitate features and functions of the Services and to comply with contractual and legal obligations including, but not limited to, an administrative or judicial proceeding'. DPA 2.3(b) requires persons authorised to process personal data to be under confidentiality obligations. The Trust Center publishes a knowledge-base question asking whether any LexisNexis language-model provider has human reviewers able to read prompts or completions; the answer was not visible without registration. Checked 2026-09-27.
Ask: Can LexisNexis or any model provider staff read Argument Analyser uploads, from which countries, under what approval, and will you publish or give us the Trust Center answer on model-provider human reviewers?
Identity, access and offshore use
Public claim only
GTC 2.7 makes each LN ID personal and confidential and allows cancellation plus additional charges where an ID is shared. GTC 2.8 makes each access method country specific and permits suspension where an ID is used outside its country for more than 30 continuous days. No SSO, SCIM or mandatory multi-factor authentication requirement was found for Argument Analyser; the Trust Center lists access-control and audit-logging topics whose detail sits behind registration. Checked 2026-09-27.
Ask: Confirm SAML single sign-on, enforced multi-factor authentication and deprovisioning for Argument Analyser, and whether we can export a per-user upload audit log.
Encryption and key management
Public claim only
The Trust Center states 'Data is encrypted both in transit and at rest.' The Australian products index states data 'is protected through advanced encryption, access controls, and compliance with global privacy and security standards'. DPA 6.1 lists pseudonymisation and encryption of personal data among measures to be implemented 'as appropriate'. No algorithm, TLS version, key management description or customer-managed key option was found. Checked 2026-09-27.
Ask: Name the encryption algorithms and TLS versions protecting Argument Analyser uploads and backups, who holds the keys, and whether customer-managed keys are available.
Independent assurance and its scope
Public claim only
The Trust Center publishes a certification list including SOC 2 Type 2, SOC 2 Type 1, SOC 3, SOC 1 Type 2, ISO/IEC 27001 and its Statement of Applicability, ISO 9001:2015, ISO 22301:2019, ISO 14001, ISAE 3402, NIST CSF and Cyber Essentials, with the reports themselves gated behind registration. A Trust Center update dated 4 May 2026 states the newly published SOC 2 Type 2, SOC 3 and HIPAA/HITECH reports cover 'Lexis, Lexis+ AI, Lexis+ with Protege and CaseMap+'; Argument Analyser is not named in that scope statement. Checked 2026-09-27.
Ask: Provide the SOC 2 Type 2 report and ISO/IEC 27001 certificate with a scope statement that names Argument Analyser and its hosting environment, plus the exceptions and the bridge letter.
Contracting entity, liability and forum
Public claim only
The Australian Global Platform General Terms and Conditions state they 'form part of the agreement between RELX Trading Australia Pty Limited trading as LexisNexis ABN 70 001 002 357 ... and the customer entity named on the Order Form'. Clause 7.6 applies the laws of New South Wales with exclusive jurisdiction in the New South Wales courts. Clause 5.7 caps aggregate liability at 'the greatest amount payable by you in any rolling 12 month period', with carve-outs in 5.8 for licence, sanctions, warranty and confidentiality breaches, and clauses 5.1 to 5.2 preserving Australian Consumer Law guarantees. Clause 7.10 incorporates the LexisNexis Privacy Policy and Data Processing Addendum. The document carries no version date on its face. Read 2026-09-27.
Ask: Confirm RELX Trading Australia Pty Limited (ABN 70 001 002 357) is our counterparty, give us the dated version of these General Terms and Conditions that applies, and confirm any negotiated change to the clause 5.7 cap.
Cross-border transfers
Public claim only
DPA clause 5.1 requires appropriate safeguards for any transfer of personal data out of the customer's country. The DPA annex sets jurisdiction-specific terms for the European Economic Area, the United Kingdom, Switzerland, Latin America, the Middle East and Africa, and the United States, and contains no Australia-specific annex; the GTCs contain no Australian Privacy Principle 8 clause. The subprocessor list gives a processing-location column per service but has no Argument Analyser row. GTC 2.8 restricts each access method to the country for which it was issued. Checked 2026-09-27.
Ask: List every country in which Argument Analyser uploads are stored, processed for inference, logged, supported and backed up, and give us an Australian Privacy Principle 8 analysis for each.
Incident notification and history
Public claim only
DPA clause 7.1 requires LexisNexis to notify the customer 'without undue delay after becoming aware of a personal data breach' and to respond reasonably to requests for further information; no fixed hour count and no Notifiable Data Breaches scheme clause appears in the GTCs. A Trust Center update dated 4 March 2026 states LexisNexis investigated a security matter, that an unauthorised party accessed a limited number of servers containing 'mostly legacy, deprecated data from prior to 2020', and that the impacted information did not contain customer client or matter information or customer contracts. Checked 2026-09-27.
Ask: State the contractual notification period in hours from discovery, confirm cooperation with our Notifiable Data Breaches obligations, and confirm whether Argument Analyser data was in scope of the March 2026 matter.
Change notice for terms, features and processors
Public claim only
GTC 7.1 permits typographical or non-substantive changes without notice, substantive changes on at least 7 days' notice, email notice where a change is considered detrimental, and a 30-day termination right with pro-rata refund in that case. GTC 2.10 allows Materials and features to be added to or withdrawn from the Services 'without notice', with a 30-day termination right where the change materially affects the value of the agreement. DPA 3.1 gives 14 days' advance notice of subprocessor changes and a 14-day objection window. Read 2026-09-27.
Ask: What notice will we receive before the model, retrieval pipeline or hosting location behind Argument Analyser changes, given clause 2.10 allows feature withdrawal without notice?
Export and exit
Public claim only
GTC 4.8 states LexisNexis is 'not obliged to store, maintain, back-up, retrieve or restore any Customer Information'. GTC 1.3(b) prohibits storing Materials for more than ninety days except under stated exceptions, which constrains what may be kept after exit. GTC 6.9 terminates the licence on termination while preserving the intellectual property, liability, confidentiality and jurisdiction clauses. GTC 6.8 limits the vendor's only obligation on termination to a pro-rata refund of charges paid in advance. No export format is published for Argument Analyser dashboards. Read 2026-09-27.
Ask: On exit, in what format can we export Argument Analyser dashboards and issue maps, and how does clause 1.3(b) apply to authorities already saved to matter files?
Connectors and third-party AI tools
Public claim only
GTC 1.3(g) permits use of the Services or Materials with large language models, machine learning models or generative AI only where the Services and Materials remain under the customer's control and are not provided to third parties, are not used to train those technologies, and such usage is 'on an incidental basis only'; LexisNexis Services are excluded from that definition. No connector catalogue or marketplace is published for Argument Analyser. Read 2026-09-27.
Ask: Does clause 1.3(g) permit us to paste Argument Analyser output into our own approved AI assistant, and what counts as 'incidental' for that purpose?
Open-web retrieval
Public claim only
The product FAQ describes a closed corpus: 'Argument Analyser processes the content against LexisNexis' comprehensive Australian case law database' and recommendations are said to be drawn from the LexisNexis case law collection. No page read states whether any open-web search or external retrieval occurs, and no tenancy control for it is described. Checked 2026-09-27.
Ask: Does Argument Analyser make any call outside the LexisNexis corpus, including to a search engine or a model provider's browsing tool, and can that be disabled for our account?
Agent actions and confirmation
Not confirmed
The product is described as returning recommendations, citation analysis, issue extraction and downloadable links in a dashboard. No autonomous action, workflow execution, write-back to another system or send capability is described on any page read, and no confirmation or stop control is documented. Checked 2026-09-27.
Ask: Does Argument Analyser take any action beyond generating the dashboard, and if agentic steps are added, will they be off by default for our account?
Human review before reliance
Public claim only
GTC 4.3(f) states 'AI systems may not always be accurate or error free, which means Authorised Users are responsible for verifying and cross-referencing any information provided in AI Services', and 4.3(d) that the Services are not a substitute for professional advice or judgement. The product FAQ repeats that lawyers 'should continue to apply professional judgment and verify results as part of standard due diligence'. No product control forces a named reviewer before output is used. Read 2026-09-27.
Ask: What in-product controls exist to record that a fee earner has verified each recommended authority, and can that step be made mandatory for our users?
