BubbleTara: Bubble Shooter — Privacy Policy
RudraArc Technologies
Updated 13 November 2026
Who we are
BubbleTara is provided by RudraArc Technologies. This notice explains data use in the current app. Contact us at rudraarctechnologies@gmail.com for privacy questions or requests.
Your game data
Levels, scores, coins, rewards, saved boards and settings are stored in the app on your device to run the game and remember progress. We do not operate our own account system or cloud save. Google Analytics usage reporting in version 1.0.6 and later is described below; it is separate from local game saves and optional Google Play Games authentication. The app does not request access to your contacts, photos, microphone, camera or precise location.
Delete BubbleTara data and manage your Play Games profile
BubbleTara is provided by RudraArc Technologies. We do not create a separate developer-operated game account. Optional Google Play Games authentication uses your Google-managed gamer profile.
To remove local BubbleTara levels, coins, saved boards and settings, clear BubbleTara storage in Android Settings or uninstall the app. This cannot be restored from a BubbleTara cloud backup; Android backup and device transfer are disabled for game data. This does not delete Google-held data.
To delete BubbleTara data held by Play Games, open your Google Play Games profile, choose Your data, then Delete Play Games account and data, and select BubbleTara under individual game data. You can also delete your entire Play Games profile there; that affects other games and profile information too. Follow Google's current deletion instructions. Play Games data and Google Play History are separate; Google's instructions explain both. Google controls its own retention and deletion processing.
For deletion of feedback or other information sent directly to RudraArc Technologies, email a BubbleTara data deletion request from the address used to contact us. Identify the correspondence to remove; never send a password. We remove support information no longer needed, except information we must retain for applicable obligations. We cannot delete your Google account, Google-held service records, or storage on your phone on your behalf. You do not need to reinstall BubbleTara to use these Google or email request options.
Ads and external services
Core gameplay works offline. Where Google ads are available, Google Mobile Ads services process information such as IP address, approximate location derived from it, ad interactions, diagnostics and device or app identifiers for ad delivery, measurement and fraud prevention. Google controls its service data under its privacy policy. This is separate from local game progress. Rewarded ads are optional and depend on availability. Coin reward ads are limited to three completed rewards per day. Eligible Journey shot rewards can be offered again at later losses.
Feedback and sharing
Email is opened only when you choose it. If you send feedback, we receive your email address and the information you include, and use it to respond and investigate your request. We retain support correspondence only as needed for that purpose and applicable obligations; you can request deletion by email. Your email provider also handles the message under its own terms. Sharing opens an Android chooser; your selected app handles delivery. App sharing includes a public feature image, a short game description and the Play Store link; your saved progress is not shared.
Security and updates
Local data is kept in Android app storage. No storage or transmission method can be guaranteed completely secure. This notice will be updated when data practices change. If you are a child, ask a parent or guardian before sending personal information. Contact us about any personal information submitted in error.
Version 1.1 and later: advertising
This version uses Google AdMob advertising, which may generate revenue for RudraArc Technologies. It does not ask for or use an age group. Every player receives the same child-protective ad settings: child treatment, general-audience (G) content rating and disabled personalization. The SDK is configured to suppress advertising-ID transmission. Privacy initialization uses under-age treatment without asking the player for an adult consent choice. If privacy checks or connectivity fail, ads remain unavailable and free gameplay continues.
Native ads may appear on Home and the exit screen, banners on Levels, and occasional interstitials between levels. Rewarded ads are optional. Coin rewards have a daily limit. At eligible Journey losses, a completed rewarded ad grants five shots directly on the same board, without adding or spending coins. Another ad may be offered at a later eligible loss; availability is not guaranteed. Rewards are granted only after the SDK confirms completion. Closing early grants no reward. Free Retry remains available. There are no real-money purchases.
The advertising-ID permission remains declared; it does not override child treatment. Earlier locally saved age answers are removed during migration. Internal QA and developer builds use Google demo ads and do not generate publisher revenue.
Earlier versions 1.0.2 through 1.0.8
These releases use Google demo ads, with no age popup and the same child-protective settings. Test ads contact Google services but do not generate publisher revenue. Optional rewarded ads grant the reward displayed in the app only after the SDK confirms completion. The direct +5 Journey-shot option is available in versions 1.0.7 and 1.0.8.
Earlier versions 1.0.0 and 1.0.1
These earlier builds use test ads only and have no real-money purchases. Their closed-test release stores an age group on this device. For users under 16 or with no age answer, it does not initialize advertising or consent services or request ads. Users aged 16 or older can receive Google demo ads only after the privacy checks succeed. Consent choices can be reviewed in Settings when required. The internal developer preview uses Google demo ads. Test ads still contact Google services and are not an offline feature. The closed-test release declares the Android advertising ID permission. For eligible older users, Google Mobile Ads may use the advertising ID, when available, for advertising, measurement and fraud prevention. You can reset or delete your advertising ID in Android settings.
Version 1.0.4: Google Play Games
The version 1.0.4 testing build includes Google Play Games Services for optional platform authentication. Google may automatically connect an existing Play Games profile according to your Google settings; automatic profile-creation prompts are suppressed. You can choose Connect in Settings, or play the entire game without signing in. Google processes account, gamer-profile, app, device and diagnostic information under its own privacy policy. BubbleTara checks authentication status but does not store your Google email, player ID or profile, and does not send local scores, coins, achievements or saved boards to Play Games in this version. Cloud save, online leaderboards and synced achievements are not yet implemented. Manage Play Games sign-in and associated service data through your Google/Play Games settings. Clearing BubbleTara storage removes local progress, but does not delete your Google account or Google-held service data.
Version 1.0.6 and later: usage reporting
Google Analytics for Firebase helps us understand app use and improve BubbleTara. Usage reporting is ON by default for new installs and upgrades without a saved choice. A saved OFF choice is retained. You can turn it off in Settings > Share usage statistics; core gameplay and rewards remain available. No age answer is requested or sent.
When reporting is on, Google processes app-instance identifiers, app and device information, usage sessions, level starts and results, scores, and rewarded-ad completion events. Google may derive approximate location from IP addresses. BubbleTara does not request precise-location permission. The Firebase SDK also includes installation identifiers and service metadata used to provide and maintain Firebase services.
BubbleTara does not attach your name, email, Google Play Games identity, age, saved board or free-text input to Analytics. Analytics advertising-ID collection, ad storage, ad user data and advertising personalization are disabled. These restrictions do not make app-instance identifiers anonymous. Google signals are off, and this Analytics property has no Google Ads, AdMob or BigQuery links. Advertising SDK data practices remain separate, as described above.
Turning reporting off stops future Analytics collection and resets local Analytics data, including its app-instance identifier. It does not delete data already processed by Google, reset every Firebase service identifier or stop other independently described services. Clearing app storage removes your local reporting choice and restores the default ON setting.
Analytics event-level retention is configured to 2 months and user-level retention to 14 months, with the user retention period reset by new activity. These settings do not limit standard aggregated reports. Google processes service data under its privacy terms. See Google Privacy Policy and how Google uses information from apps that use its services.
For privacy or deletion requests, including requests from parents or guardians, contact rudraarctechnologies@gmail.com. Explain the request without sending passwords or game saves. We will explain what information can be located and removed; because Analytics is not linked by us to your name or email, we may not be able to identify a particular Analytics record from your email alone. Local deletion and reporting controls do not automatically delete Google's server records.