← Back
Português · English · Español

Privacy Policy — Tairu Drone (beta)

Version 1.1 (beta), of November 3, 2026 · Applies to the beta versions of the bridge

What changed in version 1.1: the bridge now checks whether there is a new version on our website and downloads and installs it when you ask (section 3.8), with Android's permission to install apps (section 3.5); the diagnostics include the names of the network interfaces and a pairing identifier (section 3.6).

Updated on November 8, 2026, without changing the version: from 0.2.12 on, the stored flights and the diagnostics include the radio link to the aircraft, the bridge device's Wi-Fi, the position and angles of each marked point and the point dragged in an adjustment of the layers on the controller, without the network's name or address (sections 1.1, 3.2 and 3.6).

Updated on November 9, 2026, without changing the version: once cloud sharing is released in Tairu Maps, the pilot's Tairu Maps may relay to our server the video it receives from the bridge (sections 1, 1.2 and 2). The bridge itself still sends us nothing.

Controller: Daniel H. Saint Martin — CPF (Brazilian individual taxpayer number) 001.627.811-99
Data Protection Officer (DPO): Daniel H. Saint Martin — danielhsmartin@gmail.com


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

DataOn the bridge's deviceGoes to
Video from the drone's cameraOnly 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 statusThe 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 deviceTogether with each stored flightAnalysis 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 flightAnalysis file, if you send it
Pairing secrets (key and token)Until "Renovar segredos" (Renew secrets) or uninstallationThe QR, to whoever you show it to
Expedition layers, coming from Tairu MapsOnly 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 flightAnalysis file, if you send it
Pilot's name, expedition name and pilot device code, coming from Tairu MapsUntil the pilot slot passes to another device or is released, even if the bridge restarts; the code also in the stored flightsAll paired devices, live
Marked points: position, camera angles and the photo from the videoThe position and angles, together with each stored flight; the photo, in memory, for up to 10 minutesThe pilot device, which creates the record
Flight logs and technical logs of the DJI SDKIn the bridge's folder, for the period the SDK definesDJI, under the terms of section 4
Usage statistics of the DJI SDK—DJI (section 4)
Map area viewed in the Modo pilotoMap cacheOpenFreeMap (section 5)
New-version check: the device's IP address, in the request for the version fileThe last published version read and the date of the checkThe bridge's website, hosted by Google (section 3.8)
APK of a new version, when you askIn the bridge's folder, until installation or until you choose "nunca" (never)—
Acceptance of the Terms of Use and of this policy: version and dateUntil uninstallation—

1.2 What we never do

1.3 What we must state frankly


2. Roles: who is the controller of what

DataController
Video, stored flights and the images of people and places filmedYou, 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 pointsThe controller of the expedition in Tairu Maps (Tairu Maps Privacy Policy, section 2)
Analysis file you send usTairu Maps, for support
Data collected by the DJI SDKDJI, 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

3.5 Android permissions

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.


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:

What the bridge does to limit it:

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)

PurposeLegal 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 devicePerformance 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 usLegitimate 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 fixedLegitimate 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

DataPeriod
Stored flightsThe 5 most recent recordings; earlier ones are deleted automatically
Recorded videoTogether with the flight it belongs to
Pairing secretsUntil "Renovar segredos" or uninstallation
Tairu Maps layersWhile 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 codeUntil the pilot slot passes to another device or is released
Photo of a marked pointUp to 10 minutes, in memory
Analysis file on the deviceUntil the next export
Analysis file sent to usUp 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 checkUntil the next check
APK of a new versionUntil installation, deleted at the next opening; or until you choose "nunca" (never). An interrupted download is kept to resume where it stopped
DJI SDK logsFor the SDK's period
Everything on the bridge's deviceDisappears upon uninstallation, or when the application's data is cleared in the Android settings

8. Security

What we do:

What we do not do, and you should know:


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