Privacy

Privacy

ArxSilex MapTools is designed for local use: projects, tracks, markers, offline maps, POI and elevation data generally remain on the device until you export, share or use an online feature.

Update

Privacy update from May 27, 2026

This section adds the current privacy details for ArxSilex MapTools, Android package de.arxsilex.maptools. It is part of this privacy policy.

Controller and contact

Controller: ArxSilex, Peter Stich, Jägerweg 6, 35708 Haiger, Germany. App support and privacy requests: android@arxsilex.de. General website requests: info@arxsilex.de.

Local first

Projects, tracks, markers, offline maps, POI, elevation data, backups and received radio data generally remain on the device. Android Auto Backup is disabled for the app. Data leaves the device only when you deliberately use online maps, export, sharing, QR/live group functions (BLE), Remote ID export or another external service.

Remote ID and BLE

Remote ID and airspace data may contain personal data. Received drones are displayed live. A permanent history is not enabled by default. Lost live entries are removed after a short time, currently typically after about 90 seconds. Optional Remote ID history is local, limited to 5,000 entries and kept only for the session or up to 24 hours depending on the setting. It can be deleted in the app. BLE group functions send only the data needed for the active group, such as location, accuracy, group identifier and session token, to nearby devices in the same group.

Data categories and recipients

The app may process location data, sensor and motion data, map and project data, imported files, camera/barcode data, Bluetooth/Nearby/Wi-Fi data, Remote ID and airspace data, online map/network data, backups, exports, support emails and website logs. ArxSilex MapTools does not operate its own app servers for project, location, Remote ID or tracking data. Data may reach Google, OpenStreetMap, selected map providers, target apps, nearby group devices, hosting or email providers only when the selected function requires it or you deliberately share it.

Security and retention

Ongoing location, group, Remote ID and data tasks run as Android foreground services with notification. The app uses a network security configuration with cleartext traffic disabled. Manual backups can be password-protected with AES-256-GCM and PBKDF2WithHmacSHA256. Received BLE MAC addresses from Remote ID are not documented in plain text but processed as shortened SHA-256 hashes. There is no advertising SDK disclosure, no own profiling and no sale of personal or sensitive data.

Legal context and rights

Depending on the feature, processing is based in particular on Art. 6(1)(a), (b), (f) or, where required, (c) GDPR. Under EU Regulation 2019/945, Direct Remote ID may include position, height, course, speed, timestamp, operator or serial identifiers and in some cases pilot or take-off position. Location data and identifiers can be personal data. You may request access, correction, deletion, restriction, portability, objection or withdrawal of consent by contacting android@arxsilex.de.

Deletion and third-party rights

You can request deletion of data held by us. Because ArxSilex MapTools generally stores app data locally on your device and does not operate its own app servers for project, location, Remote ID or tracking data, we cannot delete those local records server-side. Data processed by Google, OpenStreetMap, map providers, target apps, cloud storage, messengers or email providers is controlled by those providers; access, deletion or objection requests must be addressed to them under their privacy processes.

Summary

Local Use First

The current app does not run its own user account system, tracking service, advertising or analytics platform.

Local App Data

Project files, GPS tracks, routes, markers, circles, areas, search grids, offline maps, POI, raster overlays, terrain and app backups are stored locally.

User Action

Export, sharing, QR codes, file imports, backup/restore and Live group features (BLE) are deliberate user actions and may pass data to other apps, devices or people.

Online Services

When using online maps or Google maps, IP address, device and map viewport data may be transmitted to the respective provider.

Data Types

Which Data Is Processed

The exact scope depends on used features and granted permissions.

Category	Examples	Purpose	Storage
Location and sensor data	GPS, accuracy, movement, compass, optionally barometer	Navigation, bearings, tracking, elevation and AR features	Device; inside the project when tracking
Map and project data	Markers, routes, tracks, areas, search grids, profiles	Saving and reusing your map work	Device; export only by user action
Imported files	.asmaps, GPX, KML/KMZ, GeoJSON/JSON, CSV/TSV/TXT, Mapsforge, MBTiles, GeoPackage, GeoTIFF, HGT, ASC, DTED, LOC	Offline maps, POI, terrain, overlays and geodata	Device
Backups	.asmaps.backup files with selected app content, optionally password-protected	Backup and restore by deliberate user action	Device or user-selected storage location
Radio data	Live groups (BLE) and received Remote ID broadcasts	Nearby live display and documentation of received signals	Device or participating devices

Remote ID

Remote ID and airspace data

Received Remote ID or airspace data may contain personal data. The app processes this data locally and does not automatically transmit it to cloud or app servers.

Local use

live display of received drones
short local history for map display and diagnostics when removable
export only by deliberate user action

Limits

no automatic cloud or server transfer
no permanent history enabled by default
operator, pilot or take-off positions should be handled with particular care

Legal context

Under EU Regulation 2019/945, Direct Remote ID can include position, height, course, speed, timestamp, operator/serial identifiers and, in some cases, pilot or take-off position. Under GDPR Article 4, location data and identifiers can be personal data when a person is directly or indirectly identifiable.

Sources: EU 2019/945, GDPR Art. 4, EASA privacy code, Dronetag Drone Scanner privacy policy.

User control

Offline mode and provider blocks

Global offline mode blocks every internet request initiated by MapTools, including custom WMS, WMTS, OGC, XYZ and WFS services and external web links. Only when global offline mode is off can Google and the built-in OpenStreetMap map service be blocked separately while custom services remain online. Radio silence additionally stops Wi-Fi/BLE activity initiated by MapTools. These switches do not change Android radio settings and cannot control system services, A-GNSS or other apps. Previously cached map content may remain visible.

Object alarms and location

Local processing for an explicitly enabled feature

MapTools uses location to evaluate the spatial alarm condition selected by the user. There is no MapTools-operated server for alarm locations.

Purpose limitation

Background location is used only for enabled marker or circle system geofences.

On-device data

Alarm definitions live in the project. Background opt-in, audio selection and snooze state remain local device settings.

Android system services

Optional background monitoring uses location and geofence functions provided by the Android device and its available system components.

No automatic activation

Importing a project or restoring a backup does not automatically start an alarm or restore a local audio URI.

Treat external online services separately

If an online map or feature service is also used, that operator's own processing and privacy terms apply.

Allow background location for this 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.

Geodata search

Local search and deliberately submitted service queries

Searches in imported POI data stay on the device. OGC API Features and WFS services are contacted only after you deliberately submit the online search. The selected provider then receives the entered search term and, depending on your selection, the map viewport, a reference point or a radius. The provider may receive the IP address, time and technical request data under its own privacy information. MapTools does not keep a search history by default and does not copy remote results into the local POI search database. Offline mode and radio silence block these service queries.

Add attachment

Include object attachments

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.

Photos

Position and direction

The field of view is an estimate based on available camera and focal-length data.

PDFs

Files added here belong directly to the project, not to an individual object.

Audio

Microphone access is required only while recording an audio note.

Share attachment

Attachments can contain private images, documents, voices and location metadata. Include them only deliberately.

Images, PDFs and audio notes are embedded in the .asmaps project file only when that option is selected, and are assigned back to the matching objects or project during import.

Project gallery

Preview images use a bounded private cache that can be rebuilt and cleared through app or Android storage management.

Only entered fields override the original data. EXIF and MapTools values remain unchanged.