Legal and Privacy

English | 繁體中文

Legal & Privacy

There are four legal/policy documents in the repository. This page is a plain -language map of what each one covers — the documents themselves are authoritative; this page is not a substitute for reading them.

Document	What it governs
LICENSE	Your rights (and restrictions) to the software itself — it's proprietary, all rights reserved. Also covers acceptable use, the alpha/no-warranty disclaimer, and limitation of liability.
TERMS_OF_SERVICE.md	The rules for using the software and for participating in this GitHub project (Issues, Discussions, Wiki).
PRIVACY_POLICY.md	What data the app stores locally, what's shared with a peer when you connect, and what is (and isn't) sent to the developer.
SECURITY.md	How to report a vulnerability, and what "safe use" means for a tool that opens NAT paths and tunnels traffic.

The short version

• No telemetry. The app doesn't call home. No analytics SDK, no crash reporter, no account system.
• Local storage only, for you. Your identity key and settings live in your OS's per-user app-data folder. Nothing leaves your machine unless you explicitly export a file.
• Direct to your peer, and only your peer. Connecting to someone shares your public key, NAT candidates, and — once connected — your encrypted application/game traffic, directly with them. There is no server operated by the developer in that path.
• If you host a Virtual Network, the small signaling server that helps members find each other runs on your machine, under your control — the developer has no access to it.
• It's proprietary software. You may run it, but you may not redistribute, modify, or commercially exploit it without written permission — see LICENSE §1.
• It's alpha software with no warranty. Don't rely on it for sensitive data, and don't deploy it in production — see LICENSE §4–§6.
• Acceptable use is a condition of the licence. Only use it on networks you own or are authorised to use, and never to bypass security controls — see LICENSE §2–§3.

If a summary above and the underlying document ever disagree, the document in the repository is correct — this page is maintained separately and may lag behind.