— Trust Center
How we handle the things that matter.
Trust is the precondition for any C2 platform. The decisions below are the ones we made early so we would not have to apologize for them later: local-first architecture, open standards, hardware-agnostic by design, and a clear path toward US procurement readiness.
— Principles
Three commitments.
Local-first by default.
Flight logs, mission data, and telemetry archives live on the operator's machine. Cloud sync is optional, never required, and never the default.
Open standards over lock-in.
MAVLink 2.0 for telemetry. ArduPilot and PX4 for autopilots. No proprietary radio protocols, no vendor-exclusive hardware requirements, no formats only we can read.
Built for US procurement.
Designed from day one to be hardware-agnostic and aligned with NDAA and ASDA Section 848 sourcing requirements. The full position is on the compliance page.
— Security
What we do and do not collect.
Flight telemetry, mission data, and logs are written to local storage on the operator's machine. They are not transmitted to TacLink and not transmitted to any third party as part of the default workflow.
Pre-launch builds collect no analytics. When opt-in diagnostic telemetry ships in a future release (anonymized crash reports and feature usage), it will be off by default, clearly disclosed in the settings, and documented on this page before it lands in any build.
No flight paths, no mission content, and no location data leave the machine without explicit operator action. Cloud sync, when it ships, is opt-in and per-feature.
Transport security.
When cloud sync ships, the wire protocol will use TLS 1.3 against authenticated endpoints. There is no plaintext sync path planned at any tier.
On the aircraft side, MAVLink 2.0 message signing is supported on telemetry links where the connected hardware permits it. Signing authenticates the command channel against spoofing and replay; it does not encrypt the payload, which is consistent with how the rest of the open ecosystem treats MAVLink security.