Courier supports HIPAA compliance: it maintains a HIPAA compliance program and signs Business Associate Agreements (BAAs) with Enterprise customers. 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.
| Area | What Courier does |
|---|---|
| HIPAA program | Maintains a HIPAA compliance program. The HIPAA report is in the Courier Security Portal. |
| 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. |
| Continuous monitoring | Scans the full codebase continuously, scans every code change, monitors every open-source package it depends on, and runs advanced 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. |
| Testing and backups | An independent firm runs a penetration test every year, and data is backed up daily. |
| 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.
HIPAA compliance is shared. These parts are yours:
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.
Courier maintains a HIPAA compliance program 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.
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 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.
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.