VeloraMesh

Privacy

Minimum data for private networking.

VeloraMesh v1 is designed to run on your own Ubuntu control plane without requiring a public cloud account. The goal is to process only what is needed to build the tunnel, without unnecessary telemetry or ad tracking.

Last updated: May 21, 2026

Terms Install

Short summary

VeloraMesh is not a cloud VPN designed to route your network traffic through a central service. The v1 architecture is self-hosted; the control plane, edge discovery, and clients are operated in your own environment.

  • The default product philosophy is data minimization.
  • Advertising, behavioral tracking, and third-party analytics SDKs are not part of the core goal.
  • Data-plane traffic flows directly between peers over encrypted UDP tunnels.
  • Demo or self-hosted servers process only the operational data needed to make the system work.

Required technical data

Some technical data is required for a mesh VPN to work. It is used to authenticate devices, manage membership, and discover P2P endpoint candidates, not to profile users.

  • Device identity, device name, and network membership state.
  • Sessions, membership tickets, and short-lived access material.
  • Virtual IP, peer list, and policy data.
  • UDP endpoint candidates, last-seen timestamps, and limited operational connection health logs.

Data not collected by design

The VeloraMesh core is not designed to read or centrally store your personal content.

  • Files, games, RDP streams, or application payloads crossing the tunnel are not stored by the control plane.
  • Personal messages, contacts, photos, media libraries, or similar device content are not collected.
  • The website is not intended to use non-essential advertising trackers.
  • Only a language preference cookie is intended for persistent website preference storage.

Website and download logs

When you view veloramesh.com or download files, the hosting stack, web server, or security layer may create standard access logs. These should be limited to service security, debugging, and abuse prevention.

  • Standard web logs may include IP address, timestamp, request path, user-agent, and HTTP status code.
  • A language preference cookie may be used.
  • Release downloads are provided with checksum verification.

User and server operator responsibility

In self-hosted use, most operational data is processed on the server you choose. Server security, log retention, TLS certificates, firewalls, and access control are the responsibility of the environment operator.

  • Keep join secrets strong and private.
  • Remove or block unwanted devices from networks.
  • Keep server packages updated and expose only necessary firewall ports.
  • If a device is lost or unauthorized access is suspected, revoke the relevant membership.