Data Sovereignty // Telemetry
DaemonCore operates on a strict zero-telemetry, air-gap architecture. We believe that security training platforms should not become supply-chain risks. This page explicitly details the boundaries of our data collection and our local-first execution model.
Air-Gap Architecture
Mission OS and FieldOps Pro are compiled to run entirely offline. Once the application binary and its associated rule packs are downloaded, the platform can be deployed in completely disconnected, air-gapped environments.
Zero Cloud Telemetry
DaemonCore strictly prohibits automated diagnostic, usage, or behavioral telemetry. We do not track which ranges you run, the commands you execute in the Tradecraft Lab, or your organizational IP.
Local Execution
All validations, vulnerability simulations, and CVSS generation occurs locally on the CPU. The application relies on its internal WASM engine for complex cryptography and logic, ensuring nothing is offloaded to a server.
Pack Registry Sync
The only network connections made by the client are explicit pull requests to the DaemonCore Pack Registry for updates. This connection only transmits a version delta check and can be disabled via the system proxy settings.
Egress Sandboxing
The Egress Tester and C2 labs explicitly declare their outbound targets before execution. No latent connections are established. Operators have full visibility into the sockets bound by the application.
Terms of Engagement
By downloading and running FieldOps Pro or Mission OS, operators agree that they have explicit authorization to deploy these simulation and testing tools within their target environments. DaemonCore provides the tooling; the operator assumes the liability.
For questions regarding data sovereignty in specialized DOD or government environments, please review the DCCO-1 Framework Guide.