Privacy
Gas & Steel has no accounts and no sign-up. Everything you build stays on your device unless you deliberately move or share it.
What the app stores
Your rigs, your squadrons and your display preferences are saved in your browser’s local storage, on the device you are using — as is the small amount of bookkeeping the Google Drive connection and shared-game session need, described below. Merely using the app does not send this collection anywhere. Nobody but you can see it unless you choose to export, sync or share something, and that includes us.
The consequence is worth stating plainly: clearing your browser’s site data deletes your collection, and some browsers do that on their own for sites you have not visited in a while. That is why the app asks you to keep a backup file.
Files you export
Exporting writes a file to your device. Where it goes afterwards is entirely up to you. We do not upload it, keep a copy, or know that you made one.
Links you share
A share link carries the rig or squadron inside the link itself, in the part after the hash mark. Browsers do not send that part of an address to the server, so the content of a share link never reaches our host, and never reaches us. It does reach whoever you send the link to, and anyone they pass it on to, so treat a share link as public.
Google Drive
Connecting your Google Drive is optional, and nothing about it happens unless you ask for it. If you do connect it, the app asks Google for the narrowest access there is: permission to see and change only the files it creates itself. It cannot see the rest of your Drive and it does not ask to.
It writes one file, holding the same collection you would get from the export button, into your own Drive under your own storage. You can open it, move it, copy it or delete it exactly like any other file, and it stays yours if you stop using the app entirely.
The permission Google issues is held in memory for that session only. It is never written to storage, never included in an export, and never sent anywhere except to Google. In particular, it is never sent to the shared-game rendezvous service described below. You can withdraw the permission at any time from your Google account’s security settings.
Connecting does tell the app the email address of the Google account you connected, and the app keeps it on your device so it can show you which account the file is going to. That is the whole of what it is for. It is not recorded anywhere outside the Drive connection, never sent to us or the shared-game service, and it is forgotten when you disconnect. We have no access to it, to your Drive, or to the rest of your Google account.
Games you share live
If you choose to pair a game with another player, the invitation contains a short-lived, one-use secret in the part of its address after the hash mark. The app removes that secret from the address before asking you to confirm. It then uses an encrypted Cloudflare rendezvous service to introduce the two browsers; that service receives encrypted connection setup messages, not your squadron or game state, and deletes its room after the session ends or expires.
Once connected, the two browsers exchange the table-visible state of their games directly. Your private notes, library history and unrevealed Preparation choice are not included. Each browser remains authoritative for its own game. The app keeps the room reference, encrypted signalling key and a resume secret in local browser storage so the devices can reconnect after a routine interruption or reload; leaving the shared session removes that local binding and asks the rendezvous service to delete the room.
Analytics and tracking
No analytics script runs on these pages. No advertising, no tracking cookies, and no third-party scripts of any kind — the site’s own security policy forbids loading them, which is a stronger guarantee than a promise.
The only numbers we look at are the request counts Cloudflare keeps for any site it serves, described below. We add nothing to them, and they say nothing about who you are.
Hosting
These pages and the builder are served by Cloudflare Pages. Like any web host, Cloudflare receives and briefly logs the ordinary details of a request — your IP address, the page asked for, your browser’s description — in order to serve it and to block abuse. That is handled under Cloudflare’s own privacy policy, and we add nothing to it from this end.
The testing password
While the builder is in testing it is behind a single shared password. It is not an account: there is no username, no record of who used it, and nothing tied to you.
Successful shared-game setup sets a necessary security cookie in the testing app. The cookie lets your browser open setup connections without another password prompt. The cookie expires after five minutes. Further authenticated setup requests refresh the cookie. The cookie contains no password, game data, or tracking identifier. Page scripts cannot read the cookie. The cookie grants access only to setup connections on the testing app’s origin.
Your choices
We keep no account, profile or game-data copy about you to request, correct or delete. Your saved collection is on your own device and, if you connect it, in your own Drive. A live-game rendezvous stores only short-lived credential hashes, forwards encrypted setup messages without retaining them, and is deleted when ended or after its fixed expiry. Cloudflare's ordinary request logs are covered under Hosting above.
Contact
Questions about any of this: redfoxstudiodeveloper@gmail.com.
Last updated 16 October 2026. This page describes what the app does now; if that changes, this page changes first and this date moves with it.