Privacy Policy for Bubble Booster

Android (Google Play)

Version 1.2 •

App name Bubble Booster
Platform Android (Google Play)
Provider Digital-e UG (haftungsbeschränkt)

A. Controller and scope

Digital-e UG (haftungsbeschränkt)
Managing Director: Kurt Laabs
Norderstraße 47
25436 Tornesch, Germany

Email: anfrage@digital-e.org

No data protection officer appointed.

This privacy policy explains how personal data is processed when using the mobile app Bubble Booster for Android via the Google Play Store.

B. Installation and technical provision

Google Play Store

During installation, updates and use of store functions, the respective store provider, in particular Google Ireland Limited as operator of Google Play, processes data as an independent controller. This may include store account data, payment data, device information, download information and security information. We have no influence over this processing; the privacy notices of the store provider apply.

App permissions

The app uses internet access for ads, purchases, cloud saves, error reports, optional analytics and external links. It does not request GPS location, contacts, camera or microphone access. Advertising and analytics services may infer an approximate region from the IP address; see sections D and H.

C. Game saves and local settings

Bubble Booster does not require a Digital-e account. Progress, characters, XP, cards, currencies, completed levels, achievements and settings are stored in the local app database. When signed in to Google Play Games, progress can also be synchronized (section G).

Processing required to provide the game is based on Article 6(1)(b) GDPR and section 25(2)(2) TDDDG. Purchase records and technical identifiers are processed locally to deliver purchases reliably and prevent duplicate rewards. The optional analytics choice, its timestamp and notice version are stored separately on this device and are not synchronized with game saves or transferred to another device.

Local data remains until deleted. Settings → Delete all data resets progress. If signed in with cloud synchronization enabled, the cloud save is first replaced with an empty save; the app reports any failure. When signed out, only local data is deleted. Uninstalling or clearing Android app data also removes local data but does not automatically remove Google cloud copies. Google provides deletion controls for operating-system backups. Resetting data switches usage analytics off.

Delete data or request erasure

In Bubble Booster, you can remove local progress, inventory and settings via Settings → Delete all data. If signed into Google Play Games with sync enabled, the cloud save is also cleared. Otherwise the cloud copy remains; you can also delete game data through Google Play Games.

For personal data held by Digital-e, email anfrage@digital-e.org with the subject “Bubble Booster data deletion” and identify the area concerned, such as error reports or usage analytics. We will let you know if information is needed to locate your data. Do not send passwords or payment details. Retention for error reports and analytics is described in sections F and H. Legally required records or data controlled independently by Google may have separate retention periods; we explain any exceptions when handling your request.

D. Advertising via Google AdMob

Permitted ads may be preloaded in menus and during gameplay so they are ready when requested. Videos play only after you choose to watch. Transmitted data and identifiers depend on UMP settings; changing these settings discards preloaded ads.

Google AdMob / Google Mobile Ads SDK

Use: Rewarded ads, for example for a second chance after game over. If the “remove ads” in-app purchase is active, no rewarded-ad flow is started in the game.
Possible data: IP address, advertising ID or app set ID, other device or account identifiers, ad interactions, app launches, taps, video views as well as diagnostic and performance information.
Purposes: Ad delivery, ad measurement, analytics, security and fraud prevention.
Recipients: Google Ireland Limited, and where applicable other Google group companies and advertising partners.

Consent management

The app uses the Google User Messaging Platform (UMP) to check, depending on region, device settings and Google account, whether a privacy or tracking consent is required. Where required, UMP displays a form in which you can accept or reject processing. Ads are only loaded once the UMP logic technically allows the request. Where consent is required for advertising IDs, personalised advertising or tracking, we rely on Art. 6(1)(a) GDPR and Section 25 TDDDG. For purely technical processing that does not require consent, Art. 6(1)(f) GDPR may apply.

You can change your advertising preferences via the privacy options provided in the app, the Android advertising ID settings or your Google account. Further information: Google UMP SDK, Google Mobile Ads SDK Data Disclosure and Google Privacy Policy.

E. In-app purchases

Google Play Billing handles purchases such as Remove Ads, XP packs, Star Medals, card packs and additional equipment slots. The app processes the product ID, purchase status, purchase identifier and technical verification data to deliver and restore purchases and prevent duplicate credits. Purchase records are kept locally for these purposes until app data is deleted; Google maintains its own purchase records.

The legal basis is Article 6(1)(b) GDPR. Google processes payment and billing details; the app does not provide us with credit-card or bank details. With analytics consent, product, price, currency and purchase events may be evaluated statistically (section H). We do not send receipts or verification tokens as Analytics event parameters.

F. Technical error and crash reports

From version 1.0.14, the app uses the Sentry Flutter SDK to report errors and crashes directly to a collector operated by Digital-e at server.digital-e.org/bubblebooster-backend. Older app versions use the previous address staukarte.net/bubble-booster-sentry, which forwards reports to the same collector. Reports go to our own service, not to Sentry Cloud. Data includes error messages, stack traces, timestamps, app version, operating-system and device information, technical context and identifiers. The IP address is technically processed during transmission.

Automatic transmission of additional default personal information is disabled (sendDefaultPii = false). Session replay, continuous performance tracing and automatic session tracking are not enabled. Error reporting is separate from optional usage analytics.

The legal basis is Article 6(1)(f) GDPR: our legitimate interest in stability, troubleshooting and security. Retention depends on the time necessary to investigate and resolve the error. You may object on grounds relating to your particular situation by contacting anfrage@digital-e.org.

G. Google Play Games and cloud saves

When you use Google Play Games, Google processes platform-account information, the player identifier and display name. Automatic sign-in may occur according to your Google Play Games settings. The app can display your player name; it creates no Digital-e account and does not use the name as an Analytics identifier.

With synchronization enabled, game progress, character stats, inventory, currencies, achievements and selected game settings are stored through Google Play Saved Games and synchronized between your devices. The separate Analytics choice and technical purchase records are excluded. Local saves remain usable offline. Cloud saves are retained until deleted or replaced; additional Google copies are subject to Google’s retention and deletion rules.

This game feature is based on Article 6(1)(b) GDPR. You can manage synchronization and sign-in in the app and Play Games settings. See section C for deletion; Google also provides controls to delete a Play Games account and game data. The app does not delete your Google account.

H. Optional usage analytics with Google Analytics for Firebase

Analytics starts switched off. Only after your separate consent do we activate Google Analytics for Firebase to understand usage, retention, game balance and the economics of purchases and ads. An advertising choice in the UMP form does not enable this analytics. Declining does not limit game features. Optional analytics is only offered to users who confirm they are at least 16 years old. We do not collect a date of birth.

Data includes a random, pseudonymous app-instance identifier, app and operating-system information, language, sessions and engagement, and events such as screen and shop views, level starts and ends, wins and losses, height reached, revives, purchase attempts, in-app purchases and advertising events including revenue. The IP address is processed for transmission and approximate geographic information; Google states that Analytics does not log or store IP addresses. Additional granular location and device data collection is disabled. GPS data is not requested.

We do not assign a player ID or name as an Analytics user ID. Collection of the Android advertising ID by Analytics, Google signals and the use of these Analytics data for personalized advertising are disabled. AdMob’s separate advertising processing is described in section D. The Analytics property is linked to Google Play and AdMob to measure purchase and advertising revenue.

The legal bases are consent under Article 6(1)(a) GDPR and section 25(1) TDDDG. The recipient is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, with Google group companies as service providers. Data may also be processed in the USA. Google LLC is certified under the EU-US Data Privacy Framework; Google’s standard contractual clauses apply additionally where needed. See Google’s transfer safeguards.

Our property’s retention for both user and event data is set to two months, without renewal on new activity. Automatic deletion follows Google’s deletion cycle; aggregated standard reports may remain longer. See Google Analytics data retention.

You can withdraw or give consent at any time in Settings → Optional usage analytics. Withdrawal stops further events and resets local Analytics data, including the app-instance identifier. It does not immediately delete data already stored on Google’s servers. For an erasure request, contact anfrage@digital-e.org. Withdrawal does not affect the lawfulness of earlier processing. Further information: Firebase privacy and Google Privacy Policy.

J. Rights of data subjects

Under the GDPR, you have in particular the following rights. To exercise your rights, you can contact us at any time at anfrage@digital-e.org.

Access

Art. 15 GDPR

Rectification

Art. 16 GDPR

Erasure

Art. 17 GDPR

Restriction

Art. 18 GDPR

Data portability

Art. 20 GDPR

Objection

Art. 21 GDPR

Withdrawal

Art. 7(3) GDPR

Complaint

Art. 77 GDPR

You also have the right to lodge a complaint with a data protection supervisory authority, in particular at your habitual residence, place of work or the place of the alleged infringement.

K. Changes to this privacy policy

We may update this privacy policy if app features, services used or legal requirements change. The current version can be accessed via the privacy link provided in the app.

Last updated: 19 Oct 2026