Privacy
Privacy policy
In effect now, pending a full review by outside counsel. This page describes what Railyard actually collects and stores today. We'll notify account holders before any material change takes effect.
What we collect
- Account data — name, email address, hashed password, two-factor secret.
- Operational metadata — server names and addresses, application names, repository URLs, deploy history, build logs, and audit entries.
- Billing data — handled by our payment processor; we store a customer reference, not card numbers.
What stays on your servers, and what does not
Your application's own data (its database contents, uploaded files and customer records) lives on servers in your cloud account and is not copied to Railyard. To run your apps, the control plane does hold your environment variables (encrypted at rest), build and deploy logs, the runtime log lines your apps write for the retention you choose (7 days by default, 1 to 90), and the output of commands you run from the dashboard console.
Where it is stored
Operational metadata, environment variables and logs for the hosted control plane are stored on AWS in the United States (us-east-1). Your application's database and files stay on your servers.
Who can access it
Members of your team, according to their role. On our side, the operator console shows team names, counts and limits, never the inside of a team; to help you, an operator has to be invited as a member like anyone else. Every operator action on your team (limits, suspension, invitations, password-reset links, removals) is written to your team's own activity log with the operator named as the actor.
Retention
| Data | Kept for |
|---|---|
| Account data, team membership, audit entries | Until you delete the account or the team |
| Deploy and build logs | Until the deploy is deleted or the app is deleted |
| Runtime log lines from your apps | 7 days by default; each team can set 1 to 90 days |
| Server, app and traffic metrics | 30 days |
| HTTP checks and daily uptime | 7 days and 90 days |
| Database and volume backups | In your team's bucket, per the schedule and keep count you set |
| Environment variables | Encrypted, until you change or delete them or delete the app |
Your rights
From Account in the dashboard you can correct your name and email, download a copy of everything Railyard holds about you as a person (JSON), and delete your account, which also deletes teams where you are the only member. Team data (apps, servers, logs) belongs to the team and is deleted with it by its owner. For anything else, or to object to a use of your data, write to hello@railyard.run and we answer within 30 days.
Cookies
This website sets no cookies and runs no analytics. The dashboard at app.railyard.run sets one session cookie to keep you signed in, and a second one if you tick "remember this browser" for two-factor sign-in. Neither is used for tracking.
Where it is processed, and by whom
The control plane and its data are in the United States (AWS, us-east-1). Your servers are wherever you create them, including in Canada. The companies that process data on our behalf are listed on the subprocessors page; customers who need a data processing agreement can use the data processing addendum.
Québec's Law 25 and Canada's PIPEDA
The person in charge of the protection of personal information at Railyard is the founder, reachable at privacy@railyard.run. A privacy incident that presents a risk of serious injury is reported to the Commission d'accès à l'information and to the people concerned, and recorded in our incident register. Personal information is stored outside Québec (United States); the assessment of that transfer is available on request.