Privacy Policy
Last updated: September 18, 2026
1. Data Collection
Muzi plays audio files stored on your device. Ordinary local playback does not upload your audio files. When you choose cloud sharing, the selected files and sharing metadata are uploaded so recipients can access them through the share link.
Muzi sends usage metrics to our servers, including an installation identifier, app version, song titles and artists, play counts and listening durations, library and import counts, and feature and advertising activity. Our servers also receive your IP address and use it to estimate city and country. If push notifications are enabled, we store a notification token. These records help us operate Muzi and understand feature usage. They are separate from the crash reports described below, although both are labelled with the same installation identifier.
2. Device Permissions
Muzi requests media-library access to read and play your audio files. Features you choose may also request microphone and speech-recognition access for voice search, photo-library access for artwork, location access while the app is in use, and notification permission. You can manage these permissions in your device settings.
3. Crash Reporting
Muzi uses Sentry to receive crash and error diagnostics so we can find and fix stability problems. Reports are sent when the app crashes, when an unhandled error occurs, when a handled error occurs during startup, library scanning, file import, or playback, and when a previous startup or library sync appears to have been interrupted. Sentry also records anonymous session counts so we can measure how often sessions end in a crash. Reports are processed in Sentry's US region.
A report can include the error message and stack trace, the app version and build, the operating system version and device model, the time of the event, the app environment, and limited app state: the current screen name (route templates only, never playlist names or share codes), whether the app was in the foreground or background, playback state (playing, buffering, queue size, casting), and recent operations such as library scans, imports, and queue loads with counts only. Reports are labelled with the same pseudonymous installation identifier used for usage metrics, so a crash report can be connected to that installation's usage records. Reports are therefore not anonymous, but they do not include your name or contact details.
Crash reports are not intended to include your audio files, song titles, artists, listening history, file paths, share links, notification tokens, screenshots, screen recordings, session replays, performance traces, or your device's user-assigned name or hardware identifiers. Sentry's default personal-information collection is disabled, and before a report leaves the device the app removes local file paths, URLs, email addresses, and authorization tokens from error messages. Native crash reports generated by the operating system can bypass this on-device filtering and rely on server-side scrubbing instead, so we cannot guarantee that every report is free of unintended personal information.
Sentry retains error events for its standard period of 90 days. We review crash reports in Sentry directly and do not keep a separate copy of them. This retention period does not apply to our separate usage records, aggregate statistics, or uploaded shares. Access to diagnostics is restricted to authorized administrators and to Sentry as our processor. See Sentry's privacy notice for information about its processing practices.
4. Advertising
Muzi uses Google Mobile Ads (AdMob) for advertising. This service processes information according to Google's advertising and privacy policies and your applicable device and consent settings. Its data processing is separate from Sentry crash reporting. Learn more in Google's advertising privacy information.
5. Contact Us
If you have questions about our privacy practices, please contact us at our contact page.