This policy describes which personal data are processed when you visit the website and play ZeroDayEmpire: for what purpose, on what legal basis, for how long and who receives them. The policy applies to all visitors and players. It is based on the General Data Protection Regulation (GDPR, German: DSGVO), the German Federal Data Protection Act (BDSG) and the German Telecommunications Digital Services Data Protection Act (TDDDG).
- We process your data in order to provide the game, to protect accounts and servers and to clarify rule violations.
- Website, game and database run at Hetzner in Germany. No external content delivery network is placed in front of them.
- You can delete your account yourself in the settings. Send requests and questions informally to impressum@stieg.tech.
- You can object to processing based on legitimate interests (§ 13).
Controller and contact
The controller responsible for the processing is:
Maximilian Stieg
c/o IP-Management #47083
Ludwig-Erhard-Straße 18
20459 Hamburg, Germany
Phone: +49 15678 500738
Email: impressum@stieg.tech
In this policy, “we” refers to the controller. For all questions and requests concerning data protection, you can reach us informally at this email address or by post (procedure in § 13).
No data protection officer has been appointed. The game is operated by a single individual; there is no obligation to appoint one under Art. 37 GDPR and Section 38 BDSG.
Hosting, systems and recipients
- Live server: Website, game and database run on a server of Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, in Germany (Hetzner’s privacy policy). Hetzner processes the data on our behalf; a data processing agreement pursuant to Art. 28 GDPR is in place. On the same server, a reverse proxy accepts the encrypted connections and forwards them to the game.
- Email: We send account emails via our own mail server, which the controller runs personally on a Hetzner server in Germany. The mailbox for support and data protection requests is also located there.
- Backups: Encrypted database backups are stored on the live server and as a copy on the controller’s own hardware. For testing, a backup is briefly decrypted on an isolated system and deleted immediately afterwards. In addition, Hetzner, as processor, backs up the entire live server, i.e. database, logs and keys (§ 12).
- Test system: The test system, which can only be reached internally, contains exclusively test accounts and test data. Data from the live game only reaches it as an encrypted backup.
The only recipients of your data are:
- Hetzner as processor (hosting),
- your email provider, when we send you an account email,
- other players, insofar as game functions display data (§ 05 to § 07),
- moderators and administrators of the game within the scope of § 09,
- authorities, if we are legally obliged to do so in an individual case.
We do not sell any data. A transfer to countries outside the EU and the EEA takes place, if at all, only through your own email provider.
Server and error logs
Every request to the website passes through the reverse proxy and the web server. This creates logs:
- Reverse proxy: full IP address, time, method, host and path without parameters, status code, amount of data, browser identifier (user agent) and previously visited page (referrer). Error logs of the proxy may contain the full requested address and technical error details. Deletion after 7 days from the access.
- Web server: time, shortened IP address (IPv4 without the last block, IPv6 only the first 48 bits), method, path without parameters, protocol, status code, amount of data and processing time, without browser identifier and referrer. The error log of the web server contains the full IP address and, where applicable, the full address. Deletion after 7 days from the access.
- Error log of the game: time, error reference, user ID (if logged in), shortened IP address, method, path without parameters and technical error details. Deletion after 14 days from the entry.
Purpose and legal basis: delivery of the pages, error analysis and defence against attacks such as overload or password attacks. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is secure and trouble-free operation (Recital 49). The logs are not displayed in the game and are not combined into profiles. Only extracts that we need to investigate a specific security incident are kept longer, until the incident has been concluded. In addition, an automated evaluation records error messages from these logs in cleaned-up form (without IP and email addresses and without access credentials) as tasks in our self-hosted ticket system; we delete these entries 3 months after the task has been completed.
Game account, registration and account emails
When you register, we process your player name, email address, password, the selected country, the time of registration and the time of your confirmation of the minimum age (no date of birth). We only store the password as a bcrypt hash. Until you confirm your address, the details are kept in your session (§ 08) and in a reservation without a readable email address. The confirmation link and the reservation expire after 24 hours.
The checkbox for the privacy policy only confirms that you have taken note of this policy. This is not consent; the confirmation is not stored.
In the account, we additionally store your settings (such as permission for the activity display, filter profiles, absence note when the inbox is full, mail signature) as well as the times of your last login, last action and last session check. We need these times for game processes and for deleting inactive accounts. The language of the public pages (German or English) follows from the address of each request (for example /en-privacy or lang=en). For the game pages, we take over the language of the login page when you log in; you can change it in the settings. It is only kept in the session (§ 08) and ends with it; we do not store it in the account or in a cookie.
Email address: The address is stored in encrypted form; a check value formed with a secret key is used for searching and uniqueness. We only use it for account emails:
- confirmation of the registration,
- link to reset the password, valid for 1 hour,
- change of address: confirmation link to the new address, valid for 24 hours, and a security notice to the previous address,
- a notice after an administrator has reset your two-factor authentication (§ 09),
- a notice to the address if it is entered for another registration although an account or an unconfirmed registration already exists for it: without a confirmation link and without details about the person making the request, at most 1 notice per hour,
- confirmation of a deletion request and notices before deletion due to inactivity (§ 12),
- replies to your requests.
We do not send newsletters or advertising emails. Account emails are kept encrypted in a queue until they are sent and are deleted immediately after sending, at the latest when the link they contain expires. After several unsuccessful delivery attempts, the content is dropped; technical diagnostic data remain for at most 24 hours.
Beta waiting list: As long as registration is closed, you can put your email address on the waiting list. Its only purpose is to invite you to the beta once by email: no advertising, no disclosure, no link to a game account. We store the address in encrypted form, together with a check value formed with a secret key (separate from the one used for accounts), the language for the emails, check values of the links and the times of sign-up and confirmation, but no IP address. You are only on the list once you open the link in the confirmation email and confirm there (double opt-in). We delete unconfirmed entries after 24 hours and confirmed entries when the invitation is queued, at the latest 180 days after confirmation. Each of these emails contains an unsubscribe link that deletes the entry immediately; the emails go through the encrypted queue like account emails. If an address is entered again, it receives a new confirmation link or a note that it is already on the list, at most 1 email per hour. The website never shows whether an address is already on the list. Invitations and information requests are handled with a tool on the server that does not display addresses. By signing up you confirm that you are at least 16 years old; we do not store this confirmation. The legal basis is your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time with effect for the future, most easily via the unsubscribe link.
Minimum age: ZeroDayEmpire is for people aged 16 years and over. You confirm your age when registering; existing accounts are asked once. If you are younger, please do not register.
The legal basis is Art. 6(1)(b) GDPR (user agreement for the game). Player name, email address, password and age confirmation are required for the agreement; without them we cannot create an account. You are not legally obliged to provide us with data. We store account data until the account is deleted (§ 12).
Game operation, profiles and visibility
To let you play, we store your game data: servers with their in-game, entirely fictitious IP address, upgrades, research, balance (CC), inventory, points and ranks, attacks, reconnaissance and target dossiers, bounties, daily tasks, weekly contract, NetWars, world events (raids) with your contributions, PvE campaign and attacks on NPC targets (with a daily counter of your NPC loot), the breach minigame (number of puzzles started today and failed attempts) and a preview remembered in the practice simulator (attack type, server, time) as well as achievements. We delete these daily counters and the remembered preview after 3 days at the latest. The legal basis is Art. 6(1)(b) GDPR.
Visible to other logged-in players are:
- your profile: player name, points, leaderboard position, collective with its tag and your rank in it, servers with game IP and registration date,
- search results, the terminal query
whoisand the leaderboard (calculated every 3 hours from the server upgrades), - the NetWars weekly ranking: in the current week the best 50 players with name and points, for the last 12 weeks places 1 to 3,
- the leaderboards of world events (raids) with name, collective, damage and number of attacks of the best players as well as the best collectives, also for past events until the end of the period in § 12,
- the subnet list: for each server the game IP, server name and points, plus the owner with their points and their collective,
- texts that you post yourself for others.
Visible without logging in are, on the home page, only the name of the first-placed player once at least 10 players have points, and the number of players online once there are at least 5. We do not show a number of registered players.
Activity: No other player sees your online status, last login and “last active” unless you permit this under Settings → “Activity for others”. You can withdraw the permission there at any time with immediate effect. Without the permission, only the collective leadership with the rank Root sees in the member management whether you were active in the last 14 days, without the time.
Battle archive: Other players do not see your battle archive. Exception: terminal attacks on player targets are also visible for 48 hours to the collective leadership with the ranks Root, Co-Administrator, Warlord and Sentinel, namely in the attacker’s collective and in the collective of the attacked player. Displayed are the time, type of attack, result and the names of the players involved; for attacks on members, the attacker only appears if they were detected. Costs, loot, bounties and IP addresses are not visible.
Game logs: We log attacks, transfers, purchases and other game events in the game and transfer log. The purpose is to ensure fair game conditions and to investigate complaints and abuse, such as unauthorised multiple accounts, balance shifting or bots. The legal bases are Art. 6(1)(b) GDPR and (f) (legitimate interest in fair play and in clarifying rule violations). The entries are deleted after 12 months; if your account is deleted, they lose any reference to you before then.
Server takeover: If another player takes over your server in PvP, the server passes to them with its game IP; the server name and label you assigned are reset in the process. We store the takeover event (server, previous and new owner, time) and the settlement (refunds and credits in CC). If it was your last server, a recovery claim is created with a private snapshot of your research level, which you can use to set up a replacement server; other players do not see it.
Further periods for individual game functions are listed in § 12.
In-game messages, reports and support
In-game mails: We store sender, recipient, time, subject, text, read status and folder, as well as your address book and your signature. Subject and text are stored encrypted in the database (§ 08). Each mail consists of one copy for the recipient and one for the sender; if you delete your copy, the other side keeps theirs. Maximum numbers: inbox 200 (after that, new mails are rejected and the sender may see your absence note), archive 250, outbox 100 (the oldest are deleted automatically). System messages are deleted after 90 days, read or unread; of the read ones, in addition only the newest 15 messages are kept, unread ones are never deleted because of their number. If an account is deleted, both copies of its mails are removed. The legal basis is Art. 6(1)(b) GDPR.
No insight without a report: Moderation and administration have no view of in-game mails in the game. They only see a mail if the recipient reports it.
Reporting a mail: When reporting, you choose a reason and can add a comment. A separate, encrypted copy with subject, text, sender, time, reason and comment is created for the moderation. Moderators only open it with a justification, which is logged (§ 09). Whoever sent or reported the mail does not open the report. Mails of an administrator (Root) are only reviewed by another administrator. The reporter and the sender receive a system message about the decision; we do not tell the sender who reported them. If nobody can review the report impartially, we do not accept it and refer you to support. If it has already been stored, we close it without review after 14 days and only inform the reporter. The copy is kept until the decision or until this closure and thereafter for 6 months. If one of the accounts involved is deleted, we remove its name and identifier from the copy; the content remains until the end of the period.
“Report a rule violation” form and support: The public form sends your name (optional), the reported name and your text by email to our support mailbox. To prevent abuse, the number of reports per IP address is limited (§ 08). We delete support emails and reports 6 months after the matter has been concluded.
Rule violations: If a report leads to a measure such as a suspension, we keep the extracts required for the decision for 2 years after the case has been concluded, and in the event of a complaint or legal dispute until its end.
The legal bases for reports and moderation are Art. 6(1)(b) GDPR (game rules) and (f) (legitimate interest in protecting the players, in enforcing the game rules and in defending against claims).
Collectives and collective forum
In a collective, we process membership (with the time of joining) and rank, applications for admission with comment, pinboard, forum (C-Board) with topics, posts and read markers, event log, donations in CC, tax list, funding goals, diplomacy, collective ops and weekly contract. Titles and texts in the forum are stored encrypted in the database; author, time and folder are not.
- The members of the collective see the forum, pinboard, events and finances, partly depending on their rank. The donor list of the collective shows all members the name, active title, total donations and number of donations of the top donors. The member list with names, ranks and points as well as the info page maintained by the leadership are also visible to other logged-in players.
- You can edit your own forum posts for 30 minutes; the post then shows an edit note. You can delete your own posts, but only the leadership can delete the opening post of a topic with replies from other members. Forum posts remain until their author or the collective deletes them or the collective is dissolved.
- Read markers: for each topic we store when you last opened it, only to mark unread posts. These read markers are removed when you leave or are expelled, when the topic is deleted or the collective is dissolved, and with your account.
- Of the event log, the last 20 entries are kept; we remove older ones with every new entry.
- Unanswered applications for admission expire 30 days after the application. You see the expiry and can apply again.
- If you leave or your account is deleted, your posts remain available to the other members. After an account deletion, you only appear there and in events as “deleted account”; names that others have freely written into texts remain.
- If you are the last leader of a collective with further members, you must transfer the leadership before a deletion request. In the case of deletion due to inactivity, it passes automatically to the highest-ranking member; the members only learn who the new leader is.
The legal basis is Art. 6(1)(b) GDPR.
Account security, session and encryption
- Login log: With every successful login, we store a check value formed from your IP address with a secret key (no readable IP address), the user ID and the time, in order to detect unauthorised access and account takeovers and to investigate unauthorised multiple accounts. The entries are not displayed in the game and are deleted 30 days after the login, immediately if the account is deleted.
- Failed attempts: With every login attempt, we store a separate check value of your IP address (for IPv6, of the network range), the identifier of the target account (without the name entered) and the time; a successful login removes its entry. After 5 failed attempts within 15 minutes, we block further attempts from this IP address, and after 50 failed attempts within 15 minutes we block the account for password logins. Deletion after 24 hours.
- Further abuse limits apply to registration, the beta waiting list, password reset, the report form, privacy settings and game actions. In addition, per account: at most 5 confirmations with your current password in 15 minutes when changing your password or email address and when deleting your account, and at most 3 requests for a new email address per hour. The counters are normally kept only in memory and expire after one hour at the most; otherwise we store them as a check value without a readable IP or email address and delete them after 24 hours.
- Session: After login, the server stores for your session cookie (§ 11) the account and server identifier, the language of the game pages, a security token against form abuse (CSRF), a check value of your browser identifier and time stamps, but no IP address. During registration, it also holds the player name, email address, password hash and country until confirmation. After the password check at login, it also holds the password hash of your account so that the next step only matches this login: until you enter the second factor (valid for at most 5 minutes) or, if a deletion of your account has been requested, for cancelling it (valid for at most 10 minutes). It is deleted after the step, when you log out, when you log in again or together with the session data at the latest. If the game rejects a form entry (for example a server name, notes of a target dossier or collective texts), your entry stays there until you open or submit the form again so that you can correct it; it is deleted when you log out, when you log in again or together with the session data at the latest. It also briefly holds feedback on your last action and intermediate states of ongoing game actions. The login ends after 30 minutes without activity, at the latest after 24 hours. The session data on the server are deleted automatically 25 hours after the session was last used.
- Two-factor authentication (optional, mandatory for moderation and administration): If you turn it on, we store with your account the secret of your authenticator app in encrypted form, the time of activation, the last 30-second interval used (so that every code works only once) and your recovery codes only as check values. Our server generates the QR code for the app itself, without any external service; through it the app only receives the secret, the name of the game and, as the account label, the fixed text “ZeroDayEmpire”, not your player name. Apps set up earlier may still show your player name there. To change this, rename the entry in your app; the codes remain valid. A setup that was started but not completed is deleted after 15 minutes. Per account we check at most 10 codes in 15 minutes. When you turn it off, when an administrator resets it (§ 09) and when your account is deleted, we delete all of this data.
- Security keys and passkeys (optional, as a method of two-factor authentication): If you register a security key or a passkey, we store with your account its identifier, the public key, a signature counter, the name you chose and the time of registration and of last use. The secret key and any PIN, fingerprint or face image used for confirmation stay on your device; we do not receive them. During registration, your device receives the name of the game, the address of the website, a random identifier with no link to your account and, as the account label, only the fixed text “ZeroDayEmpire”, not your player name; depending on the device or passkey provider, these details are stored with the key or passkey. If you synchronise passkeys via a provider (such as a password manager), these details are also stored there. Keys registered earlier may still show your player name there; to change this, remove the key in the settings, delete the entry on your device or with the provider and register it again. We do not request information about the manufacturer or model of the device. The one-time random number for each request is valid for 5 minutes and is only kept in your session, together with the chosen name while a registration is in progress. After that we remove it with your next page request, at the latest together with the session data (see above). Every attempt counts towards the same limit as the codes. When you remove a key, when an administrator resets two-factor authentication (§ 09) and when your account is deleted, we delete this data.
The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is the protection of your account, the game servers and fair play (Recital 49). For the session itself, Art. 6(1)(b) GDPR also applies. For mandatory two-factor authentication for moderation and administration, Art. 32 GDPR (security of privileged access) also applies.
Encryption: The connection to the website is encrypted via HTTPS. We only store passwords as a bcrypt hash, and links and tokens for account functions only as a hash. Your email address, subject and text of in-game mails and reported copies, titles and posts in the collective forum, your mail signature and the secret of two-factor authentication are stored encrypted in the database. The keys are neither in the database nor in our database backups; the server backup at Hetzner (§ 12), however, contains the database and the keys together. Our database backups are also encrypted.
This is not end-to-end encryption: the server decrypts the contents in order to display them to you and to authorised recipients. The encryption mainly protects database copies and our database backups, not against someone who obtains the web server or a complete server backup with the keys. The check values are not an anonymisation method: with the key, a known IP address can be recognised. Backups from the time before the introduction still contain the fields mentioned and IP addresses in plain text until they are deleted.
Access by administration and moderation
The game has the roles moderator and administrator (Root). Only administrators see email addresses, moderators do not.
- Only with a justification: Moderators and administrators only access personal data in the admin area (editing accounts, servers and collectives, collective forums, reported mails, fair play cases, transfer overview, list of inactive accounts, data export for access requests) after they have entered a justification.
- Access log: We store the time, role and identifier of the person accessing the data, the object concerned and the justification, but no contents. The purpose is to be able to control privileged access and to inform you on request about the time and purpose of accesses. Deletion at the end of the calendar year following the access.
- Account suspension: In case of rule violations an administrator can suspend an account, indefinitely or for 3 to 30 days. For a temporary suspension we store its end and a fixed reason from the game rules (for example multi-accounting) with the account; you see both when you log in. When it ends, the game lifts the suspension automatically and deletes the end and the reason stored with the account, at the latest after 30 days. Independently of this, the suspension with its duration, end and reason is recorded under admin actions in the game log (item after next).
- Resetting two-factor authentication: If you have lost your app and your recovery codes or your security keys, an administrator can reset two-factor authentication for your account at your request and with a justification. This also removes all registered security keys and passkeys. Afterwards you log in with your password only. So that you notice a reset you did not request yourself, you then receive a system message and an email notice to the address of your account. Both state only the date and advise you in that case to change your password and to contact support; the email contains no link for logging in or confirming anything. The email is kept encrypted in the queue until it is sent and is deleted immediately afterwards, at the latest after 24 hours; the system message is deleted like other system messages (§ 06). The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is the protection of your account (§ 08). The reset is recorded with identifiers under admin actions (next item).
- Admin actions such as editing, suspending and deleting accounts and resetting two-factor authentication are recorded with identifiers, without names and email addresses, in the game log (for a temporary suspension also its duration, end and reason) and are deleted after 12 months.
Outside the game, only the controller has access to the live server and the live database. The controller uses this access only for specific purposes: for operation and troubleshooting, the handling of requests and the investigation of security incidents.
The legal bases are Art. 6(1)(b) GDPR (moderation according to the game rules) and (f) in conjunction with Art. 32 GDPR (legitimate interest in controlling privileged access).
Fair play review
Automated game actions (for example by scripts or browser extensions) are forbidden by the game rules. If a player reports a suspicion or a moderator sees a justified reason, we review the game account concerned. For this purpose, we store the report (who reports whom, reason, comment, time) and, for at most 14 days, in justified cases at most 28 days, one summary per day of the game behaviour of this account: how many game actions of which type, how quickly after an event in the game (for example the end of an operation) and at which hours. For this, we do not store any individual clicks, IP address, device or browser data or message contents. A written review report is produced from this.
Moderators and administrators only see the report and the review report after stating a reason; every access is logged (§ 09). Consequences are always decided by a human, never by an automated system: warning, suspension for 3 days or, in the case of a repeated violation, permanent suspension. You can appeal against any measure; a different person decides on the appeal. The reported person does not learn who reported them. During the review, we do not inform the reported person separately so that the review remains meaningful.
In the case of a permanent suspension, we store a non-readable check value of your email address and your player name (HMAC) so that you cannot register again, for 5 years; after that only if we extend the suspension with a justification. The entry is deleted immediately if the suspension is lifted.
The legal basis is our legitimate interest in fair play for everyone (Art. 6(1)(f) GDPR); for warnings and suspensions, additionally the game rules (Art. 6(1)(b) GDPR). Storage period:
- Review without findings: observation data are deleted immediately, the report and the case after 30 days.
- With a warning or a 3-day suspension: 6 months after the last decision.
- Permanent suspension: a short note for as long as the suspension lasts, thereafter 6 months.
You can object to the processing on grounds relating to your particular situation (Art. 21 GDPR) and request access (Art. 15 GDPR).
Cookies and local storage
Storing and reading information on your device is governed by Section 25 TDDDG. Without consent, we only use what is strictly necessary for the function you have requested (Section 25(2) no. 2 TDDDG). We do not use statistics or analytics services such as Google Analytics.
| Name | Storage | Purpose | Duration |
|---|---|---|---|
zde_sid | Cookie (HttpOnly) | Session and protection of forms, also without login (e.g. registration) | until the browser is closed |
zdeLoginData4 | Cookie (HttpOnly) | “Stay signed in”, only if you tick the box when logging in. Contains only random values, no name and no password; the server stores an identifier, a hash and the expiry time for it. | at most 30 days from the login with password, without extension. Invalid on logout, new login, password change or reset, email change, suspension and account deletion. |
zde_privacy_preferences_v2 | Local Storage | your choice in the privacy settings and, from the first permission, a random identifier for the proof | 180 days from saving |
zde_privacy_consent_pending | Local Storage | remembers that reporting a choice to the server is still pending | until the server confirms or permanently rejects it, at most 180 days |
zde_finish_notify | Local Storage | your choice “Show completion notifications in this browser” in the player settings, only the value 1 without reference to an account or device | until you switch completion notifications off or withdraw the browser permission for notifications |
zde-draft:v3:…, zde_notifications:v2:… | Local Storage | message drafts and game notifications, only after your “comfort” permission; without permission they remain in the memory of the open page | until sent or read, until the permission is switched off (then deleted) or until you remove them |
zde-view:…, zde-filter:…, sort_…, terminal_cmd_history and further zde- keys | Session Storage | operating states: scroll position and input when returning (no passwords), filters, sorting, terminal command history, protection against double execution | until the browser tab is closed |
zde-static-… | Cache Storage (Service Worker) | static files such as stylesheets, scripts and icons for faster loading, no personal data | until the next game version |
Legal bases: for zde_sid, zdeLoginData4, zde_finish_notify, Session Storage and Cache Storage, Section 25(2) no. 2 TDDDG and Art. 6(1)(b) GDPR; for drafts and notifications, your consent (Section 25(1) TDDDG, Art. 6(1)(a) GDPR); for storing your choice, the withdrawal and the proof, Section 25(2) no. 2 TDDDG and Art. 6(1)(c) in conjunction with Art. 7(1) GDPR, because we must be able to demonstrate consent and respect a withdrawal.
Completion notifications: If you switch them on in the player settings, your browser asks once for permission to show notifications. The notification, for example that a particular upgrade, research or attack has been completed, is created by the open game page in your browser, without a push service and without any additional transmission to us or third parties. Your browser manages the permission, and you can withdraw it there; how long a notification remains visible is determined by your browser and operating system.
Proof of your choice: If you save a choice after having permitted something once, the server logs, as proof of your consent and its withdrawal, the random identifier, your choice, the version of this policy (the German version is authoritative), the language of the dialog (German or English), the version of the dialog, for an English dialog the version of the current English translation of this policy (if available), the game version as well as the times, without IP address, account or session. We store the wording of each version of the policy, translation and dialog once, separately and without reference to you, so that it can be traced which texts your choice refers to. If your browser reports the same choice again with unchanged details, we only update the time of confirmation; otherwise a new entry replaces the previous one. The legal basis is Art. 6(1)(c) in conjunction with Art. 7(1) GDPR (see above). The current entry remains in place; after withdrawal, replacement or expiry (180 days after the last confirmation) it is deleted after 3 years.
Withdrawal: Via “Privacy settings” in the footer of public pages and in the player settings, you can change permissions at any time without any disadvantage for access to the game. The withdrawal applies to the future.
Storage period, account deletion and backups
We only store data for as long as is necessary for the respective purpose. An hourly clean-up run deletes expired database entries, log files are cleaned up daily; there can therefore be up to one hour or one day between the end of a period and the deletion.
| Data | Period | from |
|---|---|---|
| Logs of reverse proxy and web server | 7 days | access |
| Error log of the game | 14 days | entry |
| Login log | 30 days | login |
| Failed attempts and abuse counters | 24 hours | entry |
| Session data on the server | 25 hours | last use of the session |
| “Stay signed in” | at most 30 days | login with password |
| Unconfirmed registration, confirmation link | 24 hours | registration |
| Beta waiting list: unconfirmed / confirmed entry (immediately with the invitation) | 24 hours / 180 days | sign-up / confirmation |
| Link to reset the password | 1 hour | request |
| Change of email address | 24 hours | application |
| Two-factor authentication: encrypted secret, check values of the recovery codes, time of activation | until turned off, reset or account deletion | activation |
| Security keys and passkeys: identifier, public key, counter, name, timestamps | until removed, reset or account deletion | registration |
| Setup of two-factor authentication that was not completed | 15 minutes | start of setup |
| Email notice after a reset of two-factor authentication (queue) | 24 hours, immediately after sending | reset |
| Game and transfer log, admin actions (for a temporary account suspension with duration, end and reason), deletion notes (account identifier only) | 12 months | entry |
| Server takeover: event and settlement | 12 months | takeover |
| Recovery claim after redemption or replacement (open until then) | 30 days | redemption or replacement |
| PvP report in the terminal | 24 hours | completion of the attack |
| Traces for defender forensics | at most 24 hours | attack |
| Battle archive | 180 days, at most 1,000 entries | event |
| Reconnaissance results | 180 days | reconnaissance |
| Target dossiers with notes, tags and favourites (the clean-up run deletes files on servers that no longer exist) | 180 days | last change (including marking as favourite) or reconnaissance |
| Collective ops | 14 days | end of the collective op |
| Collective weekly contract | 12 weeks | start of the week |
| NetWars final tables | 52 weeks | start of the week |
| World events (raids): contributions and leaderboards | 52 weeks | end of the event |
| Daily tasks: progress / selection and payouts | 3 days / 7 days | task day |
| Collective events | the last 20 entries | every new entry |
| Unanswered application for admission to a collective | 30 days | application |
| System messages | 90 days; read ones at most the newest 15 messages | receipt of the message |
| Copy of a reported mail | 6 months | notification of the decision or closure without review |
| Fair play report and case without findings (open until the decision) | 30 days | conclusion of the case |
| Daily summary of game behaviour during a fair play review (deleted together with the review report) | at most 14 days, justified 28 days | start of the review |
| Fair play case with warning or 3-day suspension (review report, measure and appeal; with an open appeal until the decision) | 6 months | last decision |
| Short note on a permanent suspension (case number, date, reason, admin ID) | as long as the suspension lasts, thereafter 6 months | lifting or end of the suspension |
| Block list against new registration (only HMAC of email address and name, no account ID) | 5 years, extension only with a justification; deleted immediately when lifted | permanent suspension or last extension |
| Support emails, report form, correspondence on data protection requests | 6 months | conclusion of the matter |
| Extracts on sanctioned rule violations | 2 years | conclusion of the case |
| End and reason of a temporary account suspension by the administration stored with the account (log entry: row admin actions) | at most 30 days, deleted when the suspension ends | suspension |
| Access log of administration and moderation | until the end of the following calendar year | access |
| Privacy choice in the browser | 180 days | saving |
| Proof of the privacy choice | 3 years | withdrawal, replacement or expiry |
| Logs of the mail server | 7 days | delivery |
| Server backups and snapshots at Hetzner (entire live server) | 7 days | creation |
| Register of data protection requests (without contents) | 3 years | end of the year in which the request was completed |
| Account and other game data | until the account is deleted | – |
Longer storage only takes place in the following cases: to investigate a specific security incident until it has been concluded, for sanctioned rule violations (2 years, see table), in the event of a complaint or legal dispute until its end, to prove that data protection obligations have been fulfilled (register) and if a law obliges us to do so (Art. 17(3)(b) and (e) GDPR).
Deleting your account yourself: Under Settings → “Delete account”, you request the deletion with your password and an explicit confirmation. A waiting period of 7 days follows; during this time the account is locked and “Stay signed in” is cancelled. You receive a confirmation by email. Until the deletion date, you can explicitly cancel the request after logging in. After that, the account is deleted automatically. Other players see your account as before until the deletion. Instead of deleting it yourself, you can also ask us to delete it (§ 13).
We delete inactive accounts 24 months after your last login or session activity (without a login: after registration). We write to you 30 days and 7 days in advance; if no valid email address is stored or the account is suspended, there is no notice. If you log in before then, nothing is deleted. Accounts of the game team are excluded.
What remains after an account deletion: game and transfer logs without reference to you until their period expires; a deletion note with the former account identifier, without name and email address, for 12 months, so that a deletion can be repeated after a backup has been restored; forum posts and events with “deleted account”; takeover events without reference to you until the end of the period; target dossiers of other players on your deleted servers until the next clean-up run; copies of reported mails without your name until the end of the period; fair play reports, cases and measures without your identifier until the end of the period (daily summaries are deleted immediately); after a permanent suspension, the block list entry (only check values, no account identifier) until the end of the period; extracts on sanctioned rule violations until the end of the period; entries in the access log, in server logs and for failed attempts until the end of the period; an entry in the register if you requested the deletion from us; backups until their scheduled deletion (see below).
Backups: Before every new version of the live game, we create a complete, encrypted backup of the database (storage see § 02). Each backup also contains data that have since been deleted. A daily run deletes backups according to a fixed plan: all backups are kept for 48 hours, the most recent one of a day for 14 days, the most recent one of a week for 8 weeks and backups made before a new version for 30 days. After that, they are deleted at the latest during the next daily run. Exceptions: the 2 newest backups are kept until newer ones exist, so that a restore is always possible; a backup that we retain for a specific reason (such as a security incident) is kept for at most 30 days longer per reason. In addition, Hetzner, as processor, backs up the entire live server including database, logs and keys; these server backups and snapshots of the server at Hetzner are deleted 7 days after creation at the latest. If a backup is restored, including a server backup from Hetzner, the game remains closed until all accounts deleted since its creation have been deleted again on the basis of the deletion notes.
Your rights
- Access to your data and a copy (Art. 15 GDPR),
- rectification of inaccurate data (Art. 16); you can change your email address yourself in the settings,
- erasure (Art. 17), yourself in the settings or on request,
- restriction of processing (Art. 18),
- data portability (Art. 20) for data that you have provided to us, as a JSON file,
- withdrawal of consent with effect for the future (Art. 7(3)) in the privacy settings,
- objection (Art. 21, see below).
How to make a request: Write informally to impressum@stieg.tech or to the address in § 01. To ensure that we only release data to the right person, we verify your identity via the email address stored in the account; we do not ask for an identity document. The request is free of charge. We reply without undue delay, at the latest within one month; for complex requests, the period can be extended by up to two months, in which case we inform you of this within the first month, stating the reasons. You receive access information as a JSON file with a readable overview; we make data of other players unrecognisable in it.
You can object at any time, on grounds relating to your particular situation, to processing that we base on legitimate interests (Art. 6(1)(f) GDPR). This concerns server and error logs, the login log and failed attempts, game logs, moderation, the access log and backups. We examine each objection individually and then no longer process the data, unless we can demonstrate compelling legitimate grounds that override your interests, or the processing serves the establishment, exercise or defence of legal claims. We do not use your data for direct marketing.
No automated decision-making: We do not make any decisions based solely on automated processing, including profiling, which produce legal effects concerning you or similarly significantly affect you (Art. 22 GDPR). Temporary blocks after failed attempts and the announced deletion of inactive accounts follow the fixed rules set out in this policy; reports and suspensions for rule violations are decided by a human.
Complaint to a supervisory authority: You can lodge a complaint with any data protection supervisory authority, in particular in the member state of your habitual residence, your place of work or the place of the alleged infringement (Art. 77 GDPR). The authority responsible for us is: Der Landesbeauftragte für den Datenschutz Niedersachsen (State Commissioner for Data Protection of Lower Saxony), Prinzenstraße 5, 30159 Hannover, Germany, www.lfd.niedersachsen.de.
Changes: We adapt this policy when processing operations change. The version published here with the date stated above applies.