Product and intended use
Define the configuration, people, information and tasks being assessed.
Plan, contracting entity and modules
Public claim only
US customers contract with LegalOn Technologies, Inc. (Delaware; 220 Montgomery St, San Francisco). Subscription Terms (1 June 2026) plus Order Form and DPA. Modules marketed: Assistant, Review, Playbooks, Matter/Entity/Board management, Vault, Translation, Word add-in, agentic workflows (intake, triage, playbook, translation, drafting). A Japanese Documenton product exists on /jp and needs its own review.
Ask: Confirm the contracting entity (Inc. versus the Japanese company), which modules are on our Order, and whether we are on the 1 June 2026 Terms or a negotiated MSA.
Deployment model
Public claim only
SaaS. Security page: hosted in the US on AWS and GCP. Trust Centre subprocessors list Google Cloud Platform as IaaS and Microsoft Azure for OpenAI Service; AWS is not on that 10-row list. No on-premises option found.
Ask: Which clouds and US regions actually hold our tenancy and run inference; is AWS in scope; and is any non-US region available?
Product features in scope
Public claim only
Pricing: Core Review includes unlimited assistant chat, AI review/redlining, 135+ pre-built playbooks, document repository, 100+ templates, Word add-in. Contracting Suite adds My Playbooks, Playbook Agent, Vault repository/projects, SSO/MFA/IP allow-listing. Agents page: intake, triage, playbook, translation and Word drafting agents. Translation via DeepL is a listed subprocessor.
Ask: Which of Core Review, Contracting Suite, each agent, Vault, Translation and Word will be enabled and billed on our Order?
Governing law and Australian coverage
Public claim only
Subscription Terms: California law; disputes by JAMS arbitration in San Francisco (class-action waiver); jury trial waived if a matter proceeds in court. Website Terms of Use also select California and San Francisco courts. Hosting described as US. No Australian law option or named Australian customer found.
Ask: Will you accept Australian law and courts (or a non-exclusive Australian forum) and an APP addendum, or is California/JAMS mandatory?
Data, controls and requirements
Compare the actual configuration with firm, client and jurisdiction requirements, supported by evidence.
Client-facing use and authority to process
Public claim only
Lawyer/in-house facing. Customer must provide notices and consents for LegalOn to collect, use and share Customer Content. Terms s 9.3 and DPA 2.4 tell the customer not to submit PHI, PII, PCI or special-category data unless an addendum is signed — yet contract files routinely contain names and counterparties. Publicity: LegalOn may use the customer's name and logo. No Australian engagement-letter template found.
Ask: Confirm there is no client-facing AI; sign an addendum allowing ordinary contract PII; provide engagement-term wording covering US hosting, OpenAI/Azure, Tavily, retention and Analyses; and opt us out of logo use.
Foundation-model providers
Not confirmed
Security page (example): Microsoft Azure OpenAI with no training and no retention even for abuse monitoring. Trust Centre lists both Microsoft Azure 'OpenAI Service' and a separate OpenAI row (United States) for prompts, contract analysis and clause generation. GPT-5.4 blog and the 2026 benchmark discuss OpenAI, Claude and Gemini; customer pin was not documented. Direct OpenAI API processing is not the same as Azure ZDR.
Ask: Name every model family, version and route (Azure OpenAI versus openai.com versus others) that will process our content; produce ZDR/DPA artefacts for each; and can we pin or disable a provider?
Subprocessors
Public claim only
Trust Centre list (10 rows): GCP (IaaS), Auth0, Microsoft Azure OpenAI Service, Datadog, Intercom, Google Workspace, DeepL, Adobe Acrobat API, Tavily (US data-retrieval API for applications and AI agents), OpenAI (US). DPA: 10 days to object to a new subprocessor or deemed consent; exclusive remedy is terminate the affected Services if LegalOn will not avoid that subprocessor. Security page also names AWS, which is not on the 10-row list.
Ask: Provide the dated list with legal entities, countries and data types; confirm whether AWS is in use; 30-day notice; and whether Tavily/DeepL/OpenAI (direct) can be disabled.
Training and secondary use
Public claim only
Security page: Azure OpenAI does not train, retrain or improve models on customer data. Subscription Terms 7.3: LegalOn may aggregate and/or de-identify Customer Content (Analyses), use Analyses to improve the Services, disclose Analyses in connection with its business if not reasonably linkable to Customer, and LegalOn owns Analyses. DPA 10.2: after deletion, de-identified/aggregated data may continue to be processed to improve systems. Direct OpenAI row does not repeat the Azure ZDR sentence.
Ask: Confirm in the Order that prompts, uploads, outputs and embeddings are not used to train any OpenAI, Google or Anthropic model, and that Analyses cannot be reverse-engineered to our matters; apply the Azure ZDR warranty to every LLM route.
Feedback, ratings and product improvement
Public claim only
Feedback is a perpetual, royalty-free, transferable licence to LegalOn to use and incorporate into products; even if designated confidential it creates no confidentiality obligation. Analyses of de-identified Customer Content may be used to improve the Services.
Ask: Can in-product ratings and Analyses derived from our contracts be disabled or confined to our tenant?
Retention of prompts, documents and logs
Public claim only
During the Subscription Term the customer may export Customer Content via available tooling. After termination LegalOn may delete or disable access after 30 days. DPA duration includes the term, transition assistance, LegalOn's legitimate business needs, or law. Azure OpenAI is claimed to store nothing, even for abuse monitoring; Datadog logs are a listed subprocessor. Administrator-configurable retention was not documented.
Ask: For our tenancy, list retention for documents, playbooks, Vault, agent traces, Datadog logs, backups and each LLM route, and confirm Azure ZDR applies to GPT-5.x calls.
Deletion on instruction and on exit
Public claim only
DPA 10.2: after Services complete, at Customer's election LegalOn will return or delete Customer Personal Data without undue delay unless law requires storage; SCC deletion certification only on request. Subscription Terms: delete/disable Customer Content after 30 days post-termination. De-identified aggregated data may be retained.
Ask: Contract a numbered deletion and return period including backups, embeddings, Analyses exclusions, DeepL/Tavily/OpenAI copies, matter-level deletion, and a written certificate.
Vendor and contractor access to content
Public claim only
DPA: access restricted to employees with a defined need-to-know; personnel under confidentiality. Intercom is used for user support. Professional Services may be purchased. Customer-visible logs of vendor access were not found. DPA 2.4's PII prohibition does not remove support access to uploaded contracts in practice.
Ask: Enumerate every human-access path at LegalOn, DeepL, Tavily, Azure and OpenAI; can we require per-ticket consent; is access logged and exportable?
SSO, MFA, admin controls and audit logs
Public claim only
Pricing: Enterprise SSO, MFA and IP allow-listing are listed under Contracting Suite, not Core Review. Subprocessors include Auth0 and Google Workspace SSO. DPA: timely provisioning/de-provisioning of user accounts; logical segregation. SCIM and customer-exportable prompt logs were not documented.
Ask: On the plan we are buying, confirm SSO-only, MFA, SCIM, IP allow-listing, and an exportable audit log of prompts, exports, admin changes and vendor access.
Encryption in transit and at rest
Public claim only
Security page and DPA Attachment 2: encryption at rest and in transit over public networks per industry-standard practice; key-management policies. AES/TLS versions, KMS owner and customer-managed keys are not named.
Ask: Name algorithms for every store (including embeddings, Datadog, backups and each LLM link), who holds keys, rotation, and whether customer-managed keys are available.
Independent security assurance
Public claim only
Trust Centre: SOC 2 Type II 2025 (EN/JP, request-access), ISO/IEC 27001:2022 and ISO/IEC 27017:2015 2025 certificates, WPT report 2024. DPA: maintain SOC 2 or comparable; summary of latest report once per 12 months on request; annual pentest. Reports were not inspected. IRAP was not found.
Ask: Provide under NDA the current SOC 2 Type II (scope, period, exceptions), ISO 27001/27017 certificates, the 2024/25 pentest summary covering agents and LLMs, and any Australian Essential Eight/IRAP mapping.
Contract, DPA, confidentiality, IP and liability
Public claim only
Published Subscription Terms + DPA (SCCs/UK Addendum). Customer owns Customer Content; licence to LegalOn to host/use it to provide the Services. Analyses of de-identified content are LegalOn's. Liability cap: fees in the prior 12 months (or USD 1,000 on a free trial); cap does not apply to customer's indemnity/payment. DPA liability is subject to the same cap. LegalOn may assign without customer consent. Publicity opt-out is not a documented click. No APP-specific addendum.
Ask: Will you sign an APP-aligned DPA with 72-hour breach notice, flow-down to OpenAI/Azure/Tavily/DeepL, Output IP indemnity, Australian law, no publicity, mutual assignment limits, and a cap that is not eroded for confidentiality breaches?
Cross-border processing and Australian residency
Public claim only
Security: US hosting on AWS/GCP. DPA 7.1: LegalOn may transfer Customer Personal Data to any country reasonably necessary, with SCCs/UK Addendum. OpenAI and Tavily are listed in the United States. DeepL location is not stated on the 10-row list. No Australian region. APP 8 analysis is required.
Ask: Is an Australian region available; if not, list every category of data that leaves Australia (including Tavily queries and DeepL text) and the APP-equivalent commitments we can rely on?
Breach notification and incident history
Public claim only
DPA 5.2: inform Customer of a Personal Data Breach without undue delay (no hour count) and remediate to the extent within LegalOn's control. Unsuccessful attacks are excluded from the definition. No public incident register. Customer is solely responsible for notifying regulators and data subjects.
Ask: Contract notification within 72 hours of suspected incidents affecting any Customer Content, NDB cooperation, Australian-hours security contact, and disclose material incidents in the last 24 months.
Change of terms, models and control
Public claim only
LegalOn may amend Terms by posting; effective no earlier than 30 days except new functions or legal reasons (immediate). Material adverse mid-term changes: customer may terminate within 30 days of Modification Notice. LegalOn may assign without consent. GPT-5.4 blog describes vendor-controlled model swaps after internal benchmarking, without a customer pin/testing window in the public Terms. Subprocessor changes: 10-day objection.
Ask: Lock the Order against mid-term term changes except by signed amendment; require written notice and a testing window before model or retrieval changes; and give termination and data-return rights on assignment, change of control or discontinuance.
Export, transition and shutdown
Public claim only
During the term, export via available tooling. After termination, content may be deleted after 30 days. DPA: return or delete personal data without undue delay; deletion certificate only on request. No bulk-export API, playbook/Vault dump format, or escrow found. Force majeure beyond 60 days allows customer termination as sole remedy.
Ask: Demonstrate a full tenancy export (contracts, playbooks, Vault, agent traces, logs) in open formats, a 30–90 day retrieval window, deletion including Analyses exclusions with a certificate, and transition assistance rates.
DMS, translation and retrieval connectors
Not confirmed
Word add-in. DeepL for translation. Adobe Acrobat for file conversion. Tavily listed as a data-retrieval API for applications and AI agents (United States). Google Workspace as identity/file sharing. iManage/NetDocuments not found. What contract text Tavily or DeepL receives is not specified in the public list.
Ask: For each connector we would enable, show identity, scopes, whether documents are copied, whether Tavily/DeepL can be disabled, and how we disconnect and purge copies.
Tavily and other retrieval
Public claim only
Tavily is a listed subprocessor for 'data retrieval API services for applications and AI agents' in the United States. That is consistent with agentic retrieval of web or external data. Whether the open contract is sent, whether the feature is on by default, and citation behaviour when nothing is found were not specified.
Ask: Can Tavily (and any other web retrieval) be disabled for our tenancy; what query payload leaves the tenant; and does the product refuse to answer when no source is retrieved?
Agent actions and confirmation gates
Not confirmed
Agents page: specialised agents for intake, triage, playbook creation from precedents, translation, and drafting/edits in Word, delivering structured review-ready outputs. Copy says agent work stays in LegalOn's environment. No public list of send/share/delete/write-back gates or prompt-injection testing was found.
Ask: List every action each agent and the Word add-in can take; which require explicit per-action approval; how untrusted document text is isolated; and provide the latest injection/red-team summary.
Human review of outputs
Public claim only
Marketing describes review-ready outputs for legal teams to trust, not a mandatory supervisor gate. Word drafting still lands in Word. No exportable per-output review log with model version that ordinary users cannot disable was found. Acceptable Use forbids customer benchmarking of the service.
Ask: Can we require supervisor sign-off before redlines leave the firm, export a per-document record of model version and reviewer, and disable agents that apply changes without a human click?
