Skip to main content
Courier stores your data in a US or EU region, and you choose which.

​
Certifications and compliance

Courier maintains SOC 2, HIPAA, and PCI DSS programs, and supports GDPR and CCPA obligations. The Security Portal is the authoritative source and holds the current reports, including the SOC 2 report, the HIPAA report, and the most recent penetration test. Request them there for a vendor review. It also covers product, data, application, access, infrastructure, endpoint, and network security practices.
Courier is a managed cloud platform, so there is no self-hosted or on-premise deployment. If you are asking because of data residency requirements, the EU region keeps notification data inside European borders.

​
How it works

​
Regions and data residency

Courier runs in two regions: US (the default, us-east-1) and EU (eu-west-1, Ireland). The EU region stores and processes your notification data inside European borders, for data residency and GDPR (RGPD) compliance. The same workspace and API key work in both regions. Only the base URL differs. To keep data in the EU region, point your server SDK’s baseURL and your client SDK’s API URLs at the EU endpoints. The EU region is provisioned by arrangement. Contact Courier to enable it for your workspace.
The Courier console cannot create a tenant in eu-west-1 and rejects the request. is not region-gated, so create tenants over the API or from a US-region workspace.

​
Personal data in logs

Message logs can contain personal data. A message’s “request received” view shows whatever you sent, which may be PII (a profile’s email or phone) or PHI (data in your payload). control who sees it: Level 2 and Full expose request data, Level 1 does not. Restrict those roles, and keep data you do not want retained out of your payload.

​
GDPR and RGPD requests

Handle data-subject requests through the API in the region that holds the data. Access or export. returns the stored profile for a subject access request. Deletion takes more than one call. removes the profile, its stored contact details, and the user’s tenant memberships. It does not reach list subscriptions or device tokens, which are separate resources. Work the list in order: Device tokens delete one at a time, so read them back with first and delete each one.
Preferences have no delete. replaces a user’s override set, so the way to clear stored choices is to replace them with an empty set. Confirm that satisfies your own retention policy before you rely on it.
For an EU-region workspace, call the EU endpoint (https://api.eu.courier.com) so you act on the EU-resident copy. Courier’s data-processing terms are on the Security Portal.

​
Limits & behavior

  • Region is fixed per workspace deployment. A workspace’s data lives in the region it was provisioned in. You reach a region by targeting its endpoints, not by a per-request flag.
  • EU blocks tenant creation in the console. eu-west-1 rejects console-created tenants. is not region-gated, so provisioning over the API still works.
  • The same API key works in both regions. Residency comes from the base URL you call, so double-check baseURL in EU deployments.

​
FAQ

For an EU-provisioned workspace, use the EU endpoints (https://api.eu.courier.com, https://app.eu.courier.com). The same API key works in both regions, so the base URL your SDK and clients target decides residency.
Not from the console: eu-west-1 rejects the request. has no region gate, so create tenants over the API, or provision them from a US-region workspace.
A deletion request takes several calls, not one. removes the profile and its contact details, and subscriptions, tenant memberships, and device tokens are separate resources you delete too. See GDPR and RGPD requests for the full list. Use the EU endpoint for an EU workspace.