Legal teams evaluating AI in 2026 face a strange asymmetry: the product demos take an hour, but the confidentiality consequences last as long as the engagement. Professional duties do not pause because a tool is impressive: a lawyer who uploads client material to a system they have not vetted is making a confidentiality decision on the client's behalf, often without realising it. This guide collects the questions that surface real posture, organised so you can run them as a procurement checklist, with notes on what a good answer looks like.
Why vendor diligence is a professional duty
ABA Formal Opinion 512 addresses competence, confidentiality and supervision when using generative AI. It interprets the ABA Model Rules; assess the rules that actually govern the responsible lawyer. For vendor diligence, record where client data goes, who can access it and which commitments bind the purchased service.
Data handling: training, retention, encryption
Start with the questions that decide whether the platform is even eligible:
- Are customer documents or prompts ever used to train AI models? The only acceptable answer is no: contractually, not just by current policy. Training on client data means fragments of confidential matters can influence outputs served to strangers.
- How long is customer data retained, and what happens on deletion? Look for a defined retention window and a real deletion process, including backups. Indefinite retention "for quality purposes" is a red flag.
- Is data encrypted at rest and in transit? Industry-standard encryption at rest and TLS in transit are table stakes; the interesting follow-up is whether any staff can read customer content, under what controls, and with what logging.
- Is my data segregated from other customers'? Understand the isolation model: logical separation at minimum, with clear tenancy boundaries.
Certifications and independent audits
Keep assurance reports, certificates and legal-compliance assessments separate. AICPA describes SOC 2 as reporting on service-organisation controls. ISO/IEC 27001 concerns information-security management. Neither a badge nor a report title establishes the scope of evidence supplied by a particular vendor.
| Evidence | What to verify |
|---|---|
| SOC 2 report | Report type, covered service, period, criteria and exceptions. |
| ISO/IEC 27001 certificate | Named entity, scope, issuer, validity and applicability to the purchase. |
| Privacy-law assessment | Applicable roles, processing terms, rights, transfers and other requirements. |
| Pending evidence | Owner, expected delivery and effect of the gap on approval. |
GDPR, UK GDPR and India’s DPDP framework are laws, not interchangeable vendor certifications. Record evidence as requested, received, reviewed or accepted. An assessment of a vendor does not establish compliance of every customer deployment.
Data residency and subprocessors
Where data lives determines which laws reach it and what your clients can mandate. Ask which regions are available for storage and processing, whether residency covers processing or only storage at rest, and what is contractually guaranteed. Then map the supply chain: every AI platform sits on other providers (cloud hosting, model APIs, support tooling) and your data may flow through them. Ask for the current subprocessor list, the regions where each operates, the terms that bind them (including no-training commitments passed through to model providers), and how you are notified when the list changes. Our companion piece on data residency for legal teams goes deeper on when residency genuinely matters and when it is theatre.
Access controls and audit trails
Confidentiality inside the firm matters as much as confidentiality against outsiders. A legal-grade platform should offer:
- Role-based access control: project-level permissions (Owner, Editor, Viewer) inside organisation-level admin and member roles, so lateral hires do not inherit every matter.
- A complete audit trail: who ran what, on which files, and when, searchable by an administrator. This is what lets you answer a client's "who accessed our documents?" with evidence rather than assurance.
- Sensible session and account controls: organisation management, clean member offboarding, and a pending-invite state you can see and revoke.
These features double as ethics infrastructure: screening walls, matter confidentiality, and client audit rights are all easier to honour when the platform enforces and records access. See data security for law firms for the firm-side controls that pair with them.
AI-specific questions most checklists miss
Generic vendor questionnaires were written for SaaS, not AI. Add these:
- Are outputs grounded in retrieved sources with citations to page and passage? Verifiability is a security property: it is your defence against acting on fabricated content.
- Are citation labels deterministic or model-written? Deterministic labels (copied from the source) prevent a real authority from being mangled into a fake-looking one.
- What is the human-in-the-loop posture? The tool should be built for lawyer review (tracked changes, accept/reject controls, confidence flags) not silent automation.
- Which model providers sit underneath, and do no-training terms bind them too? A vendor's promise means little if the model API behind it keeps prompts.
- What does the system do when it is unsure? Good answers: asks a clarifying question, flags low confidence, says "not addressed". Bad answer: it always answers.
Commercial questions with security consequences
Three commercial terms quietly shape your risk. Pricing transparency: opaque usage pricing pushes teams toward unapproved free tools: exactly the shadow-AI behaviour that causes breaches; a stated subscription with clear usage credits keeps everyone on the governed platform. Data on exit: confirm you can export your work product (and its citations) in standard formats, and that deletion follows termination on a defined schedule. Plan gating: if security features like audit trails or access roles are locked to enterprise tiers, smaller teams end up less protected: prefer vendors whose security posture applies to every plan.
Red-flag answers that should end the conversation
- "We may use customer data to improve our models": in any form, however hedged.
- "We're SOC 2 ready" or "certification is on our roadmap" with nothing independently audited today.
- No subprocessor list, or refusal to name model providers.
- "Zero hallucinations" or "100% accurate": measurable overclaim that tells you how the vendor treats truth generally.
- No audit trail, or access roles that exist only in the top tier.
- Verbal assurances the vendor will not put in the contract.
How Judicio answers these questions
Use Judicio’s security page and Trust Centre to request current evidence and applicable terms. Confirm retention, processing locations, subprocessors and support access for your purchased service. Do not infer an issued audit report or certificate from this article.
Review the collaboration controls available on the selected plan and test the required permissions. Open source references in a product trial and measure verification effort. Keep procurement approval tied to the contractual evidence and deployment you actually inspected.