Skip to content
Processing and remote-access countries for Meta App Review
maetze93
OP

6 days ago

Hello Railway team,

We need an authoritative current country list for Meta WhatsApp App Review for an application deployed in Amsterdam. Meta requires every country where Railway or its subprocessors process Platform Data, including remote operational/support access.

Please distinguish application/database/volume and object storage, backups, platform/application logs, and remote support access. Please confirm the legal provider entity and applicable subprocessor locations.

Your public DPA/Trust Center and a prior Central Station answer indicate that no fixed complete remote-access country list is published. Please escalate this to a privacy/compliance specialist or provide an authoritative document/private contact so we can answer accurately. We can provide the project identifier privately if required.

We are not requesting any configuration or plan changes. No customer data or credentials are included. Thank you.

Awaiting User Response

3 Replies

Railway
BOT

6 days ago

EU West is Amsterdam, Netherlands. A service deployed there runs there, and so does its attached volume. Native volume backups and PostgreSQL point-in-time recovery data also stay in the deploy region. Bucket (object) storage runs on Tigris in the bucket's region. All logs (application/runtime, build, deploy and HTTP) are stored in US West, whatever deploy region you choose. We have not checked the placement of your specific services, so this describes how the platform works for EU West in general.

We have a globally distributed team. When you explicitly request support, any access needed to investigate may come from wherever our team members work, and choosing a deploy region does not limit that access to the region. We will not be providing a list of countries that staff support access may originate from. Railway does not offer a contractual commitment to EU-only processing on any plan.

For the provider entity and subprocessor locations, the authoritative documents are our DPA and the subprocessor list.


Status changed to Awaiting User Response Railway • 6 days ago


Railway

EU West is Amsterdam, Netherlands. A service deployed there runs there, and so does its attached volume. Native volume backups and PostgreSQL point-in-time recovery data also stay in the deploy region. Bucket (object) storage runs on Tigris in the bucket's region. All logs (application/runtime, build, deploy and HTTP) are stored in US West, whatever deploy region you choose. We have not checked the placement of your specific services, so this describes how the platform works for EU West in general. We have a globally distributed team. When you explicitly request support, any access needed to investigate may come from wherever our team members work, and choosing a deploy region does not limit that access to the region. We will not be providing a list of countries that staff support access may originate from. Railway does not offer a contractual commitment to EU-only processing on any plan. For the provider entity and subprocessor locations, the authoritative documents are our [DPA](https://railway.com/legal/dpa) and the [subprocessor list](https://trust.railway.com/item/subprocessors).

maetze93
OP

6 days ago

Thank you. Please escalate this to a human privacy/compliance representative. The remaining issue is Meta’s mandatory exhaustive country declaration, including remote access; a region-only answer cannot satisfy that field. Can a human confirm whether Railway can provide this list privately or under NDA? If it cannot, please confirm that limitation and identify the appropriate compliance contact or written documentation we can present to Meta. We understand that Amsterdam deployment does not imply EU-only processing and that logs are stored in US West. We are not requesting a plan change or access to any customer data.


Status changed to Awaiting Railway Response Railway • 6 days ago


sam-a
EMPLOYEE

6 days ago

We understand Meta's form needs an exhaustive country list. We will not be providing a list of countries that staff support access may originate from, and that applies to private and NDA requests too. Our team is globally distributed. When you explicitly request support, any access needed to investigate may come from wherever our team members work.

For written material to present to Meta, the authoritative documents are our DPA, which names the provider entity, and the subprocessor list, with more at our Trust Center. Neither one lists where staff are located.

The storage locations from our earlier reply have not changed. Workloads, volumes, native volume backups and PITR data stay in EU West (Amsterdam), bucket storage runs on Tigris in the bucket's region, and all logs are stored in US West.


Status changed to Awaiting User Response sam-a • 6 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...