Data Safety disclosure
This page describes how BluePadel accesses, uses, and protects data. It mirrors the disclosure we submit to the Google Play Data Safety form and is provided so you can read the full picture in one place. The defining characteristic of BluePadel's data handling: everything stays on your own devices.
What BluePadel accesses
The table below lists every Data Safety category Google Play asks developers to disclose. "Collected" means BluePadel reads the data into memory or storage on your device. "Shared" means BluePadel transmits the data to a third party (we don't transmit anything). "Optional" means you can use the app without granting it.
| Data type | Collected | Shared | Purpose | Optional? |
|---|---|---|---|---|
| Personal info (name, email, address, phone, ID, etc.) | No | No | BluePadel has no accounts — we don't ask for any of this. | — |
| Financial info (payment cards, purchase history) | No | No | Handled entirely by Google Play; we don't see card data. | — |
| Health and fitness (heart rate, accelerometer) | On device | No | Live heart-rate readout and swing detection during a match. Read in real time from Android Health Services on the watch; persisted only if attached to a saved match. | Optional — denying the BODY_SENSORS permission disables these features. |
| Messages, photos, audio | No | No | BluePadel doesn't access messages, photos, or audio. | — |
| Files and documents | No | No | BluePadel doesn't read or write files outside its own private storage. | — |
| Calendar, contacts | No | No | BluePadel doesn't access calendar or contacts. | — |
| Location (approximate or precise) | No | No | BluePadel doesn't request location permission. | — |
| Web browsing history | No | No | BluePadel doesn't open browsers or web views. | — |
| App activity (in-app actions, search history) | On device | No | The match history shown on your phone is a record of your scoring actions in the app. It lives in a Room database in BluePadel Companion's private storage on your phone. | — |
| App info and performance (crash logs, diagnostics) | No | No | BluePadel does not run any crash-reporting or analytics SDK. There is no Firebase, Crashlytics, or third-party diagnostics integration. | — |
| Device or other identifiers | No | No | BluePadel does not read advertising IDs, IMEI, MAC address, or other persistent device identifiers. | — |
Permissions BluePadel requests
These are declared in the watch app's AndroidManifest.xml and granted at install or runtime.
WAKE_LOCK
Keeps the watch's CPU active during a match so the scoring engine can respond to your taps without the device going to sleep. No data leaves the device.
VIBRATE
Triggers a short haptic buzz when you tap a tap-zone or confirm an End-match action. No data transmitted.
BODY_SENSORS
Reads heart-rate from the watch's optical sensor via Android Health Services. Used solely to display a live heart-rate readout during a match. Heart-rate samples are kept in memory during the active match and only persisted to the phone if you save the match with health data attached.
ACTIVITY_RECOGNITION
Reads accelerometer events via Android Health Services to detect padel swings during a match. Used to count swings per match for the post-match stats screen. Same retention as heart rate.
FOREGROUND_SERVICE / FOREGROUND_SERVICE_HEALTH
Keeps the scoring engine and health monitor running as a foreground service while a match is in progress, so swiping away from the app doesn't interrupt scoring.
POST_NOTIFICATIONS
Shows the foreground-service notification that Android requires while the match service is active. Notifications never contain personal information.
Where your data goes
Match results sync from your watch to your paired phone via Google's Wearable Data Layer API, a direct peer-to-peer transport between paired Android devices. Data is encrypted in transit by the Data Layer. Nothing is uploaded to BluePadel servers — we don't operate any. Nothing is uploaded to Google's servers in plain-text form.
Data security
Match data is stored in BluePadel Companion's private application storage on your phone. This storage is sandboxed from other apps by Android and encrypted at rest on every supported device (API 26+). The watch and phone authenticate each other using the standard Wearable Data Layer pairing established when you set up your watch with your phone.
Data deletion
You can delete individual matches in BluePadel Companion. Uninstalling either app removes all of its locally stored data. There is no server-side data to delete because we don't operate any servers. To request written confirmation that we hold none of your data centrally (we don't), email hello@bluepadel.co.za.
Children
BluePadel is not directed at children under 18 and is not designed for the Designed for Families programme on Google Play.
Independent security review
We haven't undergone an independent security audit. The privacy-protective design (no servers, no third-party SDKs, no analytics) is verifiable by inspecting the public dependency list in our build configuration.
Contact
Questions about anything on this page: hello@bluepadel.co.za.