Privacy & deletion
Under Dashboard → Server → Datenschutz (permission eternal.web.privacy) you decide how long each kind of data is kept, handle your players' deletion requests and delete a player's data by category – for good. Players see what is stored about them under Mein Konto → Datenschutz and file a request there or in-game with /datenschutz (alias /privacy).
The tools help you with the GDPR; responsibility for your server stays with you. Which periods fit your network depends on what you need the data for – get legal advice if in doubt.
The categories
| Category | What it holds | Delete automatically |
|---|---|---|
| Connections & IP addresses | Logins with IP and server, alt-account hits, the last IP in the profile | when older than … |
| Chat & private messages | Chat history, private messages, chat-filter hits | when older than … |
| Punishments, reports & appeals | Bans, mutes, kicks, reports about the player, unban appeals | when older than … – only ended punishments, closed reports and decided appeals |
| Replays | Replays stored in the dashboard with the player as the main person (file included) | when older than … |
| Item & container traces | Item tracking, stack events, last user of containers | when older than … |
| Coins, trading & market | Balance changes, shop sales, trades, market positions, pass bookings, plot purchases | when older than … – history only, balances stay |
| Inventories & game state | Inventories, ender chests, expanded inventory, last positions | when not online for … |
| Friends, party & clans | Friendships, requests, party and clan memberships | when not online for … |
| Nick history | Nicks worn, current nick | when older than … |
| Profile, settings & consent | Name, first/last seen, settings, perks, homes, age check, privacy consent | when not online for … |
| Ranks & permissions | Ranks, personal permissions, career | when not online for … |
| Forum | Forum profile, reactions, read state; posts stay, the name becomes "[gelöscht]" | by hand only |
| Dashboard account | Login, password hash, e-mail, sessions, link codes, permission requests | when not online for … |
| Shop purchases | Orders and payments in the web shop | when older than … – not before 8 years from the end of the calendar year (see below) |
Not included: plots (they belong to the world) and clan leadership – clean those up in Plots and Clans as usual.
Retention
In the Aufbewahrung (retention) tab, pick a period per category (7 days to 10 years) or Behalten (keep – the default: never delete automatically).
- "When older than …" deletes entries older than that.
- "When not online for …" deletes the category for players who have not been online that long. At most 500 players per run and category, the rest follows the next day.
- Run: once a day automatically, Jetzt anwenden (apply now) at once. The top shows when it last ran and how many entries went.
- Turning a period on or shortening it asks for confirmation that older data will be deleted for good from the next run on.
- Profile should have the longest "not online" period – the other categories find their players through the profile.
In Germany, shop receipts (accounting vouchers, invoices) must be kept for 8 years – since the Fourth Bureaucracy Relief Act for every receipt whose period was still running on 1 Jan 2025 (§ 147 AO, § 257 HGB). The period starts at the end of the calendar year the receipt was made in. That is why shop purchases can't be set below 8 years, and Eternal never deletes an order before that period is over – not automatically, not by hand, not on request (the legal duty to keep comes before the right to erasure, Art. 17(3)(b) GDPR). Punishments and reports may usually be kept as long as you need them to protect your network.
Deletion requests
A player files a request:
- in-game:
/datenschutz löschen [reason], then/datenschutz bestätigen(English:/privacy delete,/privacy confirm) – covers all data; - Mein Konto → Datenschutz: shows every category with the number of their entries and its period; they pick categories or everything, with a message to the team.
One open request per player at a time; withdraw with /datenschutz zurückziehen (/privacy withdraw) or on Mein Konto. The status shows there and with /datenschutz.
In the Löschanträge (requests) tab (filters: open, done, rejected, all):
- Bearbeiten (handle) opens the player in the "Spielerdaten löschen" tab with the requested categories ticked ("everything": all with data). Change the selection if needed, then delete – that completes the request.
- Ablehnen (reject) needs a reason; the player sees it on Mein Konto.
- Banned players: their request is marked red "gebannt". When handling it, "Punishments, reports & appeals" is not pre-selected – deleting that category would lift the ban. If you tick it anyway, the confirmation says so explicitly. A request made only to get out of a ban can usually be rejected with good reason.
Deleting a player's data
Search the player by name or UUID (UUID if the profile is already gone). Every category shows the number of their entries; empty ones are greyed out. Tick, add an optional note, then delete for good. A dialog first sums up what happens, for example:
- Punishments: running bans and mutes are lifted;
- Coins: balance and passes go to 0;
- Inventories: inventory and position on all servers are gone;
- Profile: privacy consent is asked again on the next join;
- Ranks: bought ranks are gone too.
If the player is online, they are kicked first so nothing is written back when they leave. They can rejoin right away.
Deletion log
Every deletion – on request or by you – shows in the requests tab with player, categories, number of entries, who and when (source "vom Team" when there was no request). The automatic runs show at the top of the retention tab and in the API log ([Eternal-Privacy]).
Permissions
| Permission | Purpose |
|---|---|
eternal.web.privacy | Privacy page in the dashboard (default: admin) |
| – | /datenschutz and Mein Konto → Datenschutz are open to every player |