How does Railway protect user data?

Layer 1: Encryption (mostly handled for you)

Postgres encrypts data at rest by default and enforces TLS 1.2+ for all connections. You don't configure this — you verify it (HTTPS on your domain, no mixed content). Strong password hashing (bcrypt/argon2) is handled by Railway's auth provider if you use it, not if you roll your own. This layer rarely breaks.

Layer 2: Access control (where Railway apps actually leak data)

Server-side authorization middleware decides who reads what. Every route that touches user data needs a filter by authenticated user ID, enforced in the query (e.g., `WHERE user_id = $auth_user_id`). Client-side filtering is cosmetic — it protects nothing.

Layer 3: Secret & credential handling

Railway apps fail here predictably: service keys, third-party API keys, and admin credentials end up in frontend bundles. A service_role key in the browser bypasses all of Layer 2 by design.

Layer 4: Third-party data flow

Payment data (Stripe), analytics, email providers, webhooks — every integration is a data-protection question. Best pattern: keep sensitive data (PCI, PHI) off your servers entirely (Stripe Elements for card data, signed webhooks for integrations). Railway apps that proxy payment data through their own backend have taken on PCI scope they don't need.

Layer 5: Compliance (GDPR, CCPA, HIPAA)

No platform makes your app compliant. You need: explicit consent UI, data export endpoint (JSON/CSV of a user's data), deletion endpoint that cascades correctly (including backups, audit logs, third-party copies), breach notification within 72 hours (GDPR Article 33), and records of processing activities. Railway supports all of these at the infrastructure level; implementing them is app-level work.

The verification question

The single best test of "does Railway protect my user data": use an incognito window, no login, and try to query your database endpoint directly (e.g., a curl against your API without an Authorization header). If anything comes back that shouldn't, Layer 2 has failed. VAS runs this test programmatically across every endpoint.