8 days ago
Hello Railway community,
We operate healthcare practice-management software in Spain. The clinic is the GDPR controller and we act as its processor.
Before signing Railway’s DPA, we need to clarify two points:
-
The public DPA’s Exhibit A currently lists no special-category data. Has anyone obtained guidance from Railway on the correct agreement or annex for processing health data under GDPR Article 9? Which official channel handles this?
-
Is there a supported way to restore an existing PostgreSQL volume snapshot into a separate temporary EU service for recovery testing, while leaving the live source service, volume and pending deployment configuration unchanged?
The recovery destination must not start application integrations or attach the same writable volume to two running services.
We have tested logical pg_dump/pg_restore recovery separately, but this does not validate Railway volume snapshots.
Links to official documentation or experience with a supported workflow would be appreciated. We will request contractual confirmation privately from Railway.
Thank you.
3 Replies
8 days ago
Our published Data Processing Addendum is the only data-processing agreement we offer, and we don't amend or supplement it for any customer or plan. Exhibit A lists no special-category data and that won't change, so there is no separate agreement or annex covering intentional processing of Article 9 health data. Whether that works for your use is a decision for you and the clinic's counsel. Our subprocessor list and security materials, including SOC 2 Type II, are at trust.railway.com.
If any of your processing falls under HIPAA, a BAA is available on Enterprise at a $1,000/month minimum commitment for 12 months. It sits alongside the DPA and does not modify it.
On snapshots, volume backups can only be restored into the same project and environment they were created in. Even within that environment, there's no supported way to attach a restored volume to a separate temporary PostgreSQL service for isolated recovery testing while leaving the live service unchanged. A normal restore creates a new volume and stages a swap for the original service, and applying that change redeploys the original service. Discarding the staged swap keeps the live service on its current volume, but the restored copy is left unattached, with no supported way to connect to or test it. Your logical pg_dump/pg_restore testing remains a separate, valid way to test recovery.
Status changed to Awaiting User Response Railway • 8 days ago
Railway
Our published [Data Processing Addendum](https://railway.com/legal/dpa) is the only data-processing agreement we offer, and we don't amend or supplement it for any customer or plan. Exhibit A lists no special-category data and that won't change, so there is no separate agreement or annex covering intentional processing of Article 9 health data. Whether that works for your use is a decision for you and the clinic's counsel. Our subprocessor list and security materials, including SOC 2 Type II, are at [trust.railway.com](https://trust.railway.com). If any of your processing falls under HIPAA, a BAA is available on Enterprise at a $1,000/month minimum commitment for 12 months. It sits alongside the DPA and does not modify it. On snapshots, volume backups can only be restored into the same project and environment they were created in. Even within that environment, there's no supported way to attach a restored volume to a separate temporary PostgreSQL service for isolated recovery testing while leaving the live service unchanged. A normal restore creates a new volume and stages a swap for the original service, and applying that change redeploys the original service. Discarding the staged swap keeps the live service on its current volume, but the restored copy is left unattached, with no supported way to connect to or test it. Your logical pg_dump/pg_restore testing remains a separate, valid way to test recovery.
8 days ago
Thank you. Please escalate this to a human support representative or your privacy/legal team.
We need confirmation whether Railway’s GDPR Article 28 agreement can accurately cover our processing: Cliniflux acts as processor for a Spanish clinic and hosts patient health data under GDPR Article 9.
Exhibit A lists no special-category data. Is there any applicable contractual provision covering this scenario without an inaccurate annex, or is this processing outside the scope of the agreement Railway offers?
A HIPAA BAA is a separate issue and would not resolve the GDPR processing-description mismatch.
Please also confirm the stated limitation on isolated snapshot recovery. Please provide guidance only, without changing or restoring our resources.
Status changed to Awaiting Railway Response Railway • 8 days ago
8 days ago
On the DPA: our published Data Processing Addendum is the only data-processing agreement we offer, and it is not amended, supplemented or given a separate annex for any customer or plan. Its Exhibit A records no special-category data, and the agreement contains no other provision covering the intentional processing of GDPR Article 9 health data. Whether that works for the clinic's processing is a determination for you and your counsel, not one we make.
On snapshots, the limitation stands. Volume backups can only be restored into the same project and environment, and a restore creates a new volume mounted to the original service as a staged change, which redeploys that service when deployed, with the previous volume kept but unmounted. There is no volume-backup restore that targets a separate service while leaving the source service and its volume untouched.
Status changed to Awaiting User Response brody • 8 days ago
a day ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 23 hours ago