Anonymous game, purchase and review statistics
To improve the app, it sends a few fixed events to our Cloudflare backend: onboarding, the first three games started and completed, use of help and the archive and loading full access (where the game has these features), technical purchase and restore steps, a failed sign-in or account deletion, and availability and requests for the native review prompt. Events contain an event or error category, platform, app version and languages; no game content, answers or purchase receipts. The event itself contains no sign-in, account or device identifier. If the app already has a sign-in (including an anonymous one), it sends that session’s credential along for authentication; our backend uses it only for short-term rate limiting and to match a purchase report with a purchase the server verified for the same sign-in. Stored with the event is only whether it was signed in, neither identifier nor session; so that a confirmed purchase counts only once, a hashed reference to that purchase is kept with it for at most 8 days. We cannot tell whether you submitted a review or what it says. Depending on the game, also: the mode played (at most once per mode and day), the first to third round and daily round played to the end, and opening locked Complete content. Also, each at most once a day: whether syncing your progress worked or the coarse reason it failed, merged or unreadable saved progress, where the purchase page was opened from, whether Buy was tapped there and whether a purchase was made from it, in which mode and roughly at which point a round was left, the coarse start time until you can play (for example “1 to 2 seconds”) and whether the daily reminder is on, was switched or opened the app. Current app versions also send with every event the coarse origin of the installation (store, test or developer installation) so that test traffic is counted separately; it is determined on the device, without any device or installation identifier. If an event comes from the networks Google publishes for its automated pre-launch tests (Firebase Test Lab), our backend also counts it as test traffic; the IP address is only compared for this and not stored. Individual events are deleted after 7 days. Daily totals of game and review events are deleted after at most 120 days; aggregate daily counters of purchase steps and of purchase and account-deletion errors are kept without a fixed deletion date. Our legitimate interest is fixing problems and improving the product (GDPR Art. 6(1)(f)). Events are not linked to a person (Art. 11). Objections and privacy questions: apps@bitbeans.de. Failed reporting never interrupts play or purchases.
Updated: 7 October 2026
1. Controller
Christian Hermann & Martina Hermann GbR, An Rainen 3, 72525 Münsingen, Germany; email: apps@bitbeans.de.
2. Data processed
Optional cloud backup processes the sign-in identifier and backed-up game progress. Account deletion is available in the app; local progress can also be reset separately.
Limited technical purchase diagnostics include platform, app version, flow status and error category to identify purchase and restoration problems. There is no advertising tracking.
Progress, statistics, settings and local training rounds are generally stored on the device.
Some daily or challenge rounds may be supplied by the server. After scored rounds, an anonymous technical ID, tasks, selected answers, duration, errors and difficulty may be sent for result verification.
Apple Game Center or Google Play Games may link achievements and leaderboard scores to the platform player ID.
For purchase verification and restoration, we process product ID, store platform and technical receipt data. With a purchase we also store which purchase page it came from (a fixed category such as start page, settings or a locked mode), so that purchases per page cannot be miscounted; it is deleted together with the purchase data.
If you voluntarily send feedback, we process your message, an optional contact email address, category, app version, platform and the screen you send it from. If an anonymous or chosen sign-in exists, we link the feedback to that ID. We store it for handling, forward it to our support team by internal email and delete it when the account is deleted.
3. Purposes and legal bases
We process data to provide the app, verify purchases, deliver online features you actively use, maintain security, resolve errors and answer voluntary requests. Depending on the operation, the legal bases are Article 6(1)(b), (f) or, where expressly requested, (a) GDPR.
4. Recipients and service providers
We use Cloudflare for backend, daily rounds and result verification, Firebase/Google for anonymous or optional sign-in, and Apple and Google for store and game services.
5. International transfers
Some providers may process data outside the EU or EEA. Where no adequacy decision applies, transfers rely on appropriate safeguards, in particular EU Standard Contractual Clauses, or on applicable statutory exceptions.
6. Advertising and tracking
The app contains no third-party advertising. We do not create advertising profiles, sell personal data or use advertising tracking.
7. Retention and security
Local data remains on the device until it is removed in the app or through system settings. Server data is retained only for as long as required for the respective function, security and statutory evidence. Transfers are encrypted.
8. Delete data and account
Local data can be removed in the app or through the device’s system settings. Where an account or cloud data exists, deletion can be requested in the app or by emailing apps@bitbeans.de. Store purchases are managed separately by Apple or Google.
9. Your rights
Subject to the statutory requirements, you have rights of access, rectification, erasure, restriction, portability and objection. Consent can be withdrawn for the future. You may also lodge a complaint with a data-protection authority; the LfDI Baden-Württemberg is the authority responsible for our registered office.