Railway doesn't restore data for customers, and that holds whatever internal platform copies may exist. The DPA's backup language doesn't give you a recoverable copy of your Postgres volume, so volume backups you configure are the only backups you can restore from.

For those, you set the schedule in the Backups tab of the service's settings. Daily backups are taken every 24 hours and kept 6 days, weekly every 7 days and kept about a month, and monthly every 30 days and kept about 3 months. Each backup is deleted when its expiry is reached, unless it is locked or you delete it sooner. Wiping a volume also deletes all of its backups. Backups are stored in the region your service deploys to. Details are in the backups docs.

The published DPA is at railway.com/legal/dpa, and our security and audit materials, including SOC 2 Type II, are on trust.railway.com.

Your reply didn't say whether Railway keeps its own copies of our Postgres volume. Do they exist, how long are they kept, and are they deleted when we delete data or the volume?

The copies you can see and manage are the volume backups in the service's Backups tab. That includes any snapshot we create ourselves: before a Railway-initiated Postgres security patch we snapshot the volume, and that snapshot shows up in the same tab and is kept for 30 days. Each backup is deleted when its expiry is reached or when you delete it, and wiping the volume deletes all of its backups.

Beyond those, we don't restore data for customers, so there is no other copy of your Postgres volume you can recover and no recovery window we can quote after you delete data or the volume.