Nexus Telemetry™ Fleet is operated by Liquidbinary Ltd, a company registered in Scotland (company number SC370778). For privacy questions, contact [email protected].
For your account and the console, we are the data controller. For the telemetry your fleet's devices send to your organisation's managed server, your organisation is the controller and we act as a processor on your instructions: you decide what devices to enrol, whether to record their locations, and when to delete everything.
What: your email address (verified at signup), your organisation's name, and a password hash (we use the Argon2 algorithm; we never store or see your password).
Why and lawful basis: to create and secure your account and provision your service (contractual necessity).
Retention: for the life of your account.
What: the metrics your enrolled devices report: connection performance (speeds, latency, drops), device status and software version, and, where your operators set or enable it, terminal locations. Operator actions inside your dashboard are recorded in your organisation's own audit log.
Where: on your organisation's managed fleet server, hosted with a secure cloud provider in the United Kingdom (London), in a database encrypted at rest with keys unique to your organisation. Nightly backups are encrypted on the server before upload and are unreadable without keys we hold separately.
Why and lawful basis: this is the service: processing on your organisation's instructions under our agreement with you.
Retention: telemetry is kept on retention dials your operators control. When you cancel your organisation, its data (database, encryption keys, and device-identity certificates) is erased after a grace period, and backups age out of the backup cycle. Long-dark copies do not linger: an erased organisation's backups are removed on the normal generational cycle, typically within weeks.
Your crew and users: if your fleet's terminals are used by other people (crew, guests, tenants), telling them about the monitoring your organisation operates is your responsibility as controller.
What: operational logs (connection events, errors, administrative actions) and service health metrics. By deliberate design, telemetry values, positions, tokens and key material never appear in logs at any level.
Why and lawful basis: running, securing and debugging the service (legitimate interest).
Retention: operational logs are short-lived and rotate on the server.
When a terminal has a location and you view its weather, the service requests conditions from Open-Meteo for the terminal's coarse map cell (approximately an 11 km square), never its precise position, and never with any identifier linking the cell to you or the terminal.
Map tiles are served from our own infrastructure. No map provider learns what you look at. Map data is © OpenStreetMap contributors.
The early access programme is free. When paid plans begin, payment will be handled by a payment provider (we will not receive or store card details), and this policy will be updated before anything changes.
By category, with the data each processes:
The canonical, named subprocessor list for all Nexus Telemetry products is at nexustelemetry.com/subprocessors; we update it when anything changes.
We do not sell data or share it with advertisers. Page views are counted on our own Plausible instance, which sets no cookie and stores no personal data. If a subprocessor changes, we will update this policy.
Found a vulnerability? Report it responsibly to [email protected] (subject: "Security Vulnerability Report"). Process and expectations are in the security policy. We aim to acknowledge within 2 working days.
Under UK data protection law you can ask us for access to, correction of, or deletion of your personal data; ask us to restrict or object to processing; and ask for a portable copy. Write to [email protected] and we will respond within one month. You can complain to the Information Commissioner's Office (ico.org.uk) if you believe we have mishandled your data. For telemetry processed for your organisation, direct requests to your organisation's administrator, and we will help them fulfil it.
One first-party session cookie, set when you sign in, used only to keep you signed in. Cloudflare, which fronts this console, may set a strictly necessary security cookie (__cf_bm, bot management, expires within ~30 minutes); under UK and EU rules strictly necessary cookies need no consent. No tracking or advertising cookies. See the company-wide cookie policy.
We will post changes here and note the date above. For material changes affecting your data we will email your account address before they take effect.