Privacy Notice
This tool collects anonymous usage analytics only to understand how often it is used and which settings are common. We do not collect personal information, and you are never asked to sign in or identify yourself.
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).
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.
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.
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. The email is the only place the tool collects PII proactively (see also "Send to FlightHub 2" below); both are fully opt-in.
"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. 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.
- 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).
Operated by BZ Tracking Solution (Pty) Ltd · part of the BizTrack family. Questions: gustaff@biztrack.co.za.
‹ BACK TO TOOL · ABOUT · MANUAL