Feedback and automatic diagnostics are available in version 1.2.0 and later. Automatic diagnostics are disabled by default.
Who is responsible
The developer and data operator for Open Music Player is Vasiliy Tatarli. For privacy questions, contact Open Music Support at support-openmusic@performarc.app.
Data stored on your device
Your library, favorites, queue, playlists, recognition history and settings are stored locally. Recognition history may include a matched title and artist, an artwork URL and the recognition time. Listening counters and dates used for smart collections, positions for long recordings, bookmarks and selected LRC lyrics also remain on the device.
Open Music Player does not require an account, does not contain advertising and does not send listening analytics. The optional technical diagnostics described below are separate.
Files, folders and collection transfer
The app accesses only files and folders that you explicitly choose through the system interface. It does not scan the entire device. Access is used to read metadata and artwork, organize the library and play audio. Disconnecting a folder or clearing the library removes app records without deleting source audio.
At your request, collection export creates a JSON file containing music titles and artists, playlists, favorites, bookmarks and settings. It excludes audio, lyrics, listening history, original file paths, folder permissions and diagnostics. The system file or cloud provider you select handles the exported file under its own terms. Import validates the file and matches it against the local library; it does not grant access to new folders.
On Android Auto, a connected vehicle display may receive local section names, track details and playback state so you can browse and control music. The car catalog remains local. The microphone, feedback form and file pickers are not exposed in the car interface. CarPlay is not included in the iOS 1.2.0 release.
Microphone and song identification
Identification is optional and starts only when you request it. Microphone permission is requested when you begin microphone identification; you can refuse it or revoke it later in system settings. You may instead select one audio file through the system picker.
Audio is processed on the device to create an acoustic signature. Open Music Player does not save the source microphone recording or upload the selected source file to a developer-operated server. Apple ShazamKit receives the signature and ordinary network data to look for a match. After a match, the app may load artwork from the address returned by ShazamKit or open an external track link.
Platform differences and the Android token service
On iPhone and iPad, Open Music Player uses Apple ShazamKit directly and does not contact the Open Music Android token service.
On Android, before identification, the app makes an HTTPS request with no body to an Open Music service on Cloudflare to obtain short-lived ShazamKit access. The service does not receive audio, an acoustic signature, file names, library contents or recognition history.
Cloudflare processes the IP address and ordinary network metadata at the network edge. For abuse prevention, the Worker combines the IP address with a secret salt to create a pseudonymous HMAC code that changes daily. Only that code reaches the regional rate limiter. It is not an account or installation identifier and may be shared by users on the same network.
The Worker code does not log IP addresses, HMAC codes, access keys or responses, and Workers Logs, traces and observability are disabled for this service. Cloudflare may still process or retain network metadata to provide, secure and operate its network under its own policy.
Feedback and automatic diagnostics
The in-app form sends only after you press Send. It can include your selected category, the message you enter, an optional reply email, app version and build, device model, operating-system version, event time and a random report number. Music, library contents, microphone recordings and log files are not attached automatically.
If you include an email or personal information in the message, the report may be linked to you and is not anonymous. Without a connection, a report is held in a private on-device queue and retried later. The queue holds up to ten reports; unsent reports older than seven days are removed during the next queue operation.
Automatic diagnostics are disabled by default and require a separate opt-in. When enabled, the app may send a predefined operation category and error code, sanitized code-location information, app version/build, device model, OS version, event time and a random event number. Reports exclude raw error text and logs, song and file names, personal file paths, library contents, audio, microphone recordings, access keys, email addresses and persistent user or device identifiers. Screenshots, screen recordings, tap history, ad tracking and behavior analytics are not used.
On iPhone and iPad, up to 20 pending automatic events may be retained locally; unsent events older than seven days are removed. Turning diagnostics off stops new automatic reporting and clears pending automatic events from the device. It does not recall reports already delivered and does not remove feedback that you submitted separately.
Service providers and retention
Sentry receives feedback and optional sanitized diagnostics over HTTPS. The project uses Sentry’s European region, though supporting processing is not guaranteed to remain in one country or region. Sentry necessarily receives ordinary network metadata. The app does not add an IP address to the report payload; IP storage in events is disabled and standard server-side data scrubbing is enabled.
Developer-plan events are retained by Sentry for 30 days. Events received under trial terms may be retained for up to 90 days. Sentry backup deletion follows its published cycle. Support notifications and replies may also be stored in the project mailbox for as long as reasonably necessary to answer, investigate a problem and meet applicable legal requirements.
For more information, see the policies of Sentry, Cloudflare and Apple Music Recognition.
Sale, advertising and tracking
The developer does not sell Open Music Player data, create advertising profiles or use app data to track you across apps and websites. Optional identification, feedback and diagnostics use the providers described above only for their stated functions.
Deletion and control
Clear Library removes the local catalog, cached artwork, track references, bookmarks connected to removed tracks and folder permissions stored by the app. It does not delete source audio. Playlist names, settings and recognition history are managed separately; recognition history has its own clear action.
To stop automatic diagnostics, turn the setting off. To request deletion of a submitted support report, email support-openmusic@performarc.app and include the reply email used in the report, or enough information such as its date and message to locate it. Do not send identity documents. A report with no contact details or persistent identifier may not be reliably attributable to a particular person.
Deleting the app removes its local container, including pending feedback. It does not delete system backups or data already processed by Apple, Cloudflare or Sentry; those providers handle deletion under their policies and settings.
Contact
For privacy questions or requests, email support-openmusic@performarc.app or visit the support page.