Trust, security, and DSGVO compliance
Platform hosted on Hetzner in Germany. API keys stored as hashes, two-factor login with TOTP, a nonce-based CSP and HTTPS everywhere — for every account.
Compliance
DSGVO / GDPR compliance
Railwail is operated by Philipp Schmid in Bad Waldsee, Germany (see the imprint) and processes customer data under the EU GDPR (DSGVO). This section explains where data goes and how to exercise your rights.
The Railwail platform — website, API gateway, database, file storage and request logs — runs on Hetzner servers in Falkenstein, Germany; traffic to railwail.com passes through Cloudflare. To generate a result, your prompt and any files you send are forwarded to the provider that runs the chosen model: today Replicate for most models, otherwise OpenAI, Anthropic or DeepSeek. Many of these providers process data outside the EU. Model pages name who developed a model, which is not always the provider that runs it; the privacy policy lists the providers. Payments are handled by Stripe. Emails to info@railwail.com arrive on a mail server at OVH and are pre-sorted automatically with an AI model: depending on availability, sender, subject and up to 4,000 characters of the text go to OpenAI, Anthropic, DeepSeek, Google or xAI. Sign-in emails are sent through Resend.
Business customers who need a data processing agreement under GDPR Art. 28 can ask for one at info@railwail.com. Tell us which models you plan to use, because the providers behind them are part of the processing chain.
The privacy policy lists the service providers that process data for Railwail, including the model providers that receive your requests. Questions about a specific provider can be sent to info@railwail.com.
Requests for access (Article 15), erasure (Article 17) and your other data-subject rights can be sent to info@railwail.com. They are answered within the statutory period of one month (Article 12(3) GDPR).
Security
Platform security
The defaults are conservative — HTTPS-only transport, hashed API keys, a nonce-based CSP and optional two-factor login. We assume every request could be hostile.
Railwail currently holds no SOC 2 or ISO 27001 certification. This page describes the measures that are implemented in the platform today.
All pages and API endpoints are served over HTTPS with TLS 1.3 support and an HSTS header (includeSubDomains, preload). Plain HTTP requests are redirected to HTTPS. Card payments run in Stripe Checkout, embedded in the billing page or on Stripe's own page; your card details go to Stripe, and Railwail does not store them.
Every page is served with a Content Security Policy that uses a fresh nonce per request: scripts only run if they carry that nonce or come from an explicitly allowed source. This limits the impact of cross-site scripting.
Two-factor authentication with an authenticator app (TOTP, RFC 6238) and one-time recovery codes can be switched on for every account in the security settings.
Railwail API keys are stored only as SHA-256 hashes; the full key is shown once when you create it and can be rotated or revoked at any time. Passwords are handled by the authentication service and are never stored in plain text.
Changes to two-factor authentication, such as enabling it or generating new recovery codes, are recorded in an audit log for your account.
Privacy
Data handling & retention
Customer prompts and outputs are the customer's data. Railwail does not use them to train models, and you can ask for an export or deletion at any time.
Your generation jobs (prompt, settings and a link to the result) are kept in your account history so you can find them again. There is currently no automatic deletion period; you can ask for your data to be deleted at any time at info@railwail.com.
Railwail itself does not train models on your prompts or outputs. How the provider of the chosen model handles your data is governed by that provider's API terms: OpenAI and Anthropic, for example, state that they do not use API inputs and outputs for training by default. Other providers' terms differ; the privacy policy lists which providers receive your requests.
There is no self-service export or deletion button in the dashboard yet. Send your request to info@railwail.com; we export or delete your account data within the statutory period. Your usage and billing history is visible in the dashboard at any time.
Reliability
Uptime & outages
The gateway sits between you and many upstream providers. When one of them fails, you should not pay for it.
If the provider of a model fails, the run ends with an error and the credits reserved for it are returned to your balance. The one exception is a GPU-time run stopped at its reserved time limit: the time it used is charged. There is no public status page at the moment.
Each model in the catalog is assigned to one upstream provider. Our gateway's fallback to other vendors is switched off for every request of your runs, including streamed answers: if the provider fails, the run ends with an error and is refunded.
The platform runs at a single Hetzner location in Germany. Databases are backed up every night, and a copy of each backup is stored off-site in Hetzner object storage in Falkenstein, Germany.
Compliance & security contacts
All requests go to one address: info@railwail.com. Please name the topic in the subject line.
For the full text of our privacy notice and cookie usage, see the Privacy Policy and Cookie Policy. Terms of service are here.
Build on one API from Germany
No card required to sign up. Sign in with Google to get trial credits for the cheaper models.