Product and intended use
Define the configuration, people, information and tasks being assessed.
Plan, contracting entity and modules
Not confirmed
Public DPA names Robin AI Limited and Robin AI Inc. as authorised persons. The live site sells a Legal Intelligence Platform (chat, search, tables, obligations, workspaces, playbooks) plus a Word add-in and a managed-services (AI+) offering. Press (Dec 2025–Jan 2026) reported the services arm moved to Scissero and some engineers hired by Microsoft; Microsoft told Non-Billable it has no plans to acquire Robin AI. Which legal entity and which modules a 2026 Order actually covers is not clear from the marketing site alone. No public MSA/Terms of Use URL was found (only the DPA).
Ask: Name the contracting entity, confirm the company is a going concern for the licence term, which of platform, Word add-in and managed services are still Robin's versus Scissero's, and produce the current MSA.
Deployment model
Public claim only
SaaS on AWS. Security page: customer data never leaves Robin's secure AWS Cloud environment. Singapore blog: AWS in-country deployment there, with some advanced AI still from Europe-based centres. Word add-in via AppSource or Microsoft 365 admin centre. No on-premises software option was found.
Ask: Which AWS regions will hold our tenancy (including inference); is Singapore or another pin available for Australia; and which Word builds are supported?
Product features in scope
Public claim only
Platform: document chat (including multi-document), search, tables, obligations with alerts, workspaces, playbooks, legal library upload. Word add-in: suggested edits, summaries, chat. Research with Legal Authorities (web search). Homepage cites 80 per cent faster review and 500k+ docs processed without method.
Ask: Which of chat, tables, playbooks, obligations, Word add-in, Research with Legal Authorities and managed services will be enabled and billed on our Order?
Governing law and Australian coverage
Not confirmed
The public DPA is framed around UK GDPR and EU GDPR and ICO transfer tools. No public Terms of Use stating governing law and forum for the software licence was found. Company page: teams in the United States, United Kingdom, Singapore and South Africa. Footer lists a Singapore office. No named Australian customer.
Ask: Will the MSA accept Australian law and courts (or a non-exclusive Australian forum), and which entity (Limited vs Inc.) signs?
Data, controls and requirements
Compare the actual configuration with firm, client and jurisdiction requirements, supported by evidence.
Client-facing use and authority to process
Not confirmed
The software is lawyer/in-house facing. Managed-services pages describe Robin's team reviewing NDAs, SaaS, vendor and other agreements using the platform — that is vendor-lawyer access to customer contracts. DPA: customer remains controller and must have notices/consents. If the services arm has moved to Scissero, a new processor may be in the path. No Australian engagement-letter template was found.
Ask: Confirm whether any Robin or Scissero human will read our contracts; provide wording for engagement terms covering hosting countries, Claude/Bedrock, web research, retention and training; and can we exclude clients or matters?
Foundation-model providers
Public claim only
DPA subprocessors and security annex: Anthropic API; Amazon Bedrock for model hosting; Amazon SageMaker for 'machine learning model training and deployment'; AI processing example 'Anthropic Claude via AWS Bedrock' in isolated tenant contexts. Homepage partnership logos: Anthropic and AWS. Evals blog: Claude versions chosen per task. Customer pin/disable was not documented. OpenAI is not on the public list.
Ask: Name every Claude (or other) version that will process our content, the Bedrock region, whether SageMaker trains on our data, and whether we can pin or disable a model.
Subprocessors
Public claim only
Public DPA list: AWS, Anthropic, Amazon Bedrock, Amazon SageMaker, HubSpot, Snowflake, Mixpanel, Sentry. DPA cl 7: notice by updating the website list; customer may object per the Service Agreement. DPA also points subprocessors to the Trust Centre (security.robinai.com), which did not resolve on 2026-09-20. Datadog and CloudWatch are named on the security FAQ. ClamAV is used for malware scanning.
Ask: Provide the current dated list with entities, countries, data types, 30-day objection rights, and confirm Mixpanel/Snowflake/HubSpot/SageMaker do not receive contract text unless we enable them.
Training and secondary use
Not confirmed
Security page: customer data will not be used for model training, fine-tuning or other feature development without express consent. DPA 32.2: customer data used solely to provide the Services and not disclosed except to listed subprocessors. DPA 32.1.1: Robin may collect usage data and use it in aggregate de-identified form to improve the Services. SageMaker is listed as a subprocessor for machine-learning model training and deployment. Those statements are not reconciled in a readable spec.
Ask: Confirm in the signed Order that prompts, uploads, outputs, embeddings and logs are not used to train SageMaker, Claude or any other model for other customers, and that de-identified usage data cannot be reverse-engineered to our matters.
Feedback, ratings and product improvement
Public claim only
DPA 32.1.1 allows use of aggregated, de-identified usage and performance data to improve and enhance the Services. Mixpanel is listed for product analytics and user-behaviour tracking. No documentation of in-product thumbs or an opt-out for Mixpanel on matter content was found.
Ask: Can Mixpanel and other product analytics be disabled for our tenancy, and is any sampled contract text included?
Retention of prompts, documents and logs
Public claim only
DPA: duration of processing is the term of the Services Agreement. Backups: continuous point-in-time recovery with 30-day retention; AES-256; AWS KMS; replicated across availability zones; RTO ≤4 hours, RPO ≤1 hour. Logs in CloudWatch and Datadog, described as immutable. No numbered retention for chat threads, playbooks or embeddings beyond the term.
Ask: For our tenancy, list retention for documents, chat, playbooks, embeddings, Mixpanel, CloudWatch/Datadog and Bedrock, and whether Claude ZDR applies.
Deletion on instruction and on exit
Public claim only
DPA: on termination, securely delete or destroy Customer Data or, if directed, return and not retain, to the extent technically possible. On written request, delete Customer Data and confirm within 60 business days. Legal retention exceptions require written notice and a timeline. Derivative works without Customer Data may be kept. 30-day backup window implies a lag after deletion.
Ask: Contract a shorter deletion and return period (including backups, embeddings, SageMaker artefacts and subprocessors), matter-level deletion, and a written certificate within a defined number of calendar days.
Vendor and contractor access to content
Public claim only
DPA: authorised persons are Robin AI Limited and Robin AI Inc. employees and contractors providing the services. Customer data accessible to Robin only with explicit prior authorisation for support. MFA and RBAC (User, Admin, Owner, Internal). Managed-services marketing describes Robin lawyers reviewing customer agreements. Press reported that services group moved to Scissero — if so, those humans may now be a different processor.
Ask: Enumerate every human-access path at Robin, Scissero and AWS/Anthropic; can we require per-ticket consent; is Internal-role access logged and exportable; and is managed review off by default?
SSO, MFA, admin controls and audit logs
Public claim only
DPA: MFA required for systems handling sensitive data; enterprise SSO SAML 2.0 and OIDC; re-authentication every 10 minutes for sensitive operations; four roles; tenant isolation by tenant ID. Help: Admins/Owners invite, deactivate and change roles; permission groups (Owners see all groups including private). SCIM and customer-exportable prompt-level logs were not documented in the pages read.
Ask: On our plan, confirm SSO-only, SCIM deprovisioning, and an exportable audit log of prompts, exports, admin changes and vendor access with stated retention.
Encryption in transit and at rest
Public claim only
Security page and DPA annex: AES-256 at rest; TLS 1.2+ in transit; SSLv3/TLS 1.0 prohibited; Bedrock over HTTPS; backups AES-256 with AWS KMS; tenant-specific keys where applicable. Customer-managed keys are not offered in the public annex.
Ask: Name algorithms for embeddings, logs, backups and the Bedrock link, who holds KMS keys, rotation, and whether customer-managed keys are available.
Independent security assurance
Public claim only
Security page and DPA annex claim SOC 2 Type II, ISO 27001:2022 and Cyber Essentials. Reports were to be in the Trust Centre; that hostname did not resolve on 2026-09-20. Annual third-party network vulnerability assessment is promised on written request. IRAP was not found.
Ask: Provide under NDA the current SOC 2 Type II (scope, period, exceptions), ISO 27001 certificate, Cyber Essentials certificate, a pentest summary covering AI features, and any Australian Essential Eight/IRAP mapping. Confirm how we obtain them if security.robinai.com is down.
Contract, DPA, confidentiality, IP and liability
Public claim only
A full UK/EU GDPR Article 28 DPA is published, with SCCs/IDTA incorporated, 72-hour incident notice, subprocessor notice, deletion, AI-use clause and audit rights. No public MSA covering liability cap, Output IP, privilege, or Australian APP addendum was found. DPA 32.2 says customer IP ingested is only for providing the Services.
Ask: Produce the MSA: APP-aligned DPA flow-down including Anthropic/AWS, Output IP indemnity, Australian law, privilege language capable of NSW SC Gen 23 cl 9A, and a liability cap that is not eroded by the as-is software terms.
Cross-border processing and Australian residency
Public claim only
DPA cl 6.1 permits processing in USA, UK, Singapore, South Africa, Australia and Germany where needed for the Services (including LLM hosting), with appropriate safeguards. Security page says data never leaves Robin's AWS environment — which can still be a non-AU region. Singapore blog: in-country AWS for some features; some advanced AI still from Europe. No advertised Australian AWS pin. APP 8 analysis is required if personal information in contracts is processed overseas.
Ask: Is an Australian region available for storage and Claude/Bedrock inference; if not, list every category of data that leaves Australia and the APP-equivalent commitments we can rely on?
Breach notification and incident history
Public claim only
DPA: notify the customer as soon as reasonably possible and in any event within 72 hours of becoming aware of a personal-data breach (and related events listed in that clause). No public incident register. Trust Centre unreachable. No 24-month incident disclosure on the pages read.
Ask: Contract 72-hour notice for suspected incidents affecting any Customer Data (not only personal data), NDB cooperation, Australian-hours security contact, and disclose material incidents in the last 24 months including any related to the 2025 restructuring.
Change of terms, models, control and viability
Not confirmed
Artificial Lawyer (9 January 2026) reported a funding crisis, sale of managed services to Scissero, and an expected Microsoft acqui-hire of remaining engineers. Non-Billable quoted Microsoft: it hired several Robin AI employees and has no plans to acquire Robin AI. The marketing site, DPA, Word add-in and jobs board remained live on 2026-09-20. DPA allows subprocessor updates by website posting. No public change-of-control termination right was found.
Ask: Confirm current ownership, remaining headcount supporting the product, escrow or source-code arrangements, written notice before model or subprocessor changes, and termination plus data-return rights if Microsoft, Scissero or another party takes control or the product is discontinued.
Export, transition and shutdown
Public claim only
DPA: return or delete Customer Data on termination; deletion confirmation within 60 business days on request. No bulk-export API, open-format dump of playbooks/tables/chat, post-termination read-only window or escrow was found. Given 2025–26 restructuring reports, exit mechanics are a first-order diligence item.
Ask: Demonstrate a full tenancy export (documents, playbooks, tables, chat, logs) in open formats, a 30–90 day retrieval window, deletion including backups with a certificate, and what happens if Robin winds down mid-term.
DMS and storage connectors
Public claim only
Help: upload documents to a Robin legal library. Singapore post: SharePoint, Box and SFTP bulk uploads in development; AWS Textract for local Singapore processing. Word add-in connects to the Robin account. iManage/NetDocuments not found. What is copied versus queried is not specified.
Ask: For each connector we would enable, show identity, scopes, whether files are copied, how we disconnect and purge, and which items are generally available today.
Research with Legal Authorities
Not confirmed
Help: Research with Legal Authorities lets users explore legal sources on the web while incorporating context from the customer's documents; Robin searches the web, compiles an answer with citations, and the user can open the source webpage. Whether the open contract is sent to the search provider, whether the feature can be disabled per tenancy, and which search engine is used were not specified.
Ask: Can Research with Legal Authorities be disabled for our tenancy; what query payload leaves AWS; which search provider is used; and does the product refuse to answer when no source is retrieved?
Agent actions and confirmation gates
Public claim only
Word add-in offers AI suggested edits. Platform chat and tables generate structured extracts. Obligations create alerts. Help exists for 'Actions in Robin's Word add-in' (not fully extracted here). No public list of send/share/delete/write-back gates or prompt-injection testing was found. Tables API is marketed for structured data from documents.
Ask: List every action chat, playbooks, obligations 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
Platform marketing emphasises citations back to primary documents so lawyers can verify. Word add-in suggested edits still require a lawyer to accept. Managed services are a separate human-review path. No mandatory supervisor sign-off or exportable per-output review log with model version was found for the self-serve product.
Ask: Can we require supervisor sign-off before redlines leave the firm, export a per-document record of Claude version and reviewer, and disable managed-services access?
