---
title: "HIPAA Compliant Email Providers Compared: BAAs, Prices and Where a Shared Inbox Fits"
description: "HIPAA compliant email starts with a provider that signs a BAA. Compare Google Workspace, Microsoft 365, Paubox, Hushmail and more by plan and price."
author: "Andrew Rivers"
url: https://www.keeping.com/content/hipaa-compliant-email-providers/
datePublished: 2026-11-17
---

# HIPAA Compliant Email Providers Compared: BAAs, Prices and Where a Shared Inbox Fits

> **The short answer:** HIPAA compliant email means a provider that has a business associate agreement (BAA) with you, plus a setup that protects patient information. The BAA alone doesn't make you compliant. Consumer Gmail and Outlook.com have no BAA; Google Workspace (accepted in the Admin console) and Microsoft 365 (included in its data protection terms) do, and services such as Paubox, Hushmail and LuxSci sign their own. Your provider covers the mailbox only: a shared inbox or help desk on top needs its own BAA.

HIPAA compliant email means a provider that has a business associate agreement (BAA) with you, plus a setup that keeps patient information protected. The BAA alone isn’t enough. Consumer Gmail and Outlook.com have no BAA. Google Workspace (accepted in the Admin console) and Microsoft 365 (included by default) do, and services such as Paubox and Hushmail sign their own. Any shared inbox or help desk that reads that mail needs its own BAA too. And in Gmail, mail to outside servers is encrypted only when those servers support TLS.

## What makes email HIPAA compliant?

Email is HIPAA compliant when you have a BAA with each business associate that handles it, such as your mail provider and any tool that stores the messages, and your setup protects them with named logins, a record of activity and encryption where your risk analysis calls for it. As Microsoft puts it, using its services “doesn’t on its own achieve HIPAA compliance.”

What the rules require:

- **A BAA** with each of your business associates ([HHS guidance on business associates](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/index.html)).
- **Unique user identification.** Every person gets their own login.
- **Audit controls**, a way to record and examine activity in systems that hold patient information.
- **Protection for messages in transit.** Encryption here is “addressable” under the [Security Rule’s technical safeguards](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-C/section-164.312): you [assess whether it’s reasonable and appropriate](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-C/section-164.306#p-164.306%28d%29%283%29) and implement it if it is. If it isn’t, you document why and use an equivalent measure where that’s reasonable. Addressable doesn’t mean optional.

What we’d look for in a provider:

- Encryption in transit and at rest by default
- 2-step verification for every login
- Audit logs you can actually pull
- Required TLS for partners who receive patient information

Emailing patients has its own rule. HHS says providers may email patients, and the Privacy Rule doesn’t prohibit unencrypted email, provided you apply reasonable safeguards such as checking the address and limiting what you include ([HHS FAQ on emailing patients](https://www.hhs.gov/hipaa/for-professionals/faq/570/does-hipaa-permit-health-care-providers-to-use-email-to-discuss-health-issues-with-patients/index.html)). A patient who still prefers plain email after hearing the risk can choose it. A signature disclaimer changes none of this.

> **Sharing patient email in Gmail?**
>
> Keeping's HIPAA plan includes a signed BAA, so your front desk can assign, note and track patient emails without leaving Gmail.
>
> [See the HIPAA plan](https://www.keeping.com/lp/hipaa-compliant-help-desk/)

## HIPAA compliant email providers compared

HIPAA compliant email platforms come in two kinds. Mailbox providers host your address and sign a BAA for it: Google Workspace, Microsoft 365, Hushmail and Proton. Encryption services sit on top of the mailbox you already have and sign their own: Paubox, Virtru, LuxSci and MailHippo. Every provider in this table offers a BAA.

| Provider | What it is | How the BAA works | Starting price, with the plan | Best for |
| --- | --- | --- | --- | --- |
| Google Workspace | Hosted mailbox | Accepted by a super admin in the Admin console | $7 per user a month (Business Starter) | Practices already on Gmail |
| Microsoft 365 | Hosted mailbox | Included by default | $4 per user a month (Exchange Online Plan 1, email only) | Practices on Outlook |
| Paubox | Encryption layer on Workspace or Microsoft 365 | Included on every plan | $32 a month for up to 5 senders (Email Suite Standard) | Automatic outbound encryption |
| Virtru | Encryption layer for Gmail and Outlook | Signed BAA from the Starter plan | $119 a month for 5 users (Starter, billed annually only) | Expiry and revoking access |
| Hushmail | Hosted mailbox | Included on all three healthcare plans | $11 per user a month (Healthcare Basic) | Small practices wanting forms |
| LuxSci | Encryption gateway on Workspace or Microsoft 365 | Included on every tier | $50 a month for up to 5 users (Secure Gateway) | Automatic encryption |
| Proton | Hosted mailbox, end-to-end encrypted | Offered to any Proton user on request | $14.99 per user a month, billed monthly (Workspace Standard) | End-to-end encryption |
| MailHippo | Secure messaging alongside your current address | Included on every plan, the trial too | $4.95 per user a month (Basic) | Occasional secure messages |

Prices are from each provider’s pricing page on November 16, 2026, on the annual plan where there is one. Google bills its annual plan monthly, Proton’s price is month to month, and LuxSci doesn’t state a term.

Google and Microsoft don’t charge extra for their BAAs. Add-on services run from $4.95 per user a month (MailHippo Basic) to $119 a month for five users (Virtru Starter), on top of the mailbox.

## Do you need a mailbox provider or an encryption service?

Your current provider may be enough on its own if its safeguards cover what your risk analysis calls for. If you’re on Google Workspace or Microsoft 365, put the BAA in place, switch on the right settings and keep your address. Add an encryption service when you regularly email outside parties whose servers may not use TLS, or patients who need message-level encryption.

Gmail has one gap. It uses TLS when the receiving server supports it and sends unencrypted when it doesn’t. An admin can require TLS for specific partner domains, such as the labs and specialists you email most. Hosted S/MIME and client-side encryption need Enterprise Plus or Frontline Plus. Our [Google Workspace HIPAA setup checklist](https://www.keeping.com/content/google-workspace-hipaa/) covers those settings, and there’s a separate guide on how to [send encrypted email in Gmail](https://www.keeping.com/content/how-to-send-encrypted-email-in-gmail/).

For patients, some services deliver a secure link that opens the message in a browser portal. With a portal, expect calls from less technical patients asking how to open the message.

## The providers, one by one

### Google Workspace

Google signs its BAA at no extra charge once a super admin accepts it in the Admin console. Business Starter is $7 per user a month. What the BAA covers and leaves out is in [HIPAA compliant email in Gmail](https://www.keeping.com/content/is-gmail-hipaa-compliant/), and the settings are in our [Google Workspace HIPAA setup checklist](https://www.keeping.com/content/google-workspace-hipaa/).

### Microsoft 365 and Exchange Online

Microsoft’s BAA comes by default for covered entities and business associates and covers Exchange Online. Exchange Online (Plan 1) is $4 per user a month, email only. Microsoft 365 Business Basic is $7 with Teams or $5.40 without.

### Paubox

Paubox Email Suite encrypts outgoing mail from your Google Workspace or Microsoft 365 account, with the BAA on every plan. It’s priced per sender: Standard is $32 a month for up to five. A $20-a-month @pauboxmail.com mailbox suits people leaving a free Gmail or Yahoo address.

### Virtru

Virtru adds an encryption layer to Gmail and Outlook that lets you set an expiry date or revoke access after sending. Starter includes a signed BAA and costs $119 a month for five users, billed annually only.

### Hushmail

Hushmail for Healthcare is a hosted mailbox for small practices, on your own domain or @hushmail.com. All three plans include the BAA. Basic is $11 per user a month billed yearly. Intake forms start on Essentials at $13.75.

### LuxSci

LuxSci’s Secure Gateway encrypts outgoing mail from Google Workspace or Microsoft 365 and picks the delivery method for each recipient. It’s $50 a month for up to five users, BAA on every tier.

### Proton

Proton’s mail is end-to-end encrypted automatically between Proton users. Outside recipients get a password-protected message when you set one. Proton offers a BAA to all Proton users on request. Workspace Standard is $14.99 per user a month, billed monthly.

### MailHippo

MailHippo isn’t a mailbox. You use it alongside your current address, and recipients open messages through a secure link. Every plan includes the BAA, even the 30-day trial. Basic is $4.95 per user a month billed annually.

## Free and low-cost HIPAA compliant email

Consumer @gmail.com and Outlook.com accounts come with no BAA, so neither works for patient email. Free plans recommended elsewhere have mostly changed: MailHippo’s is now a 30-day trial, and Paubox offers a 14-day trial, not a free tier.

Proton is the open question. It offers a BAA to all Proton users but doesn’t say whether that includes free accounts, so on a free plan, ask Proton to confirm in writing first.

These paid mailbox plans include a BAA at no extra charge:

- Exchange Online (Plan 1), $4 per user a month, email only
- Microsoft 365 Business Basic (no Teams), $5.40
- Google Workspace Business Starter, $7
- Hushmail Healthcare Basic, $11 billed yearly

MailHippo Basic ($4.95) is a messaging add-on, not a mailbox.

### HIPAA compliant email for therapists

Solo therapists and small group practices usually need one or two mailboxes, intake paperwork and little friction for clients. A hosted service with forms built in, such as Hushmail’s Essentials plan, covers all three. Already on Google Workspace? An admin accepts Google’s BAA before any patient information goes in. Microsoft 365 includes Microsoft’s by default, and neither costs extra.

## Do you need to switch from Google Workspace to a HIPAA compliant provider?

Not necessarily. Google Workspace can be part of a HIPAA compliant setup once a super admin accepts Google’s BAA and the settings are right, and the same goes for Microsoft 365 with its default BAA. Switch, or add an encryption service, only for a specific gap you can name.

The usual gaps are message-level encryption to patients on a Business edition and a requirement to deliver through a portal. Before you move, compare an add-on’s ongoing cost with what switching would cost. If you’re not sure where you stand, start with [is Gmail HIPAA compliant](https://www.keeping.com/content/is-gmail-hipaa-compliant/) and the [Google Workspace HIPAA setup checklist](https://www.keeping.com/content/google-workspace-hipaa/).

## Your provider covers the mailbox. Your team’s tools need their own BAA

A shared address like frontdesk@ often has several people answering it, and sharing one password breaks the unique-login rule, because nobody can say who opened a patient’s message. Any tool that reads or stores that mail, whether it’s a shared inbox, a help desk or an AI add-on, is a business associate in its own right. Your mail provider’s BAA doesn’t cover it, and Google says outright that [add-ons aren’t part of its BAA](https://www.keeping.com/content/is-gmail-hipaa-compliant/).

So ask each tool the question you asked your provider: will this company sign a BAA, and on which plan? Our guide to [HIPAA compliant help desk software](https://www.keeping.com/content/hipaa-compliant-help-desk-software/) compares the tools small teams shortlist, and another explains how to [share an inbox without sharing a password](https://www.keeping.com/content/secure-email-collaboration/).

If you want HIPAA compliant Gmail for a shared address, Keeping is a shared inbox and help desk that runs inside Gmail. Its HIPAA plan is $49 per user per month, BAA included, with full HIPAA compliance: the lowest-priced HIPAA plan we have found among help desks that work inside Gmail.

Each teammate signs in with Google through your practice’s Google Workspace account. The shared address can connect with Google sign-in, or stay at a provider such as Microsoft 365, Hushmail or Proton and forward into a HIPAA Enabled Keeping account. Keeping’s BAA covers Keeping, and your mail provider’s covers the mailbox. Keeping doesn’t encrypt outgoing email. That stays with your mail provider.

Getting started takes three steps:

1. **Start the free trial with test data.** A trial account isn’t covered by the BAA.
2. **Request the BAA.** Leave patient details out of that message.
3. **Go live once you’re HIPAA Enabled.** The account is set to HIPAA Enabled before any patient email goes in.

[See how the HIPAA plan works](https://www.keeping.com/lp/hipaa-compliant-help-desk/), compare every plan on [Keeping pricing](https://www.keeping.com/pricing/), or [start your free trial on the HIPAA plan](https://app.keeping.com/signup?plan_id=HIPAA-USD-Yearly).

## How to choose a HIPAA compliant email provider

Five questions settle most of it:

1. Which suite are you on? If it’s Google Workspace or Microsoft 365, start with its BAA.
2. Who do you email: staff, outside partners, patients, or all three?
3. Will your patients open a secure link, or do they need mail that arrives like any other?
4. How many people share each address?
5. What can you spend per user, including any tool on top of the mailbox?

## Frequently asked questions about HIPAA compliant email

### Is Outlook a HIPAA compliant email?

Consumer Outlook.com isn’t, because it comes with no BAA. Microsoft 365 and Exchange Online business plans are different: Microsoft’s BAA comes with them by default for covered entities and business associates, through its Data Protection Addendum. You still need the right setup on top, including a named login for every person, 2-step verification and encryption settings that fit your risk analysis.

### Which emails are HIPAA compliant?

No email service is compliant on its own. Any provider that signs a BAA with you can be part of a HIPAA compliant setup, including Google Workspace, Microsoft 365, Hushmail and Proton, plus encryption services such as Paubox, Virtru, LuxSci and MailHippo. Consumer Gmail and Outlook.com have no BAA, so keep patient information out of them whatever settings you use.

### How to create a HIPAA compliant email?

Choose a provider that signs a BAA and put the agreement in place. Give everyone a named login and keep audit logging on, which the rules require. Add 2-step verification and the encryption settings your risk analysis calls for, which we recommend. Then decide how you’ll email patients, and get a BAA from any other tool that reads or stores the mail.

### Are email addresses considered HIPAA?

Yes, when they’re tied to health information. An email address is one of the 18 identifiers in HIPAA’s de-identification standard, so a patient’s address next to anything about their care counts as protected health information. A list of patient email addresses needs the same protection as the messages themselves, including a BAA with whichever company stores it for you.

### How much does a HIPAA compliant email cost?

The mailbox can cost as little as $4 per user a month with Exchange Online (Plan 1), $5.40 with Microsoft 365 Business Basic (no Teams) or $7 with Google Workspace Business Starter, BAA included. Hosted services such as Hushmail start at $11 (Healthcare Basic), add-ons at $4.95 per user a month with MailHippo Basic, and any tool on top has its own plan.

### Does an email disclaimer make it HIPAA compliant?

No. A confidentiality notice at the bottom of an email doesn’t protect the message, and it doesn’t replace a BAA, named logins or encryption. It can tell someone who received the message by mistake what to do with it, which is useful. Compliance still comes from your provider’s BAA and your own setup, not from the footer of the email.
