Privacy Policy
Last Updated: July 2026
1. Zero-Cloud Local-First Promise
Your source code, file structures, and credentials never touch our servers. OrBit is designed from the ground up as a local-first system. All conflict-free replicated data types (CRDTs) and local filesystem sync updates are stored and validated directly on your host machines.
2. Analytical & Performance Telemetry
To improve sync loops and diagnose daemon memory footprints, OrBit collects limited performance telemetry. This includes client round-trip times (RTT), platform operating systems, daemon connection states, and exception crash reports. No file names, source code text, paths, or content payloads are ever captured or transmitted.
3. Telemetry Opt-Out
We fully respect your workspace privacy. You can completely opt-out of all performance metrics, analytics, and heartbeat tracking by adding an environment variable to your terminal configuration or using the switches inside the Tauri UI settings. Review our Telemetry Opt-Out guide for explicit CLI switches.
4. P2P Cryptographic Identifiers
During mesh pairing validation, cryptographic public keys are exchanged to build local-loop handshakes. These identifiers remain on your local machines and are never centralized.