Your flights. Your data.
How Drone Ground Station handles local data, maps and optional reporting.
Updated 15 October 2026
Data on your device
Recordings, aircraft profiles, connection settings and telemetry layouts stay on this device. Saved connections include module addresses and ports. Layouts store selected field names and sources, without sensor values. Flight recordings and exports include received telemetry, aircraft positions and, when available, the saved aircraft’s ID and name captured at connection start. Recording starts automatically when a radio connection opens and saves locally until disconnection. Long sessions use bounded files displayed as one flight. No cloud sync or account is required. Browser recordings use browser storage and are separate from the installed app’s files.
Maps, location and sharing
Maps load by default using OpenFreeMap, with OpenStreetMap data. OpenFreeMap receives requests for the visible area and your network address. If loading fails, the position plot remains available. Phone location is optional and used only while the Flight view is visible in the foreground. Your choice is remembered, but phone coordinates stay in memory and are excluded from aircraft telemetry, recordings, diagnostic logs and app improvement reports. An online map centred on your phone still requests tiles for that area. Exporting or copying a recording is your choice. Sharing coordinates creates a CSV file with precise aircraft positions and available observation times. Sharing a complete flight creates a JSON file with all saved telemetry and aircraft metadata. These files stay local until you choose a receiving app or destination. No flight export is uploaded automatically.
Diagnostic logs
Optional diagnostic logs keep the latest 500 events in memory for this app session. Your logging choice is saved on this device and applies when you reopen the app. Logs include app revision, connection status, packet and byte counts, sent heartbeat counts, MAVLink message and routing IDs, declared component type/autopilot codes, GPS readiness status, available field names and error reference IDs, excluding sensor values, positions, network addresses, aircraft names, credentials and raw errors. Review the preview before copying or sharing it. These local logs are never uploaded automatically. Clear logs or close the app to remove them.
Optional app improvement reports
App improvement reports are separate and start off. In configured production builds, you can enable error reports to GlitchTip, hosted in Switzerland, or anonymous usage to PostHog in the EU. Error reports contain fixed error codes, reference IDs, app version and platform. Usage includes fixed screen names, connection methods and action outcomes, with a random session identity. No raw errors, GPS coordinates, telemetry readings, network addresses, aircraft names, recording IDs, free text, credentials or session replay are included. The services necessarily receive your network address when a report is sent.
Your choices
These choices are saved on this device. Turning an option off stops future reports and clears its local reporting state. Reports already received by a service remain subject to that service’s retention settings. Core flight tools keep working offline. Development and staging builds send no reports.
Privacy
These support and privacy pages use no analytics or tracking scripts. Your browser contacts the website host to load the page and its local assets.
drones@shumil.in