Safety & Trust
App Permissions Explained
A three-tier read on Android permissions: expected, questionable, and stop-the-install.
Expected permissions
| Permission | Why a media app needs it |
|---|---|
| INTERNET | Fetching streams and guide data |
| ACCESS_NETWORK_STATE | Detecting connectivity changes to pause or resume |
| WAKE_LOCK | Keeping the screen on during playback |
| FOREGROUND_SERVICE | Continuing audio in the background |
| READ_EXTERNAL_STORAGE | Loading a user-supplied playlist file |
Questionable permissions
- ACCESS_FINE_LOCATION — precise location is not needed for playback; coarse region checks do not require GPS.
- READ_PHONE_STATE — historically used for device identifiers, which is a tracking capability rather than a playback one.
- REQUEST_INSTALL_PACKAGES — lets the app trigger further installs; reasonable only for a self-update flow you were told about.
- SYSTEM_ALERT_WINDOW — draw-over-other-apps, used legitimately for PiP-style overlays and illegitimately for tap-jacking.
Stop-the-install permissions
| Permission | Capability it grants |
|---|---|
| BIND_ACCESSIBILITY_SERVICE | Read screen content and perform actions as you |
| READ_SMS / RECEIVE_SMS | Read messages, including one-time passcodes |
| READ_CONTACTS | Harvest your address book |
| BIND_DEVICE_ADMIN | Device-administrator control, resisting uninstall |
| READ_CALL_LOG | Access call history |
Worth knowing: BIND_ACCESSIBILITY_SERVICE is the single most consequential permission on Android — it can read screen content and act on your behalf — and no media player needs it.