Safenter Privacy Policy
Last updated on March 2026
1. Introduction (what Safenter is)
Safenter is a mobile application intended for secure control of physical access devices (for example, doors, gates, or barriers) using a smartphone.
The application interacts with Safenter physical devices that are connected to electrically controlled locks or other access control mechanisms. By using Bluetooth Low Energy (BLE) communication and proximity detection, the application enables the user’s phone to detect a nearby Safenter device and initiate secure communication.
When the user approaches, the Safenter device, after receiving a validated signal from the application, may automatically activate an electric lock or another controlled mechanism.
The Safenter system also allows access owners to manage and grant access rights to other users. Users may use the access granted to them under the defined conditions.
The application works in the background so that it can continuously detect nearby Safenter devices and automatically initiate interaction, allowing controlled locks to be unlocked without additional user actions.
2. What data the application uses
The application uses the following data:
- Bluetooth data (device identifiers, signal strength (RSSI), connection session data, and protocol data transmitted by devices)
- Location data (precise device location data, including coordinates and accuracy)
- Movement and sensor data (accelerometer, gyroscope, pressure sensor, as well as step and activity recognition data)
- Device information (device model and operating system version)
- Access identifiers (unique device identifiers, access keys, QR codes, and data transmitted through links)
- Application configuration and settings data (stored on the device and, optionally, in the user’s Google account AppData storage)
3. What the data is used for
The data used is intended solely to ensure the functionality and security of the application:
- Bluetooth data is used to detect Safenter devices and establish a secure connection with them
- Location and movement data are used to determine whether the user is actually at a specific entrance and is naturally approaching it. This allows safe automatic unlocking only when the user is truly approaching the access point, while also evaluating possible security risk indicators such as location spoofing or communication relaying (relay attacks), where an attempt is made to simulate presence at the door from another location
- Device information is used to optimize the application’s operation and ensure compatibility
- Access identifiers are used for access verification and to ensure secure communication with devices.
- Application configuration and settings data are used to store the user’s settings on the device and, if the user chooses, to synchronize them across the user’s devices using Google account AppData storage
4. Where data processing takes place
The Bluetooth, location, movement, and sensor data used by Safenter are processed on the user’s device in real time in order to ensure the application’s functionality and security.
Application configuration, access settings, and access point information are stored on the device in encrypted form using local security mechanisms.
If the user chooses to enable backup or synchronization functionality, part of the application data may be stored in the user’s Google account Google Drive AppData storage. This data is used only for creating backups and restoring data across the user’s devices.
Safenter does not use the user’s Google account profile or email data.
5. Whether data is transferred to third parties
Safenter does not transfer user data to third parties for advertising, profiling, or marketing purposes.
Data may be transferred only to the extent necessary for the operation of the application or for functionality chosen by the user:
- To Safenter devices via Bluetooth Low Energy (BLE) communication when secure communication with an access device is performed. During this communication, access identifiers (key identifiers), without transferring the keys themselves, are transmitted and used for access verification. Access devices may use these identifiers for event logging (for example, recording the time of entry) according to the rules defined by the owner.
- To Google Drive AppData storage, only if the user independently enables backup or synchronization functionality. The application uses only the “drive.appdata” permission and does not collect the user’s Google profile or email information.
Except for the cases indicated above, the data used by Safenter is not transferred to third parties and remains on the user’s device.
6. Explanation of permissions
Safenter uses only those Android permissions that are necessary for the operation of the application, secure communication with access devices, and the automatic unlocking function.
Permissions used:
- Bluetooth permissions (BLUETOOTH_SCAN, BLUETOOTH_CONNECT) are used to detect nearby Safenter devices and establish a secure connection with them.
- Location permissions (ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION, ACCESS_BACKGROUND_LOCATION) are used to determine whether the user is actually near a specific entrance and to ensure secure automatic unlocking. Background location permission is required so that this function also works when the application is not actively open.
- Physical activity permission (ACTIVITY_RECOGNITION) is used to determine the movement mode and to ensure the security of automatic unlocking.
- Notification permission (POST_NOTIFICATIONS) is used to inform about application operation and access events.
- Internet permission (INTERNET) is used only for functions related to data synchronization and backups (for example, Google Drive AppData).
- Foreground service permissions (FOREGROUND_SERVICE and related permissions) are used so that the application can run in the background and continue device detection and proximity evaluation.
- The RECEIVE_BOOT_COMPLETED permission is used to restore application operation after the device restarts.
7. Data storage
Data used by Safenter is primarily stored on the user’s device.
Application settings, access point information, and related configuration data are stored locally, while more sensitive data is stored in encrypted form using Android platform security mechanisms, including Android KeyStore.
Locally stored data includes:
- access point information;
- application settings;
- automatic unlocking configuration;
- device-related identifiers.
If the user enables backup or synchronization functionality, part of this data is stored in the user’s Google Drive AppData storage. This function is optional and is used only for restoring data across the user’s devices.
Safenter stores data for as long as necessary for the operation of the application. Locally stored data is deleted when the application is removed, while Google Drive AppData data is stored until the user deletes the backups or revokes access.
8. Security
Safenter applies technical measures intended to protect user data and ensure secure access management.
Communication with access devices takes place over Bluetooth Low Energy (BLE), using secure communication and session management mechanisms.
Locally stored more sensitive data is protected by encryption, and Android platform security mechanisms, including Android KeyStore, are used to protect encryption keys.
Location, movement, and sensor data are used not only for functionality but also for security — in order to detect unnatural approach, location spoofing, and possible signs of communication relaying (relay attacks). In such cases, automatic unlocking may be restricted or not performed.
Safenter applies technical and software measures intended to provide maximum data protection and reduce the risk of unauthorized access or misuse.
9. User rights
The user may manage which Safenter functions are used and which permissions are granted to the application.
The user may:
- grant or revoke permissions through Android system settings
- enable or disable automatic unlocking functions
- enable or disable backup / synchronization functionality with Google Drive AppData
- remove locally stored data by deleting the application or by using the application’s functions
- revoke Google Drive access
Important: certain permissions (for example, Bluetooth, location, and movement) are necessary for the automatic unlocking function to operate and to ensure its security. If these permissions are not granted, the function may not work or may work only in a limited way.
10. Changes to the privacy policy
Safenter may update this privacy policy in order to reflect changes in the application’s functions or legal requirements.
Users may be informed about material changes within the application or by other usual means of communication.
The updated version of the privacy policy is always provided with the latest publication date.