Skip to content
Are expired Railway PostgreSQL backups and PITR archives permanently deleted?
jaifallu-byte
OP

3 days ago

Hi Railway team,

I'm reviewing PostgreSQL backup retention for privacy and data-protection compliance.

Railway documents retention periods for daily, weekly and monthly volume backups, as well as point-in-time recovery. However, I haven't found a clear explanation of what happens when those retention periods expire.

Could you please clarify:

Backup expiry: When a volume backup or PITR archive expires, is its underlying data permanently deleted or rendered unrecoverable? If deletion happens asynchronously, is there a documented maximum completion period?

Infrastructure copies: Does Railway retain additional infrastructure-level snapshots, replicas or disaster-recovery copies beyond customer-configured backups and PITR archives? If so, what retention periods apply?

Contractual commitments: Is there a documented maximum deletion timeframe covering all applicable copies? If so, could you reference the relevant DPA, Trust Center control or contractual provision?

I'm particularly interested in distinguishing backup expiration, logical deletion and permanent destruction.

An answer from a Railway staff member, with supporting documentation where available, would be greatly appreciated.

Thank you.

$20 Bounty

3 Replies

Railway
BOT

3 days ago

A volume backup is deleted when it reaches the expiry it carries: scheduled daily backups are kept 6 days, weekly backups 1 month, and monthly backups 3 months. A locked backup does not expire until it is unlocked, and a backup you delete manually is removed right away. Nothing happens to a backup after its expiry beyond that deletion.

PITR data (WAL segments and base backups) is stored in the service's WAL archive bucket and is deleted when that bucket is deleted. A deleted bucket can be restored for about two days. After that, its objects are permanently destroyed. On a standalone Postgres service, disabling PITR deletes the bucket. On a Postgres HA cluster, disabling PITR does not delete it.

Separately from your backups and PITR archives, we keep platform-level storage backups for our own disaster recovery after failures on our side, such as a host or storage incident. These are not used to restore customer data, and we do not perform data restoration from them.

For contractual terms, the published materials are our DPA, the Trust Center and the subprocessor list. We can't point you to a deletion timeframe covering all copies outside those documents.


Status changed to Awaiting User Response Railway • 3 days ago


Railway

A volume backup is deleted when it reaches the expiry it carries: scheduled daily backups are kept 6 days, weekly backups 1 month, and monthly backups 3 months. A locked backup does not expire until it is unlocked, and a backup you delete manually is removed right away. Nothing happens to a backup after its expiry beyond that deletion. PITR data (WAL segments and base backups) is stored in the service's WAL archive bucket and is deleted when that bucket is deleted. A deleted bucket can be restored for about two days. After that, its objects are permanently destroyed. On a standalone Postgres service, disabling PITR deletes the bucket. On a Postgres HA cluster, disabling PITR does not delete it. Separately from your backups and PITR archives, we keep platform-level storage backups for our own disaster recovery after failures on our side, such as a host or storage incident. These are not used to restore customer data, and we do not perform data restoration from them. For contractual terms, the published materials are our [DPA](https://railway.com/legal/dpa), the [Trust Center](https://trust.railway.com) and the [subprocessor list](https://trust.railway.com/item/subprocessors). We can't point you to a deletion timeframe covering all copies outside those documents.

jaifallu-byte
OP

3 days ago

Thank you for the response.

Because this information is needed for a formal privacy and data-retention review, could a Railway staff member please verify the following?

  1. Does Railway maintain additional platform-level storage backups or disaster-recovery copies beyond customer-configured volume backups and PITR archives?

  2. If those copies exist, what is their maximum retention period, and when is the underlying data permanently deleted or rendered unrecoverable?

  3. Can you confirm whether expired volume backups are permanently deleted at expiry, and whether deleted PITR archive buckets have an approximately two-day recovery window?

  4. Is there an official policy, Trust Center control or DPA provision governing these retention and deletion practices?

I understand that customer-facing restoration and Railway's internal disaster recovery may be different processes.

A response from Railway staff, rather than another automated answer, would be appreciated.

Thank you.


Status changed to Awaiting Railway Response Railway • 3 days ago


Railway

A volume backup is deleted when it reaches the expiry it carries: scheduled daily backups are kept 6 days, weekly backups 1 month, and monthly backups 3 months. A locked backup does not expire until it is unlocked, and a backup you delete manually is removed right away. Nothing happens to a backup after its expiry beyond that deletion. PITR data (WAL segments and base backups) is stored in the service's WAL archive bucket and is deleted when that bucket is deleted. A deleted bucket can be restored for about two days. After that, its objects are permanently destroyed. On a standalone Postgres service, disabling PITR deletes the bucket. On a Postgres HA cluster, disabling PITR does not delete it. Separately from your backups and PITR archives, we keep platform-level storage backups for our own disaster recovery after failures on our side, such as a host or storage incident. These are not used to restore customer data, and we do not perform data restoration from them. For contractual terms, the published materials are our [DPA](https://railway.com/legal/dpa), the [Trust Center](https://trust.railway.com) and the [subprocessor list](https://trust.railway.com/item/subprocessors). We can't point you to a deletion timeframe covering all copies outside those documents.

jaifallu-byte
OP

3 days ago

Thank you for the response.

Because this information is needed for a formal privacy and data-retention review, could a Railway staff member please verify the following?

  1. Does Railway maintain additional platform-level storage backups or disaster-recovery copies beyond customer-configured volume backups and PITR archives?

  2. If those copies exist, what is their maximum retention period, and when is the underlying data permanently deleted or rendered unrecoverable?

  3. Can you confirm whether expired volume backups are permanently deleted at expiry, and whether deleted PITR archive buckets have an approximately two-day recovery window?

  4. Is there an official policy, Trust Center control or DPA provision governing these retention and deletion practices?

I understand that customer-facing restoration and Railway's internal disaster recovery may be different processes.

A response from Railway staff, rather than another automated answer, would be appreciated.

Thank you.


Status changed to Awaiting Railway Response Railway • 3 days ago


Railway
BOT

3 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • 3 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...