Privacy
This page says what we store, why, where, and how to have it removed. It is written to be read, not skimmed.
When you sign in with GitHub
We receive your GitHub login, display name, numeric id, avatar and verified email address. We use them to create your account and your first workspace, to show who did what in a workspace, and to email workspace admins about changes to these terms or to the service. We ask GitHub for read access to your profile and email only.
When you bake a stack
The forkstage command sends your repository (minus node_modules, .git and build output) and your forkstage.yaml to our control plane, which passes them to a host that builds and snapshots the stack. The snapshot, which contains your code and your seed data, is stored on that host while the stack exists. The recipe text is stored in our database so the dashboard can show it. We do not read, train on, or share your code.
When you run a fork
We record when it started, who started it, how long it took to be ready, when it ended and why, and the commands run through Forkstage with their exit codes and the last lines of their output. That record is the proof; it is kept for 30 days. Requests to a fork's public address are not logged beyond a timestamp used for the idle stop.
When you install the GitHub App
We store the installation id, the account it belongs to and the repositories it covers. For each pull request we fetch its diff with a short-lived installation token, store the run's status and the fork it produced, and post or edit one comment. We do not store the diff.
Where
The control plane and its database run on Railway in Amsterdam (EU West). Hosts that run forks are on Latitude.sh bare metal in Frankfurt. The dashboard is static files served from Railway. DNS for fork addresses is on Cloudflare.
Cookies
One cookie, fs_session, keeps you signed in to the dashboard for 30 days. The dashboard also remembers your theme and chosen workspace in your own browser's storage. There are no analytics or advertising trackers.
Removal
Destroying a fork removes it from the host at once. Deleting a stack removes its snapshots. To delete your workspace and account, including proofs and tokens, email hello@forkstage.com from the address on your GitHub account; it is done within seven days and confirmed by reply.
Changes
If this page changes in a way that matters to you, workspace admins hear about it by email before it takes effect.