SECURITY AND DATA INTEGRITY
A record is only useful
if it can be trusted
No claims about military grades. What follows is the actual shape of the architecture — identity, authentication, binding, transport, access, audit and record protection — described at the level a public website should describe it.
IN TRANSIT
Follow one record
through the chain.
What happens to an operational record between the device that produced it and the archive that keeps it.
Security / a record in transit
Architecture overviewTHE CHAIN
Seven links,
in order.
Security / architecture
Unique device identity
Every field device has its own identity. A record can be attributed to a device rather than to an anonymous sender.
Authentication
The ground system establishes which device is speaking before it accepts what the device says.
Authorization binding
Where required, an authorization is bound to the intended flight and device, rather than being a general entitlement.
Encrypted transport
Operational data is authenticated and encrypted in transit.
Role-based access control
A pilot, an operator and an authorized authority see different things. Authorization decisions are made in the backend, not in the interface.
Audit logging
Authorization failures, communication loss, tamper events and operational events are all audited.
Historical record protection
Records are retained and protected so that what is read later is what was written at the time.
Integrity principles
Identity for field devices
Unique identity per device, so attribution is possible.
Bound authorization
Authorization tied to the intended flight and device where required.
Backend authorization
Access decisions made server-side, never trusted from the client.
Audited failure
Authorization failures, communication loss and tamper events are recorded, not discarded.
Protected history
Historical records are protected against later alteration.
Visible provenance
Source, synchronization time, data age and version are shown where available.
No silent staleness
Stale airspace information is never presented as live regulatory information.
DATA TRUST
Know what
the data means.
An airspace layer without provenance is a guess with confident styling. Every layer carries where it came from, when it last synchronised, how old it now is and which version is in use.
If a source cannot be reached, the interface says so. It does not quietly keep drawing the last thing it saw as though it were current.
Airspace layer / provenance
WHAT WE DO NOT PUBLISH
Architecture, not
implementation.
This website describes what the system does. It does not publish proprietary decoder implementations, internal key management, private infrastructure, database schemas, private API endpoints, device secrets, proprietary packet structures or source code.
"Authenticated and encrypted transport" is the correct level of detail for a public page. The rest belongs in a technical conversation under the appropriate arrangements.
No real credentials, tokens, API keys, customer data or production telemetry appear anywhere on this website.
Ask the security question
properly.
If you need architectural detail beyond what a public page should carry, contact us and we will handle it through the appropriate channel.