MusiCo — Privacy Policy

Last updated: 8 September 2026 · Applies to the Android app com.k.sekiro.musico

The short version

MusiCo is an offline music player. Your music, playlists and listening history stay on your phone — they are never uploaded to us or anyone else, and there is no account to create.

The app does send anonymous usage and crash statistics to Google Firebase, which helps fix bugs. That is the only data that leaves your device automatically, and it is described in full below.

Who is responsible

MusiCo is an independent app developed by an individual developer. There is no company behind it, no analytics broker, no advertising network and no data is sold or shared for marketing. Questions about this policy or your data can be sent to the contact address at the bottom.

What stays on your device

The following never leaves your phone. It is stored in a private app database that only MusiCo can read, and it is deleted when you uninstall the app:

What is sent off your device

MusiCo uses two Google Firebase services. Neither receives your music, your file names, your playlists or your listening history.

Firebase Crashlytics — crash reporting

When the app crashes, a report is sent so the fault can be found and fixed. It contains the technical state of the crash: the error and stack trace, the device model, the Android version, the app version, and how long the app had been running.

Firebase Analytics — anonymous usage statistics

Aggregate, non-identifying information about how the app is used — for example how often it is opened, and on which device models and Android versions — so effort goes to the things people actually use. It includes a randomly generated app instance identifier, your approximate region (derived from your IP address by Google, not stored by us), device model, and language.

Advertising identifier

Firebase Analytics can access your device's Android Advertising ID. MusiCo shows no adverts and does not use this identifier to profile or target you, but it is technically available to the analytics library, so it is disclosed here rather than left unsaid.

You can reset or delete this identifier at any time in Settings → Privacy → Ads on your device, which also lets you opt out of personalisation entirely.

Data handled by these services is processed by Google under Google's Privacy Policy. See also Firebase and privacy.

Permissions, and why each one is needed

Android asks your permission for the sensitive ones the first time a feature needs them. You can refuse any of them — only music access is required for the app to be useful at all; the rest just disable the feature that needs them.

PermissionWhy MusiCo needs it
READ_MEDIA_AUDIO
READ_EXTERNAL_STORAGE
To find and play the music on your device. This is the core function of the app. Without it there is nothing to play. READ_EXTERNAL_STORAGE is only requested on Android 12 and older, where the newer audio-only permission does not exist.
WRITE_EXTERNAL_STORAGE To delete a song from your device when you choose to, and to save songs you accept from another phone. Only requested on Android 12 and older.
POST_NOTIFICATIONS To show the playback notification with play, pause, next, shuffle and repeat controls, and to show transfer progress. Refusing it only removes those notifications.
FOREGROUND_SERVICE
FOREGROUND_SERVICE_MEDIA_PLAYBACK
So music keeps playing when you switch apps or turn the screen off. Android requires an app to hold these to run audio in the background.
FOREGROUND_SERVICE_DATA_SYNC So a song transfer to or from another phone can finish while the app is in the background, instead of failing when you switch away.
CAMERA Only to scan a QR code when someone shares a playlist with you. The camera is used to read the code and nothing else — no photo or video is recorded, saved or transmitted, and the camera is released as soon as you leave the scanner. The app also declares the camera as optional hardware, so it installs on devices without one.
NEARBY_WIFI_DEVICES To find the other phone when sending or receiving songs directly. It is declared with Android's neverForLocation flag, which is a formal promise to the system that MusiCo does not use it to work out where you are.
ACCESS_FINE_LOCATION Only on Android 12 and older, and only for direct phone-to-phone transfer. On those versions Android required location permission before an app could scan for nearby Wi-Fi devices, whether or not it wanted your location. MusiCo does not read, store or transmit your location. On Android 13 and newer this permission is not requested at all.
INTERNET
ACCESS_WIFI_STATE
CHANGE_WIFI_STATE
CHANGE_NETWORK_STATE
ACCESS_NETWORK_STATE
To set up the direct Wi-Fi link between two phones for transferring songs, to check whether a connection is available, and to send the crash and analytics reports described above. Your music is never sent over the internet.
AD_ID
ACCESS_ADSERVICES_AD_ID
ACCESS_ADSERVICES_ATTRIBUTION
BIND_GET_INSTALL_REFERRER_SERVICE
Added automatically by the Firebase Analytics library, not requested by MusiCo's own code. They let that library read the advertising identifier and see how the app was installed. MusiCo contains no adverts and does not use them to profile or target you; they are listed here because they appear in the app's manifest and you are entitled to know why. See the note on the advertising identifier above for how to reset or opt out.
WAKE_LOCK
RECEIVE_BOOT_COMPLETED
Added automatically by the Android media and background-work libraries so playback is not interrupted and the home screen widget can be restored after a restart.

Sharing playlists and sending songs

MusiCo can share a playlist as a QR code, and can send the actual audio files to another phone running MusiCo. Both work without any server of ours:

Keeping and deleting your data

Children

MusiCo is not directed at children under 13 and does not knowingly collect personal information from them. It has no accounts, no profiles, no messaging and no user-generated public content.

Changes to this policy

If the app changes what it collects or which permissions it needs, this page is updated and the date at the top changes with it. Significant changes will also be noted in the app's release notes on Google Play.

Contact

For any question about this policy or about your data, write to khaliddeveloper2003@gmail.com.