Privacy Policy — Tairu Maps
1. In summary
Tairu Maps is a platform for collaborative mapping and geospatial data collection in the field. This policy explains what the application collects, what it does not collect, and — most importantly — what depends on a choice you make.
The central rule is this:
You decide, Expedition by Expedition, whether the data goes to the cloud.
Every Expedition has a "Sync to the cloud" switch. With it turned off, the Records, photographs, geometries, tracks and attachments of that Expedition remain on your device and are never transmitted to our servers.
The exception is the live drone: the pilot's device sends the Expedition's layers to the drone controller, over the local network, without going through our servers (section 3.9).
1.1 What is collected, and when
| Category | Always | Depends on the plan | Depends on the Expedition switch |
|---|---|---|---|
| Name, e-mail, password (encrypted), profile picture | ● | ||
| Subscription and payment data | ● | ||
| Application access logs (Marco Civil da Internet — Brazil's Internet Civil Rights Framework, art. 15) | ● | ||
| Crash diagnostics and usage metrics | ● | ||
| Records, photographs, geometries, field attachments | ● | ||
| Tracks and location history | ● | ||
| Real-time location of the team | ● | ● | |
| Chat messages between Members | ● | ||
| Data of a declared emergency: what happened, the marked victim, tourniquet time (section 3.7) | ● | ||
| Emergency Card — health data, optional (section 3.6) | ¹ | ||
| Drone photos and the Records created from them (section 3.8) | ● | ● | |
| Live drone: video, telemetry and layers exchanged with the drone controller (section 3.9) | ● | ² | |
| Drone shared with the team: position, area in view and, if the pilot chooses, video (section 3.10; from version 1.0.93, once released) | ● | ● |
¹ It exists only if you fill it in, and it goes to the cloud only when you share it with an Expedition — a decision of its own, separate from the Expedition's switch.
² Outside sharing with the team (section 3.10), the video and the telemetry do not go to the cloud, and the copy of the layers sent to the controller travels only over the local network, between your device and the drone controller. What does go to the cloud, as Expedition content, are the points marked by the pilot, with the video frame and a description drawn from the telemetry, and the indication of who is piloting (section 3.9).
On the Offline plan there is no cloud synchronization under any circumstances: the application works entirely on the device, including Tracking, Records, offline base maps and the import/export of .tairudb, KML, GPX and GeoPackage files.
1.2 What we never do
- We do not sell personal data.
- We do not use your data for advertising, nor do we allow third parties to do so.
- We do not use the content of your Expeditions to train artificial intelligence models.
- We do not access the content of your Expeditions as an operational routine.
- We do not use the Emergency Card, or the data of an emergency, for anything other than the rescue: never in metrics, crash diagnostics, advertising, pricing, insurance, ranking or any other product.
- The drone video goes through our server only when the pilot shares it with the team, and is not recorded there (section 3.10); otherwise, only the frame of a point marked by the pilot, as the Record's photo (section 3.9). The Emergency Card, the victim, the tourniquet time, the chat and the list of Members never go to the drone controller.
1.3 What we must state frankly
Tairu Maps does not use end-to-end encryption on synchronized data. Protection is by encryption in transit (TLS) and at rest, with access control by server rules. This means that the infrastructure administrator has technical access to the data stored in the cloud. There is no routine, process or purpose of accessing user content — but it would be dishonest to claim that such access is cryptographically impossible, because it is not.
If your use case does not admit this condition, use the cloud switch turned off.
Communication with the drone controller, on the local network, is also not encrypted, and the cloud switch does not prevent it (section 3.9). The video shared with the team is encrypted up to the server and from there to whoever watches but, as with other data, without end-to-end encryption (section 3.10).
2. Roles: who is the controller of what
This distinction is relevant for organizations that use Tairu Maps in institutional activity.
| Data | Controller | Processor |
|---|---|---|
| Registration, authentication, subscription, access logs, diagnostics | Tairu Maps | — |
| Expedition content: Records, photographs, geometries, tracks, Members, messages, declared emergencies, drone shared with the team | You (or the organization you belong to) | Tairu Maps |
| Emergency Card | Tairu Maps, based on your consent | — |
That is: regarding the data you produce in the field, you are the one who decides the purposes. We merely store and synchronize it according to your instruction, expressed through the application's settings. If you enter personal data of third parties (people involved, Contacts, photographs of individuals, aerial images of people, vehicles and properties), responsibility for the legal basis of that processing lies with whoever enters it.
Organizations that need to formalize this relationship may request a data processing agreement (section 12).
3. Data processed
3.1 Identification and authentication
Full name, e-mail address, password (stored in encrypted form by Firebase Authentication, never in clear text), profile picture (optional), e-mail verification status. When you sign in with Google or Apple, we receive from those providers only name, e-mail and account identifier.
3.2 Location
- During active Tracking: high-precision GPS coordinates, collected continuously while you start and maintain a Tracking session, including with the application in the background, if authorized.
- Points and features marked manually.
- Tracking never starts on its own. It is started by an action of yours and can be ended at any time.
- Background location permission is requested separately and can be revoked in the operating system settings.
- While you pilot a drone through Tairu Drone, the team sees a small airplane on your position marker (section 3.9). The position recorded in the history is your device's, not the drone's; the drone's is kept only with Track the drone on (section 3.10).
3.3 Field content
Expeditions (name, description, dates), Records with geometry (points, lines, polygons), photographs, observations, Members, Groups, record templates, Layers and imported files (.tairudb, PDF/GeoPDF, KML, GPX, GeoPackage).
Photographs may contain EXIF metadata with geographic coordinates, written by the device's camera. As a rule, the photo attached to a Record is redrawn with the stamp, which shows the coordinates and the time on the image itself, and loses the EXIF. In Plot Photos with the stamp turned off, the original EXIF travels with the image. For drone photos, see section 3.8.
3.4 Communication
Messages exchanged in the Expedition chat and in the direct chat between contacts, including sender, recipients and time. Chat is a cloud feature: it does not exist in offline mode.
3.5 Technical and diagnostic data
Application access logs (date, time and IP address of connections), crash reports (Firebase Crashlytics), aggregated usage metrics (Firebase Analytics: screens visited, application version, device model and system), device identifiers for sending notifications and for synchronization, and synchronization metadata.
Diagnostics and metrics do not include map content: no coordinate, Record, photograph, message, imported file, Emergency Card data or emergency data travels through those channels.
3.6 Emergency Card (health data)
The Emergency Card gathers what someone needs to know to help you in the field. Filling it in is optional, and it is sensitive personal data (LGPD, art. 5, II):
- allergies (or the statement that you have no known allergy), current medications, health conditions, emergency medication and where it is kept, restrictions (for example, a pacemaker or refusal of blood products), limitations for the activity;
- health plan and rescue insurance;
- up to two emergency contacts (name, relationship, phone) — data about other people: let them know you have included them;
- in a collapsed block: notes on the conditions, weight, year of the last tetanus shot, blood type and free-text notes;
- the date you confirmed the card and the record of your consent (date and version of the text you accepted).
How it works:
- When you fill it in for the first time, you see a dedicated notice about what this data is and you specifically consent to its collection. The card stays on your device.
- It goes to the cloud only when you share it with an Expedition. You choose Expedition by Expedition, or turn on "All my expeditions", which includes the Expeditions you join later. Before you share, the application shows who will be able to read it.
- Who reads it: the Members of the Expedition you shared it with — current ones and those who join later — while it is active and you are part of it. In an Expedition set so that only those in charge read cards, only the owner and the administrators read it. Nobody else: not your contacts, not Members of your other Expeditions, not the owner of an Expedition where you did not share, and not us as an operational routine.
- Whoever can read it receives a copy on their device, so that it works without signal at the scene, and can generate a PDF to hand to whoever receives you (rescue team, hospital). The copy of someone who lost access is deleted when that person's device connects again; until then, it stays there.
- On the web version, cards are read from the cloud and are not saved on the computer. Your own card is filled in on the mobile application.
- Tairu Maps stores, displays, transmits and prints the card. It does not assess, does not grade severity, does not triage and does not recommend treatment: it is not a health service.
3.7 Data of an emergency
When someone on the team declares an emergency in an Expedition, its record may contain, besides position and time: what happened (chosen from a list of events, such as a fall or an animal bite — never a diagnosis), which Member is the victim, the time a tourniquet was applied, the chosen care facility and what it needs to offer. This data is part of the Expedition's content and is seen by all of its Members, regardless of the Emergency Card being shared.
Emergency notifications carry the Expedition name, the type of emergency, the position, the name and description written by whoever declared it, and changes such as the destination, what happened or that a victim was marked. No notification carries Emergency Card content.
3.8 Drone photos
On the Realtime plan, the application places the original photo from a DJI drone on the ground it shows, with the Expedition's layers on top. On the other plans, a drone photo is treated as an ordinary photo: Plot Photos uses only the position and the time from the EXIF. To place the photo on the ground, the application reads, on the device, the metadata the camera writes into the photo: the position, the altitudes, the angles of the camera and of the aircraft, the model and the serial number of the drone, the time, the RTK data and the laser rangefinder.
What stays only on the device:
- The original photo, with all its metadata, in a folder of the Expedition, when you open it in Quick View. It is deleted when you close the Expedition or the next time the application is opened, and the team does not see it. The Expedition thumbnail, which the application takes from the map when you leave it, may show it reduced until Clear Expedition Data is used.
- A copy of the original file, on any plan, when you share an image with the application or use it as a base map, and when you save a photo as a layer. This copy is deleted when the import ends, whether it succeeded or not; if the application is closed before that, it is removed at a later opening, once a day has passed.
- The photo adjustments, made by you or by the automatic alignment (up to 500, each with the serial number or the model of the drone, the time and the position of the photo), and up to 200 ground images in grayscale of the adjusted photos, used to align the other photos of the same flight. They are kept per account: another account on this device neither sees nor uses them, and account deletion erases them on this device. The adjustments are also removed when you tap Clear Expedition Data, on the application's storage screen, or when they exceed 500; the ground images, with Reset or when they exceed 200; and both, upon uninstallation, except for what the device backup restores (section 8). On the web version, the photo is read only in the page's memory and is not kept, but the adjustments stay in the browser's storage.
What goes to the cloud, as Expedition content and according to its switch: never the original photo, nor the metadata that only the drone writes (the aircraft's serial number, the angles, the RTK data and the laser). What does go are the Records you create from the photo (Mark and Plot Photos), with a text description that includes the drone model, the time of the photo, the height, the estimated accuracy and where it comes from (GPS, RTK, laser or adjustment); the photo attached to them, redrawn with the stamp; and the layer's .tairudb file, when you send it to the cloud, with a name that carries the drone model and the time of the photo. In Plot Photos with the stamp turned off, the attached photo keeps the camera's original EXIF: the position and the altitude of the drone, the model and the serial number of the camera. A drone photo may show people, vehicles and properties: what section 2 says about third-party data applies.
Third parties. To position the photo, the application requests relief tiles from Amazon (section 6.2). These requests reveal the area and the device's IP address; nothing from the photo goes with them.
3.9 Live drone and the Tairu Drone bridge — on Android and iPhone
Tairu Drone is a separate application, installed on the drone controller or on a phone connected to it, with its own privacy policy. Tairu Maps connects to it over the local Wi-Fi network or, on Android, on the same device. The web version does not connect to the bridge; there you can only watch the drone shared with the team (section 3.10). The Drone page, the video, the layers and the marked points require the Realtime plan.
- Pairing. When pairing with the bridge, the application stores in the system's secure storage the bridge's network address, the ports, its name, the video token, the key that signs the messages, the profile (Pilot or Observer) and the account that paired. When the first Expedition is opened on Android or iPhone, it also draws a random number that identifies this installation to the bridge and keeps it on the device, even if you never use a drone. This number only leaves the device when a bridge is in use, and the bridge receives only a code derived from it and from your account.
- What the application receives from the bridge: the drone's video and telemetry — position, height, angles, battery, GPS and takeoff point. They are only displayed and stay in memory. Tairu Maps does not record the video. Outside sharing with the team (section 3.10), neither the video nor the drone's position or telemetry goes to the cloud: only what goes into the Record of a marked point does (below).
- What the application sends to the bridge: every connected device sends the installation code. The device that asks for the pilot slot (Pilot profile, Realtime plan and permission to edit Records) also sends the name of your profile and the name of the open Expedition. The one holding the slot sends the visible layers of the Expedition within a square of about 8 km on each side around the drone (lines are clipped at the square; areas and points that touch it go whole): 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; and the GRG grid. An ongoing emergency goes only as a position, with the label "Emergency" — never its name, the victim, the tourniquet time or the Emergency Card. This also applies in an Expedition without synchronization: the layers, its name and your name leave the device for the controller over the local network, without going through our servers.
- Who sees it: whoever operates the controller sees the layers in the Modo piloto (Pilot mode). Every device paired to the same controller — including those of people who are not Members of the Expedition — sees the pilot's name and the Expedition's name, even after the pilot closes the Expedition, until the pilot slot is released on the controller. Pair only the team's devices.
- The local network is not encrypted. With pairing over the Wi-Fi network, messages are signed with the QR's key: a device without the QR cannot forge them, but every device paired to the same controller has the same key. The video is not signed. The signature hides nothing: 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. Use a network of your own or the phone's hotspot.
- What goes to the cloud, besides sharing with the team (section 3.10): while you pilot, a mark with the time on your position marker, so that the team sees the small airplane — only when your position already goes to the cloud; the mark does not go into the location history and is removed 30 seconds after you stop piloting, or immediately if you close the Expedition — without a network connection, on a restricted link or if the application is terminated during the flight, it stays until the next time your position is recorded. And the points marked by the pilot, which become "Drone HH:mm" Records in the Expedition, according to its switch, with the video frame as the photo, with the stamp, and a description with the camera model, the time, the height, the estimated accuracy and where it comes from. This frame may show people, vehicles and properties: what section 2 says about third-party data applies.
- Third parties. The drone's position over the relief uses relief tiles from Amazon (section 6.2).
- Outside the Realtime plan, the live drone is off: there is no Drone page, video, layers or marked points, and the application neither looks for the bridge nor talks to it — it does not receive the telemetry, does not send the installation code and does not request relief tiles from Amazon for the flight. A pairing made before stays stored on the device and is used again when the plan returns.
- On Android, while you pilot, a local "Drone connected" notification keeps the connection alive while the screen is off. There is no drone notification from the server, and the drone generates no usage metrics.
3.10 Drone shared with the team through the cloud — from version 1.0.93, once released
This sharing is released by Tairu Maps after this version of the policy is published and may not yet be available to your account. Until it is, section 3.9 applies, and nothing from the drone goes to the cloud beyond what it describes. Once it is, it works as follows, on the Realtime plan. On the free trial you can watch, but not share the video.
- The drone's position. While you are the pilot in an Expedition synchronized with the cloud, the application automatically sends our server the drone's position, heading and height, the takeoff point, the point the camera is aimed at, the four corners of the area in view, the image size, the camera model and an indication that there is video. The serial number and your name are not sent: the document is identified by your account. Sending follows the tracking rule: at least 2 seconds and 5 meters of movement between one sending and the next and, with the drone still, every 15 seconds.
- The video. It is sent only when you tap Share with the team, and stops when you tap again, when you close or change Expedition and 30 seconds after the flight ends. It is sent without sound, with the camera data in each frame (position, angles, lens and laser) and the area in view.
- The route it takes. From the controller to your device, over the local network, not encrypted (section 3.9). From your device to the Tairu Maps video server, in São Paulo, and from the server to whoever watches, encrypted. There is no end-to-end encryption: whoever operates the server has technical access to the video while it passes through. There is no routine of access to this content.
- Nothing is recorded on the server. The video only passes through its memory.
- Who sees it. The Members of the Expedition who have their own Realtime plan, and only if they tap to watch. There is no public link. Each person receives a 5-minute authorization, renewed while watching: someone who leaves the Expedition may keep watching for up to 5 minutes.
- The flight path. It is kept only if you turn on Track the drone, on the Drone page: it becomes a "Drone tracking" Record of the Expedition, like any other, until someone deletes it.
- Technical logs. The video server logs the IP address, the Expedition and the account of whoever connects. These logs stay only in its memory and are gone when it powers off. The function that authorizes access logs the account, the Expedition and the time of each request, in Google Cloud's logs.
- What the video may show. A flight may show people, vehicles and properties: what section 2 says about third-party data applies.
4. What does not leave your device
With the "Sync to the cloud" switch turned off on an Expedition, all of its content remains only in the device's local storage, in a database encrypted with AES, whose key is derived and kept in the operating system's secure storage (Keychain on iOS, Keystore on Android).
The same applies in full to the Offline plan.
Under that condition, we have no access to this data — not because we promise not to look, but because it never reaches us.
Two caveats, neither of them going through our servers: with the live drone, the pilot device sends to the drone controller, over the local network, the Expedition's layers, its name and your name (section 3.9), even in an Expedition without synchronization. And the originals of drone photos, the adjustments and the ground images (section 3.8) stay outside the encrypted database, protected by the operating system's storage.
Caveat regarding the web version: in the browser, platform limitations prevent encrypting local storage in the same fashion. For sensitive data, prefer the mobile or desktop applications.
5. Purposes and legal bases (LGPD — Brazil's General Data Protection Law, arts. 7 and 11)
| Purpose | Legal basis |
|---|---|
| Create and maintain your account; authenticate access | Performance of a contract (art. 7, V) |
| Synchronize and store the content of the Expeditions you chose to take to the cloud | Performance of a contract (art. 7, V) |
| Share data between Members of the same Expedition | Performance of a contract (art. 7, V) |
| Collect location during active Tracking | Consent (art. 7, I), expressed by granting the permission and starting the session |
| Send operational notifications (messages, Alerts, emergencies) | Performance of a contract (art. 7, V) |
| Process subscriptions and payments | Performance of a contract (art. 7, V) and legal obligation (art. 7, II) |
| Keep application access logs | Legal obligation — Marco Civil da Internet, art. 15 (art. 7, II) |
| Diagnose failures and improve the application | Legitimate interest (art. 7, IX) |
| Prevent fraud and abusive use | Legitimate interest (art. 7, IX) |
| Keep your Emergency Card on your device | Specific and highlighted consent (art. 11, I), given the first time you fill it in |
| Share the card with the Members of one Expedition, or of all of yours | Specific consent (art. 11, I), given when you share |
| A Member reading your card during an incident, including when you cannot respond | Protection of life and physical safety (art. 11, II, "e") |
| Record the data of an emergency (what happened, victim, tourniquet time) and alert the team | Protection of life and physical safety (art. 11, II, "e") |
| Position drone photos and keep their adjustments on the device | Performance of a contract (art. 7, V) |
| Exchange with the drone controller, over the local network, the video, the telemetry, the layers, the pilot's name and the Expedition's name | Performance of a contract (art. 7, V), on your device and at your request: over the local network, this data does not reach us |
| Share with the team the drone's position and, at the pilot's request, the video (section 3.10) | Performance of a contract (art. 7, V) |
| Show the team who is piloting and create the Records of the marked points | Performance of a contract (art. 7, V) |
| Show the pilot, on the drone controller, the position of an ongoing emergency | Protection of life and physical safety (art. 7, VII) |
When the legal basis is consent, you may revoke it at any time — in the case of location, by ending Tracking or revoking the permission in the operating system; in the case of the Emergency Card, by turning off sharing with an Expedition or tapping Delete my card. Revocation does not affect the lawfulness of prior processing.
For health data we never rely on legitimate interest, which the law does not allow for sensitive data, nor on health protection (art. 11, II, "f"), which belongs to health professionals and services — and Tairu Maps is not one of them.
6. Sharing
6.1 Between Members
The data of a synchronized Expedition is visible to its Members, according to each one's role (owner, administrator or user), defined by whoever administers the Expedition. A Member does not see Expeditions they do not take part in.
With the live drone, whoever operates the controller and the devices paired to it receive data from the pilot's Expedition over the local network, even if they are not its Members (section 3.9). When shared through the cloud, the drone's position and the video are seen by the Expedition's Members who have the Realtime plan (section 3.10).
The Emergency Card follows its own rule (section 3.6): only the Members of the Expeditions you shared it with read it. In an Expedition where you did not share, the others see only that the card is not shared — neither its content nor whether it exists. Being owner or administrator grants access to nothing more. An outside responder (rescue team, firefighters, hospital) accesses nothing through the application: the Member shows the screen, reads it aloud or hands over the PDF.
6.2 Processors and third-party services
| Service | What it receives | Where |
|---|---|---|
| Google Firebase / Google Cloud (authentication, database, files, notifications, diagnostics) | Registration data, all synchronized content, the shared Emergency Card and, when shared with the team, the drone's position and video (section 3.10), on a Compute Engine machine | Database, files and server functions in São Paulo (southamerica-east1). Chat and real-time tracking in the United States (section 7). Authentication, notifications and diagnostics are global Google services and may be processed outside Brazil |
| Base map providers (Google, Esri, Microsoft, MapTiler, EOX, OpenFreeMap and others you configure) | Tile requests, which reveal the map area being viewed. | According to the provider |
| Amazon Web Services (relief tiles) | Elevation tile requests, which reveal the area queried: for the relief and to position drone photos and video | Outside Brazil |
| WMS/WFS services configured by you | Area requests and any credentials you provide | According to the server you choose |
| Apple / Google (App Store, Google Play) | Purchase and subscription data | According to the provider |
| Apple Push Notification service / Firebase Cloud Messaging | The text of notifications, including emergency ones (section 3.7) — never Emergency Card content | According to the provider |
Tairu Drone, the live drone bridge, is a separate application, with its own privacy policy: it uses the DJI SDK, which processes data under DJI's terms. Tairu Maps does not communicate with DJI, but the layers and names it sends to the bridge, including the position of ongoing emergencies, stay in the memory of the application in which DJI's closed-source SDK runs.
Land route calculation runs on your device, over OpenStreetMap data you download by region. No point of the route — including your position, when the route starts from it — is sent to third parties.
6.3 Authorities
We may share data upon court order or request from a competent authority, within the limits of the law. Whenever legally possible and not forbidden, we will notify the data subject.
6.4 What we do not do
We do not sell, rent or transfer personal data. We do not share it with data brokers, advertising networks, or for any third-party marketing purpose.
7. Where your data stays
The content of your Expeditions stays in Brazil, with two exceptions: chat and real-time tracking. The main database (Firestore), the storage of files and photographs (Cloud Storage) and the server functions operate in Google Cloud's São Paulo (southamerica-east1) region. Records, geometries, photographs, recorded tracks, the location history and the shared Emergency Card do not leave the national territory in normal operation.
Chat and real-time tracking are in the United States. Chat messages (Expedition and direct) and, during real-time tracking, your position and the most recent stretch of the track go through the Firebase Realtime Database, which Google does not offer in Brazil: our databases on that service are in the us-central1 region, in the United States, and the server functions that handle chat also run there. The lists of Members and contacts used to control access to chat and positions are kept there too. The final track is recorded in Brazil, like the other Records. When the server ends a real-time session because the device lost contact, the real-time stretch remains in the Realtime Database until you track again in that Expedition, or until the Expedition or your account is deleted.
Some Google support services are not region-bound and may process data outside Brazil:
- Firebase Authentication — your e-mail and access credentials.
- Firebase Cloud Messaging and Apple Push Notification service — sending notifications, including the text of emergency ones.
- Crashlytics and Analytics — crash diagnostics and usage metrics.
Outside Google, there is international transfer when the device requests tiles from third parties: the base map providers and the WMS/WFS services you choose, and Amazon, for relief tiles (section 6.2). These requests carry the area queried and the IP address, never the content of the Expeditions. The drone's video and telemetry leave the local network only when shared with the team, and stay in São Paulo (section 3.10); on the bridge, the DJI SDK may send data to DJI, outside Brazil (Tairu Drone policy, section 4).
Transfers to Google occur under contractual data protection clauses compatible with art. 33 of the LGPD. Tile requests to the other providers are made to carry out what you ask for in the application (art. 33, IX, together with art. 7, V).
8. Security
What we do:
- Encryption in transit (TLS) in all communication with the servers.
- Encryption at rest on the servers, managed by the cloud provider.
- Local database encrypted with AES in the mobile and desktop applications, with the key in the operating system's secure storage.
- Mandatory authentication, with an additional application integrity check (App Check), except in the request for access to the drone video, which checks the account, the plan and membership in the Expedition.
- Access control by server rules, evaluated on every read and write, per Expedition and per role.
- Automatic backups.
- The Emergency Card lives in a document separate from the profile, readable only by the readers the server computes from your choices. It is not included in the JSON backup, in exports or in Expedition files, and none of its fields goes into diagnostic logs.
What we do not do, and you should know:
- There is no end-to-end encryption. See section 1.3.
- The security of the content of a shared Expedition also depends on the Members you admit into it. Invitations grant real access to the content.
- Local encryption of the Emergency Card protects against casual reading of the file, not against someone holding your unlocked phone. Use a screen lock.
- We do not log who opened a card. A log written by the device would miss reads without signal — exactly the ones that matter in a rescue —, and promising a control that does not work would be worse than not having it. When opening someone else's card, the application reminds you that it is only to protect someone's life or physical safety.
- Cards kept on the device stay out of the device backup: on iPhone, their folder is excluded from iCloud and computer backups; on Android, their folder is not included in the application's backup. On a new device, shared cards come back from the cloud.
- Other drone data is included in the device backup, if it is turned on: on Android, the drone photo adjustments (section 3.8), which are kept in the application's preferences; on iPhone, the stored drone photos, the adjustments, the ground images and the pairing with the bridge (section 3.9).
- On the Wi-Fi network, messages with the drone controller are signed; the video is not. None of this is encrypted (section 3.9).
No system is immune to incidents. In the event of a security incident with relevant risk to data subjects, we will notify those affected and the ANPD (Brazil's national data protection authority), within the deadlines and in the manner of art. 48 of the LGPD.
9. Retention
| Data | Period |
|---|---|
| Content of synchronized Expeditions | For as long as the account exists and the data is not deleted by you |
| Local-only content | Under your exclusive control; it disappears when the application is uninstalled |
| Registration data and profile | For as long as the account exists |
| Data after account deletion | Removed from active systems within 30 days; purged from backups within 130 days |
| Application access logs | 6 months, as required by art. 15 of the Marco Civil da Internet |
| Tax and subscription records | 5 years, as required by tax legislation and the Consumer Protection Code (CDC) |
| Crash diagnostics and usage metrics | Up to 14 months, according to the provider's standard retention |
| Emergency Card on your device | Until you tap Delete my card or uninstall the application |
| Emergency Card in the cloud | While it is shared with at least one Expedition. Turning off the last share, deleting the card or deleting the account deletes it from the cloud — deletion, not flagging. Server backup copies expire within 130 days |
| Copy of the card on a reader's device | Deleted when that device connects and the access no longer exists |
| Card PDF | Not kept by the application; the temporary copy left by sharing is deleted when you return to the application. A printed PDF, or one sent to another application, is under the control of whoever received it |
| Data of an emergency (section 3.7) | Same as the Expedition's content |
| Original drone photo in Quick View (section 3.8) | Until the Expedition is closed or the next time the application is opened |
| Copy of the original of an image shared with the application, saved as a layer or used as a base map (section 3.8) | Until the import ends, or an opening of the application once a day has passed, if it is closed before that |
| Drone photo adjustments and ground images (section 3.8) | On the device, per account: until account deletion on this device; the adjustments also until Clear Expedition Data or until they exceed 500; the ground images until Reset or until they exceed 200; both disappear upon uninstallation, but the device backup may bring them back (section 8) |
| Expedition thumbnail in the list, which may show the drone photos opened on the map (section 3.8) | On the device, until Clear Expedition Data |
| Relief tiles of the area photographed or flown over | In the device's map cache |
| Copies of a file shared with the application or chosen in it, made when it is received | Those of an imported image or PDF go when the import ends. The others, and those of an interrupted import, stay in the application's temporary folder until the system clears it |
| Pairing with the Tairu Drone bridge (section 3.9) | Until Forget the pairing (on the Drone page, on the Realtime plan), another account opening an Expedition on this device, or uninstallation. On iPhone, the system may keep it in the Keychain after uninstallation, and the device backup takes it to a new iPhone (section 8) |
| Installation identifier for the bridge (section 3.9) | Until the application is uninstalled. On iPhone, the system may keep it in the Keychain even after that, and it comes back on a reinstallation |
| Pilot mark on your position marker (section 3.9) | Until 30 seconds after you stop piloting, or until the Expedition is closed; without a network connection, on a restricted link or with the application terminated during the flight, until the next time your position is recorded |
| Live drone video and telemetry (section 3.9) | Not kept by Tairu Maps. The bridge keeps the 5 most recent flights and, if you turn on recording, the video (Tairu Drone policy). For sharing with the team, see the following rows |
| Drone position shared with the team (section 3.10) | Removed 30 seconds after the flight ends, or at once when the Expedition is closed. If the device stops responding, an automatic removal deletes it 1 hour after the last update; this removal may take up to a day. Whatever coincides with a database backup follows the backup period |
| Video shared with the team (section 3.10) | Not recorded: it only passes through the server's memory during the transmission |
| Flight path, with Track the drone (section 3.10) | As Expedition content |
| Video server logs: IP, Expedition and account of whoever connects (section 3.10) | Only in the server's memory, until it powers off, usually 10 minutes after the transmission ends |
| Log of who requested the video: account, Expedition and time (section 3.10) | According to the provider's default retention |
About data in shared Expeditions: when you delete your account, we remove your personal data and the Expeditions you own — including shared ones, which cease to exist for the other Members too. For one of them to stay with the team, hand ownership to another Member before deleting your account. Your real-time position stops appearing to the team. Records you created inside third-party Expeditions, the messages you sent in their chat and the history of the positions you shared in them remain with the owner of the Expedition, who is the controller of that data set — just as a document delivered to an organization does not vanish from it when its author leaves. Requests concerning those Records must be addressed to the owner of the Expedition. Likewise, direct chat conversations remain with the other participant.
10. Your rights (LGPD, art. 18)
You may request, at any time:
- Confirmation and access — to know whether we process your data and to obtain a copy of it.
- Correction of incomplete, inaccurate or outdated data.
- Anonymization, blocking or deletion of data that is unnecessary, excessive or processed in non-compliance with the law.
- Portability — the application already offers full export, with no need for a request: backup in JSON, and export to
.tairudb, KML, GPX and GeoPackage. The Emergency Card is left out of those files on purpose, so that it does not travel with map data; you can generate its PDF at any time and, if you need another format, ask at the e-mail below. - Deletion of data processed on the basis of consent.
- Information about whom we share your data with — section 6.2 answers this permanently and in an up-to-date manner; which Expeditions your Emergency Card is shared with is shown on the card's own screen.
- Information about the possibility of not consenting and the consequences of that.
- Revocation of consent.
- Drone data kept only on the device (sections 3.8 and 3.9) does not reach us: you see it and delete it directly on the device (section 9). Anyone who appears in a drone photo or video must contact whoever flew or the owner of the Expedition (section 2).
How to exercise them: write to danielhsmartin@gmail.com. We will respond within 15 days. We may ask for identity confirmation before complying, to protect your account.
If you are not satisfied with our 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).
11. Account deletion
Deletion can be requested at tairumaps.com/delete-account or through the application's settings. It removes your registration data, profile, Emergency Card, the Expeditions you own and the associated content, within the periods of section 9. Shared Expeditions you own are deleted for the other Members too; the application lists them before you confirm the deletion.
Drone data that stays only on the device (section 9) does not reach us. Account deletion erases, on the device where it is done, that account's adjustments and ground images; the copies of images, the pairing and the installation identifier are not deleted by it. They are removed as section 9 describes or upon uninstallation of the application; on the web, by clearing the site's data in the browser. If the device backup is turned on, the copy in it comes back when the backup is restored (section 8). On iPhone, the pairing and the installation identifier may remain in the Keychain even after uninstallation.
Before deleting, export whatever you want to keep. Deletion is permanent.
12. Institutional use
For agencies and organizations with their own information security requirements, we offer:
- Local mode, without any synchronization — available today, at no additional cost and with no contract. With the live drone, the layers still go to the drone controller, over the local network and unencrypted, and the bridge runs the DJI SDK (section 3.9).
- Data processing agreement / confidentiality agreement.
- Response to an information security questionnaire.
Emergency Card in assigned teams. When taking part in the Expedition follows from an assignment — public servants assigned to an operation, employees on field duty —, consent may not be free, given the imbalance of the relationship. In those cases, the organization must define, in its own rules, the legal basis and who is the controller of the card before using it. Contact us to formalize it.
Contact: danielhsmartin@gmail.com.
13. Minors
Tairu Maps is not intended for people under 18 years of age, and we do not intentionally collect data from minors. If we identify a minor's registration without a guardian's authorization, the account will be removed. Guardians who identify such a situation should contact us.
14. Local storage and similar technologies
The application uses local storage for caching, offline operation and performance; authentication tokens to keep the session; device identifiers for notifications and synchronization; and, for the drone, the photo adjustments (in the browser, in its local storage; section 3.8), the pairing with the bridge and a random installation identifier (section 3.9). The institutional website does not use advertising tracking cookies.
15. Changes to this policy
We may update this policy. Relevant changes will be communicated in the application and by e-mail, with reasonable advance notice before they take effect.
Previous versions, kept for consultation (in Portuguese): version 2.3, of October 31, 2026 · version 2.2, of October 21, 2026 · version 2.1, of October 20, 2026 · version 2.0, of September 1, 2026 · version of May 19, 2026.
Continued use after the new version takes effect implies awareness of it. When a change requires new consent, it will be requested specifically and prominently.
Languages. This policy is published in Portuguese, English and Spanish. The translations exist to make reading easier; in case of divergence between them, the Portuguese version prevails, as it is the only one entered into under Brazilian law.
16. Contact
Data Protection Officer (DPO): Daniel H. Saint Martin E-mail: danielhsmartin@gmail.com Supervisory authority: ANPD — gov.br/anpd
Tairu Maps · Developed by Daniel H. Saint Martin