MusicXMusicX is designed around your own music library. Most MusicX data stays on your devices. Features that use a connected service or another device may send the information needed for that feature.
This policy applies to MusicX for iPhone, iPad, Mac, and Android, related widgets and shortcuts, connected media-device features, and this website. Availability varies by platform and build.
The upcoming Apple version uses local files, a selected iCloud music folder, and SMB/NAS, with only embedded lyrics or plain text or LRC you paste or import. It does not include Google Drive or online lyrics lookup. Earlier Apple and Android builds may include Google Drive or online lyrics; the disclosures below also cover those connections.
Information MusicX stores on your device
MusicX stores the information it needs to organize, play, sync, and restore your music library. This can include library entries, file paths, security-scoped file bookmarks, source names, song titles, artists, albums, genres, playlists, favorites, queue state, resume position, lyrics, artwork references or cached artwork, equalizer settings, playback settings, app preferences, and diagnostics settings.
This information is used for playback, search, library repair, metadata editing, playlist import, source preferences, offline downloads, widgets, Siri or app shortcuts, nearby playback, Direct Sync, supported sync points, and restoring selected sources after relaunch. Google Drive features apply only to builds that include them. MusicX does not use your local library information for advertising or cross-app tracking.
How MusicX gets information
MusicX gets information when you choose files, folders, libraries, discs, cloud folders, provider settings, or devices; when the app scans media that you have allowed it to access; when you edit metadata, playlists, or settings; when you connect another service; and when the operating system provides information needed for a permissioned feature.
On Android, MusicX may request media-library and storage permissions such as audio-library access, older external-storage access, or broad file-management access where the feature needs to scan or manage a user-selected music collection. MusicX can also use camera access on iPhone, iPad, or Android when you choose to scan a local Direct Sync pairing code. On Apple platforms, MusicX uses file pickers, security-scoped bookmarks, iCloud entitlements, local-network permissions, camera permission for pairing codes, Siri permission, and removable-volume access on Mac where applicable.
Optional permissions and connected features
These features are optional or depend on a user action. The data involved is used for the feature you choose.
- Local music files and folders: MusicX reads audio files and metadata from folders, app documents, removable volumes, Android media libraries, or other sources you add so it can build and play your library.
- Camera pairing codes: On iPhone, iPad, or Android, MusicX can use the camera when you choose to scan a local Direct Sync pairing code shown by your Mac, phone, tablet, or another MusicX device. The camera is used for that scan and is not used for advertising or developer analytics.
- Local network and Direct Sync: MusicX can discover, pair with, compare metadata with, and transfer selected music to another MusicX device on your local network. Pairing and transfer require your approval. MusicX may exchange device names, pairing identifiers, library metadata, file names, file sizes, file dates, sync status, and selected audio files needed for the transfer.
- iCloud: If you enable iCloud features, MusicX may store or sync MusicX documents, settings, library state, sync documents, or encrypted catalog evidence in your iCloud container so the data is available on your Apple devices. Apple processes that data under the Apple Privacy Policy, iCloud Terms, and Apple iCloud/CloudKit service rules.
- Google Drive in Android and earlier test builds: Builds with this integration use Google authorization and the permissions you grant to read selected music and separately sync MusicX app data. Android builds that support editing original Drive files request separate consent for that action. Google Drive is not included in the forthcoming Apple release. Google processes data under the Google Privacy Policy, Google Terms of Service, Drive API rules, and Google Account controls. See Google data details.
- Android phones, MP3 players, DAPs, and USB/MTP media devices: When you connect one of these devices, MusicX may read device names, storage names, serial or topology identifiers where exposed by the device, folder paths, audio file names, file sizes, file dates, and song metadata so it can show available music and copy selected files. MusicX does not read unrelated app data and does not automatically upload a USB/MTP inventory to the developer.
- SMB and NAS sources: If you add a network share, MusicX stores the server address, share name, root path, display name, user name, domain, signing or encryption preference, and related settings. Passwords or API keys are stored in Keychain or encrypted Android storage where supported and are supplied to the provider only at runtime. On Apple devices, saved NAS connections and their login credentials can be shared through iCloud Keychain on devices using your Apple Account with iCloud Keychain enabled. These credentials are not included in ordinary library sync files.
- Embedded and imported lyrics: The upcoming Apple version reads only lyrics already embedded in your music and plain text or LRC you paste or import. Timed highlighting requires timed lyrics. These lyrics features do not send online lyrics requests.
- Artwork, metadata, and identification providers: Where enabled in your build, MusicX can contact Apple ShazamKit, artwork sources, or user-installed providers. Requests can include title, artist, album, duration, catalog or provider identifiers, file metadata, or an audio fingerprint or signature. Connected services also receive network request information such as your IP address.
- Online lyrics in earlier Apple and Android builds: These builds could send song details such as title, artist, album, and duration to online lyrics providers, and may still do so when online lookup is enabled. Providers also receive your IP address with the request. Provider retention and linkage of request data are unknown. Using a version without online lookup does not delete information a provider already received.
- Custom provider manifests and add-ons: In builds that permit them, imported manifests can define HTTPS endpoints and privacy notes. MusicX stores the imported provider metadata and credentials needed for the chosen integration. Review the provider's notes before enabling it. The upcoming Apple version does not use add-ons for online lyrics.
- Diagnostics and support: MusicX keeps its diagnostics on your device and does not automatically send its issue reports or logs to the developer. Raw diagnostics may include app events, library counts, paths, song metadata, source names, transfer or network status, and errors. In Apple builds with Report Issue, recent-event summaries, selected crash excerpts, and native crash/hang summaries are optional. You can preview, share, or save the report yourself. Selected crash excerpts can retain MusicX build UUIDs and relative code offsets; redaction cannot guarantee that every private detail is removed. Apple/TestFlight diagnostics are separate and follow Apple's settings and policies.
Provider content and song-file write-back
Artwork, lyrics, metadata, and identification results can be copyrighted or limited by provider terms. MusicX may display provider results, store them in the MusicX app library, cache them for app use, or keep provider references so the feature works for your personal listening and library-management experience. MusicX does not claim ownership of provider content.
Provider results may appear in MusicX's library, cache, sync state, widgets, or now-playing surfaces. Their appearance does not by itself mean original audio files were retagged. Earlier builds may retain online lyrics in app state or caches even after a provider is disabled.
Access to a provider's service does not itself grant permission to display, cache, embed, export, or transfer third-party artwork or lyrics. MusicX does not claim ownership of or a license to third-party lyrics through that access. Older builds may retain previously retrieved lyrics.
MusicX can write track metadata when you choose to edit or transfer files or rip a CD. Supply only artwork, lyrics, and other content you are authorized to use. Earlier builds may still contact online providers. Data already held by those providers is subject to their own retention practices.
Google API data and Limited Use
This section applies to Android and earlier Apple builds that include Google Drive. The upcoming Apple version does not include Google Drive. Google may provide MusicX with an account name, email address, account identifier, OAuth access token, granted scopes, and file/folder metadata. The normal connection requests https://www.googleapis.com/auth/drive.readonly and https://www.googleapis.com/auth/drive.appdata. Read-only access applies across Drive; your folder selection limits scanning, not the OAuth grant itself. App-data access reads and writes MusicX sync documents containing library state, queue, position, favorites, playlists, lyrics state, provider choices, EQ settings, source identities, and related metadata. App-data sync does not edit original music files.
Android builds that support editing original Drive files separately request the broader https://www.googleapis.com/auth/drive permission when you explicitly choose to save metadata into original Drive song files. That file-editing consent is separate from ordinary read-only playback and app-data sync. Availability varies by Android build and account.
MusicX uses Google user data only to provide and maintain the Google Drive features you choose, keep the selected account connected, verify the account and scopes, read music metadata, stream or download audio from selected Drive music folders, and sync MusicX state. MusicX does not sell Google user data, use it for advertising, use it for credit or eligibility decisions, or use it to train generalized AI models.
MusicX does not use Google APIs or Google user data to create or distribute AI-generated non-consensual intimate imagery.
MusicX does not transfer Google user data except as needed to provide the Google Drive feature, when you direct the app to move or sync data, when required by law, or with a service provider that is bound to protect the data. MusicX's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. Learn more from Google's Drive files and folders overview, Drive app data folder documentation, OAuth policy compliance guide, and Google Account linked-app access controls.
Provider documentation and privacy links
The following external services may apply their own terms, privacy notices, or developer rules when you choose a connected feature. These links are provided so you can review the provider documents directly:
- Apple Privacy Policy, iCloud Terms, and Apple CloudKit documentation for iCloud-backed MusicX data.
- Apple ShazamKit documentation and Shazam & Privacy for music-recognition features.
- Google Privacy Policy, Google Terms of Service, the Google API Services User Data Policy, Google Drive OAuth scope documentation, Google Drive files and folders overview, Google Drive app data folder documentation, Google OAuth policy compliance guide, and Google Account linked-app controls for Google Sign-In and Google Drive features.
- Cloudflare Privacy Policy for delivery and security logs generated when this website is visited.
Sharing and third-party processing
MusicX does not sell personal information and does not share personal information for targeted advertising or cross-context behavioral advertising. MusicX does not include a developer-run advertising network or third-party tracking SDK in the current app.
MusicX shares or transmits data only when needed for a feature you choose, for example to Apple iCloud or ShazamKit services, Google Drive and Google Sign-In, a local MusicX device, an SMB/NAS server you add, a USB/MTP device you connect, or an artwork, lyrics, metadata, identification, or custom provider you enable. Those third parties process data under their own privacy terms and must protect user data consistently with their obligations and the feature's purpose.
The App Store, TestFlight, Google Play, the Microsoft Store if MusicX is distributed there, Apple, Google, and Microsoft may process account, purchase, device, crash, review, download, and store-listing information under their own policies. MusicX does not receive payment-card details from those stores.
Information you choose to send for support
If you email support, the developer receives your email address, message, and the reports, screenshots, or other attachments you choose to include. Reports may contain app/OS versions, playback and library summaries, event or error details, and optional crash/hang information. Because they arrive with your message, we treat this information as linked to you.
We use support messages and reports only to respond to support requests and investigate and fix bugs. We do not use them for marketing, advertising, or tracking. Sharing a report is voluntary; review the complete preview and attachments before sending.
The Apple beta uses private email invitations for up to 100 testers. If you request an invitation, we use your email address and the device and music-source details you choose to provide to arrange testing access and related support, not a marketing mailing list. The beta invitation form sends your request to MusicX support through Web3Forms. Invitations are reviewed and sent privately; there is no public TestFlight join link. The form does not reserve a place or create a purchase.
Privacy-policy website hosting
This website is hosted on Cloudflare Workers. It does not include MusicX analytics scripts, advertising scripts, cookies, external fonts, or client-side tracking code. Cloudflare may process basic request information such as IP address, user agent, requested URL, time, and security signals to deliver and protect the page. That website request data is separate from your MusicX library data.
When you send a beta request, your browser sends your email address, selected devices, optional music-source details and notes directly to Web3Forms for delivery to our support inbox. Web3Forms also receives network information such as your IP address. It stores submissions encrypted and uses service providers for hosting, delivery and spam prevention; its spam checks may share submitters’ email and IP addresses with CleanTalk or Akismet. See the Web3Forms Privacy Policy and data-processing agreement. We set Web3Forms to delete new submissions after seven days. Copies delivered to our support inbox are kept as needed to manage beta access and related support. We do not add form submissions to a marketing mailing list.
Retention and deletion
Local MusicX data stays on your device until you delete it, remove the related source, clear downloaded or cached data, reset MusicX data, or uninstall the app. iCloud and Google Drive sync data stays in those services until you delete it from MusicX or from the provider's storage controls. MusicX may keep local diagnostics until you delete them or reset the app.
If you disconnect Google Drive, iCloud, SMB/NAS, Direct Sync, a custom provider, or a USB/MTP device, MusicX stops using that connection. Disconnecting a provider may not automatically delete copies already stored by that provider or by another device; use the provider's own controls when you want to remove remote data.
Support correspondence and reports are kept as needed to handle the request and investigate related bugs. You can ask about access, correction, or deletion of information the developer actually received using the contact below. No fixed automatic deletion period is promised here. Retention and linkage of data from earlier online lyrics requests are unknown.
Security
MusicX uses platform security features where supported, including sandboxed app storage, security-scoped file access and Keychain storage on Apple platforms, encrypted Android credential storage, OAuth token handling in builds with Google Drive, HTTPS for remote provider requests, and local-network pairing controls for Direct Sync. No app or network service can guarantee perfect security, so only connect services and providers you trust.
Children's privacy
MusicX is a general-audience music library app and is not directed to children under 13. MusicX does not knowingly collect personal information from children through a developer-run account service. If you believe a child has provided personal information to MusicX support, contact the developer support channel listed for MusicX so it can be reviewed and deleted where appropriate.
Your choices and privacy rights
You can control MusicX data by deleting libraries, sources, downloads, playlists, cached artwork, diagnostics, provider credentials, or app data; revoking file, camera, local-network, media-library, storage, Siri, iCloud, or notification permissions in system settings; disconnecting Google Drive or revoking MusicX access in your Google Account; unplugging USB/MTP devices; declining Direct Sync pairing or transfer requests; and using iCloud, Google Drive, SMB/NAS, or device-storage controls to delete remote copies.
MusicX currently has no developer-run account database. The developer normally cannot look up, export, correct, or delete the library data that stays on your device, in your iCloud container, in your Google Drive, on an SMB/NAS share, on a USB/MTP device, or in another store account. Privacy requests to the developer can cover information the developer actually receives, such as a support message, crash report, screenshot, diagnostic log, store-review message, or other information you choose to send. If the developer has no such information, there may be nothing developer-held to access, correct, or delete. MusicX does not sell personal information or use targeted advertising.
Changes to this policy
This policy may be updated when MusicX features, connected services, store disclosures, or legal requirements change. If MusicX changes how it uses Google user data or adds a materially different data use, the published policy and any required in-app notice or consent should be updated before that new use begins.
Contact
For privacy questions or requests about information you choose to send to the developer, email Support@getmusicx.com. See MusicX support for what to include and how to protect sensitive information.