HIPAA compliant email? Which providers sign a BAA
Email services that sign a BAA, compared on what actually protects patient messages — and what you still have to configure yourself.
HIPAA email services at a glance
No email service is HIPAA compliant on its own: you may send patient information through one only if the provider signs a BAA for your plan and you set up encryption, sign-in and access as its guide requires. We compare 5 products in HIPAA email services. 5 sign a Business Associate Agreement (Google Workspace, Hushmail for Healthcare, Microsoft 365, Paubox, Proton Mail). Every value links to the vendor's own documentation and shows when it was checked.
| Sign a BAA | Google Workspace, Hushmail for Healthcare, Microsoft 365, Paubox, Proton Mail |
|---|---|
| Products compared | 5 |
| Compared on | Encryption in transit, Encryption at rest, Secure delivery to patients, Enforceable MFA, Audit logs for customers |
2 more facts
| Commissions | None — no vendor pays us |
|---|---|
| Facts checked since | 2026-10-05 |
Comparison
Alphabetical. No vendor pays us for listings, rankings or referrals — methodology.
| Product | Signs a BAA | Encryption in transit | Encryption at rest | Secure delivery to patients | Enforceable MFA | Audit logs for customers |
|---|---|---|---|---|---|---|
| Google Workspace | Yes | Yes | Yes | Partial | Yes | Yes |
| Hushmail for Healthcare | Yes | Yes | Yes | Yes | Partial | Not verified |
| Microsoft 365 | Yes | Yes | Yes | Partial | Yes | Yes |
| Paubox | Yes | Yes | Not verified | Yes | Partial | Yes |
| Proton Mail | Yes | Yes | Yes | Yes | Not verified | Not verified |
Found an outdated or wrong fact? Report it
What to check before you choose
- A BAA on the plan you will actually use
- Many email services sign a BAA only on business or paid plans, and only for the services the agreement lists. Check the plan, the covered services and how you accept the agreement before any patient information is sent (45 CFR 164.502(e), 164.504(e)).
- Encryption in transit, and a way to send protected messages
- Transmission encryption is an addressable specification (164.312(e)(2)(ii)): assess whether it is reasonable and appropriate; implement it if so, and if not, document why and implement an equivalent alternative if that is reasonable and appropriate (164.306(d)(3)). In practice: TLS between mail servers, and a secure-message or portal option for messages to patients.
- Who can reach each mailbox
- HIPAA requires access control, audit controls and person authentication (164.312(a), (b), (d)). Our recommended way to meet them: one account per person, multifactor sign-in and audit logs you can read yourself. A shared login defeats all three.
- Patients who prefer plain email
- A patient may choose unencrypted email after you tell them the risk (emailing patients). Record the choice; it does not need a different product.
- Archive and export
- Emails that are part of a patient's record or of required documentation must be retrievable. Check archiving, search and export before you sign.
Common mistakes
- Using a free or personal account of the same brand because the business plan signs a BAA.
- Turning on add-ons, forwarding or third-party apps that the BAA does not cover.
- Treating the BAA as protection against misaddressed email — a message sent to the wrong person is still an incident to assess.
How we compare
- Encryption in transit
- Messages are protected with TLS between mail servers, and the service can require encryption or switch to a secure delivery method when the recipient's server does not support it.
- Encryption at rest
- Stored mail and attachments, including backups, are encrypted by the provider by default.
- Secure delivery to patients
- You can send an encrypted message that a patient can open without installing software or buying the same service — for example through a secure web portal or one-time code.
- Enforceable MFA
- An administrator can require multi-factor authentication for every user on the account, not just recommend it.
- Audit logs for customers
- You can see sign-in and mailbox activity logs yourself, on your plan, for long enough to investigate an incident.
What it costs
Requirements behind these criteria
- Business associate agreements (BAAs) →§ 164.502(e)
- Encryption of ePHI →§ 164.312(a)(2)(iv)
- Emailing patients →§ 164.522(b)
- Access control and sign-in →§ 164.312(a)(1)
- Audit controls and activity logs →§ 164.312(b)
Relevant for
- HIPAA for dental practices →
- HIPAA for employer group health plans →
- HIPAA for health app startups →
- HIPAA for IT providers and MSPs →
- HIPAA for medical billing and coding companies →
- HIPAA for physical therapists and chiropractors →
- HIPAA for SaaS companies that are business associates →
- HIPAA for small medical practices →
- HIPAA for therapists and psychologists in private practice →