Home · Guides
How to share tax returns and client documents securely (2026)
Clients often ask for a completed return, an organizer, or a scan of a Social Security card by ordinary email. That is convenient, and it is also one of the easiest ways taxpayer data leaves the office unprotected. This guide restates what the FTC Safeguards Rule and current IRS Publications 4557 and 5708 say about sending that information. It is not legal advice, and it is not an IRS or FTC publication.
The legal baseline: encryption in transit and at rest
Tax and accounting professionals are “financial institutions” under the Gramm-Leach-Bliley Act framework that the FTC’s Safeguards Rule implements. Among the required safeguards is this sentence, quoted from the current official text of 16 CFR 314.4(c)(3):
Protect by encryption all customer information held or transmitted by you both in transit over external networks and at rest. To the extent you determine that encryption of customer information, either in transit over external networks or at rest, is infeasible, you may instead secure such customer information using effective alternative compensating controls reviewed and approved by your Qualified Individual.
Two points follow directly from that text. First, sending a tax return, a W-2, or a driver’s-license image as an ordinary, unencrypted email attachment is a transmission of customer information over an external network. Second, “we don’t have a portal” is not, by itself, an exception. The only alternative the rule describes is a set of effective compensating controls that the firm’s Qualified Individual has reviewed and approved. If you rely on that path, put the approval in writing and keep it with the WISP.
The same paragraph also covers data at rest: files on laptops, external drives, and cloud folders. Publication 4557 separately tells firms to encrypt data before uploading it to the cloud and to use drive encryption on devices that hold client files.
What IRS Publication 4557 actually says about email
The current official PDF of Publication 4557, Safeguarding Taxpayer Data (footer: Rev. 6-2024; no 2026 revision was posted on IRS.gov as of this writing) is consistent on this point in several places:
- In the basic security steps, it tells tax professionals to “Encrypt all sensitive files/emails, especially those with the taxpayer’s personally identifiable information, and use strong password protections.”
- In the phishing section, it says: “Send only password-protected and encrypted documents if you must share files with clients via email or use Secure File Transfer Protocol (SFTP) to transmit files instead of email.”
- The same section states that “A legitimate business will never email and request personal or sensitive information be sent to them via email, unless through a secured mail service.”
- The publication’s security-plan checklist adds: if you must transmit sensitive data by email over the Internet, be sure to encrypt the data. The IRS suggestion printed there is to transmit files via SFTP rather than email. The same checklist tells firms that collect information online to use a secure connection so the information is protected in transit, and to caution customers against transmitting sensitive data via email or in response to an unsolicited email or pop-up message.
The IRS repeats the core file-and-email instruction on its Identity theft information for tax professionals page: “Encrypt all sensitive files/emails and use strong password protections,” and “Send password-protected and encrypted documents only.” That page also states that the IRS cannot recommend security products.
Publication 4557’s checklist still mentions “Secure Sockets Layer (SSL)” and, as a printed suggestion, “Transport Layer Security 1.1 or 1.2.” TLS 1.1 is no longer treated as current by major browsers and payment platforms. If you run a portal or a site that collects client data, use a modern TLS configuration (in practice, TLS 1.2 or 1.3). That is a description of current platform requirements, not a substitute for the publication’s text.
The IRS sample WISP on how to exchange PII
Publication 5708, Creating a Written Information Security Plan (WISP) for your Tax & Accounting Practice (Rev. 8-2024), is an official outline and sample plan. The publication itself says it is not exhaustive and is not intended to replace your own research or to create reliance. Still, the sample “Electronic Exchange of PII Policy” is the clearest IRS-published example of an office rule on this subject:
- PII will not be in any unprotected format, “such as e-mailed in plain text, rich text, html, or other e-mail formats unless encryption or password protection is present.”
- “Passwords MUST be communicated to the receiving party via a method other than what is used to send the data; such as by phone call or SMS text message (out of stream from the data sent).”
- The firm “may use a Password Protected Portal to exchange documents containing PII upon approval of data security protocols” by the person who oversees the plan.
The glossary in the same publication defines “out-of-stream” with a concrete example: a password-protected file is emailed, and the password is relayed by text message, outside the same stream as the file. If you do use encrypted email attachments, do not put the password in the same message, the subject line, or a follow-up email in the same thread.
A practical order of preference for a tax office
The official materials do not rank products. They do, however, repeatedly prefer a secure file-transfer method over ordinary email, and they require encryption when email is used. A policy that matches those sources usually looks like this:
- Prefer a secure exchange method. Publication 4557 points to SFTP instead of email. The Publication 5708 sample plan allows a password-protected portal after the firm reviews its security. Whatever you choose, look for encryption in transit and at rest, multi-factor authentication for staff and, where offered, for clients, and a way to turn off access when an engagement ends. The IRS will not name a vendor for you.
- If you must use email, encrypt the document — not just the mailbox login. A password on the email account, or opportunistic TLS between mail servers, is not the same as an encrypted, password-protected file. Publication 4557’s instruction is to send only password-protected and encrypted documents. Use a strong password, and send that password out of stream, as the Publication 5708 sample plan describes.
- Do not put taxpayer data in the message body or the subject line. The sample plan’s “plain text, rich text, html, or other e-mail formats” language is aimed at unprotected content in the email itself. “Your refund is $X” or a Social Security number in the body is still an unencrypted transmission.
- Confirm the recipient before you send. A mistyped address is a disclosure. Publication 4557 also warns staff not to open or download attachments from unknown senders, including potential clients, and to make contact first by phone. The same caution runs in the other direction: if a client emails you unencrypted images of passports or tax forms, do not “reply all” with more data. Call, explain how you exchange files, and ask them to use that method.
- Protect the mailbox that does the sending. Publication 4557 and the IRS tax-professional identity-theft page both call for strong passwords and multi-factor authentication on email accounts, and for separate personal and business email. See the MFA requirement guide for what 16 CFR 314.4(c)(5) requires.
- Make it harder to impersonate the firm. Clients are more likely to trust a fake “your return is attached” message if anyone can send mail that looks like it came from you. SPF, DKIM, and an enforcing DMARC policy do not encrypt a file, but they do reduce that spoofing risk. You can check the domain you send from with the free in-browser test. A public-DNS review of 7,661 Florida tax-preparer mail domains, reported only in the aggregate, found that 82.1% were not enforcing DMARC; the method is in the Florida study. No firm is named.
Write the method into the WISP
Form W-12, line 11, and Publication 5708 expect a written plan, not an unwritten habit of “we usually use Dropbox in season.” The sample plan in Publication 5708 already has a place for an electronic-exchange policy, for a list of systems (including client portals and document-management tools), and for service-provider oversight. Name the method the office actually uses, who may send taxpayer files, how passwords are relayed, and how access is removed when a client leaves. Review it at least annually, or when you change software. The WISP template guide and the Safeguards Rule checklist walk through those elements. If an exchange goes wrong, the official reporting steps are in the tax-office breach-reporting guide.
What this page is not
This is not a product comparison, a certification, or a claim that following these publications, or using PreparerGuard, makes an office “compliant.” The IRS does not approve or endorse third-party security products. You still have to choose tools, train the people who handle taxpayer data, and adopt a plan that fits the office you run.
A next step, if you want one. The free email-spoofing check reads only public DNS; it will not tell you whether last week’s returns were encrypted. If you also need a written plan that includes an electronic-exchange section, PreparerGuard is a paid WISP kit based on Publication 5708. You still have to implement the controls and review the draft. It is not legal advice and is not affiliated with the IRS or the FTC.
Check my email domain Build my WISP Publication 4557 checklist
- 16 CFR 314.4(c)(3) (encryption in transit and at rest; compensating controls) — eCFR section 314.4
- IRS, Publication 4557, Safeguarding Taxpayer Data (Rev. 6-2024) — irs.gov/pub/irs-pdf/p4557.pdf
- IRS, Publication 5708, Creating a Written Information Security Plan (WISP) for your Tax & Accounting Practice (Rev. 8-2024), sample Electronic Exchange of PII Policy and “out-of-stream” glossary entry — irs.gov/pub/irs-pdf/p5708.pdf
- IRS, Identity theft information for tax professionals — irs.gov/identity-theft-central/identity-theft-information-for-tax-professionals
Related: IRS Publication 4557 checklist (2026) · FTC Safeguards Rule checklist · MFA requirement (16 CFR 314.4(c)(5)) · WISP template and Form W-12 line 11 · What to do after a data breach at a tax office · Free DMARC / spoofing check