> For the complete documentation index, see [llms.txt](https://docs.freeflysystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.freeflysystems.com/ecosystem/payloads/flux-lidar/safety-and-legal/flux-app-privacy.md). # Flux App Privacy ## Freefly Flux app: privacy This notice covers the Freefly Flux app on iOS, iPadOS, Android and desktop. It adds to the [Freefly Systems Privacy Policy](https://freeflysystems.com/privacy-policy), which covers everything else. The short version. The app has no accounts, no ads and no tracking. It never reads your phone or tablet's location. Your scans stay on your device unless you export them or send logs to our support team. ### What the app sends Usage ping. At most once a day the app sends a random install ID, the app version, the platform and the operating system version. In Debug mode it also sends build details and counts of scans processed, exports and failures. We use this to count active installs and versions. It is not tied to your name or any account. If you send Log to Team, the ticket includes the same install ID, so support can see which app versions your device has run. Turn the ping off any time in Settings › Privacy. Log to Team (only when you tap it). When you tap Log to Team and confirm, the app sends a diagnostics file to Freefly support: app and flight logs (including which screens and buttons were used), viewer performance logs, device model, operating system, storage figures, the app build, the install ID, and your payload's serial number and firmware version. Logs can include locations from your flights or base station, and scan file names. You get a ticket name to quote to support. We use it only to help you and to fix problems. Maps. To draw maps, the app requests map tiles from CARTO (map data © OpenStreetMap contributors), Esri (satellite imagery) and Amazon Web Services (terrain). They receive which map area is on screen and your device's IP address, under their own privacy policies. Nothing else is sent to them. Drone and payload. The app talks to your drone and LiDAR payload over their local network. That data does not leave your device unless you export it or send Log to Team. ### Where it is stored Usage pings and Log to Team files are received and stored privately on Vercel, our hosting provider. Vercel keeps its own request logs, which include IP addresses. All data is sent encrypted (HTTPS). ### How long we keep it, and deletion Log to Team files are kept while they are useful for supporting you and improving the app. To have yours deleted, email with your ticket name. Usage pings carry no name or account. If you also want the usage records for your install deleted, include that in the same email. We do not sell or share your data with anyone else. The app is not directed at children. ### Contact Questions: . --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.freeflysystems.com/ecosystem/payloads/flux-lidar/safety-and-legal/flux-app-privacy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.