HAVS Protect can safely be used in secure facilities because no location data is collected, used, or stored. The sensor itself has no GPS or location tracking capabilities, and the HAVS Protect app does not process location data, even if permissions are granted.
HAVS Protect is developed and owned by a fully Swedish company. No foreign entities have ownership or interests in the company, its hardware, or software.
Considerations for Android Devices in Secure Facilities
On Android devices, scanning for Bluetooth Low Energy (BLE) devices can expose nearby devices, which in theory could be used to estimate a device’s location if combined with known BLE beacons.
Because of this potential privacy risk, Android requires location permissions for BLE scanning, even if the app itself does not actively use or store location data.
Summary of Android BLE Permission Changes
Android 6.0 and Later (API 23+)
- Location permission became mandatory for BLE scanning, to prevent apps from indirectly inferring location without user consent.
Android 10 (API 29)
- Apps performing continuous BLE scanning in the background were required to request “Allow all the time” location access.
Android 12 and Later (API 31+)
- BLE permissions were separated from location permissions.
- Apps now need:
- BLUETOOTH_SCAN – to detect nearby BLE devices.
- BLUETOOTH_CONNECT – to connect to BLE devices.
- Location permission is only required if the app explicitly tries to determine geographic location using BLE beacons.
⚠️ Important for Secure Facilities:
If your phone runs Android 12 or higher, location sharing is NOT required to connect the HAVS Protect sensor. Only Bluetooth permissions are needed.
This ensures compliance with secure facility requirements, while still enabling the sensor to work normally.
