Blog

Is Twilio HIPAA compliant? BAAs for your whole stack

Emily LaneEmily Lane
Is Twilio HIPAA compliant cover

Is Twilio HIPAA compliant? Twilio signs a business associate agreement (BAA) with customers on its Security Edition or Enterprise Edition, and that BAA covers only the products on Twilio's HIPAA-eligible list. Compliance itself is shared: Twilio covers its side of those products, and you own how you build on them and what you send.

The more useful point for your build is that Twilio is rarely the only vendor in the path. Your SMS goes through Twilio, your email might go through SendGrid, your push goes through Firebase, and each of those is a separate decision. Every vendor that protected health information (PHI) touches needs its own BAA, or PHI has to stay out of that vendor entirely. So map the whole notification stack, not one provider. We're engineers, not your compliance lawyers, so treat this as the engineering reality, not legal advice.

What Twilio's BAA covers

Two conditions decide whether Twilio's BAA applies to you.

You need the right edition. Twilio says customers who want to sign a BAA "must have our Security Edition or Enterprise Edition" (Twilio HIPAA). If you use Twilio in a workflow that involves PHI, you execute a Business Associate Addendum to Twilio's Terms of Service. The HIPAA-eligible versions of the products work the same as the regular ones.

You use only eligible products. Twilio publishes a list of HIPAA Eligible Services, last updated June 30, 2026. The parts most notification builds care about:

  • Programmable SMS: SMS and MMS, on long codes, toll-free numbers, and short codes, plus messaging features like Advanced Opt-out and Message Scheduling
  • Programmable Voice and SIP
  • Verify: SMS, Voice, and Push
  • Lookup
  • Twilio Conversations (classic): chat, SMS, MMS, and group texting
  • Runtime tools: Studio and Functions, among others

Some items carry an asterisk that points to Twilio's Architecting for HIPAA on Twilio guide, which explains how to use those features in a HIPAA-eligible way. Studio is one of them. Read the guide before you put PHI anywhere near a flagged feature.

What's not on Twilio's HIPAA-eligible list

The list is the boundary. If a product isn't on it, Twilio's BAA doesn't reach it.

SendGrid isn't on it. Twilio's own SendGrid docs say SendGrid "is not a HIPAA Eligible Service" and that Twilio can't sign BAAs for SendGrid, so customers shouldn't use it for anything involving PHI (Is SendGrid HIPAA compliant?). One Twilio contract doesn't cover the whole Twilio family.

WhatsApp and Twilio Notify aren't on it either. Neither appears on the June 30, 2026 version of the list. That doesn't mean Twilio bans them. It means the BAA doesn't cover them, so PHI shouldn't flow through them. If you're moving a Notify integration elsewhere, see the Twilio Notify alternative guide.

Twilio updates the list (the June 30 change added the Compliance Toolkit and the Consent Management API), so check the current version before you build.

Shared responsibility: what Twilio covers and what you own

Twilio describes HIPAA compliance as "a shared responsibility between the customer and Twilio." Twilio covers its side of the eligible products. Everything around them is yours:

  • Content. What goes in the message body, the sender name, and the link. A BAA doesn't make a diagnosis in an SMS a good idea.
  • Consent and opt-out. HIPAA and the TCPA are separate gates. A PHI-free text still needs consent and a working opt-out. Advanced Opt-out is on the eligible list, but collecting and honoring consent is still yours.
  • Logs and access. Who on your team can see message bodies in the console, what your app logs, and where webhook payloads land.
  • Phone number reuse. Carriers recycle numbers. A text to a number the patient gave you two years ago may reach someone else, so keep numbers current and keep the content generic.

For what's safe to put in a text, see Is texting patients a HIPAA violation?

BAAs across your notification stack

Here's where common notification providers stand, each linked to the vendor's own page.

Checked November 2026.

ProviderSigns a BAA?Conditions
TwilioYesSecurity or Enterprise Edition, for products on the HIPAA-eligible list only
Twilio SendGridNoNot a HIPAA-eligible service, and Twilio can't sign BAAs for it
Amazon SES, SNS, and End User MessagingYesHIPAA-eligible under the AWS BAA (End User Messaging excludes its voice message and WhatsApp capabilities)
Firebase Cloud MessagingNoNot on Google Cloud's list of services covered by its BAA
OneSignalYesEnterprise Plan customers
BrazeYesOnly for a purchased HIPAA-eligible instance on Braze's HIPAA cluster
Customer.ioOn requestAsk your representative, and Customer.io's own guidance says not to send PHI in messages
PauboxYesEmail API, with a BAA on every plan
CourierYesEnterprise customers

A vendor family isn't a single answer: Twilio SMS can be covered while Twilio SendGrid can't. And "Yes" almost always comes with a condition, usually a plan, an edition, or a dedicated instance. Read the condition before you count a vendor as covered. For the email side in more depth, see HIPAA-compliant email.

Push is the gap

Push is where most stacks have no covered path at all. Firebase Cloud Messaging isn't on Google Cloud's list of BAA-covered services, so a Google BAA doesn't cover anything you send through it. On top of that, push payloads land on lock screens, where anyone holding the phone can read them.

So design push payloads to carry no PHI, whether they go out through FCM or Apple's push service:

  1. Send a nudge: "You have a new update. Open the app to view it."
  2. Include an opaque reference ID or a deep link, not the content.
  3. When the patient opens the app and signs in, fetch the details from your own API.

The device does the work of getting the PHI, over your authenticated connection, not through the push provider.

When a provider won't sign a BAA

A "No" in the table doesn't rule a provider out for healthcare. It rules out PHI in that channel. SendGrid works fine for "Your statement is ready, sign in to view it." It doesn't work for the statement itself.

The pattern is the same on every channel: the notification says something happened, and the details live behind sign-in.

ChannelSendsKeeps behind sign-in
SMS"Your results are ready. Sign in to view them."Test names, values, findings
Email"You have a new statement." plus a portal linkServices, codes, diagnoses
Push"You have a new update." plus a deep linkAnything clinical

Watch the sender and the URL, too. A generic message still discloses a condition if it comes from a specialty clinic or links to /oncology/appointments. For tested wording, see these appointment reminder templates, and for the architecture across every channel, see HIPAA-compliant notifications.

How Courier fits

Courier sits above your providers. It sends through the ones you connect, so you can keep Twilio for SMS under your Twilio BAA and add or swap other providers without rewriting your send code. Routing moves a notification between providers and channels, preferences let patients opt out of a category or pick a channel, and templates live in one place per notification type, so a PHI-free review happens once instead of in every service.

Here's a results-ready notification that tries SMS, then email:

JavaScript
import Courier from "@trycourier/courier";

const courier = new Courier({ apiKey: process.env.COURIER_API_KEY });

// A results-ready nudge: a portal link, never the result.
await courier.send.message({
  message: {
    to: { user_id: "patient_4821" },
    template: "results-ready",
    routing: { method: "single", channels: ["sms", "email"] },
    data: { portal_url: "https://portal.example-health.com/results" },
  },
});

The data is a link, not a result, so the SMS and the email fallback carry the same PHI-free content.

Courier maintains a HIPAA compliance program and signs BAAs with Enterprise customers, so if PHI could pass through Courier on its way to Twilio, you'd want a Courier BAA too. We recommend keeping PHI out of notification content either way, because a BAA and lean content work together. For details, see HIPAA compliance and BAAs in the docs and Courier for healthcare.

Wrapping up

Twilio signs a BAA on its Security and Enterprise Editions, for the products on its HIPAA-eligible list. SendGrid isn't one of them, and neither are WhatsApp or Notify as of June 30, 2026. Run the same check on every other vendor in your path, keep push free of PHI, and put the details in the portal, not the notification.

Frequently asked questions

Is Twilio HIPAA compliant?

Twilio supports HIPAA compliance for its eligible products. It signs a BAA with customers on its Security or Enterprise Edition, covering only the products on its HIPAA-eligible list, and it treats compliance as a responsibility it shares with you.

Does Twilio sign a BAA?

Twilio signs a BAA, in the form of a Business Associate Addendum to its Terms of Service, for customers on its Security Edition or Enterprise Edition. The BAA applies only to products on Twilio's HIPAA-eligible list. Contact Twilio sales to set it up.

Is Twilio SendGrid HIPAA compliant?

Twilio SendGrid isn't a HIPAA-eligible service, and Twilio can't sign BAAs for it. Use it for PHI-free notification email only, or send email that carries PHI through a provider that signs a BAA.

Is Twilio Verify HIPAA eligible?

Twilio Verify is on Twilio's HIPAA-eligible list for SMS, Voice, and Push, as of June 30, 2026. You still need a Security or Enterprise Edition account and a signed BAA before PHI is involved.

Can I send PHI over SMS with Twilio?

Sending PHI over SMS is best avoided, even with Twilio. Programmable SMS is on the eligible list, so a signed BAA covers Twilio's side, but not the text sitting on the patient's lock screen. A PHI-free text that links to your portal is the safer default.

Is WhatsApp on Twilio's HIPAA-eligible list?

WhatsApp isn't on Twilio's HIPAA-eligible list as of June 30, 2026. Keep PHI out of WhatsApp messages sent through Twilio, and check the current list before you build, since Twilio updates it.