
Yes. Courier maintains a HIPAA compliance program and signs Business Associate Agreements (BAAs) with Enterprise customers. Its HIPAA report, SOC 2 Type II report, and penetration test results are in the Courier Security Portal. If you're building notifications for a healthcare product, here's what Courier runs on its side, the controls you get, and the parts that stay with you.
The short version: Courier handles the infrastructure, the audits, and the security monitoring. You decide what goes into each notification, and we recommend keeping protected health information (PHI) out of it. A notification that says "Your results are ready, sign in to view them" gets the patient to the details without carrying them.
| Question | Answer |
|---|---|
| Does Courier have a HIPAA compliance program? | Yes. The HIPAA report is in the Courier Security Portal. |
| Does Courier sign a BAA? | Yes, with Enterprise customers, as part of the Enterprise agreement. |
| What can the BAA cover? | Every Courier service you use, including Journeys, Inbox, message logs, and AI features. |
| Does the BAA cover my SMS or email provider? | You need to work with your email and SMS providers for their own HIPAA terms. |
| Is Courier audited? | Yes. Courier holds a SOC 2 Type II report and runs an independent penetration test every year. |
| Can patient data stay in the EU? | Yes. Send through the EU datacenter (Ireland), available on Business and Enterprise. |
| Can I self-host Courier? | No. Courier is a managed cloud platform. |
| Area | What Courier does |
|---|---|
| HIPAA program | Maintains a HIPAA compliance program, documented in a HIPAA report. |
| SOC 2 Type II | Holds a SOC 2 Type II report, an independent auditor's assessment of how Courier's security controls operate over time. |
| Other programs | Maintains a PCI DSS program and supports your GDPR and CCPA obligations with a Data Processing Addendum. |
| Continuous monitoring | Scans the full codebase continuously, scans every code change with frontier AI models tuned for security, monitors every open-source package it depends on, and runs AI scans of its code and network posture. |
| Infrastructure | Runs on AWS across multiple availability zones, inside a private network with firewalls and intrusion detection. |
| Encryption | Encrypts customer data at rest. The API accepts HTTPS only. |
| Staff access | Staff use multi-factor authentication on internal systems, and access to customer data follows least privilege. |
| Testing | An independent firm runs a penetration test every year. |
| Data location | Your data stays in the datacenter you send it through: US or EU (Ireland). |
The monitoring runs between audits too, so security checks don't wait for the next SOC 2 report. Security in the docs has the details.
Courier gives you the controls a compliance review asks about:
Courier's AI features fit the same model. The Journeys AI node and AI Translation send data to OpenAI or Anthropic only when you use them, the providers don't store that data or train on it, and AI features can be included in your BAA. As with every notification, keep PHI out of prompts and template content. AI features and your data lists exactly what each feature sends.
HIPAA compliance is shared. These parts are yours:
| Document | Where to get it |
|---|---|
| HIPAA report, SOC 2 Type II report, penetration test | Courier Security Portal |
| Business Associate Agreement (BAA) | Your Enterprise agreement. Talk to our team. |
| Data Processing Addendum (DPA) | Courier's DPA |
| Subprocessors and their regions | Courier's subprocessor list |
For anything the reports don't cover, such as incident response, personnel security, and business continuity, contact Courier and we'll walk through it with you.
Courier signs BAAs with Enterprise customers. The BAA is part of your Enterprise agreement, and its scope is set during contracting and can cover every Courier service you use. We work through it with you one-on-one, along with any other security review questions you have.
To start, talk to our team. For how Courier supports healthcare teams, see Courier for healthcare, and for BAAs and log retention, see HIPAA compliance and BAAs in the docs.
Yes. Courier maintains a HIPAA compliance program, documented in a HIPAA report in the Courier Security Portal, and signs BAAs with Enterprise customers. Compliance is shared: Courier runs the platform and its security controls, and you decide what goes into each notification.
Courier signs BAAs with Enterprise customers. The BAA is part of the Enterprise agreement, and its scope can cover every Courier service you use, including Journeys, Inbox, message logs, and AI features.
Courier's BAA covers Courier. Your SMS, email, and push providers deliver the messages, so you need to work with them for their own HIPAA terms.
HIPAA has no official certification for vendors. Courier maintains a HIPAA compliance program, documented in its HIPAA report, and holds a SOC 2 Type II report. Both are in the Courier Security Portal.
Courier holds a SOC 2 Type II report from an independent auditor. Request access to it in the Courier Security Portal.
Courier recommends keeping PHI out of notification content and the data you send. A notification that tells the patient something is ready, and links to the details behind sign-in, works on every channel without carrying PHI.
Yes. Courier sends appointment reminders and "new results are ready" alerts across SMS, email, push, and in-app, with channel fallback and patient preferences built in. Keep clinical details out of the message and link to your app for the rest.
No. Courier's AI providers, OpenAI and Anthropic, don't store the data Courier's AI features send them or use it to train models, and AI features run only when you use them.
Yes. Courier runs separate US and EU (Ireland) datacenters with no data shared between them. Send EU patients' notifications through the EU datacenter, available on Business and Enterprise.
Courier's HIPAA report, SOC 2 Type II report, and penetration test results are in the Courier Security Portal. For more detail during a security review, contact Courier.

Clinical alert and notification systems: how escalation works
A clinical alert is easy to send and hard to close. This is how alerting works inside a hospital: where alerts come from, how routing by role and shift works, and how the acknowledge, timeout, escalate loop is actually built, including what happens when nobody answers.

How to send Slack notifications from your app
Slack is where your customers already work, which makes it a product surface rather than only an internal alerting channel. Posting an approval request or a status change into a customer's own Slack means working in workspaces you don't own, addressing people by email rather than Slack ID, and holding a separate credential for every customer.

How Product Teams Build, Test and Ship Multichannel Notifications in Design Studio
Product teams need to build, test, and ship notifications across multiple channels without filing an engineering ticket every time. Courier's Design Studio is the workspace for that: a template builder, visual channel routing, omnichannel testing, and publishing in one place. This post walks through the traditional template designer paradigm, how it splits effort across too many tools, and outlines a path for product and growth teams to ship transactional, product, and marketing notifications from a single workspace.