Privacy notice.
Last updated: 18 August 2026.
What MeshLatch processes
To operate accounts and MeshLink, MeshLatch may process account email addresses, plan and subscription status, device identifiers and names, link allocation identifiers and timestamps, viewer counts, DIRECT/EDGE/TURN path information, and aggregate transport byte counts. Security and abuse logs may also contain IP/network metadata normally provided to the service infrastructure.
What MeshLatch is not designed to inspect
MeshLatch is not designed to inspect or store the content of the local application being proxied. The admin and usage systems do not display proxied HTML or API response bodies, files, filenames, WebSocket message contents, passwords, or the content of local applications. Operational controls are based on metadata and aggregate usage, not media or content classification.
Payments and infrastructure
Payments and subscription management are handled through Stripe. MeshLatch uses Cloudflare infrastructure for web delivery, Workers, database services, signaling, the encrypted EDGE transport, and TURN relay-related functionality. When EDGE is used, proxied application traffic is carried as MeshLink-encrypted transport data through that infrastructure. Those providers may process data necessary to provide their services under their own terms and privacy practices.
Retention and controls
MeshLatch retains operational/account records only as needed to operate, secure, support, bill, and enforce the service. You can revoke MeshLink devices from the Account page. Administrative actions such as suspensions and revocations are audit logged for security and support.
Contact
For privacy questions, contact support@meshlatch.com. Do not send secrets or private MeshLink URLs by email.