Privacy Model

Invariants

1. Coordinator never sees plaintext. Weights, prompts, activations, KV cache, agent state, and files never leave the mesh in plaintext.
2. Keys live on devices. WireGuard private keys are device-local. There is no cloud key custody, no cloud key backup, and no THOX-mediated recovery.
3. Off-LAN traffic is ciphertext. Off-LAN relay carries encrypted traffic only. Relay and cellular behavior is disclosed before you turn it on.
4. Works offline on LAN. After pairing, the mesh runs offline on your LAN. The Coordinator is used for first-time pairing and registry lookups.

Naming and protocol references

Device roles are Origin, Lead Device, Inference Node, and Anchor. Coordinator refers strictly to the cloud control-plane service used for first-time pairing and registry — never a device role.

MeshStack uses the WireGuard protocol. We are not WireGuard, and MeshStack is not a WireGuard product. The mark WireGuard belongs to its owner; we reference it on first use, then describe behavior in our own terms.

What we capture on this website

The marketing site collects only the email and platform interest a visitor submits. The IP address is hashed before storage. No identity, key material, or inference data is ever transmitted to the website.