Privacy Policy — Tairu Drone (beta)
1. In summary
Tairu Drone (the "bridge") is the Android application that connects a DJI drone to Tairu Maps. It runs on the DJI controller with a screen, or on a phone connected by cable to an RC-N controller. It receives the video and the telemetry from the aircraft and passes them on to the devices with Tairu Maps that you pair.
The central rule is this:
The bridge has no account and no metrics of ours, and it sends us nothing about you or your flights. What it processes stays on the device it runs on and leaves that device only for four destinations: the devices with Tairu Maps that you pair, over the local network; DJI, through its SDK, without which the bridge cannot talk to the aircraft; OpenFreeMap, which provides the map of the Modo piloto (Pilot mode); and our website (tairumaps.com), which the bridge only asks which version is published, and from which it downloads the new version when you ask.
The bridge does not send us the video, the telemetry or the flights — unless you yourself send us an analysis file (section 3.6). The photo of a marked point becomes a record in Tairu Maps and follows the Tairu Maps policy. If the pilot shares the video with the team, it is the pilot's Tairu Maps that relays it to our server, without recording, and the Tairu Maps policy applies (section 3.10).
1.1 What the bridge processes, where it stays and where it goes
| Data | On the bridge's device | Goes to |
|---|---|---|
| Video from the drone's camera | Only if you turn on "Gravar o vídeo dos voos" (Record flight video), which is off when installed, or tap "Gravar agora" (Record now) | Paired devices, live |
| Telemetry: position, altitude and attitude of the aircraft and of the gimbal, takeoff point, battery, GPS, camera status | The 5 most recent recordings (each flight, and each "Gravar agora") | Paired devices, live |
| Model and serial number of the aircraft; model and Android version of the device | Together with each stored flight | Analysis file, if you send it |
| Radio link to the aircraft (band, channel, quality, signal, rates and interference) and the device's Wi-Fi (frequency, signal, speed, how many devices are watching the video and how much the bridge sends, without the network's name or address) | Together with each stored flight | Analysis file, if you send it |
| Pairing secrets (key and token) | Until "Renovar segredos" (Renew secrets) or uninstallation | The QR, to whoever you show it to |
| Expedition layers, coming from Tairu Maps | Only in memory, while the bridge runs, except the points in the row below | — |
| The point dragged in an adjustment of the layers on the controller, on an element coming from Tairu Maps (its position and where it was let go on the picture) | Together with each stored flight | Analysis file, if you send it |
| Pilot's name, expedition name and pilot device code, coming from Tairu Maps | Until the pilot slot passes to another device or is released, even if the bridge restarts; the code also in the stored flights | All paired devices, live |
| Marked points: position, camera angles and the photo from the video | The position and angles, together with each stored flight; the photo, in memory, for up to 10 minutes | The pilot device, which creates the record |
| Flight logs and technical logs of the DJI SDK | In the bridge's folder, for the period the SDK defines | DJI, under the terms of section 4 |
| Usage statistics of the DJI SDK | — | DJI (section 4) |
| Map area viewed in the Modo piloto | Map cache | OpenFreeMap (section 5) |
| New-version check: the device's IP address, in the request for the version file | The last published version read and the date of the check | The bridge's website, hosted by Google (section 3.8) |
| APK of a new version, when you ask | In the bridge's folder, until installation or until you choose "nunca" (never) | — |
| Acceptance of the Terms of Use and of this policy: version and date | Until uninstallation | — |
1.2 What we never do
- The bridge has no registration, no usage metrics and no crash reports: it does not use Firebase or any other service of ours, other than reading the file of the version published on the website (section 3.8), which carries nothing about you, the device or the flights.
- The bridge does not send us video, telemetry or flights, except for the file you decide to send us. The photo of a marked point becomes a record in Tairu Maps and follows the Tairu Maps policy. The video the pilot shares with the team is relayed by the pilot's Tairu Maps, under the terms of the Tairu Maps policy (section 3.10).
- We do not sell data and we do not run advertising.
- The Emergency Card, the name of an emergency, the victim, the tourniquet time, the chat and the list of members never go to the bridge.
- We do not authorize DJI to use the data of your flights for "product improvement": the bridge declines that option when it starts the SDK.
1.3 What we must state frankly
- The video and the layers travel unencrypted over the local network. With the bridge paired over the Wi-Fi network, the MAVLink messages between it and Tairu Maps (telemetry, layers, marked points and control) are signed with the QR's key, so that a device without the QR cannot forge them; every paired device has the same key, and signing is not encrypting. Anyone on the same network who captures the traffic can see the video, the photos of the marked points, the layers, the pilot's name and the expedition's name, even without the QR. Use a network of your own or the phone's hotspot.
- The DJI SDK runs inside the bridge. The layers that Tairu Maps sends (names, recorded tracks, the position of ongoing emergencies), the pilot's name and the expedition's name stay in the memory of the same application in which the SDK runs. No function of the bridge hands this data over to the SDK, but DJI's code is closed, and we have no way to audit it.
2. Roles: who is the controller of what
| Data | Controller |
|---|---|
| Video, stored flights and the images of people and places filmed | You, or the organization you fly for: whoever decides the flight, what to film, what to record and whom to pair with. Through the bridge, this data does not reach us; the video the pilot shares with the team passes through our server, without being recorded |
| Layers and marked points | The controller of the expedition in Tairu Maps (Tairu Maps Privacy Policy, section 2) |
| Analysis file you send us | Tairu Maps, for support |
| Data collected by the DJI SDK | DJI, under its own privacy policy |
If the flight films people, properties or vehicle license plates, the legal basis for that processing and respect for image rights are the responsibility of whoever flies.
3. Data processed
3.1 Video
The video from the drone's camera appears on the screen and goes, live, to the paired devices. It is recorded on the bridge's device only if you turn on "Gravar o vídeo dos voos" (off when installed), and recording starts at the next takeoff; or if you tap "Gravar agora", which always records with video.
3.2 Stored flights
With the bridge on, each flight is recorded automatically, from takeoff until 30 seconds after landing: the telemetry, the time of each video frame, the events (the aircraft's and the controller's connection and loss, a change of camera and of pilot device, marked points and Tairu Maps' answers, with the pilot device's network address) and the device's temperature and battery. Takeoff and landing are in the telemetry. Each flight also stores the model and serial number of the aircraft, the model of the device and the versions of the bridge and of the SDK. From 0.2.12 on, each flight also stores the radio link to the aircraft, as the DJI SDK reports it (band, channel, quality, signal, rates and interference), and, every 2 seconds, the bridge device's Wi-Fi (frequency, signal, speed, how many devices are watching the video and how much the bridge sends), never the network's name or address. This data is used to understand video failures. For each marked point (with the Mark button or with C1), the flight also stores what the bridge sent to Tairu Maps: the camera's position and angles at the press, without the photo. For each adjustment of the layers made on the controller, by dragging an element to its place in the video, it stores the position of the dragged point, where it was let go on the picture and the camera's angles in that frame. To keep that adjustment when the camera turns, the bridge compares reduced images of the video, only in memory and without storing them, and the flight stores how much the heading was corrected. This way a bad adjustment can be redone later. The other layers are never stored.
The bridge keeps the 5 most recent recordings: each flight is one, and so is each "Gravar agora" (Record now). Older ones are deleted automatically when a new one starts.
The takeoff point is usually where the pilot is. For that reason, the stored flights reveal where you have been.
3.3 Pairing
The pairing QR carries the bridge's network address, the ports, its name and two secrets: the video token and the key that signs the messages. The devices that scan the QR store this data. On a controller with a screen, the QR stays in view on the bridge's screen while no paired phone is heard, outside a flight; on a phone, only when you ask for it. When Tairu Maps does not find the bridge at the QR's address (the network changed), it looks for it on the phone's own Wi-Fi networks and switches to the new address, without scanning the QR again. "Renovar segredos" creates new secrets, and all devices need to scan the QR again.
3.4 What comes from Tairu Maps
- Layers: the visible layers of the expedition in a square about 8 km on a side: points, lines and areas of the records, with the name or label of each one; recorded tracks; features of imported layers and of WFS services; the GRG grid; and the position of ongoing emergencies, only with the label "Emergency". They stay only in memory, while the bridge runs, and are not included in the recorded video or in the photo of the marked points; only the position of the point dragged in an adjustment of the layers on the controller is kept with the flight (section 3.2). The position of an ongoing emergency cannot be dragged and is never recorded. They can be hidden in the Modo piloto.
- Pilot slot: the device that requests the pilot slot sends the name of the user's profile and the name of the open expedition, and every paired device sends an installation code, derived from the account. The bridge shows the name and the expedition on its screen and passes them on to all paired devices. It keeps them until the slot passes to another device or is released, even if it restarts, and the code is included in the stored flights. The analysis file does not carry the name or the expedition.
- Marked points: when you tap Marcar (Mark), or press the C1 button on the controller, the bridge sends to the pilot device the position and the angles of the camera, the laser measurement, when available, and the photo from the video as the pilot saw it, without the layers. Tairu Maps creates the record in the expedition. The bridge keeps the photo in memory for up to 10 minutes (the 20 most recent), for Tairu Maps to fetch it.
3.5 Android permissions
- Location and phone: the DJI SDK requires them, and the use the SDK makes of them follows DJI's terms and privacy policy (section 4). The bridge does not record the device's position and sends it to no one, with one exception: when you choose, in the pre-flight check, to set the home point at the controller's position, it sends that position to the aircraft. While the Modo piloto is open, its flight radar (a DJI component) reads the device's GPS to show where you are relative to the aircraft. The bridge's screen uses the same permission to show the Wi-Fi network's name.
- Notifications: so that the bridge keeps running with the screen off.
- USB: to talk to the RC-N controller.
- Network: Wi-Fi and internet.
- Install apps: to install the new version you downloaded through the bridge itself (section 3.8). Android asks you to grant this permission the first time and confirms each installation.
3.6 Export for analysis
Only when you tap "Exportar para análise" (Export for analysis) does the bridge put together a zip file with the diagnostics and the stored flights (the telemetry and, if any, the video). The diagnostics include versions, the device model, the Android version, the aircraft and its serial number, the settings, the SDK status, the radio link to the aircraft and the device's Wi-Fi (frequency, signal, speed, how many devices are watching and how much the bridge sends, without the network's name), the network addresses with the name of each interface, the addresses of the paired devices the bridge heard (and of whoever sent the shared correction), the aircraft's current position, a pairing identifier (a digest of the key, from which the key cannot be rebuilt), the result of the last version check and the bridge's latest messages; the events of each flight include the pilot device's code. It never includes the pairing token or key, nor the pilot's name or the expedition's name.
The bridge only creates the file and opens Android's share sheet: who receives it is your choice. The previous file is deleted when you export another one.
If you send it to us, we use the file only to diagnose and fix the bridge. We do not pass it on to anyone, and we delete it within 90 days after the case is resolved. Before sending, remember that the video may show people and places.
3.7 Acceptance of the terms
When opened for the first time, the bridge shows the Terms of Use and this policy, and it works only after you accept them. Before that, the bridge does not start the DJI SDK or check for a new version, so nothing goes to DJI or to our website. The bridge stores on the device the accepted version and the date, and asks for acceptance again when the Terms of Use change (their section 11) or when this policy has a relevant change (section 12). This record does not leave the device.
3.8 New version
The bridge is not on Google Play, so it tells you itself when there is a new version.
- What it asks for: the file
tairumaps.com/tairu-drone/versao.json, with the number of the published version, the address, size and SHA-256 of the APK, and the release notes. The request carries no identifier, account, serial number, device model or flight data: the bridge identifies itself only as "TairuDrone". As with any visit to a web page, the website's provider receives the device's IP address. We do not use this request to identify anyone. - When: by itself, when the bridge's screen opens, at most once every 24 hours, and only on a network that Android has marked as connected to the internet; and whenever you tap "Verificar agora" (Check now). Without internet, nothing happens and nothing is delayed.
- Your choice: under "Atualizações" (Updates), on the bridge's screen: automáticas (automatic, the default), só quando eu pedir (only when I ask: the bridge asks the website only when you tap "Verificar agora") or nunca (never: the bridge does not talk to the website; check the version on the page).
- Download and install: only when you tap "Baixar e instalar" (Download and install). The APK goes to the bridge's folder, and the bridge checks its size and SHA-256 before handing it to Android's installer. Android asks for your confirmation and only accepts a version signed with the same key as the installed bridge and newer than it. The file is deleted at the next opening after installation. On a controller connected to the phone's hotspot, the download uses the phone's mobile data.
- Never in flight: with the aircraft connected, the bridge neither downloads nor installs, because the update restarts it and drops the video, the telemetry and the Modo piloto.
- Where the website is: tairumaps.com is hosted by Google (Firebase Hosting), which may serve the request from servers outside Brazil.
4. DJI and its SDK
The bridge talks to the aircraft only through the DJI Mobile SDK. Through it, DJI processes data as a controller, under its own terms of use and privacy policy. DJI is not a party to this policy.
What the SDK does, according to DJI's terms and to what we have observed in the bridge:
- registers the application with DJI, over the internet, after your acceptance (section 3.7), the first time and after each reinstallation or update;
- collects usage statistics, including unique identifiers;
- downloads and applies DJI's flight zone database and limits;
- writes flight logs and technical logs on the device, in the bridge's folder.
What the bridge does to limit it:
- declines DJI's "product improvement" when starting the SDK;
- does not offer to send the warranty logs, which, under DJI's terms, only go to DJI with your consent;
- offers Local Data Mode (LDM), in Detalhes técnicos (Technical details), which cuts off the SDK's network access, except for registration. It requires a license requested from DJI.
DJI's servers may be located outside Brazil. This international transfer is governed by DJI's terms.
5. Modo piloto map (OpenFreeMap)
The Modo piloto map comes from OpenFreeMap (tiles.openfreemap.org), with OpenStreetMap data. Each map request reveals to the provider the area viewed and the device's IP address. What has already been viewed stays in cache; without internet, only what is in the cache appears.
6. Purposes and legal bases (LGPD — Brazil's General Data Protection Law, art. 7)
| Purpose | Legal basis |
|---|---|
| Display and transmit the video and the telemetry to the devices you paired; display the layers; display and relay to the paired devices the pilot's name, the expedition's name and the pilot device's code; keep the latest flights on your device | Performance of a contract (art. 7, V), on your device and at your request: through the bridge, this data does not reach us |
| Handle a support request with the analysis file you sent us | Legitimate interest (art. 7, IX), following your request |
| Tell you about a new version of the bridge and download it at your request, to keep it working and fixed | Legitimate interest (art. 7, IX). The request carries no data about you other than the IP address, and you can turn the check off |
7. Retention
| Data | Period |
|---|---|
| Stored flights | The 5 most recent recordings; earlier ones are deleted automatically |
| Recorded video | Together with the flight it belongs to |
| Pairing secrets | Until "Renovar segredos" or uninstallation |
| Tairu Maps layers | While the bridge runs, only in memory; the position of the point dragged in an adjustment, with the flight (section 3.2) |
| Pilot's name, expedition name and pilot device code | Until the pilot slot passes to another device or is released |
| Photo of a marked point | Up to 10 minutes, in memory |
| Analysis file on the device | Until the next export |
| Analysis file sent to us | Up to 90 days after the case is resolved |
| Acceptance of the terms (version and date) | Until uninstallation |
| Last published version read and date of the check | Until the next check |
| APK of a new version | Until installation, deleted at the next opening; or until you choose "nunca" (never). An interrupted download is kept to resume where it stopped |
| DJI SDK logs | For the SDK's period |
| Everything on the bridge's device | Disappears upon uninstallation, or when the application's data is cleared in the Android settings |
8. Security
What we do:
- With the bridge paired over the Wi-Fi network, the MAVLink messages between it and Tairu Maps are signed with a 32-byte key, the same for all paired devices, and the video and the photos of the marked points require the pairing token.
- "Renovar segredos" invalidates all pairings at once.
- The APK is published only at tairumaps.com, with the SHA-256 on the page, so that you can verify its origin. When updating itself, the bridge only follows tairumaps.com addresses, over HTTPS, without following redirects, and checks the size and SHA-256 of what it downloaded; Android refuses an APK signed with another key or older than the installed one. Tairu Maps never downloads or installs the bridge.
What we do not do, and you should know:
- The video and the layers are not encrypted on the local network (section 1.3).
- The flights stay in the bridge's folder on the device, protected only by Android's own security. Anyone who has the unlocked controller or phone can copy them. Use a screen lock.
9. Your rights (LGPD, art. 18)
The bridge's data stays on your device, and you control it directly: the flights go out in the analysis file and disappear upon uninstallation, or when you clear the application's data in the Android settings.
Regarding an analysis file you sent us, you may request access, correction or deletion by writing to danielhsmartin@gmail.com. We will respond within 15 days. Regarding the SDK's data, requests go to DJI, through its own channels.
If you are not satisfied with the response, you may file a complaint with the ANPD — Autoridade Nacional de Proteção de Dados (Brazil's national data protection authority) (gov.br/anpd).
10. Beta
This policy accompanies the bridge's beta. A version that collects a new piece of data or sends data to a new destination will only be published after this policy has been updated. The bridge tells you when there is a new version, but does not update itself: you decide when to download and install it, and Android confirms each installation.
11. Minors
The bridge is not intended for people under 18 years of age.
12. Changes to this policy
Relevant changes will be announced on the bridge's page at tairumaps.com before they take effect. The version of the bridge that brings the new policy will ask for your acceptance before it continues to work.
Languages. In case of divergence between this policy and a translation of it, the Portuguese version prevails.
13. Contact
Data Protection Officer (DPO): Daniel H. Saint Martin E-mail: danielhsmartin@gmail.com Supervisory authority: ANPD — gov.br/anpd
Tairu Drone · Developed by Daniel H. Saint Martin