YOUR PRIVACY
Cloud Music
Privacy Policy.
How Cloud Music handles information and the choices you control.
Last updated: October 7, 2026.
YU JIXUN develops Cloud Music Player - Listener (also called Cloud Music). This policy covers Cloud Music and the website section described below. It does not describe the data practices of other apps by YU JIXUN. The optional Firebase features and first-launch choices described below apply to version 6.7 and later; earlier versions may have different features.
Your choices
Usage & Diagnostics is optional and off until you allow it. On first launch, the app offers Allow and Don’t Allow and remembers your choice. An existing choice made in Settings is also respected. You can change it under Settings → Library → Usage & Diagnostics.
Declining does not prevent you from playing or importing music, managing playlists, or using CarPlay. Advertising privacy choices are separate from Usage & Diagnostics. Where available, use Settings → Privacy Settings to review advertising consent. You can also manage the app’s tracking permission in your device’s Settings.
Your music and cloud connections
The app reads music files and their metadata to display your library, artwork, and playlists and to play audio. Imported files, playlists, and preferences are stored on your device. We do not upload your music library to a developer-operated music server or Firebase storage.
If you connect Google Drive, Dropbox, or OneDrive, the app uses the provider’s sign-in process and permissions to access your account, list files, and download the files you select. Provider SDKs handle the account information and authorization tokens needed for that connection. These services receive the requests required to provide their features and handle information under their own policies.
You can sign out of a provider from Sources and revoke the app’s access through that provider’s account settings. Signing out does not delete music already imported onto your device or files in your cloud account.
Wi-Fi transfer sends files between your computer and device over your local network. The local address and pairing code support that transfer and are not added to our Firebase usage events. Your device’s own backup settings may also determine whether app data is included in a device backup.
Optional usage statistics
If you allow Usage & Diagnostics, we use Google Analytics for Firebase to understand feature use, improve reliability, and measure advertising and purchase activity. The information can include:
- App launches, sessions, screens or tabs opened, and use of features such as playlists, the timer, themes, audio effects, and CarPlay.
- Import source categories, success or failure categories, file counts, operation durations, playback activity, and total listening time.
- Advertising requests, load outcomes, impressions and revenue, and ad-supported or remove-ads purchase status.
- Purchase and restore outcomes and verified in-app purchase information, such as the product, transaction, price, and currency. We do not receive your payment card details from Apple.
- Device and app information, including device family, operating system, app version, language, and general location derived by Google from masked IP addresses.
- SDK-generated app-instance or installation identifiers used to measure sessions and usage. These are not the same as your cloud account login, and the statistics are not completely anonymous.
Our custom usage events contain predefined categories, counts, and durations. We do not add music audio, song or artist names, lyrics, artwork, cloud file contents, file paths or URLs, account email addresses, Wi-Fi addresses, or pairing codes to those events. We do not set a cloud-account user ID in Analytics. Firebase Analytics is configured without IDFA collection, with IDFV collection disabled and advertising storage, advertising user data, and advertising personalization consent denied. AdMob has its own separate data practices and consent controls.
Optional crash reports and diagnostics
When Usage & Diagnostics is allowed, Firebase Crashlytics helps us investigate crashes and selected nonfatal errors. Reports can include crash timestamps, call stacks, exception details, app state, app and operating system versions, device model and technical information, installation or session identifiers, and recent Analytics activity associated with a crash.
We add only predefined error categories and limited technical labels to our diagnostic reports, rather than attaching your music files, cloud responses, or account details.
Turning the setting off stops our new usage events, resets local Analytics data, and requests deletion of unsent crash reports. Some Crashlytics collection changes take full effect on the next app launch. Turning the setting off does not automatically delete reports or statistics already received by Google.
Advertising and tracking
The ad-supported app uses Google AdMob / Google Mobile Ads. Advertising services may process IP addresses and general location, device or app identifiers, advertising interactions, and diagnostic or performance information to deliver and measure ads, prevent fraud, and maintain the service.
Depending on your permissions and applicable consent choices, identifiers may be used to track activity across other companies’ apps and websites for advertising. Access to Apple’s advertising identifier requires the relevant device tracking permission. Denying that permission does not eliminate all data needed for ad delivery or fraud prevention, and non-personalized ads may still process technical information.
The Usage & Diagnostics switch does not grant advertising or tracking permission and does not disable AdMob. An active remove-ads purchase removes the app’s advertising placements. See Google’s Privacy Policy and how Google uses information from apps and sites that use its services.
Service providers and processing
Google receives the optional Analytics and Crashlytics data when you enable these features. We use their reports to understand app usage and fix problems. Google also processes advertising data through AdMob. Apple handles App Store purchases, and cloud providers handle the connections you choose to use.
These providers may process information in countries other than your own. For more information, see Firebase privacy and security information, Google’s Privacy Policy, Dropbox’s Privacy Policy, Microsoft’s Privacy Statement, and Apple’s Privacy Policy.
Retention and deletion
Local music remains on your device until you delete it in the app or remove the app and its local data. Cloud files are managed through the relevant provider. Removing local files does not automatically erase device backups or files retained by your cloud provider.
Google Analytics retains event and user data according to the Analytics property’s retention settings; aggregated reports may be retained longer. Google states that Crashlytics retains crash traces and associated identifiers for 90 days before beginning removal from live and backup systems. Advertising, purchase, and cloud-service information follows the relevant provider’s retention practices.
You can request information about retention or request access, correction, or deletion of personal data by contacting us below. Depending on applicable law, you may also have rights to restrict or object to processing, portability, or to complain to a data protection authority. We may need enough information to locate a relevant record; because we do not assign a cloud-account user ID to analytics, an email address alone may not identify an installation’s historical reports. Do not send passwords, sign-in tokens, pairing codes, or music files with a privacy request.
This website and links
This website is hosted on GitHub Pages and loads fonts from Google Fonts. These providers receive technical request information such as your IP address and browser information when your browser requests the site or fonts. This site does not embed Firebase Analytics or AdMob. See GitHub’s Privacy Statement and Google Fonts privacy information.
External websites and cloud services have their own privacy policies. If you contact us, we use the contact details and information you provide to respond to your request.
Contact and policy updates
For privacy questions or data requests, contact YU JIXUN: jhonbelleservice@outlook.com.
We will publish changes on this page and update the date above. The App Store privacy information describes the app’s declared data practices; available controls and data handling can depend on the app version and features you use.