No hidden background location
Le manifeste actuel ne déclare pas ACCESS_BACKGROUND_LOCATION. La localisation ne peut continuer que pendant un service de premier plan visible lancé par l’utilisateur.
Autorisations
Autorisations
Pourquoi ArxSilex MapTools demande des autorisations Android pour la localisation, la caméra, Bluetooth, le Wi-Fi à proximité, les notifications et les services de premier plan.
Overview
Permissions are feature-based
Les autorisations sont demandées uniquement pour des fonctions précises. Elles ne servent pas à la publicité, Analytics, Crashlytics, AdMob ni au suivi propre.
Control
Vous pouvez refuser ou révoquer les autorisations dans Android.
No broad storage permission
L’app ne déclare pas d’autorisation de stockage large; elle utilise les fichiers que vous choisissez. 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 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. | 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. |
Services de premier plan
Les fonctions en cours restent 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 et appareils proches
Réception Remote ID et formats
Remote ID et les fonctions BLE combinent plusieurs groupes d'autorisations Android, car les scans radio à proximité peuvent révéler des informations liées à la localisation.
Canaux de réception
Bluetooth Low Energy est analysé via annonces legacy et étendues, données de service et données fabricant. Le Wi-Fi couvre Wi-Fi Aware/NAN et Wi-Fi Beacon; les scans actifs de compatibilité Wi-Fi Beacon sont optionnels.
Protocoles et messages
Les charges utiles OpenDroneID / ASTM F3411 et ASD-STAN / EU Direct Remote ID sont analysées. Les groupes pris en charge incluent Basic ID, Location/Vector, System, Operator ID, Self ID, Auth et Message Pack.
Données affichées
L'app peut afficher l'ID du drone, l'état, l'horodatage, la position du drone, l'altitude/hauteur, la vitesse, le cap, la source de réception, la puissance du signal et, si diffusée et affichée par l'utilisateur, la position opérateur ou décollage.
Formats d'export
L'historique Remote ID peut être exporté manuellement en KML, GeoJSON ou CSV. Les positions opérateur ou pilote ne sont incluses que si vous choisissez cette option.
Plus d’informations
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.
Politique de confidentialité Sécurité des données Supprimer les données