Privacy notice

Updated July 27, 2026

This notice explains the data processed by the current public beta. It does not claim completed enterprise compliance certification.

What we collect

Registration processes email, device name, device identifier, platform, requested role and verification state. Operation requires device public keys, Mesh addresses, node status, routes, exit selection, software version and aggregate traffic counters. If an iPhone or iPad user grants location access, the app derives and sends only a coarse region for the private network map; exact coordinates stay on that device.

What we do not collect

Device private keys are never uploaded. RatelMesh does not store webpage content, passwords, complete DNS browsing history or plaintext from inside WireGuard tunnels as a product feature.

Use and retention

Data is used to authorize devices, distribute network state, diagnose faults, prevent abuse and plan capacity. RatelMesh does not sell personal data, use it for cross-app tracking or third-party advertising, or share it with third parties for their own purposes. Beta records are retained while operationally necessary; no uniform automatic deletion period is promised yet.

Network Doctor active probes

Network Doctor runs only after confirmation. It may contact the configured Coordinator and Relay, configured DNS resolver, Cloudflare IPv4 and IPv6 connectivity endpoints, and a RatelMesh- or tenant-configured media probe. Those recipients may observe the source or selected EXIT public IP. A shareable report redacts probe targets and interface identifiers; RatelMesh does not persist the observed public IP.

Deletion, access and correction

Email admin@ratelmesh.com from the registered address to request account deletion, device revocation, export or correction. Requests are currently verified and handled manually.

Service locations and third parties

The control plane is currently in Tokyo. Service providers process data only to operate RatelMesh under our instructions; Cloudflare serves the website and downloads. Tenant-owned RELAY and EXIT operators are controlled by that tenant and can observe connection metadata; EXIT operators also see destination IPs, timing and volume.