Last updated: 30 October 2026
The controller of data associated with Dicesmith and its tester feedback forms is Sebastian Gawliński, the game’s creator. Privacy contact: dev.dejmos@gmail.com.
The game uses Firebase Crashlytics to identify and fix errors. Crash reports are sent independently of the player’s choice about optional gameplay analytics. They may contain technical details of a crash, the game and Android versions, device model, and installation identifiers used by Firebase. Diagnostic context is also added to reports, such as the active screen, expedition stage, logical game state, and balance version.
Names, email addresses, and complete game saves are not added to crash reports. The legal basis is the controller’s legitimate interest in maintaining the game’s stability and fixing errors (Article 6(1)(f) GDPR). According to Firebase, crash report data and associated identifiers are retained for 90 days, after which removal from live and backup systems begins.
Google Analytics for Firebase is enabled only after the player gives consent. It collects structured events concerning, among other things, the tutorial, runs, battles and turns, offered and selected rewards, forge upgrades, language changes, as well as ad offers being shown, rewarded ads being watched, the Blacksmith’s Chest being opened, and the Blacksmith’s Seal offer being viewed. Events may include the stage, enemy type, battle outcome, number of turns, HP, gold and crystal values, skill types, and a representation of how faces are distributed across individual dice. A random run identifier links events from one run; it is not a player name or account identifier. Google Analytics may also process its own installation identifiers and device information.
Names, email addresses, free text entered by players, payment data, and complete game saves are not sent in these events. Advertising ID collection by Google Analytics is disabled in the app configuration (the Advertising ID is used only by Google AdMob, described below).
The legal basis for this analytics collection is the player’s consent (Article 6(1)(a) GDPR). Consent may be declined or the choice changed at any time in Options → Privacy and analytics. Withdrawing consent stops the collection of future events; it does not automatically erase data already sent. The retention period for event-level data depends on the Google Analytics setting and may be up to 14 months. Aggregated reports may remain available for longer.
The game shows ads provided by Google AdMob: rewarded ads that players watch voluntarily (for example, to double crystals or to open the Blacksmith’s Chest), and full-screen ads shown between expedition stages and when returning to the menu. Players who have bought the Blacksmith’s Seal do not see full-screen ads.
To serve ads, measure their performance, and prevent fraud, Google AdMob may collect: the device’s advertising identifier (Android Advertising ID), the IP address and the approximate location derived from it (country, region), device and operating system information, information about interactions with ads (impressions, clicks), and diagnostic data. The game does not pass names, email addresses, or game saves to AdMob.
In the European Economic Area, the United Kingdom, and Switzerland, the game shows Google’s consent form (User Messaging Platform) before ads are first shown. Personalised ads, based on the advertising identifier and profiling, are shown only with consent (Article 6(1)(a) GDPR). Without consent, non-personalised or limited ads may be shown; in that case data is processed to the extent necessary on the basis of the legitimate interest in funding a free game, preventing fraud, and counting impressions (Article 6(1)(f) GDPR). The choice can be changed at any time in Options → Privacy and analytics → Ad settings. The advertising identifier can also be reset or deleted in Android system settings.
Google processes advertising-related data as an independent controller under its own privacy policy. More information: https://policies.google.com/technologies/partner-sites and https://policies.google.com/technologies/ads.
The Blacksmith’s Seal can be bought once in the game. Payment is handled entirely by Google Play; the game’s creator does not receive card details or any other payment data. The game checks with Google Play whether the Seal has been bought and stores this information locally on the device to enable its effects and allow the purchase to be restored. In the Google Play Console, the creator can see order information such as the order ID, product, date, country, and price, which is needed to handle refunds and accounting.
The legal basis is the performance of a contract (Article 6(1)(b) GDPR) and legal obligations related to accounting (Article 6(1)(c) GDPR). Order information is retained for the period required by tax and accounting law. Google’s processing of payment data is described in the Google Payments privacy notice: https://payments.google.com/payments/apis-secure/u/0/get_legal_document?ldo=0&ldt=privacynotice.
Answers voluntarily submitted through a feedback form are used to understand players’ experiences, diagnose problems, and improve Dicesmith. The form contains ratings and optional open-ended questions. It does not require a name or email address. Please do not enter personal information, information about other people, or sensitive information. If information that could identify a respondent is nevertheless provided, it will be used only for the purposes described above.
The legal basis for processing such information is the controller’s legitimate interest in analysing feedback and improving the game (Article 6(1)(f) GDPR). Responses are stored in Google Forms and, if a form is linked to a spreadsheet, also in Google Sheets. They are removed from both locations no later than 12 months after each response is submitted.
Google processes technical and analytics data as the provider of Firebase and Google Analytics. Advertising-related data is processed by Google as the provider of Google AdMob, and payments are handled by Google Play. Feedback responses are processed using Google Forms and Google Sheets. Access to responses on the game creator’s side is limited to people authorised to manage the forms. Google may process data outside the European Economic Area. Information about Google’s data transfer mechanisms is available at https://policies.google.com/privacy/frameworks.
For more information about how these services process data, see https://firebase.google.com/support/privacy, https://support.google.com/admob/answer/6128543, and https://policies.google.com/privacy.
The game is not directed at children under 13 and does not knowingly collect their data.
Requests for access, rectification, erasure, or restriction of processing can be sent to dev.dejmos@gmail.com. A person may also object to processing based on legitimate interests. Consent to gameplay analytics and to personalised ads can be withdrawn in the game’s settings; this does not affect the lawfulness of processing carried out before withdrawal. Where applicable, the right to data portability also applies. For data processed by Google as an independent controller (ads, payments), requests may also be sent directly to Google.
The game does not require an account, and the forms are designed not to require contact details. As a result, in some cases it may not be possible to link a specific report or response to the person making a request. A complaint may also be lodged with a competent data protection authority. In Poland, this is the President of the Personal Data Protection Office (Prezes UODO).