Privacy Notice

This notice covers Flight Assist. The Grid generator collects anonymous usage analytics only to understand how often it is used and which settings are common: it does not collect personal information, and you are never asked to sign in or identify yourself there. Ops, the search and field-operations console, and company accounts (pilots, aircraft, flight plans, flight log, documents, operations packs and incident reports) keep personal information: see "Ops" and "Company accounts" below.

Grid generator: what we collect

• An anonymous device ID — a random identifier stored in your browser, plus a basic device fingerprint (browser/screen characteristics). This is not linked to your name, email, or account.
• Export metadata — when you generate a mission file: the pattern, camera, altitude, overlap, waypoint/strip counts, path length, and total search-area size.
• A coarse location centroid — the centre of your drawn area, rounded to roughly 1 km. We never store the full polygon, the precise boundary, or exact GPS coordinates.
• Approximate country and a one-way hash of your IP address (used only for rate-limiting; the raw IP is never stored and the hash cannot be reversed to your IP).

Grid generator: what we do NOT collect

• No names, emails, phone numbers, or accounts.
• No exact GPS coordinates and no full search polygons.
• No tracking across other websites; no advertising data.

Grid generator: Do Not Track

If your browser sends a Do-Not-Track (or Global Privacy Control) signal, we honour it: no device fingerprint is recorded and no export is logged. The tool still works exactly the same.

Grid generator: why we collect it

Purely to operate and improve the tool — usage volumes, popular settings, and broad geographic spread. This is a legitimate-interest processing of anonymised data under POPIA, and none of it identifies an individual.

"Request another drone" — voluntary email opt-in

If you submit the Request another drone form, we collect:

• The drone model you requested (and, if "Other", what you typed).
• The email address you provide — used only to notify you when that drone is supported.
• Optional notes you choose to add.

The email is not used for marketing, not shared with third parties, and will be deleted on request — email gustaff@biztrack.co.za. On the Grid generator, this email is the only personal information collected (see also "Send to FlightHub 2" below); both are fully opt-in. The flight-plan page, Ops and company accounts are described in their own sections below.

"Send to FlightHub 2" — your FH2 credential, your browser

If you use the optional Send to FlightHub 2 feature, the tool needs your FH2 Organization Key and FH2 API host so it can upload missions to your FH2 organisation:

• Both are stored only in this browser's localStorage on this device, alongside anything else you choose to keep on this site, such as saved operator details on the flight-plan page. On the Grid generator, they are not copied to any account on our side — there are no accounts.
• On each upload, both are sent to our server (because DJI's API does not accept browser-direct calls). They are used only for the duration of that one request, passed straight to DJI's FlightHub 2 API, and then released.
• On the Grid generator, we do not log, persist, or write the Organization Key, the API host, the uploaded KMZ bytes, or any temporary DJI upload credentials to any database, file, or third-party service.
• Anyone with access to this browser profile can read the stored key (it's in localStorage). On shared devices, tap "disconnect" in the modal to clear it.

The feature is fully opt-in. Skip it and you keep the standard anonymous flow (download .kmz + manual import in Pilot 2). A company account that links FlightHub 2 stores its organisation key encrypted; see "Company accounts" below.

Flight plan

Without signing in, the flight-plan page works entirely in your browser: the flight details you type (including names, phone numbers and email addresses) and the PDF it makes are not sent to us. If you choose to save operator details for next time, they are kept only in that browser's local storage; 'Forget saved operators' removes them.

When you are signed in to a company account, each filing you generate is also saved to that company's records (see "Company accounts" below). Name places, never people: a missing person's name or description never belongs in a flight plan.

The map has a "My location" button. If you allow it, your device's location is used only in your browser to centre the map. It is not saved or sent to us.

Maps and libraries

To show maps, pages load map tiles from the OpenStreetMap Foundation (United Kingdom and global) and satellite imagery from Esri (United States and global). Some pages load code libraries from Cloudflare (cdnjs) and unpkg. Each of these receives your device's network address, and the map providers also receive the area of the map you view. Nothing you type is sent to them.

Ops: search and field operations

Ops lets an organisation running a search or field operation coordinate its team on a live map. The organisation's operators sign in; field team members do not have accounts. They join an operation with its code and a name.

What Ops keeps

• About operators (signed in): the email address used to sign in, and which operations they run or help with.
• About the operation: its name, brief, location and timing; search areas, teams, map pins with photos and notes; messages broadcast to the team and who acknowledged them.
• About the person being searched for: if the operator enters them, a name, description and photo. The organisation running the search decides what it records about the person being searched for. Flight Assist asks it to record only what the search needs. For a missing child, that is normally given by the parent or guardian who reports them missing.
• About field team members: the name you type when you join; while the operation is active, where you are, your heading, how accurate the fix is, your phone's battery level and the track of where you have been; voice messages you record and a written transcript of each; photos and notes you add to map pins; and, if you allow notifications, a push address for your browser, or for the Flight Assist Tracker app a push token with the phone model and app version.
• About drones: if the operator links a DJI drone, its position, height, heading, camera and battery while it flies, from DJI FlightHub 2, and live video from its camera when someone opens it.

Who sees it. The operators who run the operation and the helpers they add see everything in it. Field team members see the operation's map, their team, and messages sent to them. Photos and recordings are reached only through the operation; they cannot be listed or browsed. Flight Assist staff do not open operations in the app; the people who maintain the service can reach the stored data directly, and do so only to keep it running or when the organisation asks for help.

Outside services Ops uses

• Supabase (London, United Kingdom): the database, sign-in, and storage of photos and voice recordings.
• OpenAI (United States): turns voice messages into text. Voice messages are transcribed automatically when the organisation's account has transcription switched on (it is off unless Flight Assist turns it on for that organisation). The recording is sent to OpenAI's API for that. It does not use API data to train its models.
• Anthropic (United States): only when an operator switches on the AI coordinator for that operation (it is off until switched on). It receives the operation's name and brief, the description of the person being searched for (never their name or photo), and whatever the operator writes in the brief and description, which can include health details where they matter to the search; also the names and last positions of up to 8 field team members, the map pins with their notes, the linked drones' status, and the conversation with the coordinator. It does not use API data to train its models.
• DJI FlightHub 2 and Agora: when you link your own DJI FlightHub 2 account, DJI and its video service Agora process the drone's data under your agreement with DJI. Your FlightHub 2 organisation key is kept only in your browser; it passes through our server on each request to DJI and is not stored there.
• Google Firebase Cloud Messaging, and your browser's own push service (Google, Microsoft, Apple or Mozilla, depending on the browser): to deliver alerts.
• Map tiles from Mapbox, CARTO, OpenTopoMap and OpenStreetMap, and place search from Mapbox: each receives your device's network address and the map area or place name looked up.
• Open-Meteo: weather for the operation's area; receives map coordinates only.

How long. Your live position is cleared, and the track of where you have been deleted, when the operation ends; position records are deleted after 90 days at the latest. A closed operation and everything recorded in it (members, messages, voice recordings and their transcripts, pins and photos, drone tracks, the person being searched for, and field members' push addresses) are deleted 30 days after it closes. An operator's own push address is kept until they turn alerts off or their account is closed.

Who is responsible. The organisation that runs the operation decides what is recorded and is responsible for it; Flight Assist (BZ Tracking Solution (Pty) Ltd) runs the service for it. When Flight Assist runs an operation itself, it is responsible for it.

Company accounts

Drone operators can keep their company records in Flight Assist: pilots, aircraft, flight plans, the flight log, document copies, operations packs and incident reports. The company decides what it records and is responsible for it; Flight Assist (BZ Tracking Solution (Pty) Ltd) runs the service for it as its operator.

What a company account keeps

• People with access: each member's email address, their role (admin or pilot), and how they sign in (a password, or a 6-digit code we email them).
• Company details: the company's name, UASOC and OpSpec numbers and dates, air service licence, operations phone, contact person and email, insurer and insurance dates, and how many days before expiry it wants reminders.
• Pilots: name, phone number, remote pilot certificate number and expiry, ratings, and the expiry date of their medical certificate. The medical expiry date is kept in a separate record that only that pilot and the company's admins can see.
• Aircraft: registration and call sign, make and model, colour and markings, letter of authority (UASLA) number and dates, cruise speed, endurance, mass, DJI serial number, and hours and flights before records began.
• Flight plans: each filing made while signed in: the date and times, kind of operation, pilot, aircraft, the survey area, route and other flight-plan fields, the operator phone number, and the FUA reference.
• Flight log: one line per flight: aircraft, pilot, take-off and landing times and places, battery readings, flight time, and the pilot's confirmation. Flights come in three ways: typed in by hand; automatically from DJI FlightHub 2, if the company links its FlightHub 2 organisation; or from DJI flight log files uploaded from the controller. The pilot logbook page prints a pilot's own logbook pages from their confirmed flights; it keeps your brought-forward totals and logbook edits on your device only, they are not sent to us, and they are cleared when you sign out.
• Flight paths and batteries: from an uploaded DJI flight log we keep the aircraft's path, simplified to within a few metres, and each battery's charge, voltage, temperature and capacity, to track battery health. The path is seen only by the flight's pilot and the company's admins.
• Document copies: if your company uploads them, Flight Assist keeps copies of its certificates and licences (UASOC, OpSpec, insurance, aircraft letters of authority and manuals, and each pilot's remote pilot certificate (which may show the pilot's identity number)) so they can be shown on site. They are stored privately in London and opened through links that expire after five minutes. A pilot's certificate copy is seen only by that pilot and the company's admins. If a pilot uploads it, Flight Assist also keeps a copy of their medical certificate. This is health information: it is seen only by that pilot and the company's admins, and apart from the copy itself only its expiry date is recorded. Each time someone opens it, we record who opened it and when. A replaced copy is deleted after 30 days; a record of it (type, number and dates) is kept for 5 years. If you save the Fly kit for use without signal, the copies are kept on your device until you clear them, sign out, or 3 days after the flight.
• Operations packs: if your company uses them, Flight Assist keeps an operations pack for each operation. It holds the site and airspace details, weather readings, risk assessment, the crew's names and roles, the landowner's name, telephone number and property address, the site's emergency contacts, the pre-flight checklist and the go / no-go decision, each with who confirmed it and when. For crew fitness (IMSAFE) only "fit to fly" is recorded, never the answers. Crew members who do not use Flight Assist are told this at the crew briefing.
• Incident and accident reports: what happened, when and where, the aircraft and pilot, photos, the actions taken and the SACAA report. Injuries are recorded only as a level (minor, serious, fatal) and the number of people: never the names of injured people or medical details. A report may list witnesses, with their name and phone number only, so the aviation authority can contact them; witnesses are told this when their details are taken. Reports are seen only by the person who made them and the company's admins.

Who sees what. The company's members (its admins and pilots) see its company details, pilots, aircraft, flight plans, flight log and operations packs. Only admins manage access and company details. A pilot's medical expiry date, certificate copies and flight paths are seen only by that pilot and the admins; incident reports only by their reporter and the admins. Flight Assist staff do not open company records in the service; the people who maintain it can reach the stored data directly, and do so only to keep it running or when the company asks for help. Every change to a company's records, including any made by Flight Assist staff, is recorded with who made it and when, and that record is kept for 5 years.

Where it is kept, and who else is involved.

• Supabase (London, United Kingdom): the database, sign-in, and storage of document copies and photos.
• Twilio SendGrid (United States): sends the sign-in emails (6-digit codes and password links). It receives the email address and the message.
• DJI: if the company links DJI FlightHub 2, its organisation key is stored encrypted and used only to read its drones' flight status from DJI about once a minute. To read an uploaded DJI flight log, the file is unlocked with DJI's service (China), which receives only the request to unlock it and a count of its use, not the flight details. The log is read on BizTrack's own server in South Africa. The log also records where the controller was; that is not kept. The uploaded file and its decoded copy are deleted within an hour; only the summary (including where the aircraft took off and landed), the path and the battery readings above are kept.
• Weather: to show the weather in an operations pack, your browser asks Open-Meteo for the forecast and ground height at the site (it receives the site's coordinates) and the US National Oceanic and Atmospheric Administration for the geomagnetic (Kp) index (it receives no location).

How long. Flight plans, the flight log, flight paths, battery readings, operations packs and incident reports are kept for 5 years, as Part 101 requires operators to keep flight records. Witness details are removed 12 months after a report is closed with SACAA. Pilots and aircraft that have been made inactive are deleted 5 years after they were made inactive. Replaced document copies are deleted after 30 days. A deactivated pilot's medical certificate copy is deleted after 30 days. The record of who opened a medical certificate is kept for 5 years.

Leaving. When a company closes its account, it can download all its records ("Export all records") for 90 days; then everything, including document copies and photos, is deleted. Part 101 requires the company to keep its flight records for 5 years, so it should keep that export.

Your rights. Pilots and other people in a company's records can ask the company to see or correct what it holds about them; the company can do this in Flight Assist, and we help it when asked. You can also contact us at gustaff@biztrack.co.za. You may also complain to the Information Regulator (inforeg.org.za).

---

Operated by BZ Tracking Solution (Pty) Ltd · part of the BizTrack family. Questions: gustaff@biztrack.co.za. Address and PAIA manual: biztrack.church/paia-manual.html.

‹ BACK TO TOOL  ·  ABOUT  ·  MANUAL