Privacy Policy
Effective date: 21 May 2026
Evalan BV built the ARMOR app as part of the ARMOR SERVICE. This SERVICE is provided by Evalan BV commercially and is intended for use as is.
This page is used to inform users regarding our policies with the collection, use, and disclosure of information when using our Service.
By using the ARMOR application, you agree to the practices described in this Privacy Policy.
The terms used in this Privacy Policy have the same meanings as in our Terms and Conditions unless otherwise defined in this Privacy Policy.
Information Collection and Use
The ARMOR application does not transmit personal data to Evalan BV or third parties. Certain user-entered information and monitoring data may optionally be stored locally on the user’s device for operational and reporting purposes.
The application may locally store:
- User-entered names
- Heart rate data
- Calculated body core temperature values
- Physical Strain Index (PSI)
- Session-related monitoring information
- Sensor device identifiers
This data is stored only on the user’s device and is not automatically shared with Evalan BV or third parties.
Users may choose to export or share files manually at their own discretion using functionality provided by the application.
Third-Party Services
The application may use third-party services that may collect information used to identify users. Link to privacy policy of third party service providers used by the app.
Special permissions
The ARMOR application uses the following device features and permissions to provide core functionality and ensure proper operation of wearable monitoring devices.
1. Camera
The camera functionality is used solely to scan QR codes on ARMOR sensor nodes. No images are stored locally or shared with Evalan BV or any other party.
2. Bluetooth and Low-Energy Wireless Connection
Bluetooth and Bluetooth Low Energy (BLE) communication are essential for connecting with ARMOR sensor nodes and wearable monitoring devices. The application uses Bluetooth functionality exclusively for communication with nearby ARMOR sensor devices and data synchronization required for operation of the service.
3. ACCESS-FINE-LOCATION
The ARMOR application requires access to precise location permission because Android operating system requirements may mandate location access for Bluetooth Low Energy (BLE) scanning and communication with nearby ARMOR sensor nodes.
The application does not track, collect, store, or share the user’s geographical location.
Location permission is used exclusively to enable Bluetooth device discovery and communication functionality required for ARMOR wearable sensor operation.
Users can manage or revoke this permission at any time through device settings.
4. FOREGROUND-SERVICE-LOCATION
The application uses foreground location service type permissions to maintain active communication with ARMOR sensor nodes while the application is running and monitoring sessions are in progress.
5. FOREGROUND-SERVICE-DATA-SYNC
This permission allows the ARMOR application to synchronize sensor-related monitoring data while active sessions are running. Only operational sensor monitoring data is synchronized for application functionality. No personal location information is transmitted or shared during this process.
6. POST_NOTIFICATIONS
This permission is used to display service and application notifications needed for ongoing monitoring status and app events. Users can manage or disable notifications from device settings.
Data Retention and Deletion
The ARMOR application may optionally store user-entered names, sensor measurements, heart rate data, calculated body core temperature values, Physical Strain Index (PSI), and session-related monitoring information locally on the user’s device for reporting and monitoring purposes.
This data is stored only on the user’s device and is not transmitted to Evalan BV or third parties unless explicitly shared by the user.
Data is retained only as long as required by the user for monitoring, reporting, and operational purposes, or until the user deletes it.
Users can delete data in the following ways:
• Delete locally stored data from within the application using in-app delete/clear functionality where available.
• Uninstall the application to remove app-local data from the app sandbox.
• Delete manually exported files from shared device storage (for example Documents or Downloads) using the device file manager.
If users request assistance regarding deletion of data or privacy-related concerns, they may contact Evalan BV at info@evalan.com.
Security
Since certain monitoring and session data may optionally be stored locally on the device and can be shared by users at their own discretion, Evalan BV cannot be held responsible for any unauthorized use, transfer, or sharing of data outside the intended use and documented functionality of the application.
We take reasonable technical and organizational measures to help protect information processed by the application.
Changes to This Privacy Policy
We may update our Privacy Policy from time to time. Thus, you are advised to review this page periodically for any changes. We will notify you of any changes by posting the new Privacy Policy on this page. These changes are effective immediately after they are posted on this page.
Contact Us
If you have any questions or suggestions about our Privacy Policy, do not hesitate to contact us at
Evalan BV
Danzigerbocht 31,
1013 AM Amsterdam
info@evalan.com