Vexaro Mesh Supplement

1. Introduction & Precedence

This Vexaro Mesh Supplement (the “Supplement”) refines and supplements the Terms of Service for Vexaro Mesh, the Product being developed to provide encrypted mesh networking and corporate VPN connectivity. Vexaro Mesh is not yet generally available: this Supplement applies once, and to the extent that, Vexaro makes Vexaro Mesh available to the Customer, and then whenever the Customer or any Authorized User uses Vexaro Mesh, in addition to the Terms of Service and the policies referenced there.

Capitalised terms used in this Supplement have the meanings given in the Definitions of the Terms of Service. In this Supplement, Vexaro, we, us, and our mean Vexaro, LLC, a limited liability company organized under the laws of the State of Delaware, USA, unless a different Vexaro contracting entity is expressly identified in your Order Form, Statement of Work, invoice, or account record.

This Supplement forms part of the agreement between the parties. If this Supplement conflicts with an Order Form, the Order Form controls. To the extent of any conflict on a matter specific to Vexaro Mesh, this Supplement prevails over the Terms of Service; in all other respects the Terms and the referenced policies continue to apply, in the order of precedence set out in the Terms of Service. Where this Supplement is silent, the Terms of Service govern.

---

2. Customer-Controlled Configuration

Vexaro Mesh builds an encrypted overlay network between the devices the Customer enrols, using the transport and tunnelling mechanisms supported by the applicable Product, plan, and deployment model. The network configuration is the Customer’s: the IP ranges and address assignments, the DNS settings, the gateways and exit nodes, the cryptographic keys, and the routes advertised across the mesh are defined, managed, and controlled by the Customer.

Accordingly, the Customer is responsible for:

• a. choosing and managing its IP ranges, DNS configuration, gateways, and routes, and for ensuring they are correct, non-conflicting, and appropriate for its environment;
• b. generating, distributing, rotating, and revoking the keys used by its devices, and for protecting them against unauthorised use; and
• c. the operation and consequences of the configuration it applies, including how traffic is routed and resolved across the mesh.

Vexaro provides the software and the connectivity service that carry out the Customer’s configuration; it does not set the Customer’s IP ranges, DNS, gateways, keys, or routes on the Customer’s behalf, except where the Customer expressly engages Vexaro to assist through a separate arrangement.

---

3. Network Authorisation & Routing

The Customer is responsible for authorising the networks it connects to Vexaro Mesh and for the routing policies it configures. Before connecting a network, device, or gateway, the Customer must have the right to connect it and to route traffic to and from it through the mesh.

The Customer determines which subnets and resources are reachable across the mesh, which devices may act as gateways, and how traffic is routed between sites and users. The Customer is responsible for ensuring that its routing policies expose only the resources it intends to expose and only to the Authorized Users it intends to reach them, and for keeping those policies aligned with its access-control requirements. Use of Vexaro Mesh remains subject to the Acceptable Use Policy, including its authorisation requirement.

---

4. No Payload Inspection

Vexaro Mesh carries the Customer’s traffic as an encrypted overlay. Vexaro does not inspect the content of Customer payload traffic carried over the mesh. Vexaro processes the connection and metadata necessary to operate the service (Section 7), but it does not read, analyse, or use the payload of the Customer’s network traffic.

The only exception is where the Customer explicitly agrees in writing that Vexaro may do so, for example in a support investigation the Customer requests in which examining specific traffic is necessary to diagnose a problem. Any such activity is limited to the scope, purpose, and duration the Customer agrees, and does not change the default position that payload traffic is not inspected. For self-hosted relays and components, payload handling follows the responsibility split in Section 6.

---

5. No Circumvention

The Customer must not use Vexaro Mesh, or any of its relays, gateways, routes, or connectivity features, to bypass, evade, or conceal a third party’s access restrictions, network policies, geographic restrictions, or terms of use, or to access any network it is not authorised to access.

This restriction reflects, and is in addition to, the Acceptable Use Policy, which prohibits circumventing controls and bypassing third-party restrictions. Vexaro Mesh is intended to connect the Customer’s own and authorised networks securely; it is not a means to reach networks or services the Customer has no right to reach. The Customer is responsible for ensuring that its use of the mesh, and its End Users’ use, stays within the networks and resources it is authorised to access.

---

6. Self-Hosted Deployment

Vexaro Mesh may be operated as a cloud service or deployed by the Customer as a Self-Hosted Deployment on the Customer’s own infrastructure (including self-hosted relay components). The allocation of responsibility differs between these models.

In a Self-Hosted Deployment, the Customer installs, operates, secures, updates, monitors, and maintains the deployment and the infrastructure on which it runs, and is responsible for its availability and for the data it holds; Vexaro is responsible for the software it provides as documented. In the cloud service, Vexaro operates the components it hosts, while the Customer remains responsible for its configuration, networks, devices, keys, and Authorized Users as described in this Supplement. The detailed division of responsibilities between Vexaro and the Customer across deployment models is set out in the Self-Hosted Responsibility Matrix.

---

7. Logs & Metadata

To operate Vexaro Mesh, Vexaro processes connection and session metadata, such as timestamps, connection duration, round-trip time, IP addresses, and relay path. This metadata is used to establish connectivity, provide failover, support the service, and maintain its security and integrity. Vexaro does not retain the payload of the Customer’s network traffic as part of this metadata (Section 4).

Session metadata is retained for a limited period and then purged, and other categories of data are retained as described, in the retention section of the Privacy Notice. The Privacy Notice is the single source for what is collected, why, and for how long it is kept; this Section identifies the categories specific to Vexaro Mesh and confirms that payload traffic is not part of the metadata Vexaro retains.

---

8. Availability & Failover

Vexaro Mesh establishes direct connections between devices where possible and uses relay and failover paths to maintain connectivity when a direct connection is not possible. Connectivity, failover, and availability depend on the Customer’s own network (its internet connectivity, devices, configuration, and the networks between the Customer and the service) and on the plan the Customer selects.

Because much of the path is outside Vexaro’s control, the quality, latency, and throughput of any individual connection are not guaranteed. The Service Availability Policy applies only as stated there: to the covered, Vexaro-operated components on the eligible plans. It expressly excludes the Customer’s own network and any Self-Hosted Deployment. The Free Plan, Trial use, and Beta features are provided without an availability commitment. Where the Customer self-hosts relay or other components, the availability of those components is the Customer’s responsibility, as described in Section 6 and the Self-Hosted Responsibility Matrix.

---

9. Contact

For questions about this Supplement or about Vexaro Mesh:

• Legal & contracting: [email protected]
• Support: [email protected]
• Privacy / data-protection contact: [email protected]
• Abuse reports: [email protected]

Contracting and notice details are provided on invoices and Order Forms.

---

This document is part of the Vexaro Legal Center.