hipaa.systems
Tool category

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.

Products 5Criteria 5Commissions None

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 BAAGoogle Workspace, Hushmail for Healthcare, Microsoft 365, Paubox, Proton Mail
Products compared5
Compared onEncryption in transit, Encryption at rest, Secure delivery to patients, Enforceable MFA, Audit logs for customers
2 more facts
CommissionsNone — no vendor pays us
Facts checked since2026-10-05

Compare the providers ↓

Comparison

Alphabetical. No vendor pays us for listings, rankings or referrals — methodology.

ProductSigns a BAAEncryption in transitEncryption at restSecure delivery to patientsEnforceable MFAAudit logs for customers
Google WorkspaceYesYesYesPartialYesYes
Hushmail for HealthcareYesYesYesYesPartialNot verified
Microsoft 365YesYesYesPartialYesYes
PauboxYesYesNot verifiedYesPartialYes
Proton MailYesYesYesYesNot verifiedNot verified
Found an outdated or wrong fact? Report it

Do not include patient information. Vendors are welcome — we check every report against the source before changing anything. Corrections policy.

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

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

Relevant for