Hello Railway team. We use Hobby with official PostgreSQL 18. The authenticated Backups page says backups/PITR require Pro; nothing is being enabled or upgraded. Before choosing a retention policy, we need staff clarification of when recovery becomes impossible, not merely when an item disappears from the UI.

1. For scheduled, manual and locked volume snapshots, what happens on nominal expiry versus explicit deletion? The API returns a workflow ID. What is the maximum time until neither the customer nor Railway Support can restore the snapshot, and what supported check proves that point?

2. For Auto Update/pre-update volume backups, what is the exact TTL? Can they be locked, do they appear in the ordinary backup list and count toward plan limits, and do they have the same deletion/finality rules?

3. Are any customer-data copies recoverable through Support or platform recovery after removal from ordinary backup/volume inventory? Please distinguish those from internal redundancy that cannot restore an individual deleted database, and state any maximum retention.

4. The official postgres-ssl implementation uses count-based pgBackRest retention after successful backups, with expiry failures deferred to a later backup; it documents old cluster prefixes surviving major upgrades without automatic expiry. Is there any independent platform cleanup or hard maximum age, including when the service is stopped? How should operators discover every still-restorable history?

5. For individual PITR backup/WAL objects or an explicitly deleted old history prefix, is there a recovery grace period or Support recovery after deletion? How can final unrestorability be verified? Please distinguish this from the documented two-day whole-bucket recovery window and PITR disablement with a preserved bucket.

6. Do PITR restore siblings persist without automatic expiry? Does deleting a service remove its attached AND previously detached volumes, or must each be deleted separately? How can operators inventory and verify destruction of all related resources, including soft-deleted ones?

Relevant docs: https://docs.railway.com/volumes/backups and https://docs.railway.com/volumes/point-in-time-recovery . If a guarantee or verification mechanism is unavailable, please say so explicitly. No account/configuration changes are requested.