Privacy Model

Processing routes

1. Local device. A local route runs on the selected device with its installed runtime and model. Confirm that route in the client; a local-looking app window is not evidence that every request stays on-device.
2. Enrolled peer. A peer route crosses a device boundary. Verify the recipient, supported transport, permissions, and connection before sharing work. Being on the same LAN does not itself establish encryption or authorization.
3. Optional hosted processing. A hosted route sends the disclosed request data to an external service. Review the provider, data handling, and consent before enabling it. Hosted inference is not on-device inference.
4. Coordination and diagnostics. Account, enrollment, discovery, heartbeat, and diagnostic traffic are distinct from inference payloads. Check the collection and retention behavior documented for your client and service; an online coordinator does not prove the peer tunnel or workload is ready.

Naming and protocol references

Device roles are Origin, Lead Device, Inference Node, and Anchor. These names describe architectural roles, not a guarantee that every client implements every role. Coordinator describes a coordination service; its exact responsibilities depend on the deployment.

MeshStack clients can use the WireGuard protocol through a supported tunnel backend. Protocol choice does not establish that a particular platform has a working backend or a successful peer handshake. WireGuard is a trademark of its owner; MeshStack is an independent THOX product.

Keys, recovery, and offline operation

Key creation, storage, backup, recovery, relay behavior, and offline operation must be checked against the installed release and deployment. Do not assume hardware-backed storage, cloud recovery, or offline peer connectivity from the product name. Follow the pairing guide and the client's specific instructions.

What we capture on this website

The website has account, inquiry, notification, and demo features with distinct data flows. Its live AI demos use external hosted processing after consent; they do not establish MeshStack client privacy or locality. Read the Privacy Policy and the relevant demo notices before submitting data. Never submit device private keys or other credentials through public forms.