Product and intended use
Define the configuration, people, information and tasks being assessed.
Self-serve versus enterprise
Public claim only
Published AUD plans with query/upload caps; enterprise is custom. Azure models are an option for larger firms, not necessarily the self-serve default.
Ask: Which plan, query caps and Azure option will we buy?
Australian hosting
Public claim only
Legal policy: databases hosted in Australia with per-organisation isolation. Models may run via Azure, Bedrock or Anthropic enterprise APIs.
Ask: Confirm storage and inference countries for our plan, including Bedrock/Azure regions.
Research and assistants
Public claim only
Closed-corpus search, paragraph-level citations, custom assistants, document upload. Hallucination mitigation is claimed via the Australian corpus.
Ask: Which assistants are in our licence, and can we disable upload?
Australian law corpus
Public claim only
Expansive corpus of Australian case law, legislation and regulatory materials is claimed. Completeness versus Westlaw/Lexis/JADE is unproven.
Ask: List courts, date ranges and whether authorised reports and current consolidations are included.
Data, controls and requirements
Compare the actual configuration with firm, client and jurisdiction requirements, supported by evidence.
SC Gen 23 positioning
Public claim only
Legal policy asserts the product is built to comply with NSW SC Gen 23 for dedicated legal research software with non-training safeguards. That is the vendor's reading, not a court endorsement. Uploads remain a disclosure.
Ask: Provide the written SC Gen 23 analysis and a client-disclosure template.
Providers
Public claim only
Anthropic via Azure/Bedrock or Anthropic enterprise is given as an example. AWS and Google Cloud are named as subprocessors. Exact production mix is 'on request'.
Ask: Name the providers and regions on our tenancy.
Subprocessors
Public claim only
Full list available on request in procurement. AWS and Google Cloud are named. No public dated list or objection right.
Ask: Provide the current list, locations, notice and flow-down of no-training.
No training on client data
Public claim only
Legal policy: queries, conversations and uploads are not used to train or fine-tune any model; retrieved documents are never used to train; public data is used to train models (security blog). Enterprise-tier API no-store/no-train guarantees are claimed.
Ask: Point to the signed API terms and confirm they apply to self-serve as well as enterprise.
Aggregated usage
Public claim only
Anonymised aggregated usage may be retained for performance trends. Not Subscriber Content training.
Ask: Can query text appear in aggregated analytics?
Retention
Public claim only
Content not retained beyond what is necessary to provide the service and legal obligations. In-product deletion of conversations and uploads. Default periods not numbered.
Ask: State default retention for chats, uploads, embeddings and backups.
Deletion
Public claim only
Users can delete conversations, uploads or the whole account in-product. Certification on exit not described.
Ask: On account deletion, are embeddings and provider logs purged, and will you certify?
Personnel access
Public claim only
Production access restricted to authorised personnel under RBAC. No customer-visible access log described.
Ask: When can staff read content, and is it logged for us?
Access
Not confirmed
Session timeouts and suspicious-activity detection are claimed. SSO/SCIM not described for self-serve.
Ask: Is SSO/MFA/SCIM available on enterprise?
Encryption
Public claim only
Encrypted in transit and at rest. Azure option adds Azure's encryption. Algorithms not named.
Ask: Name TLS/AES versions and whether customer keys are available.
Assurance
Not confirmed
Regular security reviews and vulnerability assessments claimed. AWS/GCP certifications are the cloud providers', not Habeas's. No Habeas SOC 2/ISO claim found.
Ask: Does Habeas hold SOC 2 or ISO 27001, and will you share a pen-test summary?
Legal policy versus MSA
Public claim only
Public legal-policy page, not a signed MSA/DPA. Governing law not extracted. Enterprise likely has a separate agreement.
Ask: Provide the MSA, DPA, liability cap and Australian law/forum for our plan.
Inference versus storage
Public claim only
Databases hosted in Australia. Model calls may go to Azure/Bedrock/Anthropic enterprise; region not specified.
Ask: Does any prompt leave Australia on our plan, and what is the APP 8 basis?
Incidents
Not confirmed
No public breach-notification timeline.
Ask: What notice period from discovery will you contract?
Changes
Not confirmed
Not documented.
Ask: How are model or hosting changes notified?
Exit
Public claim only
In-product account deletion. Export format unknown.
Ask: How do we export chats and uploads before deletion?
Connectors
Not confirmed
Enterprise custom integrations mentioned; not specified.
Ask: List connectors and residual copies after disconnect.
Closed corpus
Public claim only
Research is described as over Habeas's Australian corpus, not the open web. Confirm no fallback web search.
Ask: Can any skill call the open web?
Agency
Public claim only
Custom assistants are described; autonomous email/DMS actions were not.
Ask: Can assistants take actions outside the Habeas UI?
Citations
Public claim only
Paragraph-level citations to Australian law are the verification path. Lawyer checking remains required.
Ask: Show 'no source' behaviour and pinpoint links on our sample questions.