This is an AI addendum for the written information security plan (WISP) your firm already has. It is a short section you fill in and attach, so the plan covers AI without being rewritten. It works with any WISP, including one built from IRS Publication 5708.
A WISP says how the firm protects client information in general. This addendum answers the questions AI adds: which tools see client data, who may use them, what a person must check before anything reaches a client, and whether the firm obtains consent under IRC §7216.
This is a starting point, not legal advice. The §7216 position in section 5 is a decision for your firm and its counsel.
Why AI needs its own section
Three rules meet when a US tax practice uses AI:
- The FTC Safeguards Rule (16 CFR Part 314) requires a written risk assessment and oversight of every service provider that handles client information. An AI vendor is a service provider.
- IRC §7216 makes it a crime for a tax return preparer to disclose or use tax return information for anything other than preparing the return, unless an exception applies or the client has consented in writing. Sending client information to an AI provider may be a disclosure.
- The GLBA Privacy Rule requires the firm’s privacy notice to describe who client information is shared with.
Most WISP templates were written before firms used AI and mention none of this.
WISP AI addendum template (copy and adapt)
Everything between the lines is the template. Replace the bracketed text, delete rows that do not apply, and attach it to your WISP.
[Firm Name]: AI addendum to the Written Information Security Plan
- Effective date: [date]
- Owner: [name of the WISP coordinator or Qualified Individual]
- Next review: [date, no later than six months from the effective date]
1. Purpose and scope
This addendum forms part of [Firm Name]‘s Written Information Security Plan. It covers every tool that uses artificial intelligence to read, summarize, classify, draft or act on firm or client information. That includes AI features inside software the firm already uses, general-purpose AI assistants, AI meeting notetakers, and any AI tool connected to firm systems. Where this addendum and the WISP differ, the stricter rule applies.
2. AI tool inventory
Only the tools listed here may be used with client information. The owner updates this table before a new tool is used and whenever a vendor changes its terms.
| AI tool | Vendor and its AI provider | Client data it sees | Training, retention and location | Approved uses |
|---|---|---|---|---|
| [AI features in practice management software] | [Vendor; AI provider named in its sub-processor list] | [Client names, emails, Job notes, uploaded files; identifiers masked before sending] | [No training, by contract; retention per vendor contract; processed in the United States] | [Summaries, drafting, filing uploads, workflow questions] |
| [General AI assistant, business plan] | [Vendor] | [Anonymized information only] | [No training, per business terms; kept 30 days; United States] | [Drafting, research preparation] |
| [AI meeting notetaker] | [Vendor] | [Internal meetings only] | [No training; retention per vendor contract; United States] | [Internal meeting notes] |
3. What data may go where
- Client information may be entered only into a tool whose row in section 2 lists that kind of data.
- Social Security numbers, EINs, bank and card numbers, and login credentials are never typed or pasted into an AI tool. Where a listed tool reads a document that contains them, the vendor’s masking or the firm’s redaction applies first.
- Tools listed as “anonymized information only” receive no names, identifying numbers, addresses or account details. Staff remove them before submitting and re-read the input.
- Personal or free accounts are never used for firm or client information.
4. Who may use AI
- AI tools are used only by [roles or named staff], each under their own account with multi-factor authentication.
- AI tools act with the permissions of the person using them. Nobody uses AI to reach information their role does not otherwise allow.
- Connections between an outside AI tool and firm systems (connectors, plug-ins, API keys, browser extensions) require the owner’s written approval and are recorded in section 2. [State the firm’s default, for example “No outside AI tool is connected to firm systems” or “Outside AI tools may be connected with read-only access.”]
- The owner reviews AI access [quarterly] and removes it when a person leaves or changes role.
5. Client consent and IRC §7216
[Firm Name] treats information clients provide in connection with tax return preparation, including names and contact details, as tax return information.
[Choose one position and delete the other.]
Position A: written consent. Before client tax return information is sent to an AI tool listed in section 2, the firm obtains the client’s written consent to disclose under Treasury Regulation §301.7216-3, using the form in Appendix A. Consent is requested with the annual engagement letter. For clients who have not consented, staff do not use AI tools on that client’s information.
Position B: contractor exception. The firm relies on Treasury Regulation §301.7216-2(d) for disclosures to the vendors listed in section 2, on the advice of [counsel’s name] dated [date]. Each vendor is under contract, receives only what the contracted service needs, and has been given written notice of sections 6713 and 7216. A copy of each notice is kept with this addendum. The firm has confirmed with each vendor where the vendor and its staff store and access the information. Where that is outside the United States, the firm obtains the client’s consent under Position A instead.
The firm’s privacy notice and engagement letters describe its use of AI service providers.
6. Human review
- AI output is a draft. Nothing produced by AI is sent to a client, filed with a tax authority, or relied on in a return until a qualified person has reviewed it.
- AI tools do not send client communications on their own. A person reviews and sends every email, message, request and document.
- Changes to client records proposed by an AI tool are approved by a person before they take effect, wherever the tool allows it. [List any tool that applies changes without approval and the firm’s compensating control, for example “read-only access”.]
- Figures are traced to source, and tax or legal statements are checked against current primary sources.
- The person who signs off the work is responsible for it.
7. Vendor review
Before a tool is added to section 2, and at least [annually] after that, the owner confirms and records:
- A written contract or data processing agreement is in place.
- The vendor and its AI provider do not train models on the firm’s data.
- The vendor names its AI provider and other sub-processors, and gives notice before changing them.
- How long the AI provider retains inputs and outputs.
- Where the data is processed.
- Encryption in transit and at rest, and multi-factor authentication.
- The vendor will notify the firm of a security incident, and within what time.
- Independent evidence of the vendor’s security: an audit report such as SOC 2, another third-party security assessment, or the vendor’s written description of its controls.
- AI features can be switched off, and the firm’s data deleted on request.
8. Risk assessment
The firm’s written risk assessment lists each AI tool in section 2 as a way client information leaves the firm, with the likelihood and impact of misuse, and the safeguards in sections 3 to 7.
9. AI incidents
Staff report immediately to [name or role] if client information is entered into a tool that is not listed, entered outside these rules, or sent or changed by an AI tool without review. The firm then:
- Deletes the conversation or data where the tool allows it, and disconnects the tool if needed.
- Records what was exposed, to which vendor, and for which clients.
- Follows the incident response section of the WISP, including any notification the law requires.
- Updates this addendum.
Prompt reporting is not penalized.
10. Training and review
Staff are trained on this addendum before using AI tools and [annually] after that. The owner reviews the addendum every [six months], and whenever a vendor changes its AI terms or the firm adds a tool.
Approved by: [Name, title, signature, date]
Appendix A: Consent to disclose tax return information to AI service providers
[For clients who file a Form 1040 series return, Revenue Procedure 2013-14 requires this consent to be its own document, in at least 12-point type on paper, containing nothing else. The two “Federal law” paragraphs and the TIGTA paragraph below are the IRS’s mandatory wording from section 5.04(1)(a) and (d) and must not be edited. If counsel advises that your AI vendors provide auxiliary services in connection with return preparation, use the wording in section 5.04(1)(b) instead. Do not leave blanks to fill in after the client signs.]
Consent to Disclosure of Tax Return Information
Federal law requires this consent form be provided to you. Unless authorized by law, we cannot disclose your tax return information to third parties for purposes other than the preparation and filing of your tax return without your consent. If you consent to the disclosure of your tax return information, Federal law may not protect your tax return information from further use or distribution.
You are not required to complete this form to engage our tax return preparation services. If we obtain your signature on this form by conditioning our tax return preparation services on your consent, your consent will not be valid. If you agree to the disclosure of your tax return information, your consent is valid for the amount of time that you specify. If you do not specify the duration of your consent, your consent is valid for one year from the date of signature.
[Firm Name] uses software with artificial intelligence features to help with administrative work, such as summarizing correspondence, drafting messages for our staff to review, and organizing documents.
I, [taxpayer name], authorize [Firm Name] to disclose to [name each recipient: the software vendor and its AI provider] the following tax return information: [for example: my name and contact details, correspondence with the firm, and the documents I provide for the preparation of my return], for the purpose of [for example: providing the administrative assistance described above].
Duration of consent: [date or period].
If you believe your tax return information has been disclosed or used improperly in a manner unauthorized by law or without your permission, you may contact the Treasury Inspector General for Tax Administration (TIGTA) by telephone at 1-800-366-4484, or by email at complaints@tigta.treas.gov.
Taxpayer signature: ______________________ Date: ____________
[Give the client a copy of the signed consent when they sign it.]
How to use this addendum
- Fill in the inventory first. Ask every team member which AI tools they use, including features built into software the firm already pays for. The table is usually longer than the owner expects.
- Take section 5 to your counsel. The regulations allow some disclosures to software contractors without consent, and the IRS has not said whether AI providers qualify. Written consent is the cautious choice. If you choose it, note that the IRS wording says you cannot make your services conditional on the client signing, so decide how staff will work for clients who decline.
- Check the consent form against the source. The mandatory wording comes from Revenue Procedure 2013-14, which also sets the rules for electronic consents and signatures. The consent contents come from Treasury Regulation §301.7216-3.
- Attach it and train on it. Add the addendum to your WISP, note it in the WISP’s revision record, and walk the team through sections 3, 4 and 6.
For the rules staff follow day to day, pair this with an AI policy for your firm. To take identifying details out of text before it goes into a general AI assistant, use the free client data redactor.
If your firm uses Tidyflow
These are the Tidyflow settings that match each section, set up for a tax practice that wants AI help with administrative work, outside AI tools kept out, and a person in control of client communications and record changes.
| Addendum section | In Tidyflow | Suggested setting |
|---|---|---|
| 2. Inventory | AI terms of use, sub-processors, Data Processing Addendum | Copy the AI provider, training, retention and location details from these pages into the Tidyflow row. |
| 3. Data | Identifier masking | Nothing to set. Email addresses, payment card numbers, bank account details and tax identification numbers such as SSNs and EINs are replaced with placeholders before data reaches the AI provider. Client names and the content you ask AI to work on, such as an email thread or a file, are sent. |
| 4. Who may use AI | Settings → Artificial intelligence | AI is off until an owner or admin accepts the AI terms, and each person then gives their own consent. Ask only the people named in section 4 to grant it. See Turn on AI for your firm. |
| 4. Outside AI tools | Settings → Artificial intelligence → Workspace access → AI tool access | Off, so nobody can connect ChatGPT, Claude or another outside tool. Choose View only if the firm approves a connection. Changes made by a connected tool apply straight away, so avoid View and make changes. See Connect AI tools with MCP. |
| 4. Outside agents | Settings → Agents | Use Tidyflow Agent only. Do not connect an externally hosted agent unless it is listed in section 2. |
| 5. Consent | Delegated client access | Selected client groups, with a group for clients who have consented. This limits the work you delegate to the agent. Agent chat and summaries follow each person’s own client access, so for clients who decline, staff should not use AI on that client’s records. |
| 6. Human review | Agent drafts and confirmation cards | Nothing to set. The agent never emails a client: it prepares a draft for a person to send. Consequential changes wait on a confirmation card. Leave the agent’s inbox ability off, and leave Auto-sort uploads off if every file rename should be approved. See Review agent confirmations. |
| 7. Vendor review | Security page, Data Processing Addendum | Record these against the checklist: an independent CASA Tier 2 security assessment for Google, security reviews passed with Xero and Intuit, hosting in U.S. data centres that are SOC 2 audited, encryption in transit and at rest, and a contractual 72-hour breach notice. Tidyflow has started the process for SOC 2 Type 1 and has not yet completed the audit. |
| 9. Incidents and access reviews | Team activity log (Pro) | The owner reviews AI tool connections and changes to the AI tool access setting. Changes made by a connected tool are recorded under the person’s name in Job, client and file history, and the agent’s work shows in each Job’s activity feed. |
Require two-factor authentication for the whole team (Pro) to meet the multi-factor line in section 4. See signing in and account security.
If your client engagements also need a §7216 clause, add the consent as an attachment to your tax preparation engagement letter. The starter engagement letter in new US Tidyflow workspaces includes an AI consent paragraph for clients who do not file a Form 1040 series return.