Effective date: 10/16/2026

This Policy explains what data the MusicMind — AI Music Radio app processes, why it is used, and how you can manage it.

Data controller: Andrey Boytsov.

Privacy contact: moloko812@gmail.com.

1. What Data Is Processed

To operate the app and provide personal recommendations, the following categories of data are processed.

Installation and session identifiers. On first launch, the app creates a random installation identifier. It is used to link listening events and the music profile. A separate identifier identifies an app session. These identifiers are not your name, phone number, or advertising ID, but they allow actions in the app to be linked to each other.

Music information. When access to audio files is granted, the app reads information about the local music library, including track titles, artists, albums, duration, and available genre data. To analyze the favorite tracks you select, their metadata is transmitted to the recommendation server. The local audio files themselves are not uploaded to the server under this function.

Listening and interaction events. The app stores and transmits events related to playback and use of music features to the server. These may include start, progress, and completion of listening, pauses, seeks, repeats, skips, likes, track saves, playlist additions, and queue removals. These events may relate both to recommended tracks and to local music.

Technical context. Along with events, the app may transmit the time of the event, time of day, day of week, app version, network connection type, battery level, volume, headphone connection status, whether the app is running in the background, queue information, and playback errors.

Music profile. Based on selected tracks and listening events, preference data is created: interest in genres, artists, and tracks, as well as calculated indicators for selecting recommendations.

Local data. Settings, library information, playlists, playback queue, downloaded music, cache, and events awaiting transmission to the server are stored on the device.

2. Why Data Is Used

Data is used to:

• play music and operate the library, queue, and playlists;
• create and update personal recommendations;
• display the music profile;
• take into account your genre preferences and reactions to tracks;
• synchronize events and manage downloads;
• analyze errors and maintain service operation.

3. App Permissions

Access to audio files is necessary to display and play music from your device. Depending on the Android version, this is audio access or storage read permission.

Notifications and the background service are used for player operation and playback control. Internet access is necessary for recommendations, online radio, music downloads, and event transmission.

The app does not request access to the microphone, camera, contacts, or precise location. The visualizer analyzes the sound being played and does not record surrounding conversations.

You can change granted permissions in Android settings. Revoking audio file access will limit work with the local library.

4. Servers and External Services

Listening events, the installation identifier, and personalization data are transmitted to the MusicMind server over HTTPS.

To clarify track information, the server may query external music and search services, including MusicBrainz, Last.fm, Apple iTunes, Suno, and DuckDuckGo. The set of requests depends on server configuration and source availability. Such requests may contain the track title and artist name.

When downloading audio, artwork, and radio streams, the app contacts the relevant servers. The server receiving the network request obtains the connection IP address and technical information necessary to process the request. Processing by external providers is also governed by their own privacy policies.

5. Data Retention and Security

Data is stored on the device and in MusicMind’s server infrastructure depending on its purpose. Events awaiting transmission are temporarily stored on the device; after successful sending, they are deleted from the local transmission queue.

HTTPS is used to connect to the main recommendation server. The installation identifier and the deletion request confirmation key are stored on the device in encrypted form. Access to server data is restricted.

Server history and the music profile are retained until deletion through the app settings or for [specify periods or retention criteria], unless otherwise required by law. Technical logs and backups are retained for [specify period]; deletion from them is performed [specify procedure]. Depending on device and Android settings, app data may be included in system backup.

6. Data Deletion

You can use the “Delete my server data” command in the app settings.

After successful completion, related listening events, music profile, information about selected favorite tracks, and personalization calculation data are deleted from the service’s primary database. Local music files and playlists remain on the device.

An internet connection is required to complete the request. If you continue using the app, new events may again be transmitted to the server and form a new recommendation profile. Data deletion is not a permanent opt-out from data collection.

Deleting the app or clearing its local data does not by itself send a request to delete the server profile. If you want to delete server data, use the corresponding command before deleting the app.

Data deletion is performed automatically by the command. If the command is unavailable, does not work, or you have other privacy questions, contact: [email].

7. Changes to This Policy

This Policy may be updated when app features or data processing practices change. The effective date is indicated in the current version.

8. Contact

MusicMind — AI Music Radio
Developer: Andrey Boytsov
Email: moloko812@gmail.com