Hi, I run a rendering worker on Railway, and I am completing the data

residency section of my privacy policy. I need a few answers I can state

accurately to my own customers.

My service is a containerised worker

that pulls jobs from an external Postgres database, downloads media,

renders video, and uploads the result back out. It holds no database of

its own.

1. Which region is my service deployed in, and can I pin a service to a

   specific region on my plan? I want to confirm what I am reading in the

   dashboard rather than assume it.

2. Does anything I process persist on Railway after a run finishes? I am

   thinking of the container filesystem between deploys, build caches,

   and build artifacts. If something does persist, where is it stored and

   for how long?

3. Where are my service's logs stored, how long are they retained, and

   are they replicated to any other region?

4. Is any of my data replicated or backed up outside the region my

   service runs in, for redundancy or any other reason?

5. Do you offer a Data Processing Agreement, and do you act as a data

   processor for customer data that passes through a running service?

   If there is a signable version, please point me to it.

6. Where is your current sub-processor list published?

I am asking because I have to describe this accurately to my customers,

not to challenge anything. Questions 1 and 4 are what I need most.

Thanks