No hidden background location
El manifiesto actual no declara ACCESS_BACKGROUND_LOCATION. La ubicación solo puede continuar durante un servicio en primer plano visible iniciado por el usuario.
Permisos
Permisos
Por qué ArxSilex MapTools solicita permisos de Android para ubicación, cámara, Bluetooth, Wi-Fi cercano, notificaciones y servicios en primer plano.
Overview
Permissions are feature-based
Los permisos se solicitan solo para funciones concretas. No se usan para publicidad, Analytics, Crashlytics, AdMob ni seguimiento propio.
Control
Puede denegar o revocar permisos en Android.
No broad storage permission
La app no declara permisos amplios de almacenamiento; usa archivos elegidos por usted. MANAGE_EXTERNAL_STORAGE, READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE.
Manifest
Declared Android permissions
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 BLE group features. | 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. | Camera frames are processed for the selected function, not for ads or analytics. |
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. |
Servicios en primer plano
Las funciones en curso permanecen visibles
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.
User started
Ongoing processing starts from an app action and can be stopped in the app or from the Android notification.
Location while not visible
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.
Remote ID
Drone reception processes publicly broadcast Remote ID data locally. The app does not connect to or control drones.
No ads
Permission-gated data is not used to provide ads and is not shared with advertising SDKs.
Remote ID y dispositivos cercanos
Recepción Remote ID y formatos
Remote ID y las funciones BLE combinan grupos de permisos de Android porque los escaneos de radio cercanos pueden revelar información relacionada con la ubicación.
Vías de recepción
Bluetooth Low Energy se evalúa mediante anuncios legacy y extendidos, datos de servicio y datos de fabricante. Wi-Fi cubre Wi-Fi Aware/NAN y Wi-Fi Beacon; los escaneos activos de compatibilidad Wi-Fi Beacon son opcionales.
Protocolos y mensajes
Se procesan cargas OpenDroneID / ASTM F3411 y ASD-STAN / EU Direct Remote ID. Se admiten Basic ID, Location/Vector, System, Operator ID, Self ID, Auth y Message Pack.
Datos mostrados
La app puede mostrar ID de dron, estado, marca temporal, posición del dron, altitud/altura, velocidad, rumbo, fuente de recepción, intensidad de señal y, si se emite y el usuario lo muestra, posición de operador o despegue.
Formatos de exportación
El historial Remote ID puede exportarse manualmente como KML, GeoJSON o CSV. Las posiciones de operador o piloto solo se incluyen si eliges esa opción.
Más información
Privacy, safety and deletion
Details about data purposes, recipients, storage periods and deletion options are described on the privacy, data safety and data deletion pages.