This notice covers the Flightops beta (0.2.0b1): registration, the per-device license and the usage metrics that installed builds send. The same notice is online at beta.flightops.dev/privacy. Questions and deletion requests: beta@flightops.dev.
What we keep
Registration. Your name, work email, company, team size, ROS 2 distribution, your answer about a recent failure, and whether coding agents write your robot code. We use them to run the beta and to contact you about it. Do not put confidential details in the free-text answer.
License. Each activated device is one user account on one machine. We keep a one-way fingerprint of the machine ID and the user ID (never the raw values), a hash of the device's secret, its Ubuntu, Python and ROS 2 versions, the Flightops version, the country reported by Cloudflare at activation, and when it was last seen.
Usage metrics (required during the beta). For each command: the tool and subcommand from a fixed list, whether JSON output was requested, the outcome and exit code, the duration, and for a crash the Python exception class. For license changes: the event (activated, renewed, deactivated, refused by the license check, suspended or revoked). With each batch: the Flightops version, Ubuntu version, CPU architecture, Python version, ROS 2 distribution, middleware name, whether it ran in CI, and which coding agent started it when that is detectable. Every value comes from a fixed list.
Never collected: command arguments, file or directory paths, package, node, topic, frame or parameter names, launch files, recordings, evidence, results, logs, AI prompts or answers, code, host names or user names. IP addresses are used only to limit request rates, as a keyed hash that expires within two days.
Website and service traffic. Daily counts of visits and requests to the beta website (flightops.dev), the download site and this service, and of the service's unsuccessful answers, taken from Cloudflare's analytics. They contain no IP addresses, query strings or other identifiers, and cannot be linked to you.
See what your device sends
flightops telemetry showThis prints exactly what the next sends contain. flightops telemetry status shows the queue size and the last send. The license and metrics reference explains the files on your machine.
Where it is processed
The beta service runs on Cloudflare (Workers, the D1 database and Email Service). Cloudflare processes the requests and stores the data for us. Email is sent from beta@flightops.dev.
How long we keep it
| Data | Kept |
|---|---|
| Raw metric events | 180 days |
| Daily counts without device or person identifiers, including website and service traffic | until 31 December 2027 |
| Registrations, licenses and devices | until 30 June 2027, or until you ask us to delete them |
| Email delivery records | 30 days |
| Unconfirmed registrations | 30 days after the confirmation link expires |
Deletion
Write to beta@flightops.dev from your registered address. Deletion removes your registration, license, devices and every raw event from your devices. Daily counts carry no identifiers and remain. On your machine, flightops license deactivate removes the local license and frees the device slot.