Railway Corp.
Railway · Infrastructure
- Jurisdiction
- United States (Delaware). EEA workloads hosted in Netherlands (GCP europe-west4).
- Registered address
- 548 Market St, PMB 20429, San Francisco, CA 94104, USA
- Processing purpose
- Application compute and request routing for the HumanKey API.
- Data categories transferred
- Request metadata (URL path, timestamp, status), pseudonymised identifiers, transient inbound payloads during processing. Raw IP addresses are NOT persisted in our application data — all stored IPs are hashed via SHA-256 + daily salt before write. A narrow exception applies to short-lived rate-limit buckets in Railway-managed Redis: the canonical express-rate-limit middleware retains an IPv6-normalised raw IP as a Redis key with a TTL equal to the limiter window (≤15 minutes), purely as an anti-abuse control. No raw IPs in persistent logs, analytics, or audit trails.
- Retention
- Compute layer: transient — processed in memory; no persistent storage by Railway. Managed Redis (rate-limit buckets only): keys auto-expire at TTL ≤15 min via Redis EXPIRE — no operator action required.
- Transfer mechanism (GDPR Art. 46)
- EU data residency (GCP Netherlands) for production workload; Standard Contractual Clauses 2021/914 Module 2 cover control-plane access from US.
- Data Processing Addendum
- View DPA →
- Sub-processor chain (Art. 28(4))
- See vendor's own sub-processor list →
- Security certifications
- SOC 2 Type II