Seguridad de datos

Esta página resume cómo ArxSilex MapTools gestiona los datos para la sección Seguridad de datos de Google Play. El formulario de Play Console debe mantenerse por separado en Google Play.

Última actualización: 2 de septiembre de 2026

Overview

Local-first, with user-controlled transfers

Most project, map and Remote ID data is processed on the device. Data leaves the device only through selected online services, radio features, exports, sharing or support contact.

No app-operated account

ArxSilex MapTools does not currently provide user accounts or an app-operated cloud sync service.

No advertising or analytics

No AdMob, advertising SDK, Firebase Analytics, Crashlytics or app-owned analytics platform is used in the checked release.

User action matters

Import, export, sharing, backups, Remote ID history and BLE group mode are started or configured by the user.

SDK responsibility

Google Mapas, Play services, ARCore and other SDKs must be reflected in the Play Console Seguridad de datos form where they transmit data.

Data categories

Google Play Data Safety matrix

The table below is a practical release checklist. Local-only processing is separated from off-device collection or sharing, because the Play Console form focuses on data that is collected or shared.

Google Play category	Collection / sharing path	Purpose	Control and retention
Location: approximate and precise	Processed locally for map position, navigation, tracking, AR/LiveView, viewrange, Remote ID and BLE group mode. Can be sent to Google Mapas, OpenStreetMap tile providers or other selected map providers when online maps are used. In BLE group mode, short live position updates are broadcast to active group participants.	App functionality: maps, navigation, situational awareness, group coordination and drone Remote ID display. Not used for advertising or analytics.	Runtime permission controlled by Android. Tracking and group/Remote ID foreground services are visible and user-started. Local tracks and projects remain until deleted by the user.
Personal info	No account, name or email is required in the app. Personal data can appear if users enter it in project names, POI notes, imported files or support emails.	User-generated content, support communication and project organization.	Local project data can be edited or deleted. Soporte emails are handled outside the app through the selected mail provider and the support/privacy contact process.
Files and documents	Imported maps, projects, Datos POIbases, tracks, terrain files, overlays, backups and reports are selected by the user. Exports and Android shares transfer files to the user-selected destination or app. Soporteed export formats include GPX, KML, KMZ, GeoJSON, CSV, PDF, JSON, ZIP, .asmaps and Remote ID KML/GeoJSON/CSV.	Import/export, backup/restore, reporting and interoperability with GIS/map tools.	Files remain locally or at the selected storage/share target until the user deletes them. No broad all-files permission is declared.
Photos, videos and camera frames	Camera frames are used locally for QR/barcode scanning, AR/LiveView and live bearing. Generated images such as QR codes or viewrange images can be shared only by user action. Hacer foto; Grabar nota de audio.	QR import/export, AR orientation and visual map tools.	Los adjuntos se gestionan localmente en el almacenamiento privado de la app. La cámara y el micrófono solo funcionan durante una captura iniciada expresamente; exportar y compartir requieren una selección consciente.
Device or other IDs	No Advertising ID, IMEI or phone identifier is requested. Remote ID broadcasts may contain drone serial/operator identifiers. BLE/Wi-Fi MAC/BSSID values used for reception diagnostics are shortened with SHA-256 hashing. Google Mapas/Play services may process app/device identifiers according to their SDK practices.	Nearby reception, duplicate detection, diagnostics, map services and Remote ID display.	Remote ID history is off by default. Operator details are hidden/anonymized by default and included in exports only if the user enables that option.
App activity and diagnostics	No app-owned analytics or crash-reporting upload is used. Local settings, cache status, map state, Remote ID counters and diagnostics may be processed on device; they leave the device only if the user exports or sends them.	Operate features, troubleshoot imports/maps/Remote ID and support user-requested diagnostics.	Settings and cache can be reset or cleared in the app/Android settings. Soporte messages are user-initiated.
Nearby devices / BLE / Wi-Fi	BLE group mode exchanges short encrypted packets with active group members. Remote ID reception reads public BLE, Wi-Fi Aware/NAN and Wi-Fi Beacon broadcasts without connecting to or controlling drones.	Group coordination and drone Remote ID situational awareness.	Group mode and Remote ID are optional. Remote ID live states expire automatically; optional history is session-only or 24 hours and can be exported manually as KML, GeoJSON or CSV.
Online map and network request data	When online maps or external links are used, providers can receive technical request data such as IP address, requested map area/tile, user agent, connection metadata and SDK telemetry required for the service.	Display online maps, provider attribution, external map links and service operation.	Online maps can be avoided by using imported/offline maps where available. Provider-side retention follows the selected provider's terms.

Sharing

What leaves the device

There is no sale of user data and no sharing with advertising SDKs. Relevant off-device paths are feature-based.

Map and SDK providers

Google Mapas / Google Play services and OpenStreetMap tile providers may receive technical request and map context data when their services are used.

Android Sharesheet

Exports, reports, QR images, viewrange images and Remote ID files are shared only to destinations selected by the user.

BLE group mode

Group packets are exchanged over local radio with active group participants and are protected with AES-GCM using the group key.

Soporte contact

If users contact support, the message and any attachments are handled by the selected email provider and ArxSilex support/privacy contact.

Seguridad

Seguridad, retention and deletion

The app relies on Android's permission model, sandboxing and local-first storage. Additional protection is used for backups, group mode and Remote ID diagnostics.

Area	Implementation
Encryption in transit	The production Network Seguridad Configuration disables cleartext traffic. Online services are accessed over HTTPS where provided by the provider.
Local storage	Android app sandbox; `android:allowBackup=false`; no automatic app-operated cloud backup.
Backups	Manual backups can be password-protected with AES-256-GCM and PBKDF2WithHmacSHA256. Backups remain where the user stores them.
BLE group data	Group keys are stored via Android Keystore AES-GCM; group packets use AES-GCM and replay protection.
Remote ID	Remote ID data is processed locally. BLE/Wi-Fi identifiers are shortened with SHA-256 hashes. Live entries expire; optional history is session-only or 24 hours and can be cleared.
Deletion	Local data can be deleted inside the app, by clearing Android app data/cache or by uninstalling. Exported files, backups and shared copies must be deleted at their destination.

Play Console

Suggested review points before submission

Before submitting a release, compare the Play Console Seguridad de datos form with the actual APK/AAB, dependencies and enabled features.

Check	Release note
Collected data	Declare data that leaves the device through SDKs, online maps, support, exports/shares or group features. Local-only data should be described in the privacy policy even if it is not Play-Console collection.
Shared data	Declare user-initiated Android sharing, map/SDK provider transfers and BLE group sharing where applicable. Mark advertising/analytics sharing as not used.
Optional vs required	Most transmissions are optional by feature. Online map requests are required only when the selected online map/provider is used.
Deletion	No app account exists. Local deletion paths and the public data deletion page should stay consistent with the Seguridad de datos form.

Política de privacidad Permisos Eliminar datos

GooglePlay

Datos de ubicación para alarmas de fondo opcionales

La información de seguridad de los datos debe reflejar la característica de alarma de objeto publicada, su propósito limitado y la ruta de procesamiento local.

Función

Notificación espacial para una alarma de marcador o círculo habilitada explícitamente por el usuario.

Estado predeterminado

La ubicación en segundo plano para alarmas de objetos no se solicita sin una activación explícita.

MapTools no envía ubicaciones de alarma a su propio servidor y no las utiliza para publicidad o análisis.

controlar

La alarma, la opción de fondo y el permiso Android se pueden desactivar o revocar.

Liberar alineación

La declaración de la tienda, el vídeo de reseña, la página de privacidad y la versión de la aplicación publicada deben mostrar el mismo alcance de funciones antes de cargar Play.

Google Play

Base actual de declaración de Google Play

MapTools no tiene publicidad ni análisis propio. Por Maps SDK, ARCore y Play Billing, una declaración general de «no se recopilan datos» no es correcta.

SDK

Al usar la función, declara IDs de usuario (ARCore), IDs de dispositivo u otros, interacciones, registros de fallos y diagnósticos. Finalidad: análisis del SDK, estabilidad y mejora del servicio, no publicidad; transmisión cifrada.

Ubicación / Compra

Declara ubicación aproximada/precisa como función opcional cuando la transmitan mapas online, rutas, servicios geográficos o grupos. El historial de compra Pro se considera funcionalidad; MapTools no accede a datos de pago.

Compartición

No hay venta, redes publicitarias ni perfiles publicitarios. ARCore indica que no comparte sus datos con terceros. Las transferencias a proveedores o iniciadas por el usuario deben revisarse según las excepciones de Play en cada versión.

Local

Proyectos, adjuntos, importaciones y alarmas locales no se recopilan solo por procesarse en el dispositivo. Las geovallas permanecen locales, sin servidor MapTools ni historial.

Añadir adjunto

Incluir adjuntos de objetos

Los adjuntos pueden contener imágenes privadas, documentos, voces y metadatos de ubicación. Inclúyalos solo de forma consciente.

MapTools comprueba primero el archivo y después muestra los contenidos y destinos de importación adecuados. No se importa nada sin confirmación.

Android filtra según el tipo de archivo informado. La extensión y el contenido se comprueban de nuevo antes de importar.

Datos internos de la aplicación

Los adjuntos se gestionan localmente en el almacenamiento privado de la app. La cámara y el micrófono solo funcionan durante una captura iniciada expresamente; exportar y compartir requieren una selección consciente.

Las vistas previas usan una caché privada limitada que puede reconstruirse y borrarse desde la gestión de almacenamiento de la app o de Android.

Corregir datos de la foto

Solo los campos introducidos sustituyen los valores activos. Los datos EXIF y MapTools permanecen sin cambios.

Compartir adjunto

Los adjuntos pueden contener imágenes privadas, documentos, voces y metadatos de ubicación. Inclúyalos solo de forma consciente.

Las imágenes, PDF y notas de audio solo se incrustan en el proyecto .asmaps si se selecciona la opción, y al importar se vuelven a asignar a los objetos o al proyecto correspondientes.