Is Gmail HIPAA compliant? Not the free kind.
By David Freeland4 min read · 
A reply to an email you never sent
It’s Thursday evening, and you’re checking the clinic’s email from home. A patient has written back to a message that asked her to update her card through a link. “Is this really from you?” she asked. Your clinic never sent that email.
You open the Sent folder. That afternoon, the same message went to every person in your contacts, patients included.
It went out from your clinic’s own email address, the one on your website and business cards. That address is a free Gmail account you’ve used for years. You have an IT company, and they look after your computers and network. But a free account has no administrator, so they’ve never had a way to watch it. If Google noticed anything, its warning went to the phone or email on file, and no one else.
Now you need to know how someone got in and how long they were there. The account keeps a short history: the last 10 places it was opened from, with rough locations. That’s not enough to piece together what happened, or how.
What a free account can’t do
Free Gmail isn’t unprotected. By default, Gmail warns you about untrustworthy messages and moves them to spam. Mail between Google accounts is encrypted on the way. But on a free account, those defaults are all you get. Your clinic can’t add protection of its own:
- Encryption depends on the other side. Gmail encrypts a message on the way only when the receiving email service supports it. When it doesn’t, Gmail sends the message anyway, without encryption. A free account can’t make encryption a rule.
- Phishing protection stays at the default. HHS calls email phishing “a common cyberattack that can lead to a breach.” In a business account, an administrator can add stronger checks on attachments, links, and senders pretending to be someone else.
- No one is watching, not even your IT company. A business account can alert an administrator to suspicious sign-ins, keep six months of sign-in records, and connect to your IT company’s security tools. A free account has no administrator, so none of that is possible. It’s a blind spot, and it’s how a clinic that thought it was protected gets hacked.
The rules your email has to follow
The HIPAA Security Rule sets out three requirements that matter here:
- 45 CFR § 164.312(e)(1) requires measures that guard patient information sent over a network. § 164.312(e)(2)(ii) adds encryption “whenever deemed appropriate,” and labels it “addressable.”
- 45 CFR § 164.308(a)(1)(ii)(D) says your clinic must regularly review records of what happens in its systems, like who signed in and when.
- 45 CFR § 164.308(b)(1) lets a company handle your patient information only if your clinic gets “satisfactory assurances” that it will protect it. That’s the BAA. Google offers its BAA through a business account’s Admin console, and a free account doesn’t have one.
The “addressable” label on encryption doesn’t mean optional. Under 45 CFR § 164.306(d)(3), your clinic has to decide whether encryption is reasonable and appropriate. If it is, you use it. If it isn’t, you document why and use an equal alternative, if one is reasonable. For email that carries patient information, the case against encryption is a hard one to make.
In February 2026, HHS announced a $103,000 settlement with an Illinois treatment center. A phishing attack let an outsider into a staff member’s email account, and information on 1,980 patients was exposed.
Protect it, and watch it
- Ask who’s watching: Make sure your IT company knows about every email address your clinic uses, free ones included. Then ask: “If someone signs in to our email in a way that’s out of the ordinary, who gets the alert, and how far back can you look?”
- Move to a business account and sign the BAA: Have your IT company move you to a service like Google Workspace or Microsoft 365, in your clinic’s name, and set it up properly for healthcare. Sign the BAA before patient information goes in. Google’s is accepted in its Admin console, and Microsoft includes its BAA by default for customers covered by HIPAA.
- Make encryption a rule: In Google Workspace, an administrator can require encryption for mail to the domains you choose and test the connection. Services like Paubox and LuxSci encrypt every email you send by default, with no extra steps for your staff. Both work with Google Workspace and Microsoft 365.
Move to a business email account with encryption as the rule and someone watching, and you’ll lower your risk of a break-in. If someone does get in, the first notice is more likely to come from your IT company than from a patient.
Disclaimer: This guide shares general information about HIPAA. It isn’t legal advice. For advice about your clinic, talk with a compliance professional or a lawyer who knows healthcare law.
Last reviewed November 10, 2026.
References & statutory citations
- Google: Email Encryption FAQs (Transparency Report Help Center, no date shown). (opens in a new tab)
- Google: About the alert center (Google Workspace Help, last updated October 26, 2026). (opens in a new tab)
- Google: Last account activity (Gmail Help, no date shown). (opens in a new tab)
- U.S. Department of Health and Human Services (HHS): 45 CFR Part 164 Subpart C — Security Standards for the Protection of Electronic Protected Health Information (§§ 164.306(d)(3), 164.308(a)(1)(ii)(D), 164.308(b)(1), 164.312(e)(1) and 164.312(e)(2)(ii); eCFR, up to date as of October 23, 2026). (opens in a new tab)
- Google: HIPAA Compliance with Google Workspace and Cloud Identity (Google Workspace Help, last updated October 26, 2026). (opens in a new tab)
- Google: Set up recovery options (Google Account Help, no date shown). (opens in a new tab)
- Google: Advanced phishing and malware protection (Google Workspace Help, no date shown). (opens in a new tab)
- Google: Send email over a secure TLS connection (Google Workspace Help, no date shown). (opens in a new tab)
- U.S. Department of Health and Human Services (HHS): HHS’ Office for Civil Rights Settles HIPAA Investigation of Ambry Genetics Phishing Attack Affecting 225,000 Individuals (press release, September 17, 2026). (opens in a new tab)
- Google: Data retention and lag times (Google Workspace Help, last updated October 26, 2026). (opens in a new tab)
- U.S. Department of Health and Human Services (HHS): HHS’ Office for Civil Rights Settles HIPAA Security Rule Investigation with Top of the World Ranch Treatment Center (press release, February 19, 2026). (opens in a new tab)
- Microsoft: HIPAA and HITECH Act (Microsoft Learn, last updated July 29, 2025). (opens in a new tab)
- Paubox: Paubox Email Suite (product page, no date shown). (opens in a new tab)
- LuxSci: HIPAA Compliant Email (product page, no date shown). (opens in a new tab)