VolumeDial is developed for CauGiay Hotel. This Privacy Policy explains what information VolumeDial (“the App”) accesses, why, and how it is handled. It reflects the App’s actual code and configuration, and is kept up to date whenever the App’s data behaviour changes.
If you have questions about this policy, contact us at cghotel1206@gmail.com.
| Permission | What it is used for |
|---|---|
| Display over other apps | Required to draw the floating volume dial on top of whatever app you’re using when you press the volume keys. |
| Accessibility Service | Required so the App can detect physical volume-key presses (Android does not allow apps to intercept hardware key events any other way) and to know which app is currently in the foreground, so the dial can be skipped for apps you’ve chosen to exclude (e.g. camera or phone apps). The App does not read, collect, or share the content of your screen or of other apps — see § 4. |
| Foreground service / “Special use” foreground service | Keeps the overlay ready to appear the instant you press a volume key, with a persistent notification as Android requires for any always-on background service. |
| Notifications (POST_NOTIFICATIONS) | Shows that persistent “volume overlay is running” notification. Not used to read notifications from other apps. |
| Modify audio settings | Lets the App change your device’s media volume when you use the dial or press the volume keys. |
| Vibrate | Produces the haptic feedback you can customize for volume changes and limit boundaries. |
| Notification access (optional) | Only if you separately grant this in Android system settings, the App can read the title of the track currently playing to show a “now playing” label on the dial. Not used to read the text/content of your notifications. Off unless you turn it on. |
| Ignore battery optimizations (optional) | Lets you exempt VolumeDial from battery optimization so the background service isn’t stopped by the system. Entirely optional and user-initiated. |
| Internet / network state | The App itself has no backend and does not upload your settings or files anywhere. Needed because the bundled Firebase SDKs (§ 3) require network access to send analytics/crash data and fetch remote configuration. |
| Notification policy access, Wake lock | Standard Android permissions declared for background-service/audio interoperability. Neither is used by VolumeDial to read personal data, your contacts, or the content of your notifications. |
VolumeDial uses the following third-party services, and no others:
The App includes the Firebase SDK, which automatically collects:
This data is processed by Google under Firebase’s own terms and privacy policy (firebase.google.com/support/privacy). We do not combine this data with any personally identifying information, because VolumeDial has no account system to tie it to.
No other third party receives data from VolumeDial. In particular:
Android requires an Accessibility Service in order for an app to detect and act on physical volume-key presses while running in the background (there is no other public API for this). VolumeDial’s Accessibility Service is used only to:
The service’s configuration also requests the Android capability needed to receive key-event callbacks (a required technical combination on Android), but VolumeDial’s code does not read, store, log, analyze, or transmit anything about the text, images, or layout displayed on your screen or inside other apps — that data is never accessed by the App’s logic. You can review or revoke this permission at any time from Android Settings → Accessibility.
VolumeDial is a general-purpose utility and is not directed at children. We do not knowingly collect personal information from children. If you believe a child has provided us information, contact us at cghotel1206@gmail.com and we will address it.
We may update this Privacy Policy as the App’s features or the services it uses change. We will update the effective date above when we do. Continued use of the App after a change means you accept the updated policy.