Privacy Policy

Bubble Days — Privacy Policy
Version 2026-10-21.1 | Effective 20 October 2026

1. Who operates the game
Thirty operates Bubble Days (com.bubbledays). For privacy questions and requests, contact mjdeveloper123@gmail.com. This policy describes device storage, Google Play Games Saved Games, Google AdMob (Google Mobile Ads SDK), and Google User Messaging Platform (UMP). The current test build requests Google test rewarded ads. Production ad serving requires separate AdMob app approval and configuration. Test mode still uses Google SDKs and network services. This build integrates Google Analytics for Firebase for optional gameplay measurement. Firebase Authentication links your Play Games identity to a support ID. Cloud Firestore stores a support summary and operator-issued item grants. The startup agreement is separate from advertising privacy choices.

2. Data and purposes
On your device we store stage progress and stars, gold and item counts, lives and regeneration times, attendance rewards, roulette state, piggy-bank savings and purchase records, treasure-hunt targets/timers/claims, daily rewarded-ad claim counts, season-pass purchase status/progress/reward claims, settings and the document version and time you accepted. This supports play, rewards, purchase delivery and your preferences.
Google Play Games provides a player identifier used to bind the local save to the correct account. When available, the game uploads and downloads the player archive through Google's Saved Games service to restore and synchronize progress. The archive contains the gameplay state and purchase-delivery records; it is not a public leaderboard. Google Play Games may authenticate at Android startup before the game's consent screen. The game's own cloud synchronization begins only after acceptance. Google handles its platform authentication under its own policies.
This version does not initialize offer in-app purchases or collect new purchase tokens. Existing hashed purchase-delivery records remain in the player archive to preserve past entitlements and prevent duplicate grants. Thirty does not receive card numbers or Google account passwords. Google retains past transaction records under its own policies. If you contact support by email, Thirty receives your address and the content you send to respond.
Google Mobile Ads may collect and share IP addresses (including approximate location inferred from them), app/ad interactions, diagnostic information, advertising ID, app set ID and other applicable device/account identifiers for advertising, measurement and fraud prevention. UMP handles privacy-message requests and choices. These services process data under Google's policies even when test ads are used. Google's advertising explanation is at https://policies.google.com/technologies/ads.
Player support uses Firebase Authentication and Cloud Firestore to identify your account, show support staff your latest reported stage, Gold and item balances and app version, and deliver requested support items. We retain unique grant IDs, reward contents, support reasons, an installation identifier and reservation/delivery timestamps to prevent repeated delivery and resolve support requests. This supports account assistance and is separate from optional gameplay analytics. Contact the privacy address with your support ID for access or deletion requests; deleting Play Games data alone does not delete Firestore records.
Optional analytics records stage starts/results, retries, score/stars, shots and booster use, screen visits, and app background/resume activity. Google Analytics for Firebase also processes app-instance, device, app-version and engagement information under its policies. A pseudonymous identifier derived from the Play Games player ID links activity across devices. Analytics events do not contain email addresses or purchase tokens. Analytics is disabled until you explicitly allow it in a separate choice; declining does not block play. Settings lets you change this device-local choice. The analytics integration disables advertising-ID collection and denies advertising personalization consent. These settings do not change the separate advertising SDK.

3. Sharing and security
Game save, purchase, advertising and privacy-message requests are sent to Google to provide their respective services. Google advertising services may process and share information as described in their policies and applicable privacy choices. Optional analytics is sent to Google to measure gameplay and retention. Thirty does not sell player data. Google services use encrypted network connections. Device files are stored in the application's storage area; access to your device or Google account can expose your saved data. No storage or transmission method can be guaranteed completely secure. Google's privacy policy is at https://policies.google.com/privacy.

4. Retention and deletion
Device data remains until you clear the application's storage or remove it, subject to Android backup and restore settings. Acceptance is recorded on the device and is not part of the cloud archive. Analytics data follows the configured Google Analytics retention and deletion controls; contact the privacy address for help with identifiable analytics deletion requests. Turning analytics off stops future collection from this integration and does not automatically erase previously collected records. Google manages advertising/UMP data under its own policies and controls; deleting a game save does not itself delete those Google records. The game keeps progress, granted purchases and duplicate-delivery records while the save exists; season expiry resets current-season access but is not a request to erase your save.
Google Play Games keeps cloud data under your Google account until you delete it through Google's controls. To delete it, close Bubble Days, go to https://play.google.com/games/profile, choose Your data, then Delete Play Games account and data, and delete the individual Bubble Days game data. Also clear Bubble Days application storage in Android settings to remove the local copy before playing again; otherwise the local copy may be synchronized again. Google's current instructions are at https://support.google.com/googleplay/answer/9130646. Deleting progress or Google Play Games data does not delete Google's legally retained transaction records, revoke purchases or issue refunds. This game does not create a separate Thirty login account. For help with data or correspondence you supplied directly to Thirty, contact the privacy address. Support correspondence is retained only while needed to resolve the request or meet applicable legal obligations; request its deletion through that address.

5. Your choices and children
You may leave without accepting and can review these documents later from Settings. Google account permissions and Google Play Games data are managed through Google's controls. After the startup agreement, UMP checks whether an advertising privacy message is required. The game requests ads only when UMP permits requests, which may use an existing valid choice. Settings shows Ad privacy choices when UMP requires that entry point, allowing you to revisit available choices. Ad forms and availability depend on Google's service configuration. You can decline to watch optional rewarded ads; this does not prevent ordinary local play. Android provides advertising-ID controls. Privacy choices are not a promise that all Google processing stops. Depending on local law you may have rights to access, correct or delete personal information and to complain to the relevant authority; contact the privacy address for assistance. This game is not directed to children under 13 or users below the applicable local minimum age. If you believe a child has provided data, contact us and use Google's deletion controls for the account's game data.

6. Policy changes
The version and effective date appear above. Changes to bundled documents invalidate the stored acceptance and are presented before further play. New data uses will be disclosed before they are introduced, with a separate consent request where required. A terms checkbox does not replace a legally required permission or specific data-processing consent.

Terms of Service · Privacy Policy · Contact Thirty