Privacy policy.
Orange is a fully local, offline-first private network management tool built with Rust. It does not collect, transmit, or store any of your data on external servers. This policy explains exactly what that means in practice.
- All configuration data stored locally on your device.
- No analytics, telemetry, or crash reporting sent to us.
- No cloud sync, no Orange-run servers, and no hosted mesh — you supply the infrastructure.
- No third-party trackers, advertising SDKs, or data brokers.
- Network connections, routing rules, and DNS settings stay entirely under your control.
01Data storage
All your data — including network configurations, WireGuard tunnels, HTTPS gateway settings, DNS rules, routing policies, and Fake-IP mappings — is stored exclusively on your local device. Orange does not provide any cloud synchronization, remote backup, or account system. Your data never leaves your device through Orange itself.
02Network connections
Orange is a private network management tool that helps you bridge home, office, and cloud networks. However, Orange itself does not operate any internet services, relay servers, or proxy infrastructure. All network connections — including WireGuard tunnels, HTTPS, Trojan and Shadowsocks upstreams, SOCKS5 proxies, TUN gateway traffic, and DNS queries (UDP/TCP/DoT/DoH) — are established directly between your device and the endpoints you configure. Orange simply manages and orchestrates these connections locally.
03Mesh and self-hosted infrastructure
Orange’s mesh runs entirely on infrastructure you provide. The control and relay server, orange-mesh-server, is a free binary you deploy and operate yourself — there is no Orange-hosted control plane, no Orange account, and no hidden cloud endpoint the client can fall back to. If your own server is unreachable, the client reports an error rather than quietly switching to something we run.
Your node’s identity key, mesh state, and — on a control node — the database of members, names and addresses are stored locally, under the same protection as the rest of your configuration. Traffic between peers is encrypted end to end with WireGuard. When a direct path can’t be established and traffic falls back to your relay, that relay forwards sealed packets and cannot decrypt them, because it never holds the session keys.
04Local diagnostics
To make network behaviour explainable, Orange produces diagnostic data on your device: log files, Prometheus-style metrics, and per-request traces recording things like which rule matched and how a name resolved. We would rather describe this accurately than claim a blanket “zero logs” policy.
None of it is uploaded, and none of it is visible to us. Traces are disabled or subscriber-driven by default, so nothing is retained unless you are actively watching. Log files are written only when you configure a log path, are capped in size, and are compacted in place rather than growing without limit. The admin interface that exposes this data binds to a loopback address only and requires a token you generate yourself.
05Default outbound endpoints
Two things Orange contacts are chosen by default rather than by you. We would rather list them here than have you find them in a packet capture.
Bootstrap DNS. Before any tunnel exists, Orange has to resolve the names of your own infrastructure — proxy servers, DoH/DoT providers, WireGuard and mesh endpoints. Those lookups go to a small set of public resolvers by default: Cloudflare (1.1.1.1) and Google (8.8.8.8), together with their IPv6 addresses. Only the hostnames you configured are ever looked up this way, and you can replace the entire list with your router or any resolver you trust.
Upstream health probing. If you switch on health checks for proxy upstreams, the default probe target is a Google endpoint that answers with an empty response (www.gstatic.com/generate_204). It is off unless you enable it, carries no identifying information, and can be pointed anywhere you like.
Nothing else reaches out on its own. Rule datasets are downloaded only from URLs you list yourself, and there is no update check, licence call-home, or crash upload.
06What we don't collect
We do not collect any form of personal data, usage analytics, crash reports, or telemetry. There are no third-party trackers, advertising SDKs, or data brokers integrated into Orange. We have no visibility into how you use the app, what network configurations you create, which DNS rules you set, or what traffic flows through your private network.
07Your control
Since all data resides on your device, you have complete control at all times. You can export, modify, or delete your configurations — including routing rules, DNS settings, and tunnel profiles — as you see fit. Uninstalling Orange removes all associated data from your device.
08Changes to this policy
If we make changes to this privacy policy, we will update it here with a new revision date. We encourage you to review this page periodically.