We do not restore data on a customer's behalf, so there is no platform-side recovery window to quote. After a record is deleted from your volume, or the volume itself is deleted, we have no restore process that would bring that data back.

That is separate from volume backups you create yourself. With no manual or scheduled backups configured, none exist for that volume. If you turn them on later, scheduled backups expire on a fixed schedule: daily backups are kept 6 days, weekly backups 1 month, and monthly backups 3 months. Locked backups stay until you unlock them, and a backup you delete is removed right away. Volume backups are stored in the region the service deploys to, so a Singapore service is backed up in Southeast Asia (Singapore).

For the infrastructure providers involved in processing, the published subprocessor list at railway.com/legal is the authoritative reference for your notice.

Thanks. The automated answer addresses customer-visible backups and whether Railway restores data for customers, but not whether Railway retains its own internal platform recovery copies after a record or volume is deleted. Could a Railway staff member please confirm (1) whether those internal copies exist for a Singapore-hosted SQLite volume without configured backups, (2) their maximum retention or state explicitly that no maximum can be provided, and (3) where such copies are stored? We need to describe deletion accurately to users. Please distinguish platform-managed copies from customer-created backups.

Separate from the volume backups you configure, we keep internal platform backups for disaster recovery. They are not a recovery path for your data, because we do not restore customer data from them, and we cannot give you a maximum retention period or a storage location for them. For your notice, that means you should not say that no platform copy exists anywhere. You also should not give a fixed date by which every platform copy is gone.

Here is what we can state about deletion. A record deleted inside your SQLite database is removed from the live volume as soon as your application deletes it. When you delete a volume that still holds data, it goes into a 48-hour window during which workspace admins can cancel the deletion and restore it. After that window the volume is permanently removed, and it cannot be recovered unless you kept your own backup.

Volume backups you create follow the retention we described earlier and are stored in your service's deploy region. Plan-cancellation retention is a separate policy.