AI in law firms: confidentiality, Rule 1.6 and Opinion 512

Jan Elvers, founder of Elevate Consulting
Jan Elvers spent seven years as a DevOps engineer building and running software that has to hold up in production. In 2026 he founded Elevate Consulting, where he builds automation, internal tools and integrations for small law firms and businesses. He leads every project himself, from the first call to operations.
Published · 9 min read
A law firm may use generative AI, but Rule 1.6 still governs every piece of client information that goes into it. ABA Formal Opinion 512 (July 2024) says lawyers must assess the disclosure risk of each tool, obtain informed consent before feeding client information into self-learning tools, read the vendor's terms, supervise staff and bill honestly. In England and Wales, the SRA expects contractual, technical and organisational safeguards. This guide explains the rules and the setup that meets them. It is not legal advice.
Part of the guide Law firm automation: what pays off and where to start
Key takeaways
- ABA Formal Opinion 512 requires informed client consent before information relating to a representation is entered into a self-learning generative AI tool.
- A general clause in the engagement letter authorizing AI use is not informed consent, according to Opinion 512.
- Before using any AI tool, a lawyer should read its terms of use and privacy policy, or rely on someone who has analyzed them.
- The SRA's August 2026 warning notice says client data should not train AI models unless explicitly authorised and appropriate.
- Lawyers billing hourly may charge only for time actually spent, including prompting and reviewing AI output, and not for learning a tool they use regularly.
What does ABA Formal Opinion 512 require of lawyers using generative AI?
Opinion 512 says the existing Model Rules apply to generative AI: competence (1.1), confidentiality (1.6), communication (1.4), meritorious claims and candor (3.1, 3.3, 8.4(c)), supervision (5.1, 5.3) and reasonable fees (1.5). The ABA Standing Committee on Ethics and Professional Responsibility issued it on July 29, 2024.
On competence, the opinion does not require lawyers to become AI experts. It requires a reasonable understanding of the capabilities and limitations of the specific tool, kept current as the tools change, which ties to Comment 8 to Rule 1.1 on the benefits and risks of relevant technology. Output must be reviewed to a degree that fits the tool and the task, and the lawyer remains fully responsible for the work.
The Model Rules are a template. Your state's adopted rules and its bar's ethics opinions are what bind you; Opinion 512 itself cites AI opinions from the Florida, Pennsylvania, West Virginia and California bars. Check yours before relying on this summary.
When does Rule 1.6 require client consent before using an AI tool?
Under Opinion 512, informed consent is required before information relating to a representation is entered into a self-learning AI tool, because such a tool may later reveal it to other users inside or outside the firm.
Rule 1.6(a) bars revealing information relating to the representation without informed consent, implied authorization or an exception. Rule 1.6(c) requires reasonable efforts to prevent inadvertent or unauthorized disclosure or access. Comment 18 lists the factors: sensitivity of the information, likelihood of disclosure without added safeguards, the cost and difficulty of safeguards, and their effect on the lawyer's ability to represent the client.
For consent to be informed, the opinion says the client needs the lawyer's judgment on why the tool is used, the specific risks, what kinds of information will be disclosed and the benefits. It states that boilerplate in an engagement letter is not sufficient. Where no client information goes into the tool, for example pure idea generation, the opinion says consent is not needed.
For tools that do not learn from inputs, the opinion does not set a blanket rule. It asks for a fact-driven risk assessment that depends on the client, the matter, the task and the tool.
What should a firm check before client data goes into an AI tool?
At minimum, read and understand the tool's terms of use, privacy policy and related contract terms, or consult a colleague or external expert who has. Opinion 512 calls this a baseline for every lawyer using a generative AI tool.
The opinion carries over checks from earlier cloud computing and outsourcing opinions. Rule 5.3 Comment 3 adds that the extent of the duty depends on the provider's reputation, the services, the terms protecting client information and the legal environment where the service is performed.
Confidentiality and security
The tool is configured to preserve confidentiality, the obligation is enforceable, and you will be notified of a breach or of legal process seeking client information.
Reliability and liability
You have looked at the provider's security measures, policies and any limits on its liability.
Retention and ownership
You know whether the provider keeps your inputs before and after the service ends, and whether it claims rights in them.
Training use
You know whether inputs are used to improve the model, and you have switched that off or chosen a plan where it is off.
Outsourcing basics
Reference checks, the vendor's security protocols, confidentiality agreements and a forum where you could enforce the contract.
Do you have to tell clients about AI use, and how may you bill for it?
Not always: under Opinion 512, Rule 1.4 disclosure depends on the facts, but it is required if the client asks, the engagement terms demand it, Rule 1.6 consent is needed, AI affects the fee, or output influences a significant decision.
The opinion gives evaluating litigation outcomes or jury selection as examples of significant decisions. It also names the engagement agreement as a logical place to explain how the firm uses AI, even where no disclosure is required.
On fees, Rule 1.5 applies. A lawyer billing hourly charges for actual time, which includes the time to prompt the tool and to review the draft. A flat fee that stays the same although AI made the work much faster may be unreasonable. Tools that work like general office equipment are overhead; a per-use third-party charge for a specific client may be billed as an expense at actual cost. Time spent learning a tool the lawyer uses regularly may not be billed.
What do Rules 5.1 and 5.3 mean for AI in a small firm?
Managing lawyers must establish clear policies on permitted AI use, and supervising lawyers must make reasonable efforts to ensure that lawyers and nonlawyer staff follow them. Opinion 512 applies this to both the firm's own people and outside AI providers.
Training should cover the basics of the technology, the limits of the tools, the ethical issues and secure data handling. The opinion also suggests marking AI-generated material as such when it is stored in a client or firm file, so later users know it may be fallible. In a two-lawyer firm the policy and the training can be short, but both should exist.
What applies to firms in England and Wales?
The SRA's warning notice on misuse of AI, published 17 August 2026, says client information should only enter AI systems where appropriate contractual, technical and organisational safeguards are in place, citing paragraph 6.3 of both Codes of Conduct on confidentiality.
It asks firms to satisfy themselves that client data stays in a secure environment, is not accessed by unauthorised third parties, is not used to train AI models unless explicitly authorised and appropriate, and is not kept longer than necessary. It warns that both free and paid tools can store or reuse inputs depending on terms, settings and architecture, and that privilege may be lost. Supervisors remain accountable under paragraph 3.5 of the Code for Solicitors.
Data protection applies on top. Where an AI provider processes personal data for the firm, the ICO says UK GDPR requires a written contract that limits processing to the firm's documented instructions, requires security measures, controls sub-processors and provides for deletion or return at the end. The SRA's compliance tips add that it should always be clear to clients when they are interacting with AI.
What does a confidentiality-safe AI setup look like in practice?
A safe setup keeps client data inside the firm's own tenant, uses a provider contract that excludes training on inputs, puts a named lawyer's review before anything leaves the firm, and logs every step. These are design choices, not features you add later.
We build this way because it maps directly to the duties above. It does not replace your own assessment of your state's rules or the SRA's standards, and whether a specific tool is acceptable for a specific matter remains a professional judgment.
| Control | What it does | Duty it supports |
|---|---|---|
| Runs in the firm's tenant | Client data is not copied to the developer or to a shared service | Rule 1.6(c); SRA Code 6.3 |
| No training on inputs | Contract and settings exclude model training and limit retention | Opinion 512 on self-learning tools; SRA warning notice |
| Review step before output leaves | A lawyer approves every AI draft; nothing goes to a client or court unreviewed | Rules 1.1, 3.3; SRA Code 3.5 |
| Log of every AI step | Input, output, reviewer and time are recorded | Rules 5.1, 5.3 supervision; SRA Code for Firms 2.1 |
| Documented vendor review | Terms, retention, breach notice and sub-processors are on file | Opinion 512 vendor checks; UK GDPR processor contract |
Cite this page
Elevate Consulting (Jan Elvers). "AI in law firms: confidentiality, Rule 1.6 and Opinion 512". https://elevate-consulting.net/en/guides/ai-in-law-firms-confidentiality-rule-1-6-opinion-512. Updated September 24, 2026.
Frequently asked questions
Can I paste a client email into a free public chatbot?
If the tool learns from inputs, Opinion 512 requires informed client consent first, and the SRA warns that doing this with public tools will likely breach confidentiality. The safer route is a business plan or deployment where training is off, retention is limited and the terms are reviewed. Check your state bar's guidance as well.
Is a clause in our engagement letter enough to cover AI use?
Not for informed consent under Rule 1.6. Opinion 512 says general boilerplate authorizing AI use is not sufficient; consent must be based on specific information about the tool, the risks and the benefits. The engagement letter is still a good place to describe how the firm uses AI.
Does Opinion 512 bind my firm?
ABA formal opinions are guidance on the Model Rules; what binds you are the rules your state has adopted, as interpreted by your state's bar and courts. Several state bars have issued their own AI opinions. This guide is general information, not legal advice for your jurisdiction.
Can we charge clients for our AI subscription?
Opinion 512 treats tools that work like general office equipment, such as AI built into a word processor, as overhead that should not be billed without advance disclosure. A per-use third-party charge incurred for one client's matter may ordinarily be billed as an expense at actual cost.
Does Elevate build systems that use AI?
Where it measurably helps, for example reading documents or sorting inquiries. Every AI step has a review point and a log, runs in your environment, and nothing AI-generated goes to a client unreviewed. No system we build makes legal decisions.
Sources
- ABA Formal Opinion 512, Generative Artificial Intelligence Tools (July 29, 2024), americanbar.org, accessed September 24, 2026
- ABA Model Rule 1.6, Confidentiality of Information, americanbar.org, accessed September 24, 2026
- ABA Model Rule 1.6, Comment (Comments 18 and 19), americanbar.org, accessed September 24, 2026
- ABA Model Rule 1.1, Comment 8, americanbar.org, accessed September 24, 2026
- ABA Model Rule 5.3, Comment 3 (nonlawyers outside the firm), americanbar.org, accessed September 24, 2026
- SRA, Misuse of AI: warning notice (17 August 2026), sra.org.uk, accessed September 24, 2026
- SRA, Compliance tips for solicitors regarding the use of AI and technology, sra.org.uk, accessed September 24, 2026
- ICO, What needs to be included in the contract? (controllers and processors), ico.org.uk, accessed September 24, 2026
This guide explains technology and workflows. It is not legal advice and does not replace a professional-responsibility review of your situation.
Deutsche Version: KI in der Kanzlei: Verschwiegenheit, § 203 StGB und DSGVO