01Controller
c/o POSTFLEX PFX-551-949
Emsdettener Straße 10
48268 Greven
Germany
02The short version
There is no account and no email list held here. The game runs in your browser and your saved colonies stay in it. Two things leave your machine while you play: the hosting provider’s own logs and, only if you say yes, measurement: a plain count of how the site is used that identifies nobody, two measurement scripts and a record of each run you finish. A third leaves it only if you send one: a bug report, which is what you typed and, if you tick the box, the colony you were in, and later any answer you send to a question we ask about it. A fourth leaves it only if you play the Challenge: the player name you choose, which is shown on its public leaderboard, a note when each Challenge run starts, and its score and end figures when it ends, so our server can rank it. A fifth only if you play the Academy under your organisation’s licence: the name you type and each run’s result, on that licence’s own board. If you buy the full game, one record exists on our side: the code, the edition, the transaction it belongs to, and the address it was emailed to, kept for as long as the licence exists and joined to nothing about how you play.
03Kept in your browser
Local storage holds your saved colonies, your achievements, the worlds you wrote, a few remembered choices and your answer to the measurement question; the full list is below. None of it is transmitted, with one exception: if you said yes to measurement, the random id your finished runs are filed under goes with each run, as described under Finished runs. None of it has an account behind it, and clearing your browser’s site data removes all of it, as does the button below, which works here without the game running.
Everything Powerstate keeps about you is in this browser, and this is all of it. There is no account behind these and no copy on a server, with two exceptions you choose yourself: if you agreed to it, your finished runs are held by our server under the random id listed below, and if you play the Challenge, your player name and the Challenge runs you play are held there too, as the privacy page describes. Clear these and this browser has forgotten you.
powerstate.save.slot.*your saved colonies, up to five, in this browser onlypowerstate.saves.v1the names of those saves and which one you are playingwattmark.save.v1a run saved by an older version, kept only until it is moved to a save slotpowerstate.gate.dismissedthat you chose to play on a small screen anywaypowerstate.tour.sentthat a small screen has already been shown the gameplay page oncepowerstate.consent.measurement.v3this consent decision, so you are not asked againpowerstate.install.v1a random id your finished runs are filed under, only if you agreed to thatpowerstate.runlog.v1your own finished runs, so the end screen can compare them, in this browser onlypowerstate.commendations.v2which achievements you have been awarded, per world, in this browser onlypowerstate.commendations.v1the same record in its old shape, kept only so this button can erase itpowerstate.scenarios.v1the scenarios you wrote in the editor, in this browser onlypowerstate.lesson.opened.v1that you have opened the lesson, so the console stops holding the worlds shutpowerstate.units.v1that you picked metric or US units yourself, written only if you overrode the guesspowerstate.lang.v1the language you picked for the game, written only if you overrode the guesspowerstate.posts.v1which update posts you have read, so the start screen stops pointing at thempowerstate.windows.v1where you moved the windows to, written only once you move onepowerstate.sound.v1whether sound is on, and how loud the room and the desk arepowerstate.tooltips.v1how long a tooltip waits before it stays in place, and the key that holds it, written only if you changed thempowerstate.framerate.v1how many times a second the map is drawn, written only if you changed itpowerstate.renderer.v1which renderer draws the map, written only if you changed itpowerstate.challenge.player.v1your Challenge name and the key that lets this browser post runs under itpowerstate.challenge.entries.v1the Challenge runs you sent, and any waiting to be sentpowerstate.challenge.save.v1*your Challenge run, saved apart from your colonies, in this browser onlypowerstate.bugreplies.v1a random key for each bug report you sent, so the game can show you our questions about it
Your saved colonies are included, and cannot be recovered afterwards.
A code bought in this browser is left in its local storage by the page the checkout returns to, so the game can enter it for you, and the game removes it once it has. If you activate a code, two further items are stored: the signed activation itself and a random device identifier it is bound to. They are deliberately not part of the erase button above, because removing them would spend one of your three device slots without telling you; an activated copy hands its slot back from Your code in the game’s menu. The device identifier is minted at activation, describes nothing about your machine, and is kept apart from every identifier the game may record runs under.
If you play the Challenge, three more items are stored: your player name with the key this browser made for it and the random player id our server gave it, a note of the Challenge runs you finished and any still waiting to be sent, and your Challenge run itself, saved apart from your colonies. The key is the one item on this list that is transmitted: it goes to our Challenge service when you choose a name, when a run starts and when it ends, as proof the name and the run are yours. A Challenge run’s save holds the ticket our server gave the run when it started, which goes back with the finished run. The button above removes all three. After that this browser can no longer change that name or send runs under it; the name itself stays on the leaderboard until the retention below ends, or until you ask for it to be deleted.
Storage strictly necessary to provide a service you explicitly requested is exempt from consent under Art. 5(3) ePrivacy Directive and §25 Abs. 2 TDDDG. It is disclosed here rather than negotiated in a banner.
04Hosting
The site is hosted by Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, USA. Serving a page necessarily processes your IP address and request metadata. Legal basis: Art. 6(1)(f) GDPR, our legitimate interest in operating a reachable website. Transfers to the United States are covered by the EU Standard Contractual Clauses and Vercel’s certification under the EU-US Data Privacy Framework.
05Counting how the site is used, only with consent
If you say yes to measurement, a small number of counts are kept. Nothing is written to your device for them. Each page load is given a random number that is held in memory for as long as the page is open and then lost, so reloading this page makes you a different one and there is no way to recognise you on a second visit, or on a second page. If you have not said yes, or said no, nothing is counted, and these pages count nothing unless you said yes inside the game.
Nine things are counted, and this is the whole list:
- a page was opened, with which page it was, whether the link came from this site, from an AI assistant such as ChatGPT, from elsewhere or from a phone that sent it on, which of five size bands the window fell into, and whether your browser asks for reduced motion
- which card of the gameplay tour was on screen, and for how long
- how far through the tour someone got before leaving, and how long they stayed
- which of the three links out of the tour was clicked, and whether its link was sent on to a computer
- a run was begun, in which world, and what kind of run it was: scored, sandbox, the lesson, the Challenge or a world you wrote
- the years a run reached, up to twenty and then every tenth, in which world, and whether it was running free, and whether a code is active in this copy
- a code was entered in the game, from which panel, and for which edition
- a panel offering the full game came up, which one, and at the end of the free years the colony’s year
- a checkout was opened in the game, and whether it was then paid, closed or failed, from which panel, for which edition, and how long after it opened. Nothing you type into the checkout reaches these counts
Every count also carries the version of the game. The counts are stored in our database at Supabase, hosted in the EU, as our processor.
What none of these counts records: your IP address, the page address you came from, your browser’s user agent string, and any free text of any kind. The referrer and the address of this page are read in your browser to decide one of eight words, such as whether you came from one of our ads, and neither is ever sent. The exact width of your window is turned into a band for the same reason. The one place free text does reach us is a bug report, which happens only when you write one and press send; it is described below.
Legal basis: Art. 6(1)(a) GDPR (your consent), together with §25 Abs. 1 TDDDG, because the window size, the motion preference and the referrer are read from your browser. If your browser sends a Global Privacy Control signal or a Do Not Track header, none of it happens at all, whatever you answered. Consent can be withdrawn at any moment under Settings in the game’s menu. The individual counts are deleted after ninety days. The daily totals they are rolled into contain no identifier of any kind and are kept.
06Measurement, only with consent
If, and only if, you accept, two Vercel scripts run as well: Web Analytics, which counts the page view, and Speed Insights, which reports how quickly the page rendered on your device. Both are cookieless. Neither builds a profile, follows you across sites, or feeds any advertising.
Between them they record the page, the referrer, a coarse country, the class of device and browser, and page-load timings. The visitor identifier is derived from the request and rotated daily, so nothing links one day to the next.
Legal basis: Art. 6(1)(a) GDPR (your consent), together with §25 Abs. 1 TDDDG. Decline and neither script is fetched, so there is nothing left running to opt out of. Consent can be withdrawn at any moment under Settings in the game’s menu; withdrawal takes effect on the next event rather than the next visit, and does not affect the lawfulness of what was processed beforehand.
07Finished runs, only with consent
The same yes also lets the game record each scored run you finish, when its end screen opens, so the end screen can show where a run sits among everyone else’s and so the game can be balanced against real play. The lesson, sandbox runs, worlds you wrote yourself, Challenge runs and Academy runs are never recorded this way.
What is sent is what your end screen already shows: the world and its difficulty, how the run ended, the score and grade and what they were made of, the years played, warming, renewable share, carbon intensity, emissions, days of blackout, the tariff, hardship, industry lost, cash, programmes finished, and the version of the game. With it goes a random id your browser makes the first time it records a run and keeps in its local storage, so that runs from the same browser share it. The id carries no name, no address and no purchase, and is joined to nothing else we hold.
Runs are stored in our database at Supabase, hosted in the EU, as our processor. What anyone can read back is only the totals made from them, per world. Legal basis: Art. 6(1)(a) GDPR (your consent), together with §25 Abs. 1 TDDDG, because the id is stored in and read from your browser. Withdraw consent under Settings in the game’s menu and no further run is recorded.
08Bug reports
The game has a button marked Bug report. Nothing is sent by it until you write something and press send, and nothing about it is switched on for you in advance.
What arrives is this, and this is the whole of it:
- what you typed, up to five hundred characters
- the version of the game, and whether the copy you are playing is the one we published
- which world you were in, what year of it you had reached, and which phase
- a block of figures about the run: the seed the map was generated from, the difficulty, the money and the debt, the score, how many settlements there are, a count of each kind of asset and circuit you had built, how many development programmes were finished and which was running, the seven operating dials, and whether this was a sandbox run or the lesson
There is no account, no email address, and no identifier for you, so nothing here follows you between runs, between colonies or between visits. One thing is worth stating plainly rather than glossing: two reports sent from the same colony carry the same map seed, so they can be recognised as coming from the same run. That is a property of describing a game state accurately, and it says nothing about who you are.
So that we can ask you about a report, the game makes a random key for each report it sends and keeps it in your browser’s local storage. The report carries only a code calculated from that key (its SHA-256), which cannot be turned back into it. When you next open the game in that browser, it shows the key to our server, which answers with any questions we asked about that report, and you can answer them from the same form, with your colony attached if you choose. Each report has its own key, so the keys do not link your reports to each other. The questions and your answers are stored with the report. “Erase everything stored” deletes the keys, after which the game can no longer show our questions; the reports themselves stay, as below.
You can also tick a box to attach the colony you are playing. That is the same kind of file the export button on the saved games screen writes, minus its charts and its ledger: the map, your assets, the money and the clock. The only words in it are any names you have given your own machines, and, if you wrote the world yourself in the scenario editor, its name, its tagline, its briefing and its world code. The name you gave the save on the shelf is not among them, and neither is the lesson, which cannot be attached at all. The box starts empty and the form says all of this beside it.
The form also asks you not to put your name, your email address or anything else about you into the message or an answer, because there is nothing here that needs it. For a conversation, write to info@powerstate-game.com.
Reports are stored in our database at Supabase, hosted in the EU, which acts as our processor and does nothing with them but hold them. They go nowhere else: no ticketing service, no mailing list, no third party of any kind.
Legal basis: Art. 6(1)(f) GDPR, our legitimate interest in being told that our own software is broken, and Art. 6(1)(b) where fixing it is part of providing the game to you. §25 Abs. 1 TDDDG does not apply: nothing is stored on or read from your device to send one.
09The Challenge
Nothing about the Challenge is sent unless you play it. If you do, this is what our server receives, and this is the whole of it:
- the player name you choose and whether the leaderboard shows it in full, with a random key your browser makes for it. Our server keeps a one way hash of the key, never the key, and gives your browser a random player id
- if your copy is unlocked with a game key, that game key and the id of the device it is unlocked on, to check the key. Our server keeps a one way hash of the game key with your name, never the game key itself
- for each Challenge run, the time it started and, once it ends, the score and grade, how it ended, the score at the end of each year, the end figures (renewable share, citizens supplied, peak population, cash, debt, days of blackout, carbon intensity) and the version of the game
- a salted hash of your IP address with the time of each request, to limit how often names can be tried and runs sent. The address itself is not stored
It is used to rank your runs and for nothing else. Your best result is shown on the public leaderboard under the first two letters of your name, or under your full name if you choose to show it. A name chosen before 23 October 2026 is shown in full until you change that. Your player id and your key are never shown, and the player id is not linked to anything else the game records. If you play with a game key, your player is linked to the hash of that key, and it is used only to keep your name yours on every device where you enter the key.
You can change your name, choose whether it is shown in full, or remove it in the game at any time: open the Challenge and choose Change name. Removing it deletes your name and every run under it at once, and takes them off every leaderboard.
Before a name is stored, the name alone is sent to the moderation service of OpenAI, L.L.C. (USA), acting as our processor, to check that it is not offensive. OpenAI does not use it to train its models. The transfer to the United States is covered by the EU Standard Contractual Clauses.
Names, runs and leaderboards are stored in our database at Supabase, hosted in the EU, as our processor. Legal basis: Art. 6(1)(b) GDPR, because playing a Challenge run is asking us to rank it, and Art. 6(1)(f) for the address hashes, our legitimate interest in keeping the leaderboard free of abuse. How long each is kept is set out under Retention.
10The Academy
The Academy is a course we license to organisations, played at /academy/ with a login and password the organisation receives from us. Nothing about it is sent unless you sign in to it. If you do, this is what our server receives and keeps:
- for the organisation: its login, a one way hash of its password, its name as the board shows it, when its licence ends and when it last signed in
- for each browser signed in: a one way hash of a random session key, kept for twelve hours. The key itself stays in that browser tab and is gone when the tab is closed
- for each run: the name you type before it starts, when it started and, once it ends, the score and grade, how it ended, the score at the end of each year, the end figures (renewable share, carbon intensity, energy delivered, unserved and thrown away, average price, affordability, cash, debt, peak growth), the style of play the debrief named and the version of the game
- a salted hash of your IP address with the time of each sign-in attempt, to stop passwords being guessed. The address itself is not stored
Runs are ranked on the board of the licence they were played under, which only people signed in to that licence can see, and are used for nothing else. The name you type is yours to choose: it need not be your real name. The Academy page uses no analytics and no measurement scripts, and writes nothing to your device beyond the tab’s own session.
Licences, sessions and runs are stored in our database at Supabase, hosted in the EU, as our processor. Legal basis: Art. 6(1)(b) GDPR, the licence agreement with your organisation and your asking us to rank your run, and Art. 6(1)(f) for the address hashes, our legitimate interest in keeping licences safe from password guessing.
11Payments
Purchases are handled by Paddle.com Market Ltd, which sells the software to you as merchant of record. Paddle collects the payment and billing details it needs and is the controller for them under its own privacy policy; those details are not passed to us in full. We receive what is necessary to fulfil and support the order: the fact of a purchase, its code and edition, and the contact address you bought with. Legal basis: Art. 6(1)(b) GDPR, performance of the contract.
The email that delivers the code is sent through Resend, Inc. (USA), acting as our processor; it handles your address for that delivery and nothing else. Activating the code sends the code and a random device identifier to our licence service, hosted on Supabase, so the three-device limit can be enforced. Transfers to the United States by both are covered by the EU Standard Contractual Clauses. Legal basis for each: Art. 6(1)(b) GDPR, performance of the contract.
12Your rights
Under Art. 15–21 GDPR you may request access to your data, a copy of it, correction, deletion or restriction, object to processing based on legitimate interests, and receive your data in a portable form. Where processing rests on consent you may withdraw it at any time. Requests go to info@powerstate-game.com.
In practice the answer to “what do you hold about me” is short: unless you have bought something, nothing that identifies you exists here at all. That is also why a bug report cannot be looked up by who sent it — there is no identifier on one — so if you want yours deleted, quote roughly what you wrote and roughly when, and it will be.
If you agreed to run records, the finished runs filed under your browser’s random id are held too. To have them deleted, write to info@powerstate-game.com with that id: it is the value of the powerstate.install.v1 entry in this browser’s local storage.
If you play the Challenge, the name you chose and the runs sent under it are held too. To have them deleted before the retention below ends, write to info@powerstate-game.com with the name, and they will be.
If you play the Academy, a run can be taken off your organisation’s board and deleted on request: write to info@powerstate-game.com with the organisation and the name you played under.
You also have the right to complain to a supervisory authority, which in Germany is the data protection authority of the federal state in which you live.
13Retention
The individual usage counts described above are deleted after ninety days by a scheduled job. What survives is a table of daily totals with no identifier in it, which is kept for as long as the site runs. Data from the two consented scripts is aggregated and retained by Vercel under its own retention windows.
A colony attached to a bug report, or to an answer, is deleted from the database by a scheduled job thirty days after the report is marked solved, and after ninety days whatever state it is in. The report itself is kept, with the questions and answers on it: it is a few hundred bytes, it has no identifier for you on it, and it is the record of what was wrong with the game. Where a colony has to be opened to reproduce a fault, the working copy of it is deleted once the fault is fixed.
Finished run records are deleted by a scheduled job two years after they were recorded, and yours sooner on request.
Challenge runs and everything sent with them are deleted by a scheduled job twelve weeks after the Challenge they were played in ends. A Challenge’s leaderboard, which carries the names and scores of its top hundred, is deleted a year after that Challenge ends. A player name is deleted, with every run under it, a year after it was last used to choose a name or play a Challenge run, or at once when you remove it in the game, and the IP address hashes after two days.
An Academy session is deleted a day after it expires, a run that was started and never finished after two days, and the IP address hashes after two days. A licence’s board, with every run on it, is deleted a year after the licence ends, or sooner if the organisation asks.
A bought code, its edition and the address it was sent to are kept for as long as the licence exists, because activating it on a new device and sending it again both need them; if you ask for them to be deleted, the code can no longer be activated anywhere new. The devices holding a slot are kept with the code. The log of activations, releases and codes sent again is deleted by a scheduled job after two years. The sale itself is recorded by Paddle as merchant of record, and our own accounting records are kept for as long as German commercial and tax law requires (§257 HGB, §147 AO).