Privacy Policy for BLE Finder: Bluetooth Scanner
Last updated: October 6, 2026
Developer: diamond-dave
Contact: davedvlee@gmail.com
This policy explains how BLE Finder: Bluetooth Scanner handles information when you use the Android app. The app helps you find nearby Bluetooth Low Energy (BLE) devices using their advertised signals. The app also uses Google AdMob, Google Analytics for Firebase, and Firebase Crashlytics. These services collect information as described below.
1. Bluetooth information and information stored on your device
When you start a scan, the app reads information broadcast by nearby BLE devices, including Bluetooth addresses, advertised device names, signal strength (RSSI), available transmit-power information, whether a device is connectable, the time a signal was received, and an advertised beacon web address when available. The app uses this information on your device to display nearby devices and changes in signal strength.
Scanned Bluetooth information is processed in the app and is not uploaded by the app to a developer-operated server. The app does not include scanned Bluetooth addresses, advertised device names, signal readings, beacon web addresses, or custom names in its analytics event parameters or custom crash-reporting logs.
If you give a device a custom name, the app stores that name, its associated Bluetooth address, and a last-updated time locally on your device. The app also stores local preferences, whether you dismissed the guide, and a count of devices you marked as found to decide when to request an app review.
You can delete individual saved names or use Settings > Delete all saved names. Turning off Device Names keeps existing names on your device. Clear List clears the scanned-device list and does not delete saved names. Clearing the app's storage in Android settings or uninstalling the app removes its locally stored app data.
2. Permissions and location
On Android 12 and later, Bluetooth scanning and device-name access require Nearby devices permissions. On Android 11 and earlier, Android requires location permission for BLE scanning. You can deny or revoke these permissions in Android settings, but scanning will then be unavailable.
The app does not request GPS coordinates or upload precise GPS location. The Bluetooth signal display indicates relative signal strength rather than your geographic position. Separately, Google's advertising and analytics services can derive approximate location from network information such as an IP address, as explained below.
3. Advertising: Google AdMob
The app displays banner advertising through Google AdMob's Google Mobile Ads SDK. Google describes the following automatically collected and shared information:
- IP address, which can be used to estimate general location.
- Product interactions, such as app use and interactions with advertisements.
- Diagnostics about the app and advertising SDK's performance.
- Device or account identifiers, including the Android advertising ID, app set ID, and other applicable identifiers.
Google uses this information for advertising, analytics, and fraud prevention. Advertising ID availability depends on your device and Android settings. The app does not provide an in-app switch to disable advertising data collection or an in-app advertising consent form.
Google's official explanation:
https://developers.google.com/admob/android/privacy/play-data-disclosure
4. Usage analytics: Google Analytics for Firebase
The app enables Google Analytics for Firebase to understand usage and improve the app. Information can include an app-instance identifier, advertising ID where available, approximate location derived from IP information, and app lifecycle activity such as sessions and screen views.
The app also records feature-use events, including starting or stopping a scan, scan status, selecting a device, marking a device as found, using the saved-name controls, and requesting an app review. Event details can include status, whether a setting is enabled, how a feature was opened, and review-flow timing or results. These events do not contain the scanned device's address, advertised name, or your custom name.
The current app does not provide an in-app option to disable Analytics collection.
Google's official explanation:
https://support.google.com/analytics/answer/11582702?hl=en
5. Crash reporting: Firebase Crashlytics
The app enables Firebase Crashlytics to identify errors and improve reliability. Crashlytics processes crash and error reports, stack traces, relevant app state, device and operating-system information, and installation or session identifiers. The app attaches activity logs such as app startup, screen names, and scan states, and reports certain non-fatal errors. Crash reports may also contain recent analytics activity.
The current app does not provide an in-app option to disable Crashlytics collection.
Google's official explanations:
https://firebase.google.com/docs/android/play-data-disclosure
https://firebase.google.com/support/privacy
6. Sharing, security, and retention
Google receives and processes the advertising, analytics, and crash-reporting information described above to provide those services. Google's processing may take place in countries other than your country of residence. Its handling of this information is also subject to its applicable privacy policies and service terms.
Google states that Mobile Ads and Analytics SDK data is encrypted in transit using TLS and that Firebase services encrypt data in transit using HTTPS. Locally saved names are stored within the app's storage on your device.
The scanned-device list is held in app memory. Saved names and local preferences remain on your device until you delete them or remove the app's local storage. Retention of information processed by Google depends on the service, its published policies, and the applicable account settings. Deleting the app's local data or uninstalling it does not itself delete information already transmitted to Google.
Google Privacy Policy:
https://policies.google.com/privacy
7. Your choices and privacy requests
You can manage Bluetooth and location permissions in Android's app settings. Where supported, you can reset or delete your advertising ID and manage advertising privacy controls through Android settings. These controls do not disable all analytics or crash reporting. Denying Bluetooth permission also does not disable the app's advertising, analytics, or crash-reporting services.
The app does not require an account and does not offer account registration. Depending on your jurisdiction, you may have rights to request access, correction, deletion, restriction, or other choices concerning personal information. Contact davedvlee@gmail.com with a privacy request. We will review requests according to applicable law and the data and controls available to us. Because the app does not associate SDK records with a registered account, we may be unable to identify a particular record from an email address alone. We cannot promise deletion of every record held independently by Google; its privacy controls and policies also apply.
If you contact us by email, we receive the address and information you choose to include and use them to respond to your inquiry or request. Please avoid sending unnecessary sensitive information.
8. External links
Some Bluetooth beacons advertise web addresses. The app opens such a link in an external browser or another app only when you choose to open it. It also lets you open its Google Play page to leave a review. Those external services may collect information under their own privacy policies. An advertised beacon link can use HTTP or HTTPS; its security and content are controlled by the destination.
9. Children
The app is not designed to ask children to submit personal information. Advertising, analytics, and crash-reporting services can nevertheless process device and usage information as described in this policy. If you are a parent or guardian and have a concern about a child's information in connection with the app, please contact davedvlee@gmail.com.
10. Changes and contact
We may update this policy when the app's data practices change. The date at the top identifies the latest revision. For questions about this policy or the app's handling of information, contact diamond-dave at davedvlee@gmail.com.