Privacy Policy
Last updated: November 10, 2026
Contents
- 1. Who is responsible for your data
- 2. The short version
- 3. How we recognise your account
- 4. What we process, why, and on what legal basis
- 5. Who we share data with
- 6. Where the data is
- 7. How long we keep data
- 8. Your rights
- 9. Deleting your account
- 10. Children
- 11. Security
- 12. Changes to this policy
- 13. Contact
1. Who is responsible for your data
The controller of personal data of Bell of Ash (“the Game”) players is Tobias Bak - Software Development (BakIT), Im Oberdorf 13a, 36399 Freiensteinau, Germany. Contact for data protection matters: info@bellofash.pl.
We have not appointed a data protection officer — we are not required to.
2. The short version
- The Game never asks for your name, e-mail address or phone number. Accounts have no passwords.
- You can play offline — nothing leaves your phone then. Data reaches the server only when you use online features (online Camp, chat, Order, Ash Bazaar, rankings, notifications, purchases).
- The Game server is located in Germany. Only the data needed for notifications, purchases and Play Games sign-in (Google, Apple) may leave the European Economic Area (section 6).
- On iPhone and iPad the Game links your account to Game Center, and on Android to Play Games (Google Play Games) — if you are signed in there. That way, after reinstalling or on a new device of the same platform, you get your progress back. We take only the identifier from these services — no profile name, picture, e-mail address or friends.
- No ads, no advertising identifiers, no third-party analytics. We collect the Game's errors and crashes ourselves, on our own server, without a player identifier.
- We count anonymous statistics — how many people visit the Shop, what they look at and buy, and how many players come back to the Game after a few days — only as daily totals, without a player number. You can turn them off in Options (“Anonymous statistics”).
- Discord is a separate service, under Discord's rules — the Game works without it. If you use the “Translate” translator on our Discord server, we translate the selected message on our server in Germany and keep its text only in memory, for at most 15 minutes (section 4).
- You can delete your account yourself in the Game (Options → Account → Delete account) — immediately — or by an e-mail request described on this site (within 30 days).
3. How we recognise your account
The first time you enter the Camp, the Game draws a player identifier on your device — the prefix boa- followed by 32 random characters. It is not a phone number, a serial number or any identifier issued by Android or iOS: it comes from a random number generator and is stored only in the app's storage on your device and on our server as the account key.
Worth knowing: whoever has that identifier has access to the account. Uninstalling the Game or clearing the app's data erases the identifier and — unless the account is linked to Game Center or Play Games (below) — may cut you off from your progress for good. We will never ask you for this identifier — do not give it to anyone, including someone who claims to be us.
The server gives the account its own player number (shown in Options → Account). You give it to us with requests (section 8), and when you buy something the Game passes it to the store so that the purchase lands on the right account (section 4, “Purchases”).
Game Center and Play Games. At launch the Game tries to sign in to Game Center (Apple — on iPhone and iPad) or to Play Games (Google Play Games — on Android). Sign-in happens in Apple's or Google's own window and under their rules, and they then know that you play Bell of Ash. You can decline — you then keep playing as before and can link the account later in Options → Account → Progress backup. If you sign in, our server stores the Game Center or Play Games identifier with your account (section 4) as a second key to the account. After reinstalling the Game, or on a new device signed in to the same Game Center or Play Games, you return to the same account and progress, and on several devices at once you play on one account. This works only within one platform — it does not move an account from Android to iPhone or the other way round.
If the Game Center or Play Games identifier already belongs to another Game account, the device switches to that account: the player identifier from this device is assigned to that account, and the Game data stored on the device is replaced with the account's state from the server. The account you had been playing on with this device is deleted only if it is new and empty (no progress and no purchases). If it has progress or purchased Tears, we do not delete it — it stays on the server, without the login key from this device, together with a short record of the switch (section 4), so that at your request its contents can be moved to the account you play on now, or it can be deleted (section 8).
4. What we process, why, and on what legal basis
| Data | Purpose | Legal basis (GDPR) |
|---|---|---|
| Player identifier, player number, technical account name, creation and last login date | so the account exists and you can return to it | Art. 6(1)(b) — performance of a contract (the Game's terms) |
| Game Center and Play Games (only if you are signed in to the service): on iPhone and iPad, the identifier Apple assigns to your Game Center account for the games of one developer; on Android, your Play Games player identifier in Bell of Ash. To check that the identifier is yours, the Game sends the server a one-time Game Center signature (the server verifies it with Apple's public key) or a one-time Play Games code (the server exchanges it with Google for the identifier). We do not store the signature, the code or Google's access token — for about 20 minutes the server keeps only a hash of the used signature in working memory, so that nobody can use it a second time. We do not fetch the profile name, picture, e-mail address or friends list from Game Center or Play Games (along with the identifier, Google also returns, among other things, the Play Games profile name and picture — we discard them without storing them); you choose your character name in the Game. When switching to another account (section 3) — a record of the account that stayed on the server: which account the device moved to, when, through which service, the number of purchases and the reason it was kept | keeping progress off the device: returning to the account after reinstalling the Game or on a new device of the same platform; protection against taking over someone else's account; moving the contents of a kept account, or deleting it, on request | Art. 6(1)(b); the record of a kept account — Art. 6(1)(f) (so that progress and purchased Tears are not lost) |
| Game progress: characters, levels, gear, currencies (gold, Bell Tears, Shards), talents, achievements, Season Pass, the state of the Vigil Seal (its days and the Tear portions collected), expedition log | keeping progress on the server, shared across devices and resistant to cheating | Art. 6(1)(b) |
| Character names — visible to other players in chat, in the Order, at the Bazaar and in rankings | recognising players in social features | Art. 6(1)(b) |
| Friends: friend list, sent and received requests, highest number of friends at once (Chronicle deed), Order invitations from friends; the server's technical notifications about a friend request and about being added to an Order (the sender's technical account name, the Order's name) | the friend list; a friendship starts only once a request is accepted. Friends see each other's name, class, level, best floor and CP of the last played character, and in the character preview — equipped gear, Wings, Awakening and worn cosmetics (never the Stash, gold or materials) | Art. 6(1)(b) |
| Last activity: the moment the Game last contacted the server (at least every 2 minutes while the Game is running, also during a run) | the “online” / “last seen …” status shown, among players, only to your friends; members of your Order see whether you are online. An Order member's Game receives the time since your last activity and uses it to arrange the figures in the Order Hall, but does not display it. The moderator sees this moment in the panel. | Art. 6(1)(b) |
| Order: membership, rank, Treasury contribution, completed Tasks, Bell participation. Order members also see the name, class, level, best floor and CP of the last played character, its look (worn cosmetics), your rank and whether you are online. In the Order Hall the figures stand according to rank and last activity. | running guilds and the tournament of Orders | Art. 6(1)(b) |
| Rankings — Book of Glory and the weekly ranking: character name and class, level and Awakening, highest floor, number of bosses slain, dungeon mastery, power (CP), weekly score; in the Book of Glory also the Order's results. Any player can open your character's window: they see its name, class, level, Awakening and power (CP), the Order tag, the names of your other characters and worn cosmetics. A player you have blocked in chat, or one who has blocked you, cannot open this window. The rankings, including the look of the top three places on the podium, are visible to all players, even with such a block. | rankings visible to all players; while an account is banned, its characters disappear from the Book of Glory | Art. 6(1)(b) |
| The Chasm: for each character the unlocked and the best Depth, the time to spare and the moment of the record, the last descent (time, Depth, class, CP, week, result). The weekly ranking shows the character name, class, Depth, time to spare and CP, and on the podium also the character's look; the Book of Glory shows Depth and time to spare. A result above the Depth that the server accepts without a check at the given power goes to a review queue: player number, class, Depth, time, number of enemies slain, CP, limit, week and moment. Until the moderator's decision it stays out of the ranking and opens no further Depths | running the mode and the rankings; fair competition and protection against cheating | Art. 6(1)(b); review queue — Art. 6(1)(f) — our legitimate interest (fair rankings) |
| Chat: message content (global, Order, private), sender (player number and character name), time sent, your character's portrait and name style (class, garb, colour, frame), visible to those reading the channel, the sender's Game language (it helps the translator recognise the message's language; we do not show it to other players), list of private conversations — for both participants: the other person's name and the last message | delivering the chat | Art. 6(1)(b) |
| Chat translations: a player who turns on chat translation in Options sees other players' messages in their own language — so your messages may be translated for such readers, regardless of your own setting. We keep the translation and the detected language with the message so it is not translated twice | letting players from different countries understand each other; translation runs on our own server, the text never reaches a third-party company | Art. 6(1)(f) — legitimate interest (communication between players who speak different languages); for the reader who turns the option on — Art. 6(1)(b) |
| Chat reports and blocks: the reported message, who reported it, the time; the list of players you blocked. For a new report the moderator gets a short notification on their phone: the channel (global, the Order's name or “private conversation”), the reported player's name and up to the first 80 characters of the message — no account identifiers. The notification is delivered by our own notification server (ntfy), running on our server in Germany; no outside company is involved | moderation and a response to every report within 24 hours, player safety, an obligation under store rules | Art. 6(1)(f) — legitimate interest (a safe game environment) |
| Moderation: chat mute, temporary or permanent account ban, change of a character or Order name, removal of Bazaar listings and account deletion on request — each with a reason, an end date and the moderator's note; when handling a report the moderator sees 5 messages before and after the reported one, also in the private conversation where it was sent | carrying out moderation and showing why a penalty was imposed (appeals, disputes) | Art. 6(1)(f) — legitimate interest (a safe game environment) |
| Admin panel activity log: what the moderator did, when and to whom, their IP address and browser, and logins to the panel | evidence of how moderation was carried out and security of the panel itself | Art. 6(1)(f) |
| Ash Bazaar: listings, seller, buyer, mail with items and gold | player-to-player trading | Art. 6(1)(b) |
| Beacons (game invitations): your account's code, whose code was entered and when, for 30 days the days with a cleared floor and the best floor — the inviter sees your character name and this progress | invitations and rewards for active invitees; entering a code makes both players friends straight away | Art. 6(1)(b) |
| Letters from the creators (Mail): letters sent to you or to all players — title, text, a reward in Game currency, materials or cosmetics, the date sent and whether you collected it; in the panel — the list of letters sent to individual players with the recipient's player number and character name | compensation after outages, tournament rewards, gifts | Art. 6(1)(b) |
| Gifts from players: who sent which cosmetic to whom and when, for how many Tears and with which of the 8 ready-made messages (there is no text written by the player); the state of the gift (collected, Tears returned, revoked); a block on sending after a refund that did not take back all the Tears, with the order number and date. The recipient sees the sender's character name and the message. The sender sees whether the addressee can receive a gift and, if not, why, and may learn from the letter returning the Tears that the recipient already owned the item. A moderator sees in the panel the gifts sent and received by a player. | running the feature; enforcing limits, preventing abuse after refunds | Art. 6(1)(b); block and revocation — Art. 6(1)(f) |
| Server notifications (only if you turn them on — permission in the phone's system plus reminders and “Online events” enabled in Options; “Online events” are off by default): your device's notification identifier (on Android a Google Firebase Cloud Messaging token, on iPhone and iPad an Apple notification service token), platform, Game language, the phone's time-zone offset, the time of registration, the number and times of notifications sent; on iPhone and iPad also the reminder plan (times of planned and shown reminders, daily limit, quiet hours), because there the server enforces the shared limit | notifications about a Bazaar sale, a letter from the creators, a friend or Order invitation and the answer to a request to join — with general wording, without other players' names or item names; together with reminders at most two notifications a day and never at night. Expedition reminders are scheduled by the phone itself | Art. 6(1)(a) — consent, which you can withdraw at any time in Options or in the phone's settings (storing and reading the identifier on the device — also § 25(1) of the German TDDDG) |
| Purchases of Bell Tears: the store receipt — on Android the purchase confirmation from Google Play, on iPhone and iPad the signed App Store transaction (including the order or transaction number, the product, time and state of payment, the store's country); the result of verifying the receipt with the store; a settlement marker (account, product — Tear pack, Vigil Seal or Welcome Pack, number of Tears credited, the look added from the Welcome Pack, the days of the Vigil Seal, time of purchase, test or real purchase, any refund). When you buy, the Game passes your player number to the store. Once an hour we ask Google and Apple whether any purchase has been refunded — if so, we take back the Tears credited for it, down to zero at most (for the Welcome Pack also its look, for the Vigil Seal also the Tears collected from its days, and the Seal is shortened) | confirming the purchase and crediting Tears, preventing reuse of the same receipt, handling refunds and complaints, accounting | Art. 6(1)(b); keeping proof of purchase — Art. 6(1)(c) (accounting obligations); checking refunds — Art. 6(1)(f) (protection against abuse) |
| Error and crash reports: the error description and the place in the Game's code, Game version (build and patch), platform and system version, device model, graphics chip, amount of memory, Game language, the last Game screen, play time in the session (rounded), the latest entries of the Game's technical log, and after an unexpected shutdown on Android — the reason given by the system (e.g. crash, out of memory). We store a report without a player identifier and without a character name, round its time to the full hour and strip numbers, identifiers and e-mail addresses from the text. The Game sends reports only after logging in to the server; the server counts the daily limit on reports per account only in working memory, without storing it in the database | finding and fixing bugs in the Game | Art. 6(1)(f) — legitimate interest (a working, stable Game) |
| Gameplay statistics: how long a floor took, the wave a run ended on and why, the type of run, rerolls in the Labyrinth (how many, how much gold they cost, on which floor) | tuning the pace of the Game — we want to know whether a floor drags on; the numbers go into a daily aggregate counter, with no player identifier | Art. 6(1)(f) — legitimate interest (developing the Game) |
| Shop and return statistics (“Anonymous statistics”): how many times the Shop was opened and how many different accounts opened it on a given day, which Shop tabs were chosen, which cosmetics were previewed, how many purchases were started and completed per item (cosmetics for Bell Tears, Season Pass, Tear packs, Vigil Seal, Welcome Pack) and how many Tears were spent on each item; how many accounts were created on a given day and how many of them came back to the Game after 1, 3, 7, 14 and 30 days (or later). The server stores only daily totals, with no player identifier or player number; it tells accounts apart (to count distinct people and enforce daily limits) only in working memory, without writing it to the database. To count returns, we store with your account — next to the moment of your last activity — the day the account was created and which day thresholds you have already reached. Test accounts are not counted | assessing and improving the Game and the Shop's offer — we want to know what players look at, what they buy and whether they come back. Our own server does the counting, with no outside company, no Google Analytics and no ads | Art. 6(1)(f) — legitimate interest (developing the Game and its offer). You can object (Art. 21 GDPR): turn off the “Anonymous statistics” switch in Options (on by default). The Game then stops sending Shop counters, and the server leaves your account out of the return figures and the purchase counters — it stores only an objection flag with the account |
| Game updates: at launch and from time to time the Game asks our server whether a new fix is available and downloads it — the request contains only the platform and the Game's version number, no player identifier; the update server does not store IP addresses | delivering fixes without waiting for a new version in the store | Art. 6(1)(b) |
| Server logs: IP address, time and type of request — in the logs of the Game server, the reverse proxy and this website. For some events the Game server's logs also contain the player number, a character name or an Order name: purchase and refund (with the order number), Bazaar trade (buyer and seller), sending a gift (the numbers of both players, the cosmetic, the price), entering a Beacon code, a chat report (reporter and author of the message), setting a character name, founding and handing over an Order, anti-cheat checks of runs, of the Bell and of the Chasm, linking an account to Game Center or Play Games and switching a device to another account (the numbers of both accounts), moderation actions, account deletion and server errors | security, fault diagnosis, protection against abuse, handling complaints | Art. 6(1)(f) |
| Backups: a daily copy of the Game's entire database on our server and a daily copy of that server's entire disk (database copies included) at Hetzner; occasionally also a manual copy of the database on the server administrator's computer | restoring the Game after a failure or loss of the server | Art. 6(1)(f) |
| Translator on the Game's Discord server (“Translate”; only if you use it): when you choose Apps → Translate on a message, or the button for another language under a translation, Discord sends our translator the content of that message (including embeds and a forwarded message), your Discord account identifier and your Discord language, along with the data it attaches to every such request (such as your account name, your roles on the server, details of the message's author, and the server and channel identifiers) — we do not use or store the latter. The text is translated by a program on our own server (the same one as for the Game's chat), and the translation goes back to Discord as a reply only you can see. That is why anyone who uses the translator can have your messages on the Game's Discord server translated. We keep the message text only in working memory, so that the buttons for other languages work, and the account identifier only for the limit (at most 8 translations per minute). For each use, the service log records only the kind of request, the target language, the duration and the result — no content and no identifiers | communication between server members who speak different languages; the limit protects the translator from abuse; the translation runs on our own server and the text reaches no company other than Discord | Art. 6(1)(f) — legitimate interest (communication between members of the Game's community who speak different languages) |
| The Game's Discord community server (“Bell of Ash”): messages, forum posts (bug reports, suggestions, help) and the roles chosen on joining (languages, platform, favourite class) are visible to the server's members, and to us — its owner and moderators — also when moderating. Discord's AutoMod blocks messages with offensive words, spam, mass mentions and invites to other servers, and reports a blocked message (with its content and author) in a channel only the team can see. Moderators can delete messages, warn, time out and remove members from the server, and they take reports of rule-breaking in direct messages. You give your player number in a bug report voluntarily, and all members of the server can see it — we can use it to find your account in the Game and look into the bug. This data is stored by Discord; the only data that reaches our servers from Discord is what the translator row describes | running the Game's community, moderation and members' safety, receiving bug reports and suggestions | Art. 6(1)(f) — legitimate interest (the Game's community and a safe place to talk); beyond that — Discord under its own rules (section 5) |
Separately, the app stores may show us their own aggregated crash and performance statistics (Google Play — Android vitals, Apple — App Store Connect). They collect these themselves, under their own rules and according to your phone's settings; we receive no player identifier with them.
What we do not collect
Names, e-mail addresses, phone numbers, postal addresses, dates of birth, phone contacts, photos, location (GPS), advertising identifiers, the list of installed apps, microphone or camera recordings. The Game shows no ads and contains no advertising or analytics libraries — on Android the only third-party libraries are the Google Firebase Cloud Messaging notification library (without Google Analytics), the Google Play billing library and the Play Games library (Google Play Games Services) — for sign-in only; on iPhone and iPad the Game uses Apple's system services (including Game Center). We do not profile players and make no automated decisions with legal effects.
We never see payment details
Payment is handled entirely by the app store (Google Play or the App Store) under its own rules — for that part the store is a separate controller and its own privacy policy applies. Card numbers, billing addresses and bank details go to the store, not to us. All we receive is the receipt, which we verify with the store operator to confirm the purchase is genuine, and information about refunds.
5. Who we share data with
- Hetzner Online GmbH (Germany) — the provider of the server the Game runs on (together with our notification server for the moderator) and of the copies of that server's entire disk. A processor.
- Google (Google Ireland Limited, Google LLC) — on Android, only if you turn notifications on: the Firebase Cloud Messaging service delivers notifications from the server to the phone and receives the phone's installation identifier, notification token, the notification content and basic technical information about the device and the app that the Firebase library sends by itself (such as the system version, device model and brand, installation source and library versions) — a processor. For purchases in Google Play: verification of the receipt and of refunds, and the player number passed at purchase; for the payment itself Google is a separate controller. On Android, when you sign in to Play Games: Google runs the sign-in on your phone under its own rules — to that extent Google is a separate controller. The Game receives a one-time code from Google; our server passes it to Google and receives the Play Games identifier in return. The Play Games library also sends Google analytics and diagnostic data about its own operation by itself (according to Google, for the library's stability and to improve the service); to that extent Google acts under its own rules.
- Apple (Apple Distribution International Ltd., Apple Inc.) — on iPhone and iPad, only if you turn notifications on: the Apple Push Notification service (APNs) delivers the notification and receives the device's notification identifier and the notification content. For purchases in the App Store: verification of refunds and the player number passed at purchase; for the payment itself Apple is a separate controller. On iPhone and iPad, when you are signed in to Game Center: Apple runs the sign-in on your device under its own rules — to that extent Apple is a separate controller. Apple signs the Game Center identifier, the Game sends it with the signature to our server, and the server verifies the signature with a public key downloaded from Apple's server — Apple receives none of your data from us in the process.
- Discord (Discord Netherlands BV, the Netherlands — for people in the European Economic Area; elsewhere Discord Inc.) — the Game's community server and the “Translate” translator run on the Discord service. Discord processes your Discord account, messages, roles, reports to Discord and whatever Discord itself collects when you use the server as a separate controller, under its own rules — its privacy policy applies. We are responsible for what our translator receives and for moderating our server (section 4). Our translator sends back to Discord only the finished translation.
- Public authorities, where the law requires it.
We do not sell player data and do not share it with marketing companies.
6. Where the data is
The Game's data sits on a server in a data centre in Germany. The database copies are there too. Copies of the server's entire disk are kept by Hetzner, and manual database copies sit on the server administrator's computer. Data may leave the European Economic Area only in these cases:
- notification data — Google (Android) and Apple (iPhone, iPad) may process the notification identifier and the notification content in the USA as well. The basis is the European Commission's adequacy decision of 10 July 2023 under the EU-US Data Privacy Framework (both companies are certified under it), supplemented by standard contractual clauses;
- Play Games sign-in data — exchanging the one-time code for the Play Games identifier means a request to Google's systems (Google LLC), which may process it in the USA as well; the basis is the same as for notification data;
- data from the Game's Discord server — Discord processes it (including translations sent back by our translator) under its own rules, in the USA as well, as described in Discord's privacy policy; the translator itself runs on our server in Germany;
- purchase data — verifying a receipt or a refund means a request to Google's or Apple's systems, which operate globally under their own compliance mechanisms.
7. How long we keep data
| Data | Period |
|---|---|
| Account and Game progress | until you delete the account — we do not remove unused accounts automatically |
| Game Center or Play Games identifier stored with the account | until the account is deleted — the link disappears with the account and the identifier becomes free again |
| Hash of a used Game Center signature | about 20 minutes, only in the server's working memory (a server restart erases it sooner) |
| Account kept when switching to Game Center or Play Games (section 3) and the record of the switch | like any account — until it is deleted, at your request (section 8); we do not remove unused accounts automatically; the record of the switch disappears together with that account |
| Chat messages and their translations | the Game shows only messages from the last 14 days (up to 100 per channel); older ones stay on the server and nobody sees them any more; we delete your messages together with your account when you delete it — from all channels, including private conversations and the chats of Orders you once belonged to, together with your entry in other players' conversation lists; a translation disappears with its message. Messages from other players in conversations with you remain until their accounts are deleted (section 9). |
| Chat reports | 12 months after being resolved — we need them to judge repeated violations; then the server deletes them by itself |
| The moderator's notification about a report | on our notification server (ntfy) — only in a short cache until delivery (at most 12 hours); on the moderator's phone — until the moderator deletes it |
| Penalties (mute, account ban) | until the penalty ends; the penalty history — until the account is deleted |
| Admin panel activity log | 24 months; logins to the panel (including failed ones) — 90 days |
| Bazaar listings and mail | a listing expires 48 hours after it is posted; mail — until the player collects it |
| Friends and last activity | until the friendship (also by blocking the player) or the account is removed; for activity we keep only the latest moment — each new one overwrites it; an Order invitation expires after 7 days; the server's technical notifications about invitations are deleted by the daily data clean-up once they are more than a day old, and immediately when the account is deleted |
| Rankings (Book of Glory, weekly ranking) | until the account is deleted |
| The Chasm — records and results in the rankings | until the account is deleted |
| Review queue for Chasm results | until the moderator's decision, an account ban or the account's deletion; at most the last 200 entries, one per character and week; there is no fixed period in days; the decision remains in the admin panel log |
| Contribution to the Order Bell (weekly points stored with the player number, without a character name) | until the summary of the closed week and the clean-up after it, also after the account is deleted; only the Order's result remains in the summary, without player numbers |
| Letters from the creators | an uncollected letter expires after the period stated in the letter (usually 30 days, at most 90 days); the mailbox (the last 40 letters) and the sent list in the panel — until the account is deleted |
| Gifts | an uncollected gift waits for 10 years; the list of gifts sent and received (at most the last 300 entries of each kind) and the block after a refund — until the account is deleted; after the sender's account is deleted, gifts stay with the recipients without the sender's character name, and the sender's account number disappears from other players' lists; and the account numbers of players with whom gifts were exchanged, until the account is deleted (needed to remove these entries as well when an account is deleted) |
| Notification identifier and reminder plan | until you turn notifications or “Online events” off in Options, withdraw permission on the phone (at the next launch of the Game with internet), Google or Apple invalidates the identifier, the account is deleted, or after 60 days without launching the Game online; the sending counters (the last time each kind of notification was sent and the number sent in the current day) and, on iPhone and iPad, the list of times of the latest notifications sent (at most 20) disappear together with the identifier |
| Purchase receipts and markers | until the end of the fifth year after the year of purchase (a purchase from 2026 — until 31 December 2031), also after the account is deleted; then the server deletes them by itself |
| Error and crash reports (no player identifier) | 90 days after the last occurrence of the given error; the last 5 reports are kept per error; on the phone a report waits in a queue (at most 20) until it is sent |
| Gameplay, Shop and return statistics (daily totals, no player identifier) | kept indefinitely — the totals themselves are not personal data; after an account is deleted, its earlier visits and purchases remain in them, with no trace of whose they were |
| Account creation day, return thresholds reached and objection flag (with the account, for the return statistics) | until the account is deleted |
| Game server logs (IP address and, for the events listed in section 4, also the player number, a character name or an Order name) | until overwritten automatically: the log of each Game service holds at most 60 MB (3 files of 20 MB) — the oldest entries disappear as new ones arrive, and the whole log of a service disappears when a new version of it is deployed. There is no fixed period in days; entries remain until overwritten even after the account is deleted |
| Reverse proxy and website logs (IP address, time and type of request) | for as long as needed for the purposes in section 4 (security, diagnosis); there is no fixed period in days |
| Backups | Database copies on the server: 14 daily and 8 weekly. Copies of the entire disk at Hetzner: 7 daily, with everything that was on the disk at the time (including database copies and logs). Manual database copies on the server administrator's computer: we delete them no later than 9 weeks after they are made. Data deleted from the server (including a deleted account) disappears from the last copy after about 9 weeks at the latest; we restore copies only after a failure and during a restore test in a temporary container, which we delete straight away |
| Text of a message passed to the translator on Discord | only in the translator service's working memory — at most 15 minutes after its last use (that is how long the buttons for other languages work), at most the last 500 texts at a time; a restart of the service erases it sooner; it is never written to disk |
| Discord account identifier (translation limit) | only in working memory — we count only uses from the last minute; an identifier not used in that time disappears at the next clean-up (every minute) |
| Messages, posts and roles on the Game's Discord server, AutoMod notices in the team channel | with Discord, under its rules — until you delete them yourself or a moderator deletes them; we do not delete AutoMod notices automatically (there is no fixed period) |
8. Your rights
You have the right to access your data and obtain a copy, to rectification, erasure, restriction of processing, data portability, and to object to processing based on our legitimate interest. You can withdraw consent to notifications at any time in Options or in the phone's settings — this does not affect the lawfulness of notifications sent before. Send your request to info@bellofash.pl — we reply within one month.
Because we do not know your name or e-mail address, we need your player number (Options → Account) or a character name (if you have several, all of them) to handle the request; without it we cannot link the request to an account and, under Art. 11 GDPR, we may refuse to act on it. We do not link error and crash reports or statistics totals (gameplay, Shop and returns) to accounts, so we cannot identify or delete them at the request of a particular player. The easiest way to object to the Shop and return statistics is the “Anonymous statistics” switch in Options — it takes effect immediately, for the future; totals added earlier remain, because it is no longer known whose they are.
If, when switching to an account with Game Center or Play Games, your earlier account stayed on the server (section 3), write to us — we will move its contents, above all purchased Tears, to the account you play on now, or delete it; please give us the player numbers of both accounts if you know them, or the character names.
You exercise your rights regarding data on Discord (account, messages, roles) primarily with Discord, under its privacy policy. You can also ask us to delete messages from the Game's Discord server, or to tell you what our moderation did with your messages — please give us your Discord account name. The translator does not store your data, so there is nothing from it for us to hand over or delete.
You also have the right to lodge a complaint with a supervisory authority, in particular in the country where you live or work — in Poland, the President of the Personal Data Protection Office (ul. Stawki 2, 00-193 Warsaw). The authority competent for the Game's creator is the Hessian Commissioner for Data Protection and Freedom of Information (Hessischer Beauftragter für Datenschutz und Informationsfreiheit, Wiesbaden, Germany).
9. Deleting your account
You delete your account together with progress, character names, friends, your chat messages (from all channels, including private conversations and the chats of former Orders) and their translations, Bazaar listings, letters from the creators, gifts (the list of those sent and received; gifts you sent to others stay with them, without your character name), ranking entries, the notification identifier, the link to Game Center or Play Games and Order membership in the Game (Options → Account → Delete account) — immediately — or by an e-mail request described on this site — within 30 days. If you lead an Order, leadership passes automatically to the highest-ranking member, and an Order with no other members is dissolved.
Deleting the account also unlinks it from Game Center and Play Games: after reinstalling, the Game creates a new, empty account, which may link to the same Game Center or Play Games. An account kept earlier during a switch (section 3) is a separate account — deleting the current one does not cover it; you can request its deletion by e-mail (section 8).
Deletion is irreversible. Only the following remain:
- purchase receipts and markers — until the end of the fifth year after the year of purchase (section 7);
- moderation reports filed by other players in which your message is the evidence, and reports you filed yourself — deleted 12 months after being resolved;
- admin panel log entries about the moderator's actions concerning your account (among others penalties, change of character name, corrections of currencies and items, letters, revoking a gift, decisions on Chasm results, refunds) — stored with the account number, but without the character name, message text and moderator's note: only “what and when” remains, with the data of that action, as evidence of how moderation was carried out (deleted after 24 months);
- your contribution to the Order Bell — points stored with the deleted account's number, without a character name, as part of the Order's result — until the summary of the closed week and the clean-up after it (section 7);
- gifts sent to other players — stay with the recipients, until their accounts are deleted: the cosmetic, price, date and a ready-made message chosen from 8, without your character name and account number, sometimes with a marker that the moderator may revoke them because the money for the Tears came back to you;
- Order invitations sent by you — with the invited players, with your character name, visible for at most 7 days from sending;
- messages that other players wrote to you — these are their messages, and the record of the conversation contains your account number; until their accounts are deleted;
- entries in the server logs (section 7) — until they are overwritten automatically;
- database backups made before the deletion — until they are overwritten or deleted, after about 9 weeks at the latest;
- error and crash reports and statistics totals (gameplay, Shop and returns) — they are not linked to the account.
A name previously taken away by moderation stays reserved so that nobody can impersonate your character, but after deletion it no longer points to your account. Purchase records kept by Google and Apple remain with the stores under their own rules. Deleting your Game account does not cover your messages on the Game's Discord server — that is a separate service (section 8).
10. Children
The Game is not directed at children. It includes open chat with other players, so we intend it for people aged 16 and over. We do not knowingly collect data from children below that age; if a guardian finds that a child has created an account, please contact us and we will delete it.
11. Security
The connection between the Game and the server is encrypted (HTTPS/TLS). Administrative access to the server and the database goes exclusively through a private VPN and SSH keys, with no panels exposed to the public internet. The database is not reachable from outside, and we download database copies from the server only over an encrypted connection (SSH). We store no player passwords, because the Game does not use any.
12. Changes to this policy
We may change this policy as the Game develops — for example when a new online feature arrives. The current version always sits on this page together with the date of the last change. We will announce significant changes in the Game.
13. Contact
Tobias Bak - Software Development (BakIT), Im Oberdorf 13a, 36399 Freiensteinau, Germany · info@bellofash.pl