JuJu Music Privacy Policy
Thank you for using JuJu Music ("the App", "we", "us", or "our"). We take your privacy and personal data protection seriously. Please read this Privacy Policy carefully before using our software to understand how your data is collected, handled, and protected.
1. Information We Collect and Purpose
We adhere to strict data minimization principles and only collect data strictly necessary for core functionality, licensing, product analytics, and stability improvements:
- Device Identifier (Android ID / UUID): Used solely for the 30-day Pro trial counter, online activation-code verification, and device migration authentication. This identifier is never linked to any personal identity.
- Device Information and Usage Telemetry: To perform product analytics, measure feature usage, and diagnose compatibility and stability issues, the app submits a form-encoded report to our own statistics endpoint (jujumusic.zzxia.vip) at startup or when your level increases. The reported fields are: device identifier (Android ID), event type (first install / active), install time, report timestamp, app version, operating system name and OS version (for example, the Android release), device brand, device model, and basic usage metrics (growth level, level name, cumulative play count, activity percentage, and play count over the rolling last 3 days). Metrics such as the cumulative play count are accumulated from your own playback activity on the device.
- Google Play channel: Firebase Analytics (Google Play build only): The Google Play build also uses Firebase Analytics, provided by Google LLC, to collect anonymous analytics events (such as app launches and level changes), app version, OS version, device model, and the Firebase App-instance ID assigned to each app instance, for product analytics, feature-usage assessment, and stability improvements. In addition to app-launch and level events, it records feature-usage events (for example, which category or tool was opened, which type of action was performed, playback format, cloud-drive protocol, sync result, AI feature and model, and voice-processing mode); these events do not include content data such as song titles, artists, albums, file paths, or search terms. We also set this device's identifier (Android ID / UUID — the same identifier used by our own telemetry) as the Firebase User-ID, so Firebase-side statistics are linked to that device identifier for reconciliation with our own telemetry. Firebase derives coarse region (country / region level) statistics from masked IP addresses. We do not collect the Advertising ID: the AD_ID permission and related advertising-service permissions have been removed, and advertising-ID collection and personalized-advertising signals are disabled. When the Firebase project is linked to Google Play, Analytics automatically records purchase events completed through Google Play (product ID, price, and currency); whether or not the project is linked, purchases and entitlement verification are handled by Google Play billing and RevenueCat (see Section 3). This collection is enabled only after you accept this Privacy Policy (disabled by default in the app manifest and turned on at runtime after consent), and the data is transmitted over TLS. The official-website (official) build contains no third-party analytics SDK.
- Google Play channel: Firebase Crashlytics crash diagnostics (Google Play build only): After you accept this Privacy Policy, the Google Play build uses Firebase Crashlytics, provided by Google LLC, to collect crash and ANR diagnostic information, including crash stack traces, the app state at the time of the crash (for example, whether the app was in the background and the screen orientation), device model, CPU architecture, RAM and disk space, OS version, app version, and the Crashlytics installation UUID generated for each installation (used to measure how many installations are affected by a crash). We also bind the device identifier described in Section 1 (Android ID / UUID) as the Crashlytics user identifier, so crashes from the same device are grouped together; no name, email address, or other real-world identity information is bound. This information is used only to locate, reproduce, and fix crashes and stability issues. The official-website (official) build does not include this service.
- IP Address: when our server receives a telemetry request, it records the IP address that sent the request. This record is used only for endpoint rate limiting and abuse prevention (for example, traffic inflation or automated attacks). It is not used for user profiling or for cross-site tracking.
Please note that because the device identifier and the IP address can consistently point to the same device over time, the telemetry described above is not fully anonymous data. We use it only for product analytics and security protection, we do not link it to your real-world identity, and we do not use it for advertising.
2. System Permissions and Usage
- Audio & Media Read Permission (READ_MEDIA_AUDIO / READ_EXTERNAL_STORAGE): Used solely to scan, index, and play local audio files (MP3, FLAC, WAV, AAC, M4A/ALAC, OGG, OPUS, APE, DSF) and embedded cover artwork on your device. The app does not request all-files access such as MANAGE_EXTERNAL_STORAGE; it relies only on the standard media read permissions.
- Audio Recording / Microphone Permission (RECORD_AUDIO / FOREGROUND_SERVICE_MICROPHONE): Used only when you actively enable the voice assistant or the wake-word feature ("Mambo"). Wake-word detection runs on-device in a built-in 33KB ONNX model, and that audio never leaves your device. Once awake, speech-to-text uses one of two engines: the system engine delegates recognition to the speech-recognition service provided by Android or your device manufacturer; whether that service uses the network and whether it uploads the recording are determined by that service, which the app neither controls nor stores; the LLM engine is optional and requires your own API key and a network connection — the app records on-device, encodes the clip to WAV in memory, and sends it directly to the AI provider you configured (for example Google Gemini or Alibaba Cloud DashScope) for transcription; release builds never write that recording to disk. The assistant uses the system engine by default; the LLM engine takes effect only after you enable it and configure your own key.
- Camera Permission (CAMERA): Used solely to scan QR codes in order to import or export LAN P2P share codes and pairing information. The app does not take photos or record video through the camera and does not upload any images.
- Notifications & Foreground Service (POST_NOTIFICATIONS / FOREGROUND_SERVICE / FOREGROUND_SERVICE_MEDIA_PLAYBACK): Used to render ongoing playback controls in the system notification shade and lock screen for smooth background listening.
- Network and Network State Permissions (INTERNET / ACCESS_WIFI_STATE / ACCESS_NETWORK_STATE): Required for online lyric retrieval, online cover artwork lookup, WebDAV/SMB/Aliyun/Subsonic direct transfers and sync, P2P local sharing, and license verification. Network and Wi-Fi state are read to determine whether you are currently on a local network, so that the app can choose between a direct transfer and a relayed transfer.
- External Storage Write Permission (WRITE_EXTERNAL_STORAGE, Android 12 and below only): Used to write download caches and cover images to device storage.
3. Data Flows and Third-Party Services
- Online lyric and cover matching: When you use the online lyrics or online cover features, the app sends the song title and artist name to third-party lyric and cover lookup services (NetEase Cloud Music, QQ Music, Kugou Music, Kuwo Music, and the Apple iTunes Search API) for the sole purpose of matching lyrics and artwork. No device identifier, audio content, or listening history is sent in this process.
- Speech recognition (optional): As described in Section 2, with the system engine, whether the recording is uploaded and to whom is determined by the system or manufacturer speech service; the app neither controls nor stores it. With the LLM engine, a locally recorded audio clip is sent to the AI provider you selected (for example Google Gemini or Alibaba Cloud DashScope) for transcription only when you actively enable it and enter your own API key. Apart from these two engines, the app does not send recordings to any other third party.
- Files the app writes: downloaded cache files are written to the app's external files directory (removed when the app is uninstalled); cover images and caches are written to the JuJuCache folder inside the device's public Downloads directory, which is readable by other apps on the device and can be deleted by you at any time. We state explicitly that the cover cache is not kept in private sandbox storage.
- P2P direct LAN sharing: LAN transfers connect directly between this app and the receiving device and travel over plaintext HTTP within the local network; the data does not pass through our servers. Because this channel uses neither transport encryption nor access authentication, please use this feature only on a home or office network you trust.
- Optional "burn after reading" relay sharing: when you actively choose this sharing mode, the file to be shared is temporarily uploaded to and stored on the developer's server, and the server deletes that temporary file after roughly 10 minutes or once the recipient has finished downloading it. Please do not use this mode to share sensitive or private files.
- Google Firebase Analytics (Google Play channel only): As described in Section 1, the Google Play build uses Firebase Analytics, provided by Google LLC, to process the anonymous analytics events and related device information described above. Google acts as our data processor and handles this data solely to provide us with analytics services for product analytics, feature-usage assessment, and stability improvements; the data is transmitted over TLS. When the Firebase project is linked to Google Play, Analytics automatically records purchase events completed through Google Play (product ID, price, and currency); whether or not the project is linked, purchases and entitlement verification are handled by Google Play billing and RevenueCat. Statistics are retained according to the Firebase Analytics data-retention setting (configurable in the Firebase console). See the Google Privacy Policy and Firebase Privacy and Security for Google's privacy practices. The official-website (official) build does not include this service.
- Google Firebase Crashlytics (Google Play channel only): As described in Section 1, the Google Play build uses Firebase Crashlytics, provided by Google LLC, to process crash and ANR diagnostic information (including the device identifier described in Section 1). Google acts as our data processor and handles this data solely to provide us with crash-diagnostic services; the data is transmitted over TLS. Crash data is retained according to Crashlytics' retention policy. See the Google Privacy Policy and Firebase Privacy and Security for Google's privacy practices. The official-website (official) build does not include this service.
- Google Play billing and RevenueCat (Google Play channel only): In-app purchases in the Google Play build are processed by Google Play billing, and Google handles charging and refunds. We use RevenueCat (RevenueCat, Inc.) to verify purchase receipts, restore previously purchased entitlements, and detect anomalous purchases. RevenueCat receives purchase receipts and transaction information plus an anonymous app user identifier generated by the RevenueCat SDK (used to associate one user's purchase records); the app does not collect or provide your name, email address, or other real-world identity information. See the RevenueCat Privacy Policy for its privacy practices. The official-website (official) build does not use Google Play billing or RevenueCat; it uses activation codes instead.
4. Data Protection & Security Commitments
We explicitly commit that:
- Your audio files are uploaded to a server only when you actively choose the "burn after reading" relay sharing mode. Otherwise the app does not upload or back up your private audio files, documents, contacts, or photos, and its file scanning is limited to audio files.
- The app contains no third-party advertising SDK, and we will never sell, lease, or share your data with third-party advertisers or data brokers. The official-website (official) build contains no third-party analytics SDK; the Google Play build includes only Google Firebase Analytics and Firebase Crashlytics (see Sections 1 and 3) for anonymous usage statistics and crash diagnostics, respectively. Crash diagnostics are likewise enabled only after you accept this Privacy Policy.
- The security of cloud drive (WebDAV, SMB, Aliyun Drive, Subsonic/Navidrome, etc.) sync connections depends on the server you configure yourself; we recommend always using HTTPS addresses and keeping your access tokens safe.
- LAN P2P sharing uses plaintext HTTP; do not use it on public or untrusted networks.
- If you wish to access, correct, or delete the telemetry statistics associated with your device identifier, or if you have other questions about this policy, please contact us through our official channels.
5. Policy Updates and Contact Us
As our features evolve, we may update this policy from time to time; the "Last updated & Effective Date" shown on this page governs the current version. If you have any questions or feedback regarding this Privacy Policy, feel free to contact us via our official website:
Official Website: https://jujumusic.zzxia.vip