Region selection controls where your workload and attached volumes run, so a service pinned to EU West runs in Amsterdam. One important detail: all application, deploy, build, and HTTP logs are stored in US West regardless of deploy region, so selecting EU West does not keep logs in the EEA. For the subprocessor and infrastructure questions in both (a) and (b), the authoritative sources for your processing records are the DPA at railway.com/legal/dpa, the published subprocessor list, and the security and compliance materials at trust.railway.com.

Thanks — the log answer is useful and I'll act on it.

However my question (a)/(b) was specifically about request payload content (audio bodies and derived text in memory), not logs or subprocessors. The DPA and trust page don't answer whether payload data can transit through or be accessible from non-EEA infrastructure. Could this be escalated to someone who can confirm that specific point?

Happy to move to a support ticket :)

Railway does not offer a contractual data-residency commitment, on any plan including Enterprise, so we cannot confirm that payload data will never leave the EEA. The region picker (EU West = Amsterdam) controls where the workload and its volumes run, but it is the entire mechanism - there is no residency addendum or per-customer written guarantee beyond it, and the DPA is not amended or supplemented. The published documents (DPA, subprocessor list and trust materials) are the authoritative sources for your Article 30 records, and they are the same answer an escalation would arrive at.