Document Automation
Product features
By practice area
By company size
Contract Review
PRODUCT FEATURES
Resources
LearN
Case Studies
Pricing

Twelve security questions to ask legal AI vendors, what a good answer looks like, and why vendor terms matter for privilege and ABA Opinion 512.
Gavel Exec reviews, redlines and drafts contracts inside Microsoft Word, checked against your own playbooks. Start with 25 free queries, no credit card required.
The security questions to ask a legal AI vendor come down to four things: what happens to your data when it reaches an AI model, who can see it, where it is stored and how long it is kept. Ask each vendor for documents that prove its answers, such as its SOC 2 Type II report, its subprocessor list and the data protection terms in its contract.
Last updated November 10, 2026. Gavel publishes this guide and makes Gavel Exec and Gavel Workflows.
In the rapidly evolving world of legal technology, law firms increasingly rely on AI-driven tools to enhance efficiency and accuracy. However, with great power comes great responsibility: specifically, the responsibility to ensure that these powerful tools do not compromise client data or firm integrity. Here are essential security questions every law firm should ask their legal software vendors to safeguard their operations. Check out our CEO's video on this topic:
Start with the four questions below on how a vendor handles, uses, stores and deletes your data. Then add the eight that follow on certifications, subprocessors, hosting, access, uploads, testing and breach notice, integrations and contract terms.
At Gavel, we prioritize data security in all our handling and partnerships with AI models. Legal software often integrates with large language models from providers like OpenAI, Google, or Anthropic, each offering different data usage terms. Our agreements ensure that these models do not retain or train on your data, giving you confidence in how your information is managed.
It's crucial to verify that your client data is used solely for the intended services. At Gavel, we commit to not using your client data for training our models. We maintain strict data isolation and robust security measures to prevent unauthorized access.
Inquire about the storage locations and the security protocols in place. Ensure that your data is protected with end-to-end encryption, both in transit and at rest, and managed through secure encryption key practices, along with stringent data segregation.
Especially important in less regulated jurisdictions, understand your rights under the vendor's data retention and deletion policies. For instance, Gavel pledges to delete all customer data within a defined period post-account termination or upon customer request, ensuring compliance with laws like GDPR or CCPA.
A System and Organization Controls (SOC) 2 Type II report is an independent auditor's test of whether a vendor's security controls actually operated over a review period of several months. Ask for the report itself under a nondisclosure agreement, check the dates it covers and read the exceptions the auditor found. ISO/IEC 27001 certifies an information security management system, and ISO/IEC 42001 is the newer standard for managing AI systems. If your matters involve health records, ask whether the vendor will sign a Health Insurance Portability and Accountability Act (HIPAA) business associate agreement.
Ask for the subprocessor list and the name of every AI model provider on it. For each provider, ask whether the vendor has a zero data retention agreement, under which the provider processes a request and keeps nothing afterward, and whether that agreement covers every provider or only some. Ask too whether an administrator can switch off a provider your firm has not approved.
Data residency matters for clients in regulated industries and outside the United States. Ask which cloud provider and region hold your data, whether you can choose another region, and how the vendor handles transfers out of the European Union, for example under Standard Contractual Clauses.
Ask whether you can require single sign-on (SSO) and multi-factor authentication, set permissions by user or matter, and see a log of who opened what. Then ask which vendor employees can reach customer data, who approves that access and whether those employees pass background checks.
Some tools keep uploaded files in a project until you delete them, and others process a document and discard it. Ask where uploads, prompts and outputs are kept, for how long, whether backups hold copies, and how you delete one matter's data without closing the account.
Ask for the date and scope of the last independent penetration test and whether critical findings were fixed. Then ask for the breach notification period written into the contract. State breach laws give a firm fixed deadlines to notify affected people (California's is 30 calendar days), so the firm needs to hear from its vendor well inside that window. Our breach notification letter page covers what the notice itself must say.
AI tools increasingly connect to email, document management systems and chat apps, and some act on a user's behalf. Ask which connections exist, whether they respect your document management permissions and ethical walls, whether an administrator can switch each one off, and whether the tool asks for approval before it sends anything.
Ask for the data processing agreement (DPA) and confirm that it names the vendor as a processor acting on your instructions, lists the subprocessors, sets deletion timelines and gives you audit rights. Clients with outside counsel guidelines often impose security terms of their own, so compare the DPA against those guidelines before you sign.
By asking these questions, law firms can better understand their legal software vendors' commitment to security and make more informed decisions about who they trust with their sensitive data.
A good answer names specifics and comes with a document behind it. The table shows what to look for on each topic and the answers that should prompt a follow-up question.
| Topic | A good answer | A warning sign |
|---|---|---|
| AI providers and training | Named model providers, a written commitment not to train on your data, and zero data retention with each provider | Unnamed "leading models," or zero retention only "where feasible" with no list of exceptions |
| Certifications | A SOC 2 Type II report covering a recent review period | Only a Type I report, a badge with no report behind it, or a report more than a year old |
| Hosting | A named cloud provider and region, and a choice of region | No region stated |
| Access controls | SSO, multi-factor authentication, permissions by user or matter, and audit logs | Shared logins or no record of who opened what |
| Uploads and retention | A stated retention period for uploads, prompts and outputs, and deletion you can run yourself | "Deleted on request" with no timeline |
| Security testing | An annual third-party penetration test with a summary available | No independent testing |
| Breach notice | A notice period in the contract, stated in hours or days | "Promptly" with no number |
| Integrations and agents | Administrator control over each connector, and connections that honor your permissions | Connectors on by default with no administrator control |
A vendor's terms decide whether client information stays confidential, and confidentiality underpins both attorney-client privilege and a lawyer's duty under Model Rule 1.6. Rule 1.6(c) requires reasonable efforts to prevent unauthorized disclosure of client information, and a vendor's retention and training terms are part of that analysis.
In United States v. Heppner, No. 25 Cr. 503 (S.D.N.Y.), Judge Jed Rakoff held on February 17, 2026 that reports a criminal defendant prepared with a public AI platform on his own initiative were protected by neither privilege nor the work product doctrine. The court pointed to the platform's privacy terms, which allowed retention, model training and disclosure to third parties, and to the fact that no lawyer directed the work. It left open how it would treat an AI tool used at counsel's direction under enforceable confidentiality commitments.
ABA Formal Opinion 512, issued July 29, 2024, applies the existing Model Rules to generative AI. It expects lawyers to understand a tool's capabilities and risks (Rule 1.1), to protect client information (Rule 1.6) and to obtain informed consent before entering client information into a tool that learns from its inputs. Check your state bar's AI guidance as well.
An IT director should collect the vendor's security documents, test the controls during the trial and record the decision in the firm's AI policy. These six steps cover it.
Gavel Exec is SOC 2 Type II certified after an independent audit covering security, availability and confidentiality under the AICPA Trust Services Criteria. Gavel has zero data retention agreements with the AI models it uses, including OpenAI, and does not use customer data, prompts or documents to train AI models. AI features are optional, and customers can use Gavel without them.
Data is encrypted in transit with Transport Layer Security (TLS) and at rest with AES-256, and each customer has its own separate file storage and database. Data is hosted on Amazon Web Services (AWS) in the United States by default, with hosting in the European Union, Canada, Australia or another AWS region available. A leading cybersecurity firm tests the software every year, customers can turn on two-factor authentication or SSO with their preferred provider, and customers can delete all data in their account at once. Details are on Gavel's security page.
A SOC 2 Type I report says whether a vendor's security controls are suitably designed on a single date. A Type II report also tests whether those controls operated effectively over a review period of several months. For a vendor that will hold client files, ask for the Type II report.
Not necessarily. Zero data retention usually describes the agreement between the legal software vendor and its AI model provider, under which the provider deletes inputs after processing them. The vendor may still store your uploads, projects and outputs in its own systems, so ask about both layers.
It can put privilege at risk. In United States v. Heppner (S.D.N.Y. February 17, 2026), Judge Rakoff held that a defendant's own exchanges with a public AI platform were not privileged, partly because the platform's terms allowed retention and disclosure. The court left open how it would treat a tool used at a lawyer's direction under enforceable confidentiality terms.
Sometimes. American Bar Association (ABA) Formal Opinion 512 says a lawyer needs the client's informed consent before entering client information into a tool that learns from its inputs, and that boilerplate in an engagement letter is not enough. For other tools, the facts of the matter decide whether disclosure is required, and you must answer a client who asks.
Related: the AI vendor evaluation checklist for law firms, AI tools for solo lawyers, which AI model is right for your law firm and Gavel Exec.
What Claude offers lawyers and law firms in 2026: which plan to buy, how client data is handled, Claude for Legal plugins, Cowork and Claude's limits.
Client intake and CRM software for law firms compared by firm size: what each tool does, what it costs and how it hands off to documents.
28 verbatim Reddit comments about Gavel Exec and Gavel Workflows from r/LawFirm, r/legaltech and r/Lawyertalk, grouped by topic, each linked to its thread.