1. Scope
This Privacy Policy applies to the Android application Cosmic Bubble Relax (the “App”). It covers data handled locally by the App and data that may be handled by the Google advertising, consent, and Google Play update services integrated into the App.
The App does not require registration, login, or a developer-operated account. It has no chat, leaderboard, social posting, cloud synchronization, or developer-operated backend server.
2. How the App works
- Opening and instructions: The App displays a ShuChi Studio opening animation and bilingual instructions before the user enters the main screen.
- Bundled offline content: The App contains 12 backgrounds, 10 music tracks, bubble artwork, and three bubble visual styles. These assets are included in the App and are not downloaded from a developer server.
- Bubble interaction: Bubbles drift across the screen. Tapping a bubble creates visual, particle, vibration, or full-screen effects locally on the device.
- Music playback: Users can select a track, play or pause, loop all tracks, or repeat one track. The Android version uses a foreground media playback service so music may continue in the background or while the screen is off.
- Audio coordination: Playback may pause when another app takes audio focus, during a call, or when headphones are disconnected. Playback stops when the App is removed from recent tasks, the notification's Close action is used, or the service is otherwise stopped.
- Performance adaptation: Bubble and effect load may be adjusted locally based on device performance. This performance information is not sent to a developer server.
3. Data stored locally by the App
The App stores only a small amount of local information needed to preserve user choices:
| Local data | Purpose | Storage and retention |
|---|
| Background index, playback mode, and bubble style | Restore the user's most recent visual and control preferences. | App-local WebView storage until app data is cleared or the App is uninstalled. |
| Current track, requested playback state, and loop/repeat mode | Control background playback, notification actions, and restoration after relaunch. | Android SharedPreferences until app data is cleared or the App is uninstalled. |
| Whether music was playing before a full-screen ad | Resume music after the ad only when it was previously playing. | Temporary local state that is reset after the ad flow. |
| Whether notification permission was already requested | Avoid repeatedly showing the same Android permission request. | Local app settings until app data is cleared or the App is uninstalled. |
The developer does not upload these settings, track selections, bubble taps, or playback history to a developer-operated server and does not create an identifiable user profile from them.
4. Offline use and network access
Backgrounds, music, bubble interactions, and core controls work without an internet connection. The App primarily uses the internet to:
- obtain applicable privacy messages and consent status through Google UMP;
- request, load, and display Google AdMob ads; and
- check Google Play for an available update and start the Google Play update flow.
The App does not connect to a developer-operated API, account server, or database. If the device is offline or an ad fails to load, the offline core features remain available, but ads and update checks may be unavailable.
5. Advertising mechanics
The App uses Google Mobile Ads (AdMob) for interstitial ads and rewarded ads. It currently does not use banner ads.
5.1 Interstitial ads
- An advertising cooldown starts after the main screen is entered. An interstitial may be attempted only after approximately 10 minutes have elapsed.
- An interstitial is attempted only at a natural interaction break, such as after popping a bubble, changing the background, or selecting a music track. It is not intentionally shown while the App is in the background.
- After an interstitial closes or fails to display, the cooldown is restarted. Interstitial and rewarded ads are not shown on top of one another.
- Actual availability depends on the network, ad inventory, consent status, Google rules, and successful SDK loading.
5.2 Rewarded ads
- A rewarded ad never starts automatically. The user must select “Watch Rewarded Ad” in the Bubbles menu.
- Completing the ad summons one large special bubble on the local screen. Popping it produces an enhanced visual and vibration effect.
- If the ad is not completed, cannot load, or fails to open, the special bubble is not granted. Completing another rewarded ad replaces any unpopped reward bubble.
- The special bubble is a visual in-app reward with no cash, product, crypto-asset, or transferable value and is not required to use the App's core features.
5.3 Music during full-screen ads
Before a full-screen ad is shown, the App records whether music was playing and pauses playback. After the ad closes, the App attempts to resume music only when it was playing beforehand.
6. Data that Google Mobile Ads may handle
According to Google's disclosure for the Google Mobile Ads SDK version used by the App, the SDK may automatically collect and share the following data with Google or its advertising, measurement, and fraud-prevention partners for advertising, analytics, and fraud-prevention purposes:
| Data type | Examples | Main purposes |
|---|
| IP address | The device's network IP address, which may be used to estimate a general area. The App does not request GPS-level precise location. | Ad delivery, regional requirements, security, and fraud prevention. |
| Product interactions | App launches, taps, ad requests, ad impressions, and video views. | Advertising performance, analytics, and service operation. |
| Diagnostic information | App or SDK launch time, crashes or hangs, performance, and energy usage. | Service reliability, analytics, and fraud prevention. |
| Device or account identifiers | Android advertising ID, App Set ID, and, where applicable, other identifiers related to accounts signed in on the device. | Ad delivery, frequency control, analytics, and fraud prevention. |
Google states that user data collected by the Google Mobile Ads SDK is encrypted in transit using TLS. The ads shown, degree of personalization, retention periods, and participating vendors depend on the user's region, consent choices, Google or Android advertising settings, and Google's policies.
Because the App does not ask users to enter a name, phone number, email address, or postal address, the developer does not pass those direct identity details to AdMob. The Google SDK may still handle device, interaction, and network data as described above.
7. Consent and advertising choices
The App integrates the Google User Messaging Platform (UMP). When the main screen is entered, UMP updates consent information and may display a privacy or consent form when required by the user's region or Google's configuration. The App initializes and requests AdMob ads only when UMP reports that ads may be requested.
- Available modes may include personalized ads, non-personalized ads, limited ads, or other legally applicable modes.
- When UMP requires an ongoing privacy entry point, the Bubbles menu displays “Privacy Options” so the user can review or change choices.
- Users may also reset or delete the Android advertising ID in Android settings and manage certain ad preferences through Google My Ad Center.
8. Android permissions and purposes
| Permission / capability | When and why it is used |
|---|
INTERNET, ACCESS_NETWORK_STATE | Load UMP privacy messages, AdMob ads, and Google Play update information, and determine network availability. |
FOREGROUND_SERVICE, FOREGROUND_SERVICE_MEDIA_PLAYBACK | Create a foreground media service while the user plays music so it can continue in the background or with the screen off. |
WAKE_LOCK | Maintain the minimum processing needed for music playback while the screen is off. |
POST_NOTIFICATIONS | On Android 13 or later, requested when the user starts or restores background playback, to display media controls for play, pause, and close. It is not used for marketing notifications. |
VIBRATE | Provide a brief haptic effect when a rewarded giant bubble is popped. Other features continue to work if vibration is unavailable or disabled. |
The App does not request location, camera, microphone, contacts, call logs, SMS, calendar, health, or photo/file storage permissions.
9. Google Play in-app updates
After a cold start, the App may use Google Play In-App Updates to check for a newer version. Where allowed by Google Play, it prioritizes an immediate update; otherwise it may use a flexible background download. When a flexible update finishes downloading, the App prompts the user to restart and complete installation.
Update checking, downloading, and installation are handled by Google Play. The App does not send update history to a developer-operated server. If the update service is unavailable, the main App continues to operate.
10. Third-party services
The App uses or may interact with the following services. Each provider handles data under its own policies:
This privacy-policy webpage does not contain analytics scripts, advertising, login forms, or developer-set tracking cookies. Cloudflare, as the hosting and security provider, may process standard request data such as IP address, browser information, request time, and security logs under its own policy.
11. Sharing, sale, and developer analytics
- The developer does not sell, rent, or trade users' personal data.
- The developer currently operates no custom analytics platform, account system, cloud database, or remote playback/activity history service.
- The App does not integrate separate social login, third-party payment, subscription, location, camera, microphone, or contacts SDKs.
- Data exchange related to advertising, consent, and updates is limited to the Google SDKs and services described above.
12. Security and retention
The App follows a data-minimization approach. Core content and preferences remain on the device, and the App disallows cleartext HTTP traffic. Google states that Google Mobile Ads data is encrypted in transit using TLS. No device, network, or third-party service can be guaranteed absolutely secure.
Local settings remain until the user clears app data or uninstalls the App. Advertising, consent, and diagnostic data retained by Google or its partners is governed by their policies, legal obligations, and the user's account settings. The developer cannot directly access or delete all third-party data.
13. Children and minors
The App is a general relaxation and entertainment tool. It does not ask users for age, name, or contact details and is not intended to build profiles about children. Advertising and data handling for minors are subject to applicable law, device or Google Account age settings, the Google Play target-audience configuration, and Google advertising policies.
A parent or guardian who believes a child provided personal data through the App or related third-party services may contact the developer using the email below.
14. User controls, deletion, and rights
- Delete local data: Open Android Settings → Apps → Cosmic Bubble Relax → Storage → Clear data, or uninstall the App.
- Notifications: Notification permission may be denied or withdrawn in Android settings.
- Advertising choices: Where applicable, use the in-app Privacy Options entry point, Android advertising settings, or Google My Ad Center.
- Third-party data: Use Google's account, privacy, and advertising tools to access or delete data held by Google.
Because the App has no developer-operated account and no developer server storing account data, there is no App account that must be deleted through the developer.
15. Changes to this policy
This policy may be updated if the App's features, advertising frequency, third-party SDKs, permissions, or data practices change. The latest version will be published at the same URL with a revised date. Material changes may also be described in the App or Google Play listing where appropriate.
16. Contact
For questions about this policy, privacy choices, advertising mechanics, or data handling, contact:
Back to top ↑