Privacy: Disaster Movers' game data

Last updated: 4 November 2026

This privacy policy is in German and English. Where they differ, the German version prevails.

1. Controller

Maik Kühne IT-Dienstleistungen (sole proprietorship / small business)
Maik Kühne
Postfach 1103
37171 Nörten-Hardenberg
Germany

E-mail: privacy@kuehne.dev

2. What this is about

The game Disaster Movers sends this service (https://data.api.disaster-movers.com) how it is played and how it runs, so we can make it better. The service is one of its own: it has nothing to do with the website disaster-movers.de, its accounts or game keys, and doesn't know them. We sell no data, give it to no one, show no ads and use no third-party services: the service, its database and the dashboard run on our own server.

3. What the game sends

At its first start the game asks whether you send only the required data or all of it. You can change it any time in the game under Settings > Privacy; there you also find every field in a sentence ("What we send") and what was sent last ("What was sent"). The full list is at the end of this page.

Required data. At each start, every 5 minutes and as the game closes: the game's version, the system, the graphics settings, the window's height as a class, your company's progress in steps; what you did since the last time, as counts (how often you used a tool, petted a cat, looped a swing); and at each job's end, from the crew's host, how the job went (the building, the disaster, the money, the damage, the pieces loaded by their model, the frame rate). This data carries no name and no ID: only a random number the game makes at each start and stores nowhere, so one run's packets belong together. It can't be traced to anyone, us included (Art. 11 GDPR). Legal basis: in the closed playtest's test builds, taking part in the playtest (Art. 6 (1) (b) GDPR); in the Steam version, our legitimate interest in making the game better (Art. 6 (1) (f) GDPR), which you can object to there with "Send nothing".

Optional data ("Accept all"). An ID and your PC's hardware on top (processor, graphics card and driver, memory, system version, refresh rate), so we see how often you come back and how the game runs on your PC. In the playtest the ID is a random number the game makes on your PC; in the Steam version, your SteamID. Legal basis: your consent (Art. 6 (1) (a) GDPR), which you can withdraw in the game any time (Art. 7 (3) GDPR): we then take the ID off everything sent under it at once. Switched on again, your PC gets a new ID.

Performance reports. Only when you send one in the game (F3): the measurements of the last minutes (report.md, frames.csv, timeline.csv), your words about it and, only if you tick them, two screenshots. Before it goes, the game takes your user name out of paths, removes chat lines, IP and e-mail addresses, your PC's and your company's names, and shows you what goes. A report carries no ID. Legal basis: your consent at each send (Art. 6 (1) (a) GDPR).

4. What we don't collect

No names, no chat messages, no e-mail addresses, no location. The service sees your IP address in order to answer, but writes it down nowhere: there are no access logs, and the limit on how often an address may send holds it in memory only, for an hour at most.

5. What the game stores on your device

Your choice (the file analytics.cfg), so the game keeps to it; with "Accept all", the ID too; a list of what the service took from your PC, so you can read and download it; and, until the service has taken them, a withdrawal or a deletion and the performance reports you send (all in analytics/). Storing your choice, the list and what you yourself sent or asked for is strictly necessary for it (§ 25 (2) no. 2 TDDDG); the ID is stored only with your consent (§ 25 (1) TDDDG). All other data not yet delivered the game holds in memory only: it is gone when you close the game.

6. How long it is kept

• Required data: for good; it names nobody.
• The optional data's ID: taken off all data at the latest 15 months after your last session; the data then stays without it. So do counts that name nobody (how many of a month's players came back in later months).
• Withdrawn: the ID at once when the service gets the withdrawal; if it can't be reached just then, the game sends it as soon as it can. "Delete my data": everything under the ID, the same way.
• Performance reports: 2 years, then deleted with their files.
• Backups of the database: 7 days; what was deleted is gone from them with that.

7. Recipients and hosting

No one but us gets the data. The service runs on our own servers, hosted by: Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany (data centre in Germany). The provider processes the data only on our behalf and on our instructions (Art. 28 GDPR). We transfer no data to countries outside the European Union.

8. Your rights

You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18) and data portability (Art. 20). In the game you do it yourself: "Download my data" gives you everything your PC sent and everything we hold under your ID as a zip; "Delete my data" deletes it. We can't trace the required data to you (Art. 11 GDPR); what your PC sent of it is in the download all the same.

Right to object (Art. 21 GDPR). Where we process data on the basis of legitimate interests, you can object any time: in the Steam version with "Send nothing", otherwise by e-mail to privacy@kuehne.dev.

Automated decisions. We use no automated decision-making, including profiling, within the meaning of Art. 22 GDPR.

Right to complain. You can complain to a data protection supervisory authority, in particular in the EU/EEA state of your habitual residence, your place of work or the place of the alleged infringement. The authority responsible for us is: Der Landesbeauftragte für den Datenschutz Niedersachsen (LfD Niedersachsen), Prinzenstraße 5, 30159 Hannover, Germany, lfd.niedersachsen.de.

Data protection officer. We have not appointed a data protection officer.

9. Security

Encrypted connections only (HTTPS/TLS); the database can't be reached from the internet; the dashboard is behind a login and reads only views without an ID; every packet is checked against the list of fields and anything unknown dropped; the size and number of requests are limited.

10. Children

If you are under 16, please ask your parents before you choose "Accept all" (Art. 8 GDPR).

11. Changes and contact

We update this policy when the game or the service changes; the current version is at https://data.api.disaster-movers.com/privacy. A new optional field, the game asks you about anew. Questions about privacy: privacy@kuehne.dev

Every field

This list is the game's own: what isn't in it, the game doesn't send and this service doesn't take.

In everything sent

• packet: Which kind of packet it is.
• session: A random number made at each start and kept only while the game runs, so one run's packets belong together.
• game_version: The game's version.
• build: Which build: the playtest's, Steam's or a developer's.
• list_version: The version of this list.
• at: When it was sent, to the minute (UTC).
• cheated: Whether chat commands ran in this run: such numbers stay out of the totals.
• id: Your ID: one made at random and kept on this PC (on Steam, your SteamID). (only with Accept all)

At each start

• platform: The system: Windows, Linux or macOS.
• language: The game's language.
• preset: The graphics preset (or your own mix).
• render_scale: The 3D resolution's scale.
• msaa: The anti-aliasing.
• vsync: Whether VSync is on.
• window_mode: Windowed or fullscreen.
• window_height: The window's height, as a class: up to 1080, up to 1440, up to 2160, more.
• ultrawide: Whether the window is wider than 2 to 1.
• period: Your company's pay period, in steps (1, 2, 3–5, 6–10, 11–20, more).
• hq_tier: Your HQ's tier.
• jobs_done: The jobs your company has done, in steps (0, 1–2, 3–5, 6–10, 11–25, 26–50, more).
• company_days: Your company's age in days, in steps (0, 1, 2–7, 8–30, 31–90, more).
• abandoned: Whether the last run ended in the middle of a job.
• cpu: Your processor's model. (only with Accept all)
• cpu_threads: Your processor's threads. (only with Accept all)
• gpu: Your graphics card's model. (only with Accept all)
• gpu_driver: Your graphics driver's version. (only with Accept all)
• ram_gb: Your PC's memory, in GB. (only with Accept all)
• os_version: Your system's version. (only with Accept all)
• refresh_hz: Your screen's refresh rate. (only with Accept all)

Every 5 minutes, and as the game closes

• seconds: Seconds since the game started.
• where: Where you are: the menu, the HQ, a job or the orientation.
• online: Whether you play alone, host a crew or are a guest.
• crew: How many are in the crew.
• last: Whether the game is closing.
• counts: Your counts since the last one (below).

What you did since the last one, as counts

• tool: How often you used each tool.
• pet_cat: Cats you petted.
• pet_dog: Dogs you petted.
• bonks: Crewmates you hit on the head with the sledgehammer.
• glued: Times you were glued.
• thrown: Times a crewmate threw you.
• thrown_knocked: Times that throw's landing knocked you over.
• thrown_downed: Times that throw's landing put you down.
• car_hits: Times a car hit you.
• swing_loops: Loops you made on a swing.
• carousel_flung: Times the carousel flung you off.
• ride_seconds: Seconds on each kind of playground ride.
• emote: How often you played each emote.
• beers: Beers you drank at the HQ's bar.
• keeled_over: Times you keeled over from them.
• hq_glass: The HQ's glass smashed, counted by the crew's host.
• arcade: Games you played on each HQ cabinet.

At each job's end, from the crew's host

• profile: The job's kind of building.
• seed: The job's seed, the number its building is made from.
• disaster: The disaster.
• town: The kind of town.
• weather: The weather.
• players: How many players were in the crew.
• bots: How many bots were in the crew.
• period: The pay period, and the job's place in it.
• hq_tier: The HQ's tier.
• seconds: How long the job took.
• end: How it ended: driven off, total collapse, crew wipe or left.
• outcome: What it did to the period: nothing yet, the rent paid, or bankrupt.
• money: The money: value loaded, the bonus, what the customer's list and the ending cut, fines, ambulance fees, the theft, the pay.
• left: The pieces in the building at the start, and the ones left behind and their worth.
• losses: The damage in dollars, pieces broken, walls and floors down, windows smashed, crew members down.
• pieces: Each kind of piece loaded: its model, how many, their worth, whether it was on the customer's list.
• customer_list: The customer's list: its lines, and how many were filled.
• ducks: The rubber ducks found (which ones).
• porsuk: Whether Porsuk's statue came home.
• stolen: The stolen piece's worth, if one was.
• tools: The tools the company owns, how many of each.
• board: The work orders the board offered (their kind and disaster), and which was signed.
• frames: The frame rate over the job: the average, the 1 % low, the worst frame.

A performance report, only when you send one

• code: The report's short code, to name it on Discord. (only when you send a report)
• words: What you wrote about it. (only when you send a report)
• files: The report's files: report.md, frames.csv and timeline.csv, without your user name, chat lines, IP addresses or company name. (only when you send a report)
• pictures: The two screenshots, only if you tick them. (only when you send a report)

When you withdraw or delete

• forget: What to do with what was sent under your ID: take the ID off it, or delete it. (only with Accept all)