Blog

EU data residency for notifications

Kyle SeylerKyle SeylerMarch 09, 2026
EU Data Residency for Notifications: What Engineering Teams Need to Know — cover

EU data residency means your notification data is stored and processed in the EU. GDPR doesn't require that on its own: a US vendor can lawfully hold EU personal data under Standard Contractual Clauses or the EU-US Data Privacy Framework. Many enterprise security reviews do require it, though, and notifications carry personal data on every send: user IDs, email addresses, phone numbers, device tokens, and message content with names and account details.

As of November 2026, Courier and Novu let you keep data in an EU region, OneSignal runs its data centers in the EU, SuprSend offers a custom data center region on its Enterprise plan, and Knock expects to add EU residency by the end of 2026.

Which notification platforms support EU data residency?

Courier

Courier runs two datacenters, US and EU (Ireland), and the EU datacenter is available on every paid plan: Business and Enterprise. The two are fully separate. Your EU workspace keeps its own templates, brands, users, logs, and API keys, and you send through https://api.eu.courier.com. Your team signs in to both with the same email address.

You don't have to move everyone at once. One account can send some users through the US API and others through the EU API, and each send's data stays in the datacenter it went through. Every server SDK and the CLI accept the EU base URL, and every client SDK accepts EU URLs for Inbox.

Novu

Novu Cloud offers an EU region in Frankfurt alongside its US region in Virginia, and its Enterprise plan adds the UK, Singapore, Australia, Japan, and South Korea (pricing page, November 2026). You pick the region when you create the account, and Novu keeps data strictly separate: it can't copy or move data between regions. Novu is SOC 2 Type II, ISO 27001, and GDPR compliant, and it also offers a self-hosted option if you'd rather run the infrastructure yourself.

OneSignal

OneSignal moved its data centers to the EU in 2025. That's one location for every customer rather than a region you choose, so there's no separate US or EU endpoint to pick. For GDPR requests it has a Delete User API, and it doesn't collect IP addresses from EU and UK users.

SuprSend

SuprSend is GDPR compliant and SOC 2 Type II certified, and its security docs say it supports EU data residency options. Its pricing page (November 2026) lists a custom data center region only on the Enterprise plan, along with self-hosted deployment and bring-your-own-cloud, which is in beta.

Knock

Knock is GDPR compliant, holds SOC 2 Type II certification, and supports data deletion through its API. It doesn't offer EU data residency today. Knock's plans documentation (November 2026) says it expects to support EU data residency by the end of 2026.

How Courier handles EU data residency

Set up the EU datacenter

  1. Sign up at app.courier.com if you don't have an account yet.
  2. Sign in at app.eu.courier.com with the same email address and open your workspace.
  3. Set it up the way you set up your US workspace: copy its API keys, connect your providers, and add your templates and brands.

Nothing carries over from the US on its own. A template published in the US console doesn't send through the EU API until you add it to your EU workspace, and a provider connected in the US isn't used for EU sends. Data you've already sent through the US stays in the US, so new notifications go through the EU API from the day you switch.

Two features run in the US datacenter only for now: AI journey nodes and the Template Metrics API.

Send through the EU API

Every server SDK and the CLI read COURIER_BASE_URL, so you can set it to https://api.eu.courier.com alongside an EU API key. To set it in code instead, pass the base URL when you create the client:

JavaScript
import Courier from "@trycourier/courier";

const courier = new Courier({
  apiKey: process.env.COURIER_API_KEY, // an API key from app.eu.courier.com
  baseURL: "https://api.eu.courier.com",
});

await courier.send.message({
  message: {
    to: { user_id: "user_123" },
    template: "ORDER_SHIPPED", // a template in your EU workspace
    data: { order_number: "A-1042" },
  },
});

The option is base_url in Python, option.WithBaseURL(...) in Go, .baseUrl(...) in Java, BaseUrl in C#, and --base-url on the CLI.

Connect Inbox to the EU

Inbox needs both halves pointed at the EU. Your backend mints each user's token with the EU client, because a US-issued token won't authenticate against EU hosts:

JavaScript
const { token } = await courier.auth.issueToken({
  scope: "user_id:user_123 inbox:read:messages inbox:write:events",
  expires_in: "2 days",
});

Then your app signs in with the EU URLs:

JSX
import { getCourierApiUrlsForRegion } from "@trycourier/courier-react";

courier.shared.signIn({
  userId,
  jwt,
  apiUrls: getCourierApiUrlsForRegion("eu"),
});

iOS, Android, Flutter, React Native, Vue, Angular, and Web Components each have an EU equivalent. Connect to the EU datacenter has the code for every SDK.

Handle GDPR access and deletion requests

Data-subject requests use the same Profiles and Users endpoints as the US, sent to the EU host. Run each request in every datacenter you've sent that user notifications through, because each datacenter keeps its own data.

Terminal
export COURIER_BASE_URL="https://api.eu.courier.com"
AUTH="Authorization: Bearer $COURIER_API_KEY"

curl "$COURIER_BASE_URL/profiles/user_123" -H "$AUTH"                         # export the stored profile
curl -X DELETE "$COURIER_BASE_URL/profiles/user_123" -H "$AUTH"               # profile, contact details, tenant memberships
curl -X DELETE "$COURIER_BASE_URL/profiles/user_123/lists" -H "$AUTH"         # list subscriptions
curl "$COURIER_BASE_URL/users/user_123/tokens" -H "$AUTH"                     # list device tokens
curl -X DELETE "$COURIER_BASE_URL/users/user_123/tokens/DEVICE_TOKEN" -H "$AUTH"  # delete each token

Preferences have no delete call. To clear them, replace them with an empty set using PUT /users/{user_id}/preferences. Compliance lists every call, plus where to get Courier's SOC 2 Type II and HIPAA reports.

Translations stay in your EU workspace

Each template stores its translations alongside its content, so they live in your EU workspace with everything else, and Courier sends each recipient the version that matches the locale on their profile or the send. Template translations covers syncing them from your translation tool over the API.

What to look for in a GDPR-compliant notification provider

Where the data is stored. A "GDPR compliant" badge tells you the vendor follows the regulation, not where your data sits. A vendor can store everything in the US and rely on Standard Contractual Clauses or the Data Privacy Framework. That's lawful, but it isn't residency, and a security review that requires EU residency won't accept it.

Which features run in the EU. Regional deployments sometimes trail the primary one. Ask for the list. Courier's EU datacenter has its own console, API, and Inbox hosts, and AI journey nodes and the Template Metrics API run in the US for now.

What happens to data you've already sent. Some vendors fix the region when you create the account. Others offer support-led moves. With Courier, data you've sent through the US stays there, and new sends through the EU API stay in the EU. The integration change is a base URL and an API key.

Self-serve data-subject tooling. You need API endpoints for access and erasure that cover every place the data lives: profiles, list subscriptions, device tokens, and preferences. If the only way to handle a deletion request is to email support, that won't scale.

Certifications. SOC 2 Type II, ISO 27001, and HIPAA programs show how a vendor runs security day to day, which residency alone doesn't. Courier maintains SOC 2 Type II, HIPAA, and PCI DSS programs, with reports on the Courier Security Portal.

Subprocessors and the DPA. Your provider might store notification data in the EU while a subprocessor handles analytics, logging, or delivery somewhere else. The DPA and subprocessor list should say where each one operates. Courier publishes its subprocessor list with regions and its Data Processing Addendum.

Where notification data leaves the EU

Your delivery providers. If you send email through SendGrid and SMS through Twilio, each has its own residency posture. The orchestration layer on top of them, which stores recipient profiles, preferences, and delivery logs and routes across channels, is a separate concern. Check both layers, and connect EU-appropriate providers in your EU workspace.

In-app notifications. Your inbox and toasts hold user IDs, message content, read state, and engagement events. That's personal data, and it needs the same residency as email and SMS. With Courier, Inbox region is per user: a user signed in with EU URLs reads from the EU datacenter.

Logs and observability exports. Delivery logs and error logs hold recipient identifiers and message metadata. Ask where they're stored, how long they're kept, and whether exports to an observability tool leave the region. Courier keeps message logs 30 days on the Developer and Business plans and 365 days on Enterprise, in the datacenter the message went through. Logs has the details.

EU data residency is on Courier's Business and Enterprise plans. Follow the regional datacenters guide to set it up, or talk to our team about your residency requirements.

Frequently asked questions

Do I need EU data residency for push notifications?

Yes, if your push notifications are tied to personal data of EU residents, and they almost always are, since every push is addressed to a device token and a user ID. Delivery itself goes through Apple (APNs) or Google (FCM), but the platform that stores recipient profiles, tokens, and delivery logs should meet your residency requirement. With Courier, connect APNs and FCM in your EU workspace and store EU users' device tokens through https://api.eu.courier.com, since providers and tokens in the US workspace aren't used for EU sends.