Privacy policy
This is a translation for convenience. Only the German version is legally binding.
Version 1.5.13, last updated: 20 November 2026
We care about protecting your data. This policy explains which personal data is processed when you visit and use this website and the game Saltwarden Online, and why. In short: as little as possible.
Saltwarden Online is in development. Sections marked “not yet in operation” describe features we are preparing; they apply from the day the feature launches. Until then, the processing described there does not take place.
1. Controller
Strukturaflow IT e.U.
Owner: Natascha Reiner
Flatschacher Straße 10, 8724 Spielberg, Austria
E-mail: office@strukturaflow.com
Saltwarden Online is a project of Strukturaflow IT e.U. For privacy questions about Saltwarden Online you can also reach us at kontakt@saltwarden.com. No data protection officer has been appointed, as there is no legal obligation to do so.
2. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21). You can withdraw any consent you have given at any time with effect for the future. Just write to office@strukturaflow.com or kontakt@saltwarden.com. You can download an export of your account data as a JSON file yourself in your account under “My data” (once per hour).
You also have the right to lodge a complaint with the supervisory authority: Österreichische Datenschutzbehörde (Austrian Data Protection Authority), Barichgasse 40-42, 1030 Vienna, www.dsb.gv.at. There is no automated decision-making within the meaning of Art. 22 GDPR; account bans are always decided by a human.
3. Hosting, server logs and delivery
This website and the game servers run on our own server in Austria, not with a hosting provider. The web service of this website keeps no access log: we do not store IP addresses or a log of individual requests. Only start, stop and technical errors of the service are logged, without reference to individual visitors. Instead of a log we count page views (see section 17): per day, path (without search terms and parameters), language, country (from the header Cloudflare adds as tunnel) and referring website (its address only, without path). We estimate the number of visitors with a daily hash: from a random salt, the date, your IP address and your browser string we form a hash (SHA-256, truncated to 16 bytes) whose only purpose is to recognise another request on the same day as the same visit. The IP address itself is never stored; the hash cannot be traced back to a person, changes every day and is deleted after one day at the latest. The salt exists only in the server's memory, changes daily and is stored nowhere; for that reason a hash cannot be traced back to an IP address afterwards either. Not counted are requests by signed-in administration accounts, known bots, and account, sign-in, interface and file paths. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in knowing which pages are read and whether the website works). No cookies are set and nothing is passed on to third parties. To tell real page views from automated requests, every page contains a small script of our own that, after loading, reports a short-lived identifier valid only for that page view back to our server once. The script sets no cookie, stores nothing in your browser and loads nothing from third parties. Views without this report are counted separately as “unconfirmed”. We also count visits, the first focus on the waitlist field, submitted forms, confirmed sign-ups and issued invitations, as well as loading time, responsiveness and layout shifts (LCP, INP, CLS; grouped into coarse mobile, tablet or desktop width classes), solely as independent daily counts and rounded measurement buckets for 400 days, without cookies, stored IP addresses, identifiers or links to individuals. The viewport width is assigned to a coarse class (mobile, tablet or desktop) only in the browser; neither the exact width nor an identifier is transmitted or stored for this purpose. We keep the daily figures for 400 days. You can object to the count at any time by e-mail to kontakt@saltwarden.com; since we cannot attribute requests to a person, please understand that we cannot look up a single request.
Search: for common questions the search of this website shows a written answer card, otherwise the results. If a search query returns neither an answer card nor a result, we store the query in simplified form (lower case, without numbers and without character strings that look like e-mail addresses or links, at most 80 characters) with a daily counter, without IP address, without any link to a session or an account and without a time of day. In the administration we see such a query only once it has been entered at least three times within the 90 days, and we use it to add missing answers. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in improving the website). The counters are deleted after 90 days. Please do not enter personal information into the search.
Backups: we back up the database and the uploaded files daily, encrypted, locally and to a second storage. Backups are deleted after a rotation of 14 days. When a record is deleted or a retention period of this policy ends, it therefore disappears from the backups at the latest 14 days later; on a restore we do not bring deleted data back.
Delivery takes place via the network of Cloudflare Inc., 101 Townsend St., San Francisco, CA 94107, USA. Cloudflare performs four tasks for us: the name service (DNS) for the domains saltwarden.com and rivenwardonline.com (former address, redirects to saltwarden.com), the proxy at the network edge (Cloudflare accepts your connection, encrypts it with TLS and fends off attacks), a tunnel through which our server collects requests without being reachable from the internet itself, and forwarding e-mail sent to kontakt@saltwarden.com (Cloudflare Email Routing). In doing so Cloudflare processes IP addresses, connection and request data (e.g. address requested, browser identifier, time) and, because encryption ends at Cloudflare, also the content of requests, such as an e-mail address entered in a form. For e-mail to kontakt@saltwarden.com, Cloudflare receives the message with sender, recipient, subject and content and forwards it to the project's mailbox; according to Cloudflare, it does not store message content, only delivery information. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in fast, secure and stable delivery and in a reachable contact address).
Cloudflare is our processor; Cloudflare’s Data Processing Addendum under Art. 28 GDPR applies. Requests are handled in the nearest data centre, for visits from Europe usually in data centres in the EU. Processing exclusively in the EU is therefore not guaranteed; transfers to the USA are based on the EU-US Data Privacy Framework, under which Cloudflare is certified, and additionally on the EU standard contractual clauses. Cloudflare may also ask your browser to send reports about failed connections (Network Error Logging) to Cloudflare; these contain no page content.
4. Contact by e-mail
If you contact us by e-mail, we process your details to handle the request and any follow-up questions (Art. 6(1)(b) or (f) GDPR). The data is deleted as soon as it is no longer needed for these purposes and no statutory retention obligations apply. For the forwarding of e-mail to kontakt@saltwarden.com see section 3.
5. Waitlist and transactional e-mails
For the waitlist we process your e-mail address, the chosen language, the times of sign-up, confirmation and unsubscription, and the place on the website where you signed up (for example the start page, the header or the devlog), so that we can see without analytics tools which references to the waitlist work. Sign-up uses double opt-in: you receive a confirmation link, and only clicking it activates the sign-up; the times of sign-up and confirmation are logged as proof. If you sign up while signed in to the account whose address you have already confirmed, using exactly that address, no confirmation link is needed and the sign-up is active at once. In all other cases, even if a confirmed account exists for the address, the confirmation link applies; confirming an account address does not confirm a waitlist entry. The legal basis is your consent (Art. 6(1)(a) GDPR in conjunction with § 174 Austrian Telecommunications Act 2021). You only get mail when a test is coming up (such as an invitation to the closed alpha, section 12) or the project ends; the address is not passed on to third parties and not used to advertise other offers.
Mail is sent via our processor Brevo (Sendinblue SAS), 106 boulevard Haussmann, 75008 Paris, France; the data is processed on servers in the EU (data processing agreement under Art. 28 GDPR). Brevo receives your e-mail address and language for this. You can unsubscribe at any time via the link in every e-mail; this counts as withdrawal of your consent. Your data is stored until withdrawal; unconfirmed sign-ups are deleted after 30 days.
We also use Brevo to send transactional e-mails required for an account: confirmation of the e-mail address, sign-in links, password resets and notices about security or bans, and a single thank-you mail after a donation (section 19). The legal basis is Art. 6(1)(b) GDPR (terms of use). These e-mails contain no advertising.
Opens and clicks: For all e-mails sent via Brevo, Brevo technically records whether an e-mail was opened and whether a link was clicked. We have configured Brevo so that this recording is anonymised and not linked to any person. We do not analyse this data and do not use it for profiles or advertising.
Newsletter “Neu in Saltwarden”: In addition to the waitlist, you can voluntarily subscribe to a digest of project news sent roughly every two weeks, using a separate, never preselected checkbox on waitlist sign-up, in your account, or independently on the newsletter page and in the footer. The independent sign-up also requires a consent checkbox that is never preselected and does not create a waitlist entry. Joining the waitlist is not newsletter consent. Double opt-in applies here too: only clicking the confirmation link activates the subscription. We store the address, language, sign-up source, request and confirmation times and the version of the consent text; confirmation and unsubscribe links are stored only as hashes and confirmation links expire after seven days. The legal basis is your consent (Art. 6(1)(a) GDPR in conjunction with § 174 Austrian Telecommunications Act 2021). Every mail offers one-click unsubscription without signing in; you can also end the subscription immediately in your account. Existing confirmed waitlist addresses receive at most one invitation to subscribe voluntarily, and only after explicit release by the administration. We delete unconfirmed requests without earlier proof after 30 days. While subscribed, we retain the data until withdrawal; we delete proof of consent and withdrawal three years after unsubscription. Recipient-specific rows in the newsletter delivery log are deleted 90 days after the delivery attempt. Account deletion removes newsletter data. Delivery uses only the transactional route named above, no Brevo marketing list and no additional processor.
Newsletter content links carry only an issue number shared by all recipients (nl=<number>); the existing cookieless visit counter aggregates this source into daily counts without linking visits to recipients, removes the parameter from the stored path category and displays only sums of released daily cells.
Delivery log: for every mail sent or failed (waitlist, newsletter, account, alpha, donations, notifications) we store, as proof of delivery and for troubleshooting, the time, the type of mail, a hash (SHA-256) of your address, a shortened display of the address (for example “a***@g***.com”), the response code and message ID of our sending service, a shortened error text without the address and, where known, the internal ID of your account or waitlist entry. The full address is not in the delivery log; we can only check whether an address we are given has an entry. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in traceable and working mail delivery). We delete the entries after 90 days in the hourly cleanup run. If you did not receive the waitlist confirmation mail, the administration can send it again; this creates a new confirmation link and the old one becomes invalid.
For the mobile waitlist bar, your browser stores only “bar closed” (closed) in localStorage under sw.waitlist.mobile.v1 when you close the bar or successfully submit a sign-up. The entry contains no e-mail address or identifier, is not sent to our server and remains until browser storage is cleared.
6. Account for website and game
One account covers the website, the forum, the wiki and the game. We process:
- e-mail address and the time it was confirmed,
- display name and optional profile details (avatar, short bio, language),
- the password only as a hash (scrypt with salt); we do not know the password itself,
- sessions: a random session identifier (stored by us only as a hash), expiry time, IP address and browser identifier, so that you can see and sign out your signed-in devices,
- a sign-in log (sign-in, sign-out, failed attempts, password resets, bans) with time, IP address and browser identifier to prevent abuse and to investigate account takeovers,
- ban records with time and reason.
The legal basis is Art. 6(1)(b) GDPR (terms of use) and, for the sign-in log and bans, Art. 6(1)(f) GDPR (legitimate interest in account security and fair play). Short-lived counters limiting sign-in attempts are kept only in memory (Redis) and expire after minutes.
Passkeys: when you create a passkey we store its public key, an identifier, a counter, the device name you choose or one derived from your browser, and the times of creation and last use. The private key and any biometric data never leave your device. The legal basis is Art. 6(1)(b) GDPR; stored until you remove the passkey or delete your account. For signing in we briefly (at most 10 minutes) set a technically necessary cookie and a sign-in state.
Retention: sessions end after 30 days or on sign-out. Sign-in logs are deleted after 90 days. Ban records are kept for the duration of the ban and at most 2 years afterwards to recognise repeated abuse. You can delete your account in the account settings; after a 14-day period during which you can cancel the deletion, account, profile and characters are deleted.
Cookies: we only set technically necessary cookies: for signed-in use a session cookie, and a cookie protecting forms against cross-site requests (CSRF), which is also set without signing in as soon as you open a page with a form (for example registration, waiting list or support); it serves only this protection and not tracking. In addition there are a short-lived cookie for status messages, plus, if you choose, a cookie storing your colour scheme. The legal basis is § 165(3) Austrian Telecommunications Act 2021; no consent is required. There are no tracking or advertising cookies. The public pages of this website currently set no cookies at all.
7. Forum and wiki
Forum posts and wiki edits are publicly visible together with your display name and the time. We keep earlier versions of edited posts and wiki pages (revisions) so that changes remain traceable and abuse can be reverted. We process reactions, read status and reports of posts to provide the forum.
Moderation: reported posts are reviewed by a human. We store the report, its reason and the outcome (deleted, dismissed, ban). The legal basis is Art. 6(1)(b) GDPR (terms of use) and (f) (legitimate interest in respectful and lawful conduct). Details on reports and moderation decisions are in section 9.
If you delete your account, your public posts and wiki edits remain in anonymised form so that conversations and pages stay understandable: they are no longer linked to any name or account (“deleted account”). On request we also delete your forum posts completely; write to kontakt@saltwarden.com before or after deleting your account.
8. Notifications
Replies to your threads, mentions with @name, changes to wiki pages you watch and moderation decisions are shown in your account. By e-mail only if you turn this on per type; every such e-mail contains an unsubscribe link. Moderation decisions that affect you are always sent by e-mail (Art. 17 Digital Services Act). The legal basis is Art. 6(1)(b) GDPR, for the optional e-mails point (a). We keep notifications for 12 months.
9. Reports and moderation decisions
Reports without an account: anyone reporting a post, wiki page, character page or Tide Register profile card via “Report content” provides a name, e-mail address, an explanation and a statement of good faith. We use these details to confirm receipt, review the report and communicate the outcome (Art. 16 Digital Services Act, Art. 6(1)(c) GDPR). The person concerned does not learn your name. We keep these details until 6 months after the report is closed, including any appeal.
Reports about character pages and profile cards: anyone reporting a character page or profile card chooses a reason (offensive or insulting name or title, infringement of third-party rights, impersonation, fraud or advertising, other rule violation or illegal content) and explains the report. For this we store the realm and character name or the reported account, the reason, the explanation and the reporting person’s details as described above. The person reported does not learn the reporting person’s name. A report does not confirm that a non-public character exists: reports can also be received for characters that are not publicly visible; they are reviewed without any feedback about game data.
Measures against characters: if moderation decides that a reported character violates the law or our rules, only at that moment do we internally link the character to the account it belongs to. Only moderation sees this link; the reporting person learns neither the account nor whether the character exists. The person concerned receives the decision with a statement of reasons and information about the possibility to appeal (Art. 17 and 20 DSA) in their account and by e-mail, or via a one-time link if the account is suspended. Possible measures are: hiding the character in the Tide Register (it can only appear there again once moderation lifts this), requiring a new name (until the name is chosen at the next login, the character carries a temporary name), muting the character in the game or suspending the account. In the case of a forced rename, we store the old name and reserve it for 90 days so that nobody can take it immediately and it can be returned after a successful appeal. After this period the reservation is released. Six months later (appeal period) we delete the old name and the identifier of the acting moderator on the character, as soon as the character is no longer hidden and no rename is pending; the decision itself is retained in accordance with section 9. The marking appears in the account’s data export (hidden since, pending rename, old name, reserved until). The legal basis is Art. 6(1)(c) GDPR in conjunction with Art. 16, 17 and 20 DSA and Art. 6(1)(b) GDPR (enforcement of the terms of use).
Moderation decisions and appeals: for every measure we store the content concerned (text at the time of the decision), the ground, the statement of reasons, who decided and when, and any appeals with the reply. This serves the duty to give reasons, the appeal procedure (Art. 17 and 20 Digital Services Act) and anonymous transparency figures. The legal basis is Art. 6(1)(c) and (f) GDPR. We keep these details for 2 years after the decision.
10. Memorials
For fallen characters on the One Life realm you can write an epitaph. Only if you choose “show publicly” will the character's name, level, class, race, cause and time of death, the epitaph and your display name appear in the public Hall of the Fallen. You can change or delete the entry at any time; the legal basis is your consent (Art. 6(1)(a) GDPR).
11. Images in the devlog
Only the administrators upload images for devlog posts. Embedded metadata (e.g. camera or location data) is removed on upload.
12. Closed alpha
Alpha operation starts with the first invitation; the processing described in this section only begins then. Participation is also governed by the alpha agreement.
Alpha invitation: we only invite people to the closed alpha who are on the waitlist and confirmed their address. For this we process the e-mail address, language, the place of sign-up on the website (source field), the invitation wave number and the times of invitation, acceptance or revocation. The invitation link is stored as a hash for verification and is valid for 7 or 14 days depending on the invitation. On acceptance we store your consent to the alpha agreement (version and time), your confirmation that you are 16 or older and, if you provide it, your Discord name so we can give you the tester role. The legal basis is Art. 6(1)(b) GDPR (participation in the alpha). Retention: until the end of the alpha; we delete the Discord name when the alpha ends, and all invitation details on account deletion.
One-time alpha messages: we use your address and language, the invitation deadline, first alpha sign-in, presence of a character, saved playtime and last completed logout to remind you once about an open invitation, help you get started without a character and request voluntary feedback after a first play session. For bug reports, we also use your address and language to notify you once per report when the reported issue has been fixed. These service emails support alpha participation under the legal basis stated above and include an unsubscribe link; account messages can also be switched off in your account. Delivery jobs contain the necessary links until delivery, cancellation or expiry; we then delete this payload. One-time markers, delivery status and unsubscribe link hashes remain until the associated account or invitation is deleted, to prevent repeat messages. The one-time marker for a bug report's status email is instead deleted with the report after 90 days.
Session questionnaire: participants answer six questions on a scale from 1 to 5, optionally one sentence, plus session date, class played and realm. We only evaluate the forms in aggregate (median, minimum, distribution per question) to tune the game. The legal basis is Art. 6(1)(b) GDPR (feedback is the purpose of the alpha under the alpha agreement) and (f) (improving the game). When the alpha ends or on account deletion we remove the link to your account; the answers remain without personal reference for evaluation.
Bug reports: when you report a bug via “Report a bug”, you submit the steps to reproduce, the realm, optionally a character name and a time. Only moderators and administrators see the report; it is stored with your account in the moderation log. Only if you tick the box does it also appear as a public forum topic (section 7). The legal basis is Art. 6(1)(b) and (f) GDPR. Bug reports are deleted after 90 days; a forum topic stays like other posts. Feedback from inside the game: if you use the command “/bug” or “/idea” or the menu entry “Report a bug or idea” (Help tab) in the game, you submit the text you typed (up to 800 characters) and the category (bug or idea). The game server adds the realm, the name of the character you play, the zone, the character's position in the zone, the game version (build) and the time automatically; account and character come from your signed-in connection. When the browser detects a rendering failure it may also send a short report without free text on its own (“Client frame interrupted” with the error type and build); it counts separately from your own reports. Only moderators and administrators see the location and position, in the moderation log and never publicly; for One Life characters the zone and position appear only there. We notify the project lead about new reports with the number, a short title (the start of the text, at most 80 characters), the category and the zone by a Discord message in a non-public channel and optionally by email to an internal address; the rest of the text, the position and the character name are not included. The report gets a processing status, a priority and, where needed, an internal note from moderation. The purpose is to reproduce and fix bugs; the legal basis is Art. 6(1)(b) and (f) GDPR. Retention is the same as for other bug reports (90 days). Moderators and administrators may additionally publish a short title they have written themselves and the coarse processing status of a confirmed, in-progress or fixed bug report on the public “Status” page. The text you submitted and the reporters remain private; without this staff-written short title, the report remains private. Ideas and automatic reports are not published there. In the private “My reports” account area, you can see only your own reports with their number, date, category, processing status, any build containing the fix and a safe short title; when a report is marked fixed, we send you one service email with the build number and link, provided alpha messages are enabled and your account is not deleted or banned.
Short questionnaires and follow-up questions
When you submit a short questionnaire about your first session or first week of the alpha, we store your optional answers (up to three free texts and one comment, up to 2,000 characters each), individually optional combat ratings and optional session date, class and realm with a link to your account. This lets you view and update your answers. There is one current questionnaire per account and period; submitting again replaces it. We use the answers to improve the introduction and the game. The admin results show aggregated answer counts and ratings, along with answer texts grouped by question without displaying your account. Free text may itself contain personal information.
The legal basis is Art. 6(1)(b) GDPR (alpha agreement), supplemented by Art. 6(1)(f) GDPR for analysis; our legitimate interest is improving the alpha. Participation is voluntary. Answers are stored until account deletion, and no later than twelve months after the alpha ends. Your saved answers and follow-up permission details are included in your account export. When your account is deleted or anonymised, these short questionnaires are deleted too.
If you tick the optional follow-up box, only administrators may use your account email address to ask a follow-up question about this answer. The legal basis is your consent under Art. 6(1)(a) GDPR. Your choice and its timestamp are stored for each answer. Only the dedicated admin view “Follow-up questions allowed” shows the answer linked to the account email. Emails are sent from this view and recorded in the delivery log described in section 5. You may reply by email voluntarily; section 4 applies to this correspondence.
You can submit the questionnaire without ticking the box. This choice does not subscribe you to a newsletter or change your alpha messages. You can withdraw your consent at any time under “My questionnaires” in your account by unticking the box and confirming withdrawal. Withdrawal does not affect the lawfulness of processing before it. Permission automatically expires after 90 days; the contact link for follow-up questions is then removed by the existing maintenance job. Sending is no longer possible once permission expires. Withdrawal removes the contact link immediately. Your answers remain linked to your account for your own viewing, editing, export and account deletion; that link is no longer made available for follow-up questions.
13. Game moderation in the portal
Bans, mutes and reversed deaths triggered by administrators through the portal are logged with time, acting person, affected account or character, reason and result. On a ban the portal passes the account identifier to the game server so that a running game session ends. The legal basis is Art. 6(1)(c) and (f) GDPR (statement of reasons under Art. 17 Digital Services Act, a safe game). These logs are deleted after 2 years.
14. Discord
The website links to our Discord server at /discord. The link is a plain redirect; the website loads no content, scripts or cookies from Discord, and no data flows to Discord when you visit the website. Only when you follow the link does Discord Inc. (USA) process your data under its own terms (discord.com/privacy); for transfers to the USA, Discord states that it relies on the EU-US Data Privacy Framework. When we publish a new devlog post, we send its title, teaser, link and cover image to a Discord channel; it contains no personal data of users.
15. Game operation (not yet in operation)
Friends lists belong to a character and realm. Friends see the existing online status as well as class, level and realm of the played character. We store each character’s last logout timestamp until the character is deleted and show friends the rounded elapsed time as “Last seen”. While online, friends see the broad area by default, never a subzone or position; “Show my zone to friends” on the Privacy tab disables this area display per character. The switch setting is stored until the character is deleted. For One Life characters, this display never transmits an area, location or last logout timestamp.
We store pseudonymous mobile diagnostics per account (build, disconnect reason, close code, duration, network type, touch/desktop device category and visibility changes) for 30 days, with opt-out through the telemetry switch, without IP addresses or browser identifiers.
The game is not yet public. Game operation begins with the closed alpha, which starts by invitation only (section 12); from the first invitation, this section applies to the invited participants.
We process playtime per character to display it to you in the game and in your data export, never publicly.
Economy review. We log movements of money and items from loot, rolls, quests and vendor transactions with the time, internal character identifier, the other character identifier where applicable, operation identifier, items and in-game currency amounts. Loot, quest and vendor records also include the source, class, level and realm. This supports traceable transactions and the detection of errors and abuse in the game (Art. 6(1)(b) and (f) GDPR). We delete loot, roll, quest and vendor records after 90 days through the hourly cleanup job. Separately, the game keeps a booking journal per character, from which we prove the character's balance and which prevents an operation from being booked twice: for each booking the time, type, in-game currency amount, operation identifier and the items affected. We remove the details of the operation (for example source, guild, gross amount and share, class, level and realm) from it after 90 days in the same cleanup job; the booking itself with time, type, amount and operation identifier stays until your account is deleted. Only our team sees this journal. For optional economy telemetry we also count active playtime per character and UTC hour, split by session, class, level and realm. The telemetry switch and existing deletable pseudonymous mapping apply; these data are also deleted after 90 days. Characters and accounts that have been deleted or opted out of telemetry are excluded from new reports. Daily reports already generated contain only totals by class, level and content source, with no character or account identifiers, names, IP addresses or sessions; the daily cache is deleted after 90 days. Unusual results are for manual review only and never lead to automatic sanctions. The telemetry switch prevents optional analysis, but does not disable the economy records needed for traceable game transactions. You may object to processing based on legitimate interests under Art. 21 GDPR.
Inspecting other characters. Other players who currently see your character in the game and stand within a short distance can inspect it. They see name, level, race, class, appearance and the equipped items (item, quality, item level). They never see stats, gold, bags, bank, quest progress, playtime, online times, location, account or friends. With “Hide my equipment from others” on the Privacy tab you hide your equipment per character; name and character stay visible because they are on screen anyway. Living characters on the One Life realm can only be inspected up close and reveal no location and no activity. Legal basis is Art. 6(1)(b) GDPR (contract of use: a multiplayer game in which characters are visible to each other). We only store your switch setting for as long as the character exists; other players' requests are not logged, only a two-second lock against repeated queries.
Standing with factions. For each character we store its standing with the game world's factions (value, display switches, time of the last change) so the game can calculate merchant prices and access and show you your standing. We also count, per character, faction and hour, how much standing was gained (points and number of awards) to detect errors and automated play (abuse review). Reports drawn from this contain only distributions with no reference to an account, character or name. Unusual hours are only flagged for manual review; no ban ever follows automatically, and nothing in the game reacts to it. We delete the hourly counters after 90 days and the standing itself together with the character. Your standing is included in your data export; the hourly counters are not, because they expire after 90 days and serve abuse review only. Legal basis: performance of the contract (running the game, Art. 6(1)(b) GDPR) and legitimate interest in a fair game (abuse review, Art. 6(1)(f) GDPR). You may object to the abuse review under Art. 21 GDPR; the in-game telemetry switch does not apply here because the counters belong to the game mechanics.
Guilds. When you found a guild, join one or sign a guild charter, we store for your character the membership (guild, rank, time of joining), the note about your character (at most 60 characters, visible only to ranks with that right), your “Show me online” switch (off unless you turn it on), open invitations to your character and your signatures on charters (character, account, time; the account only serves the rule “one signature per account”). The roster shows other members your name, rank, level and class; whether you are online and in which zone only with your switch, and never the zone on the One Life realm. We keep the guild log (joins, rank changes, departures) for 90 days and only link names when it is read. Guild chat and the “Chancery Talk” channel are not stored unless a line is reported (see Reports). Guild name, “Chancery Notice” and info text of a guild have their own report reason. If your character is deleted, we delete membership, note, invitations and signatures with it; if it dies on the One Life realm, it leaves the guild, and we keep rank and note for a possible reversal of an incident death until the character is deleted. The data is part of your data export. Legal basis: performance of the contract (community feature of the game, Art. 6(1)(b) GDPR).
Guild bank “Guild Strongbox”. Once the guild bank is switched on (Haven realm only, not the One Life realm), we store every movement of the guild treasury and its tabs: for money the type (deposit, withdrawal, repair, tab purchase, expiry), character, time, amount and the new balance; for items the type (stored, taken out, tab renamed, rights changed), character, time, tab, item and quantity. These movements are shown to members whose rank has the right to read the log (the item log only for tabs they may see); they are not shown to other members or third parties. We delete the item log after 90 days. The money log serves complete bookkeeping of the treasury and therefore stays as long as the guild exists; after a guild is dissolved we delete it after 90 days. If your character is deleted, the rows remain without any link to your character. For the daily limits of ranks we count per character and guild how much it has taken on the (UTC) day; we delete these counters after 2 days, at the latest with the character. We also store a receipt per request so that a repeated request is not executed twice; we delete receipts after 7 days. Your own movements (guild, type, time, tab, item, quantity, amount) are part of your data export. Legal basis: performance of the contract (community feature of the game, Art. 6(1)(b) GDPR) and legitimate interest in traceable, tamper-resistant management of shared assets (Art. 6(1)(f) GDPR); you may object under Art. 21 GDPR.
Guild Share. On the Haven realm (not on the One Life realm) a guild's leadership can set a rate from 0 to 10 percent; a raise is announced in the guild channel and only applies after 72 hours, a cut applies at once. If a rate is set and your character is level 10 or above, that share of the coins your character loots from foes goes to the guild strongbox; quest rewards, sales, trade, mail and the market are exempt. For this we store one line per share in our economy log (character, guild, time, loot and amount given), in the guild's cash book only amount, time and the new balance without reference to your character, for you the total of the current week and the total in this guild, and for the guild the total per week. Only you see your own totals; the leadership and ranks with the right to read the log see only the weekly total of the whole guild, never amounts of single members. Rate changes are listed in the guild log (90 days). Only our team sees the economy log lines; they serve to check for gold selling and abuse and are deleted after 90 days like the other loot lines. After 90 days we merge the single share lines in the cash book into one daily total per guild and day; after that no single share can be told apart in the cash book, and the strongbox total stays the same. The booking itself stays in your character's booking journal, from which we prove the character's balance (section Economy review): we remove the guild and the loot there after 90 days, while time, amount and transaction ID stay until your account is deleted; only our team sees this journal. We delete the guild's weekly totals after eight weeks; we delete your own totals when you leave the guild or the character is deleted. Your own totals are part of your data export. Legal basis: performance of the contract (community feature of the game, Art. 6(1)(b) GDPR) and legitimate interest in traceable bookkeeping and in preventing gold selling (Art. 6(1)(f) GDPR); you may object under Art. 21 GDPR.
In-game mail (“Wingpost”). In-game mail lets player characters send each other letters, optionally with in-game money and up to four items attached. For each letter we store: the sending character (with its name at the time of sending and the account behind it), the receiving character, subject, text (at most 300 characters), amount of in-game money, postage, attachments, status, and the times of sending, delivery, reading and expiry. There are no mass mailings; each letter has exactly one receiving character. The purpose is to deliver the letters and to transfer items and in-game money between characters. The legal basis is Art. 6(1)(b) GDPR (contract of use); for reviewing reported letters and preventing abuse (rate limits, traceability of transactions) it is Art. 6(1)(f) GDPR.
Retention. A letter is kept until it is deleted. Letters without an attachment are deleted automatically 30 days after delivery. Letters with an attachment go back to the sending character after 30 days where possible; letters that came back this way have no expiry date so that no items are lost as long as the sending character exists. If you delete a letter (only possible without a remaining attachment), it is erased and no text remains. We keep no full-text log of letters. We treat the bookings of in-game money and items (without the letter text) like the bookings of the market and of trades between players: they serve traceability and abuse checks and are not subject to the 90-day periods of the other economy logs; bookings for checking orphaned attachments after an account deletion are kept until that check is complete. Request receipts that prevent double bookings and enforce rate limits are deleted after 14 days. If a character moves from One Life to Haven (transfer), its letters move with it.
Who sees your letters? The sending and receiving characters, or the accounts behind them, see the text of a letter. Our team does not read letters routinely or without cause; letter texts are accessible only through a report. If the recipient reports a letter, we store its subject and text together with the sender and time in the report; moderators then review it by hand (section 9 applies accordingly; no automated decision is made). We treat reported letters like reports from chat: they are kept until the review is complete; if no action is taken we delete the report 30 days after it is closed, and at the latest after two years. If action is taken, the retention period of the ban record applies (section 6).
Export. Your data export (“My data”) contains the letters held by your characters (sender name, subject, text, money, items, times) and your outgoing letters that still exist (recipient name, subject, text, times).
Deletion. If you delete your account, the letters held by your characters are deleted; attachments go back to the sending character where possible and are otherwise forfeited. Letters you sent to others stay with the recipients so that their mailboxes are not altered, but lose any link to your account: sender name and account link are removed, the sender ID is replaced by a random ID, and the letter can no longer be sent back. The letter text stays with the recipient; if it contains personal data itself, that data may remain there. Your request receipts are deleted.
For the game we process:
- character data: name, race, class, appearance, level, experience, inventory, position, progress, realm and, on the One Life realm, the death record (time, place, cause);
- connection data: IP address, time of sign-in and sign-out, latency and technical errors, to provide the connection and to prevent fraud and attacks;
- chat logs: we store in-game chat messages with sender, channel and time so that reported insults, fraud or other violations can be reviewed.
The legal basis is Art. 6(1)(b) GDPR (terms of use) and, for connection data and chat logs, Art. 6(1)(f) GDPR (legitimate interest in a secure and fair game). Character names may be visible to other players. The record lists planned for after the alpha appear only from ten participants who have expressly consented (opt-in). This threshold of ten applies to record lists; the threshold of five for map cells is described below.
Retention: character data for as long as your account exists. Connection data is deleted after 30 days, chat logs after 30 days. If a message has been reported, we keep it until the review is complete, and in case of a ban as long as the ban record (section 6).
Improving the introduction to the game. We summarise existing server-side records of successful portal sign-ins, character creation, world entry, first quest turn-ins and reaching levels 3, 5 and 10 into daily counts. This helps us understand which early milestones are reached and where the introduction could be clearer. Administrators see only the number of distinct accounts per completed UTC day and milestone. Several characters or sessions from the same account count at most once in each daily cell. Numbers are shown only for cells covering at least five distinct accounts; smaller cells, including zero, are suppressed together. The report contains no account, character or session identifiers, names, IP addresses or individual events. It covers either the last seven or thirty completed days and does not show individual journeys or dropout rates.
You can disable this analysis using the existing telemetry switch. Every query excludes accounts with telemetry disabled and deleted accounts; character-based milestones also exclude deleted characters. This analysis creates no additional event collection or report cache. It uses existing records within their existing retention periods and does not extend those periods. First quest turn-ins and first level milestones also take older available character history into account so that later events are not counted again as a first milestone. Missing records are not reconstructed.
The legal basis is Art. 6(1)(f) GDPR (legitimate interest in a clear introduction to the game); you can object at any time using the telemetry switch.
World map on the website (not yet in operation). On the “World” page we will show what is happening in the game world right now: whether a realm is reachable, the time of day in the game, the state of world events and the latest entries of the world chronicle. For this, our server builds an overview once a minute from realm totals that are rounded as they are counted (below 10 players it only says “few”, above that rounded to tens or fifties). The planned live map has its own threshold: map cells are shown only from five characters; below that no cell is shown. Living One Life characters never appear on the map. The overview contains no character names, no accounts, no positions and no IP addresses, and it is not linked to your visit to the website; the map sets no cookies and loads nothing from third-party servers. Names appear in the chronicle only if you have expressly agreed to this in your account (as in section 10). The legal basis for the rounded numbers is Art. 6(1)(f) GDPR (legitimate interest in showing a living game world); we keep the overviews for 7 days. Later stages that could show information about individual characters (for example, which area a character is in) will only exist with your express consent (Art. 6(1)(a) GDPR), with a delay and a coarse location, never for persons under 16 and never for living characters on the One Life realm; you can withdraw consent at any time with the same switch. Every layer of the map is listed with its data source, update interval, rounding and legal basis in a transparency list in the portal.
15a. Tide Register
At your request, the Tide Register can display these basic character details: name, realm, race, class, level, title if applicable, a predefined portrait and the snapshot publication date as a calendar day. Memorial pages may also display the epitaph you have released and the state “fallen” or “transferred”. Publication is voluntary and is not required to play. The legal basis is your consent under Art. 6(1)(a) GDPR.
When creating a regular character, visibility is offered as a choice between “Hidden” and “Basic details public” with no preselected option. Without an explicit choice, the character stays hidden. You can change the choice for each character at any time in your account settings on the portal. For this we store, per character, the chosen visibility and the time of your first explicit choice for as long as the character exists. Linking it to your public portal profile additionally requires a separate choice per character, initially off, and the account switch for the character list. You can hide all characters across your account; this overrides individual choices.
Living One Life characters are initially hidden. Character creation does not ask about publication. Only an explicit opt-in through your account enables a public individual page. Even then, location, online status and activity are never published; living One Life characters do not appear in the profile list. Memorials require separate consent. Memorial pages remain quiet, without animation, sound, visitor counts or sympathy counters.
In addition to the basic details, you can choose the “In detail” level for a character. On the character page it also shows the character’s appearance (build, skin, hair, face, eyes and whether headgear and cloak are visible), the equipped items per slot (item, rarity and item level) and the talent choices (ranks per talent tree). Like the basic details, this information is visible to every visitor of the website, including players of the other faction (unlike inspection in the game). Achievements and titles may be added later, and we will inform you about this in advance. “In detail” is a separate consent of its own: it is offered only in your account settings on the portal, per character, with no preselected option, never when a character is created, and an existing release of the basic details is never extended automatically. If you have set in the game that your equipment stays hidden from inspection, the Tide Register shows no equipment either. Bags, bank, gold, stats, durability, location, online status and play times are never part of the output at this level either; search, the profile list and memorial pages continue to show only the basic details. The snapshot of the additional information is renewed at most once a day, like the basic details. Living One Life characters require the same explicit opt-in in your account as for the basic details; their snapshot of appearance, equipment and talents is renewed at most once a week, and no additional information about location, online status or activity is produced. You can withdraw “In detail” at any time by setting the character to “Public basic details” or “Hidden” or by hiding all characters; the additional information is then no longer shown on subsequent requests, immediately, and its snapshot is deleted with the change or at the latest at the next synchronisation. The legal basis is your consent under Art. 6(1)(a) GDPR.
Public characters can also be found through the search in the Tide Register on the website (the “Tide Register” page: search by the start of the name, filters for realm, race, class and level range). The search shows the same basic details as the character page (name, realm, race, class, level, title and portrait if applicable) and only characters you have released; hidden characters, living One Life characters and characters of hidden accounts never appear. Results are ordered only by name; there is no ranking. The search is limited against mass retrieval (a short-lived counter per IP address, without storing search terms); the results page is not cached and is served with noindex, nofollow, noarchive. Withdrawal or hiding takes effect for the search as for the character page on subsequent requests, immediately.
You can withdraw consent in your account settings or hide all characters at any time. New requests check the current permission; output is not cached in the browser, portal or CDN. Withdrawal stops output immediately on subsequent requests. For publication we store a snapshot of the basic data listed above, renewed at most once a day (name, death, transfer and inscription changes at the next sync); after withdrawal, hiding, a ban, a deletion request or deletion of the character it is deleted at the next sync, usually within ten minutes. We cannot retrieve content already read or copied by others. A ban, deletion request or account deletion also prevents publication. Withdrawal does not affect the lawfulness of processing before withdrawal; existing deletion and backup periods are not extended.
Character pages, profiles and memorial pages use noindex, nofollow, noarchive and are excluded from the sitemap. This asks search engines not to include them; it is not a technical access restriction. There is no public API, score, average item level (the level of individual items appears only at the In detail level) or character comparison. Position, current zone, online status, last seen, session times, level increase times, friends, ignored players, gold, bags, bank, individual quest progress, account email address, disconnection rate, reports and bans are never part of public output.
15b. Guild pages
A guild's leadership can set in the game that the guild gets a page on saltwarden.com, either as a preview for members only or public. It shows the name, crest, faction, realm, founding month, the approximate size (in bands, never the exact number), the info text and, if the leadership provides it, whether the guild is recruiting, its focus and language, as well as world chronicle entries about the guild from the day it is switched on. The name of your character appears there only if you yourself turn on “Show my name on the guild page” and your character is visible in the Tide Register (section 15a); your rank, your note, join date, online status, location and play times never appear. Living characters of the One Life realm never appear by name on guild pages; fallen ones only with a public memorial page (section 10) and if the leadership turns on the memorial line. The guild's treasury, guild bank, levies and logs are never published. Guild pages are served with noindex, nofollow, noarchive; guilds that are recruiting can also be found in a list per realm.
The info text is content provided by the leadership and can be reported like other user content (section 9). If it contains links or email addresses, it is not shown on the page. If three different signed-in accounts report it within seven days, we hide it until moderation has reviewed it.
You can withdraw your consent at any time in the game or in your account; your name disappears with the next request. If the leadership switches the page off, or the guild is dissolved or suspended, the page is immediately unavailable and its snapshot is deleted; chronicle entries about the guild then show no guild name. If a character is deleted, its release for the guild page is deleted too. The data export contains your release per character and, for leaders, the guild's visibility, recruiting status, focus, language and contact character. The legal basis for showing your name is your consent (Art. 6(1)(a) GDPR), separate from the consent in the Tide Register and without preselection; for the guild data itself, the community function of the game (Art. 6(1)(b) GDPR) at the leadership's request.
16. App and mobile use
You can use Saltwarden in the browser or add it to your home screen as a web app (PWA). No additional data is transmitted to us. An installed web app may cache program files and graphics on your device so that it starts faster; these files contain no personal data and can be deleted in your browser settings. We only send notifications if you explicitly allow them (not planned at present). For later apps in app stores, the respective store’s privacy policy also applies; this policy will be extended then.
17. Analytics
This website uses its own count without cookies and without third parties, with a small script of our own that confirms real page views, see section 3; no tracking pixels, no embedded third-party content and no fonts from third-party servers. The count runs on our server and records only figures per day, path, language, country and referring website, no IP addresses and no individual requests. If you open a link with a channel tag (parameter via, only from a fixed list such as bsky or presse), we count the channel per day without personal reference, also if you then sign up for the waitlist or the newsletter; the tag is not stored with the entry, only a daily counter per channel is increased, and the tag is then removed from the address bar. We set no cookies for this.
18. Minimum age and minors
The waitlist, accounts and the closed alpha are open to people aged 16 and over. The basis is Art. 8 GDPR: where processing for a service like this one is based on consent, a child under 16 can only consent validly with parental approval; member states may lower the limit to as low as 13 (Austria: 14 under § 4(4) DSG). We apply the limit of 16 uniformly because the site can be reached throughout the EU. If we learn that a child under 16 has provided data without parental approval, we delete it.
19. Support (donations via Stripe)
The plan is a one-time purchase, with no subscription and no pay-to-win. If you would like to support the project voluntarily with money now, you can do so on the Support page, one-off or monthly. A donation is not a pre-purchase and gives no advantage in the game and nothing in return except a thank-you. There is no donation receipt, because no charitable body stands behind the project.
Payment takes place entirely at Stripe, not on this website. This website loads no Stripe script and sets no cookie for it; only the button "Continue to Stripe" takes you to Stripe's payment page (checkout.stripe.com). The provider is Stripe Payments Europe, Limited, 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland. Stripe processes payment data as an independent controller under its own privacy policy (stripe.com/at/privacy), for example to process payments, prevent fraud and meet legal obligations; Stripe may set its own cookies on its payment page.
Payment methods: card (including Apple Pay and Google Pay), and EPS bank transfer; monthly support only by card. We do not offer SEPA direct debit for now. We do not offer other methods (such as instalments or "pay later"). Depending on the method, the provider of the payment method (for example Apple or Google for a wallet payment) and your bank (for example with EPS) also process your data as independent controllers under their own privacy terms. The payee is Strukturaflow IT e.U.; for card payments your statement also shows the reference SALTWARDEN.
What we send to Stripe: the chosen amount, whether one-off or monthly, the language and, if you are signed in, your account identifier and e-mail address (to prefill it and to link the payment to your account). What you enter at Stripe: name, e-mail address, payment details (such as card number or bank details) and, depending on the method, further details such as country or billing address. Optionally you can state there whether you want to be named in the supporter list and, without an account, a name for that list.
What we receive from Stripe and store: amount, currency, time, type (one-off or monthly), a payment identifier, the Stripe customer identifier and, if you were signed in, the link to your account. We do not receive full payment details. We use your e-mail address from checkout only to send a single thank-you mail via Brevo (section 5); we do not store it separately for this. Stripe sends the payment receipt.
You manage monthly support and receipts in Stripe's customer portal (billing.stripe.com), which you reach from your account or via the link in the Stripe receipt. A running monthly donation does not end by itself when you delete your account.
Supporter list: we name people on the Support page only with your explicit consent (Art. 6(1)(a) GDPR), given in checkout or in your account. With an account, your current display name appears; without an account, the name you enter in checkout, only after we have reviewed it. You can withdraw consent at any time: in your account by removing the tick, or informally by e-mail to kontakt@saltwarden.com; the entry is then deleted.
Legal bases: Art. 6(1)(b) GDPR for processing the donation and linking it to your account, Art. 6(1)(c) GDPR for retention under § 132 of the Austrian Federal Fiscal Code (BAO), Art. 6(1)(f) GDPR for the thank-you mail and preventing abuse, Art. 6(1)(a) GDPR for the supporter list.
Retention: we keep payment records for 7 years (§ 132 BAO), unlinked from the account if the account is deleted. Identifiers of events reported by Stripe are deleted after 30 days, names for the list that were not approved after 6 months, list entries on withdrawal or account deletion. According to Stripe, it stores data as long as legal obligations require.
Transfers to third countries: Stripe may transfer data to Stripe, Inc. in the USA and to other group companies. This is based on the European Commission's standard contractual clauses and on Stripe's certification under the EU-US Data Privacy Framework.
20. Status and changes
Version 1.5.13, last updated: 20 November 2026. We adapt this policy when features of the website or the game or the legal situation change. Earlier versions and changes are listed in the change log.
Change log
| Version | Date | Change |
|---|---|---|
| 1.5.5 | 15 November 2026 | Section 15a: Tide Register, visibility choice at creation and in the account settings, account-wide hiding, withdrawal, One Life and no search indexing; approved by Harald on 15 November 2026. |
| 1.5.13 | 20 November 2026 | Section 5: waitlist without a confirmation link only from your own session with exactly the confirmed account address; otherwise always double opt-in, also for addresses with a confirmed account; confirming an account address does not confirm a waitlist entry (security review SEC8); following Harald's decision on 20 November 2026. |
| 1.5.12 | 20 November 2026 | Section 15b: guild pages (a guild's page on saltwarden.com, preview for members only or public; name, crest, faction, realm, founding month, size in bands, info text, optionally recruiting status, focus, language; character name only with your own consent “Show my name on the guild page” and a visible Tide Register entry; never rank, note, online status, location, play times, treasury or logs; One Life without names of living characters; info text can be reported, hidden if it contains links or addresses, and hidden after three reports from signed-in accounts within seven days until reviewed; noindex; snapshot deleted immediately); approved by Harald on 20 November 2026. |
| 1.5.11 | 20 November 2026 | Section 15: booking journal per character (time, type, in-game currency amount, operation identifier, items affected; proof of the balance and protection against double booking) with retention: operation details such as source, guild, gross amount and share, class, level and realm after 90 days, the booking itself until the account is deleted; Guild Share aligned. |
| 1.5.10 | 20 November 2026 | Section 15: Guild Share (rate 0 to 10 percent, from level 10, only coins looted from foes; one line per share in the economy log for 90 days, cash book without reference to the character and merged into daily totals after 90 days, booking in the character's booking journal until account deletion, own totals until leaving or deletion, guild weekly totals eight weeks, data export); approved as recommended on 20 November 2026. |
| 1.5.9 | 19 November 2026 | Section 17: channel tag via in the visit counter (fixed list, daily count per channel without personal reference, also on waitlist or newsletter sign-up, nothing stored on the entry, no cookies); approved by Harald on 19 November 2026. |
| 1.5.8 | 19 November 2026 | Section 15: guilds (membership, note, “Show me online” switch, invitations, charter signatures, guild log 90 days, “Chancery Talk” channel not stored, own report reason) and guild bank “Guild Strongbox” (money and item movements with character and time, item log 90 days, money log while the guild exists and 90 days afterwards, daily counters 2 days, receipts 7 days, data export); approved by Harald on 19 November 2026. |
| 1.5.7 | 16 November 2026 | Section 15a: second consent level “In detail” in the Tide Register (appearance, equipped items with rarity and item level, talent choices; separate consent only in the account with no preselection, visible to everyone, One Life renewed at most weekly, immediate withdrawal). Section 9: reports about character pages and profile cards, measures against characters (hiding, rename with 90-day name reservation, muting, suspension; periods and data export); approved by Harald on 16 November 2026. |
| 1.5.6 | 16 November 2026 | Section 15a: Tide Register search (start of name, filters for realm, race, class, level; released characters only, ordered by name only, rate limiting without storing search terms); approved by Harald on 16 November 2026. |
| 1.5.4 | 15 November 2026 | Section 5: shared issue source without recipient linkage; anonymised technical open and click recording by Brevo, no analysis; approved by Harald on 15 November 2026. |
| 1.5.3 | 15 November 2026 | Section 5: independent newsletter sign-up on the newsletter page and in the footer, without a waitlist entry; approved by Harald on 15 November 2026. |
| 1.5.2 | 10 November 2026 | Section 15: improving the introduction to the game from existing records as daily counts of at least five accounts, objection via the telemetry switch. |
| 1.5.1 | 9 November 2026 | Section 12: consent per answer for follow-up questions, 90 days, withdrawal in the account, admin view and delivery log. |
| 1.5.0 | 9 November 2026 | Section 12: optional short questionnaires after the first session and the first week, linked to the account, with aggregated evaluation, export and deletion. |
| 1.4.9 | 7 November 2026 | Section 5: voluntary newsletter with separate consent, double opt-in, proof of consent, one-time invitation, immediate unsubscription and retention; newsletter included in the delivery log. |
| 1.4.8 | 6 November 2026 | Section 12: private “My reports” page and one-time status mail when a report is marked fixed. |
| 1.4.7 | 6 November 2026 | Section 12: staff may publish a short title they wrote themselves and the coarse status of a bug report on the public “Status” page; text and reporters remain private, an empty short title means private, ideas and automatic reports are never public. |
| 1.4.6 | 6 November 2026 | Section 12: feedback from inside the game (“/bug”, “/idea”, Help menu): text, category, realm, character, zone, position, build, time; automatic crash report without free text; notification of the project lead without text and position; processing status and internal note; retention unchanged at 90 days. |
| 1.4.5 | 6 November 2026 | Section 15: in-game mail (purpose, legal basis, retention, access only through a report, export, deletion, One Life to Haven transfer). |
| 1.4.4 | 3 November 2026 | Section 5: delivery log of mails (hash and shortened address, type, response code, 90 days) and resending the waitlist confirmation. |
| 1.4.3 | 1 November 2026 | Sections 3 and 5: independent daily funnel counts and rounded Web Vitals by coarse width class without identifiers, 400 days; local “bar closed” preference. |
| 1.4.2 | 1 November 2026 | Section 12: one-time alpha service emails, triggers, unsubscribe and delivery jobs. |
| 1.4.1 | 1 November 2026 | Section 15: loot, roll, quest and vendor records with 90-day retention, optional hourly playtime telemetry, daily cache without personal identifiers and manual review. |
| 1.4 | 30 October 2026 | Sections 3 and 17: page views are confirmed by a small script of our own (short-lived identifier valid only for the view, no cookie, nothing stored in the browser, no reading of device characteristics, no third parties); views without confirmation are counted separately as “unconfirmed”. “Without script” removed. |
| 1.3.10 | 29 October 2026 | Section 15: standing with factions, hourly counters for abuse review (flag only, no ban, 90 days), standing in the data export without hourly counters. |
| 1.3.9 | 19 October 2026 | Section 15: stored last logout and rounded friends display; per-character area switch, One Life never reveals a location. |
| 1.3.8 | 19 October 2026 | Section 15: inspecting other characters (name, level, race, class, appearance, equipped items up close; “Hide my equipment from others” per character; One Life reveals no location or activity; only the switch setting is stored, requests are not logged). |
| 1.3.7 | 15 October 2026 | Section 15: pseudonymous mobile diagnostics, fields, 30 days, telemetry opt-out, no IP or browser identifier. |
| 1.3.6 | 12 October 2026 | Section 15: separate rules explained, map cells only from five characters, record lists only from ten participants with opt-in; realm totals still rounded separately. Thresholds clarified: map cells from five characters, realm totals below ten rounded, record lists from ten participants by opt-in; the earlier sentence on leaderboards on One Life is replaced by the opt-in rule. Section 6: CSRF cookie also set without signing in for forms (registration, waiting list, support), purely technical, no tracking. |
| 1.3.5 | 12 October 2026 | Section 15: playtime per character for private display in the game and in your own data export, never publicly. |
| 1.3.4 | 10 October 2026 | Section 19: SEPA direct debit not offered for now, to follow after verification; payment methods one-off card and EPS, monthly card only. |
| 1.3.3 | 10 October 2026 | Section 3: backups (daily, encrypted, 14-day rotation; deletions take effect in the backups after 14 days at the latest). |
| 1.3.2 | 10 October 2026 | Section 3: searches without an answer (normalized query without numbers and addresses, at most 80 characters, daily counter without IP, session or account; visible in the administration only from three occurrences; deletion after 90 days). |
| 1.3.1 | 10 October 2026 | Section 2: data export in the account (“My data”, JSON file, once per hour, without password hash and tokens). |
| 1.3 | 10 October 2026 | Sections 3 and 17: own visit counter without cookies, script or third parties instead of “no audience measurement” (figures per day, path, language, country and referring website; visitors approximated with a daily hash deleted after one day; no IP addresses, no log of individual requests; legal basis Art. 6(1)(f) GDPR; daily figures 400 days; objection by e-mail). |
| 1.2 | 10 October 2026 | Section 15: paragraph “World map on the website” (not yet in operation): rounded numbers once a minute without personal reference, no cookies, names in the chronicle only with consent, retention 7 days, later stages with information about individual characters only with consent, not under 16 and never for living One Life characters, transparency list. |
| 1.1.1 | 9 October 2026 | Section 19: pricing model corrected (one-time purchase planned, no subscription, no pay-to-win; a donation is not a pre-purchase), payment methods listed (card incl. Apple Pay and Google Pay, EPS, SEPA direct debit), payment method provider and bank as independent controllers, payee. |
| 1.1 | 9 October 2026 | New section 19 Support (donations via Stripe Checkout, supporter list with consent, thank-you mail, retention, transfers to the USA); status and changes now section 20. |
| 1.0 | 9 October 2026 | First complete version: all retention periods set, portal additions (passkeys, notifications, reports, moderation, memorials, devlog images, closed alpha, game moderation, Discord) placed as regular sections, Cloudflare Email Routing added, forum posts after account deletion anonymised or deleted on request. |
Legal review by counsel pending; adjustments will follow.