Privacy

Short version: no accounts, no ads, no cross-site tracking. The simulator runs in your browser.

What stays on your machine

Your saved plant states and training progress live in your browser's local storage and are never uploaded.

Page views

An anonymous page-view count, processed by Cloudflare, who host this site. It records the page address, the referring link, and coarse device info (country, device type, browser, OS).

It sets no cookies, stores no identifier on your machine, and does not build a profile of you or follow you to other sites. If your browser blocks it, everything works the same and the visit simply is not counted.

Cloudflare only keeps this in detail for a week, so once a day we copy out a daily total — how many page views came from each country, referring link, page, device, browser and operating system on that date — and keep those totals for two years. They are counts and dates only: there is nothing in them that is one person, no address, and no way to follow a visit from one day to the next. We keep them so we can tell whether the site is growing, which is not a question a seven-day window can answer.

Usage data in the simulator

The simulator sends anonymous usage data while you use it.

Almost nobody sends feedback, so this is the only way to find out which parts of the plant are confusing. What it sends is counts, and how long things took:

• which plant and starting condition you chose, which build you are on, and how long the session ran
• the names of the controls you use — never the values you set them to — and whether the plant refused one
• which panels you open, and which one you were on when you left
• how far through a startup you get (the plant mode the engine reports), and whether the plant went on the grid, scrammed, or was damaged
• which training missions you start, finish, or leave, and how far into one you got
• which walkthrough you are following, which step you are on, how long each step took, whether the step checked itself off or you ticked it by hand, when you rewind a step, and where you were if you stopped part way through

Each of those carries the time it happened, measured from when the page opened — enough to put one visit's actions in order and see where the time went, and not tied to a clock or a calendar date.

It does not send any text you type, any plant recording, or anything about your machine beyond what a web request unavoidably reveals. It carries an identifier that lasts for one visit and is discarded when you close the tab, so two visits cannot be linked together. There is no account, no profile, and no advertising of any kind.

The exact list of what can be sent is site/telemetry.js in the source code, which is published under the AGPL — you do not have to take this page's word for it.

Bug reports you send

The Contact panel in the simulator can send a report with a recording of that session attached: plant readings, alarms, and the commands you issued, so what you saw can be replayed. It also carries whatever you type in the message box.

This is sent only when you press send, and it is separate from the usage-data setting above — turning usage data off does not stop you reporting a bug, and leaving usage data on never sends a recording on its own. You can untick the attachment to send only your message, or download the recording and inspect it before mailing it yourself.

Every report also carries which build and which of our three sites sent it — so a report from the test site is not mixed up with one from the released game. Nothing else about the request (your IP, browser, or any other header) is attached.

If you write to [email protected] instead, you choose what to include. Mail is used only to reply; it is not sold or shared for advertising.

The offline download

The single-file download contains none of this. The usage-data code is not merely switched off in it — it is not in the file at all, so an offline copy has nothing to send and nothing to send it with.

Contact

Privacy questions: [email protected].