Country-neutral structure for a written policy. US rule where section 7216 and the FTC Safeguards Rule are named. Check your own regulator for AI, privacy and professional rules where you live. General information, not legal advice.
Why a solo practice needs a written AI-use policy
Software that drafts, summarizes, extracts or classifies is now built into email, spreadsheets, document tools and research tools. A freelancer on someone else's file can paste client data into one in seconds, often without noticing where it goes. A short written policy settles in advance what you will and will not do, gives you an answer when a firm or client asks, and tells you what to do when you slip.
No statute or regulation cited on this page is written specifically for AI tools. What bites are the general duties that already govern client information: professional confidentiality rules, the limits of section 7216 on return information, the firm's contract, and security controls. A policy applies those to a new kind of software. A template is on the template page for this cluster.
The rules the policy has to respect
- Confidentiality. The AICPA Code of Professional Conduct addresses confidential client information in its section 1.700. Its official text is on the AICPA site. One interpretation matters for tools: before disclosing confidential client information to a third-party service provider, a member should either have a contract requiring the provider to keep it confidential, with reasonable assurance about the provider's procedures, or get the client's specific consent (ET 1.700.040). The ethics page on AI tools with client data works through what follows.
- Section 7216 (US rule). For return information, disclosure means making it known to any person in any manner, and use means referring to or relying on it as the basis for an action (26 CFR 301.7216-1(b)(4) and (5)). A preparer may not disclose or use return information except as the statute or regulations permit or with the taxpayer's written consent (26 USC 7216(a) and (b); 26 CFR 301.7216-3(a)(1)). Whether a given tool amounts to a disclosure or an unpermitted use is a question to put to the firm's responsible CPA or counsel; do not assume it does not.
- Service providers (US rule). A firm covered by the FTC Safeguards Rule must select service providers that can maintain safeguards, require them by contract and assess them periodically (16 CFR 314.4(f)). A software tool that handles client data is the sort of arrangement that duty reaches.
- Contract. The firm's contract may limit tools, storage and sub-contractors more tightly than any rule. Follow it.
What a good policy covers
- Scope and owner. Who it covers, which tools it covers (built-in assistants count) and who is responsible, which for a solo practice is you.
- Approved tools. A short list of tools you may use, with the purpose for each. Anything not on the list needs a check first.
- Data you never put in a tool. Client names, taxpayer identifiers, bank details, return information and any file the firm has not approved. Where a task needs facts from a client file, use only what the firm has approved for that tool, in the form it approves.
- Client and firm permission. Use client data in a tool only when the firm's contract or the client's written consent allows it, and keep a record of which.
- Tool terms. Before you approve a tool, read what its terms say about retaining what you enter, using it to improve the tool, where it is processed, who else sees it, how you delete it and what happens in a breach. If you cannot find the answers, treat the tool as unapproved for client data.
- Accuracy and accountability. Output from a tool is a draft. You check each figure, citation and conclusion against the source and own the result. If you used a tool in preparing work, say so where the firm's procedures ask for that.
- Security. The same controls as your other tools: unique passwords, multi-factor authentication, updated devices. See the data-security pages.
- Incidents. If client data goes into an unapproved tool, tell the firm promptly. The page on suspected breaches sets out what to keep and say.
- Records. Keep the approved-tools list with dates of review.
- Review. Revisit the policy at least once a year and when a tool's terms change or the firm changes its rules.
Questions to ask before approving a tool
- Does the tool keep what I enter, and for how long?
- Can the provider use my input to train or improve its models?
- Where is the data processed and stored? Could that raise the question of disclosure outside the United States for return information?
- Who else, such as sub-processors, can see it?
- Can I delete everything I entered, and how do I confirm that?
- Does it log who used it?
- What does it say it will do if there is a breach?
If the answers are unclear, the practical rule is to assume the data is not protected.
Tasks that usually need less care
Some uses involve no client data: drafting a generic checklist, explaining a technical standard in your own words, or tidying your own notes. Even so, make sure nothing about a client, a file or a firm slips in, and check the output against the primary text.
Frequently asked questions
Can I use an AI tool on a client file if the firm does not mention it?
Treat silence as no. Ask the firm in writing which tools you may use.
Is anonymizing the data enough?
It reduces risk but does not end it. Names, numbers and context can identify a client. Under section 7216, the regulation's definition of return information includes derived information and statistical compilations, even if no one can be identified. Ask the firm before using even an altered extract.
Do I need a policy if I never use AI?
A short policy that says "none, unless the firm approves it in writing" still helps. Tools arrive inside software you already use.
Does a policy replace the firm's own rules?
No. The firm's contract and procedures come first.
Sources
- AICPA, Code of Professional Conduct (official text, section 1.700 on confidential client information): https://www.aicpa-cima.com/resources/landing/code-of-professional-conduct
- AICPA, Code of Professional Conduct, full text updated through July 2026 (PDF hosted by the Minnesota Board of Accountancy): https://mn.gov/boa/assets/AICPA%20Code%20of%20Professional%20Conduct_tcm1233-764395.pdf
- 26 USC 7216, Disclosure or use of information by preparers of returns: https://www.law.cornell.edu/uscode/text/26/7216
- 26 CFR 301.7216-1, Penalties for disclosure or use of tax return information: https://www.ecfr.gov/current/title-26/section-301.7216-1
- 26 CFR 301.7216-3, Disclosure or use permitted only with the consent of the taxpayer: https://www.ecfr.gov/current/title-26/section-301.7216-3
- 16 CFR Part 314, Standards for Safeguarding Customer Information (FTC Safeguards Rule): https://www.ecfr.gov/current/title-16/part-314
- NIST, Small Business Cybersecurity Corner: https://www.nist.gov/itl/smallbusinesscyber