Permissions
ArxSilex MapTools requests Android permissions only for specific app features. Many tools remain usable when individual permissions are not granted.
Overview
Permissions are requested in the flow where they are needed. They are not used for advertising, Firebase Analytics, Crashlytics, AdMob or an app-owned tracking platform.
ACCESS_BACKGROUND_LOCATION is requested only when you explicitly enable optional background monitoring for a marker or circle alarm. Tracking, BLE groups and Remote ID continue to use visible foreground services.
You can deny or revoke permissions in Android settings. The affected feature may then be unavailable or limited.
The app does not declare MANAGE_EXTERNAL_STORAGE, READ_EXTERNAL_STORAGE or WRITE_EXTERNAL_STORAGE. Imports and exports use files and folders selected by you through Android.
Manifest
This list follows the permissions currently declared in the Android manifest.
| Permission / area | Use in ArxSilex MapTools | Data context |
|---|---|---|
ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION | Map position, target navigation, bearings, tracking, track recording, elevation context, viewrange, AR/LiveView, Remote ID and Live group features (BLE). | Approximate or precise device location, accuracy and timestamps while the selected feature is active. |
FOREGROUND_SERVICE, FOREGROUND_SERVICE_LOCATION | Visible ongoing location features such as GPS tracking, navigation context, group mode or Remote ID monitoring. | Location processing while the user-started foreground service is active, including when the app is minimized or the screen is off. |
FOREGROUND_SERVICE_CONNECTED_DEVICE | BLE group mode and Remote ID / nearby-device functions that work with close devices or public broadcasts. | Nearby-device state, BLE packets, group session data and received Remote ID broadcasts. |
FOREGROUND_SERVICE_DATA_SYNC | Longer local data tasks such as POI or file indexing when Android expects a visible service. | Local files, POI and import data; no app-owned server synchronization. |
POST_NOTIFICATIONS | Visible status notifications for tracking, BLE group mode, Remote ID monitoring and longer local tasks. | Notification text about the active app feature. |
CAMERA | QR/barcode scan, QR import and AR/LiveView. Take photo: Camera access is required only while taking a photo. | Attachments are managed locally in private app storage. Camera and microphone operate only during a capture explicitly started by the user; export and sharing require a deliberate selection. |
RECORD_AUDIO | Record audio note. Microphone access is required only while recording an audio note. | Attachments are managed locally in private app storage. Camera and microphone operate only during a capture explicitly started by the user; export and sharing require a deliberate selection. |
BLUETOOTH, BLUETOOTH_ADMIN up to Android 11 | Compatibility for Bluetooth features on older Android versions. | Bluetooth state and BLE nearby data. |
BLUETOOTH_SCAN, BLUETOOTH_ADVERTISE, BLUETOOTH_CONNECT | BLE group mode, nearby participants, sending own group data and receiving Remote ID over BLE. | BLE packets, group identifiers, session tokens, active group location data and public Remote ID broadcasts. |
NEARBY_WIFI_DEVICES, ACCESS_WIFI_STATE, CHANGE_WIFI_STATE | Nearby Wi-Fi and Wi-Fi-aware features, network state and Remote ID variants when supported by device and Android. | Wi-Fi / nearby status and technical nearby data; not used for advertising profiling. |
INTERNET, ACCESS_NETWORK_STATE | Online maps, Google Maps, OpenStreetMap tiles, provider requests, network status and external links. | Provider-side technical request data such as IP address, map area, user agent and connection metadata. |
Android file picker / share targets | Import and export of projects, maps, POI, elevation data, overlays, backups and reports. | Only files or destinations selected by you or shared to the app. |
Foreground services
If you start tracking, BLE group mode, Remote ID monitoring or a longer local data task, Android may keep the task running as a foreground service and show a persistent notification.
Ongoing processing starts from an app action and can be stopped in the app or from the Android notification.
For tracking, group mode or Remote ID monitoring, location may be processed while the app is not visible, but only during the visible foreground service.
Drone reception processes publicly broadcast Remote ID data locally. The app does not connect to or control drones.
Permission-gated data is not used to provide ads and is not shared with advertising SDKs.
Remote ID and nearby devices
Remote ID and Live group features (BLE) combine Android permission groups because nearby radio scans can reveal location-related information and Android protects them separately.
Bluetooth Low Energy reception covers legacy and extended advertisements, service data and manufacturer data. Wi-Fi reception covers Wi-Fi Aware/NAN and Wi-Fi Beacon; active Wi-Fi Beacon compatibility scans are optional.
OpenDroneID / ASTM F3411 and ASD-STAN / EU Direct Remote ID payloads are parsed. Supported message groups include Basic ID, Location/Vector, System, Operator ID, Self ID, Auth and Message Pack.
The app can show drone ID, status, timestamp, drone position, altitude/height, speed, heading, receiver source, signal strength and, if broadcast and enabled by the user, operator or take-off position.
Remote ID history can be exported manually as KML, GeoJSON or CSV. Operator or pilot positions are included only when you choose that option.
More information
Details about data purposes, recipients, storage periods and deletion options are described on the privacy, data safety and data deletion pages.
Object alarms
MapTools requests permissions only inside the relevant workflow. Foreground and background monitoring remain separate.
| Area | Needed for | Without permission or service |
|---|---|---|
| Location while using the app | Current position and precise checks for markers, circles, areas and routes while MapTools is visible. | No position-based evaluation and no object alarm in the visible app. |
| Background location | Optional Android system geofence for explicitly selected markers and circles while MapTools is in the background or not open. | Background monitoring remains off; the visible-app evaluator still works. |
| Notifications | Visible alarm with snooze, quieter signalling and stop actions. | A background event cannot be presented reliably as a visible alarm notification. |
| Google Play services and location services | Local, battery-efficient Android geofence for markers and circles. VTM and Google Maps do not run it. | No background system geofence; visible-app monitoring remains available. |
An enabled system geofence needs neither an online map nor a connection to a MapTools server. The device must still be able to determine a position. Depending on Android settings, GNSS, Wi-Fi and mobile signals may be combined.
Object alarms
A normal object alarm while the app is visible does not require permanent background access. The additional system-geofence option is explained separately.
Required to compare the visible-app position with a marker, circle, area or route.
Optional and used only for explicitly enabled system geofences for markers and circles.
Required so a triggered background alarm can show snooze, quieter and stop actions.
A custom tone is selected through Android's file picker. MapTools receives read access only to the explicitly selected document.
Revoking permission, force-stopping the app or restricting background work may suspend or delay the alarm.
ArxSilex MapTools collects and uses your precise location for this optional object alarm, even when the app is closed or not in use. This lets Android detect whether you cross the selected marker or circle boundary and trigger the alarm. Android and Google Play services perform geofence monitoring on this device. MapTools does not upload the location to its own server, use it for ads or analytics, or create an alarm location history.
Add attachment
Attachments are managed locally in private app storage. Camera and microphone operate only during a capture explicitly started by the user; export and sharing require a deliberate selection.
Camera access is required only while taking a photo.
Microphone access is required only while recording an audio note.
Maximum recording length: 10 minutes
Choose PDF
Android filters by reported file type. The file extension and content are checked again before import.
Attachments can contain private images, documents, voices and location metadata. Include them only deliberately.
Attachments are managed locally in private app storage. Camera and microphone operate only during a capture explicitly started by the user; export and sharing require a deliberate selection.
