Effective 4 November 2026 · previous version 5 October 2026
SoundPilot collects nothing, stores everything on your device, and has no ability to send data anywhere itself. The app does not request Android's INTERNET permission, so it is technically incapable of transmitting your information — this is not only a policy commitment but a property of the build.
One thing does leave the phone, and it is not us: if you have Android backup switched on, the system copies your profiles into your own Google account. We never receive it and cannot read it. How that works.
Nothing. SoundPilot has no accounts, no sign-in, no analytics, no advertising, no crash reporting, and no third-party SDKs of any kind. We do not collect personal information, usage statistics, device identifiers, or diagnostics. No information about you or your device ever reaches us, because the app cannot make network requests.
SoundPilot saves the sound profiles and trigger rules you create — volume levels, ringer and Do Not Disturb settings, and which Bluetooth device a rule is attached to. All of it is written to the app's private storage on your phone, where no other app can read it.
Clearing the app's data from Android's app settings erases it at any time. Uninstalling SoundPilot removes the copy on your phone — but if Android backup is on, a copy may remain in your Google account, and reinstalling can restore it. That is the one qualification to "it stays on your device", and it is explained next.
SoundPilot takes part in Android's standard backup, which is a platform feature, not something the app operates. Two transports use it: Auto Backup, which copies app data into your Google account, and device-to-device transfer, which moves it directly when you set up a new phone.
Exactly one file is included, and the app names it explicitly rather than backing up everything it holds: the profiles store. In practice that means your profiles, your trigger rules, which profile is active, and the names of the Bluetooth devices you have attached to rules. Caches and anything transient are excluded.
What this does and does not mean:
| Permission | Why SoundPilot needs it |
|---|---|
ACCESS_NOTIFICATION_POLICY |
Lets a profile change Do Not Disturb and silent-ringer state when it is applied. Without it, Android will never allow those modes to be set. |
BLUETOOTH_CONNECT(Android 12 and newer) |
Reads your list of paired Bluetooth devices so you can choose one when creating a rule, and detects when that device connects or disconnects so the matching profile can be applied. |
BLUETOOTH(Android 8–11) |
The older equivalent of the above, used on versions of Android that predate the runtime permission. |
REQUEST_OBSERVE_COMPANION_DEVICE_PRESENCE |
Asks Android to tell SoundPilot when one specific Bluetooth device — one you chose and confirmed by name — comes into range. Some phones freeze background apps so aggressively that the ordinary connect signal never arrives; on those, this is the route that still works. |
REQUEST_COMPANION_RUN_IN_BACKGROUND |
Lets SoundPilot act on that signal while it is not open. Without it the phone would wake the app and stop it again before your profile could be applied. |
SYSTEM_ALERT_WINDOW |
Draws the floating volume control on top of other apps, which is the whole point of that feature. You grant it from a system settings screen, and the control only appears while you have switched it on. |
FOREGROUND_SERVICE(Android 9 and newer) |
Keeps the floating control running while it is switched on, instead of the system shutting it down moments after you leave the app. The service starts when you enable the overlay and stops when you disable it. |
FOREGROUND_SERVICE_SPECIAL_USE(Android 14 and newer) |
Newer Android versions require an app to state what kind of foreground service it runs. This is that declaration for the floating control — it grants no additional access. |
POST_NOTIFICATIONS(Android 13 and newer) |
Shows the notification that Android requires alongside the floating control, so the feature is never running invisibly. It is the only notification SoundPilot posts. |
RECEIVE_BOOT_COMPLETED |
Brings the floating volume control back after you restart the phone or after the app updates — and only if you had it switched on. Nothing else happens at startup; the app does not launch itself to do anything in the background. |
VIBRATE |
Gives the short tap you feel when a button on the floating volume control changes the volume. Some phones refuse that feedback to an app without this permission. It is granted when you install the app, without a prompt, and it lets SoundPilot do nothing except vibrate. |
That is the complete list — eleven permissions, and no others. SoundPilot requests no location permission, no camera, no microphone, no contacts, no storage access, and no INTERNET permission.
Bluetooth information is read on your device, used immediately to decide whether a rule should fire, and never stored beyond the device name you deliberately attach to a rule. SoundPilot does not scan for nearby devices and does not use Bluetooth to determine where you are.
Two of those permissions deserve a plainer sentence than a table row gives them. Asking Android to watch for a companion device is a presence observation: for the one device you picked, the system tells SoundPilot when that device is there. Android asks you to confirm each device once, by name, in a dialog you have to accept — the app cannot add a device quietly. It learns nothing about where you are, nothing about any other device, and nothing it could send anywhere even if it wanted to.
Some manufacturers shut background apps down aggressively, which would stop your profiles from being applied. So that the setup screens can send you straight to the right settings page, SoundPilot checks whether certain manufacturer settings apps are present — the battery and auto-start managers from Samsung, Xiaomi, Huawei, Honor, OPPO, OnePlus, vivo and Transsion.
This is a fixed list, written into the app's manifest and visible to anyone who inspects it. SoundPilot can check only for those specific apps — it cannot see the rest of what you have installed — and the answer is used on the spot to decide whether to show a button. Nothing is recorded, and nothing is sent.
We share nothing, because we hold nothing. There are no third parties involved in the app: no analytics provider, no advertising network, no hosting backend, no data processor. The Android backup described above is not a sharing arrangement of ours — it is a transfer between you and Google, using your own account, which you can switch off.
SoundPilot is a general-purpose utility and is not directed at children. It collects no data from anyone, including children.
Regulations such as the GDPR give you rights to access, correct, export, and delete personal data held about you. We hold no personal data about you, so there is nothing for us to disclose or erase. The data SoundPilot creates lives on your own device — and, if you have Android backup on, in your own Google account — and is entirely under your control in both places.
If a future version of SoundPilot adds a feature that changes any of the above — for example optional crash reporting — this page will be updated before that version ships, the effective date will change, and the Google Play Data safety declaration will be updated to match.
Questions about this policy or about SoundPilot's handling of data: privacy@soundpilot.dev