[{"data":1,"prerenderedAt":24},["ShallowReactive",2],{"site":3,"static-page-pages-privacy-en":23},{"status":4,"contentType":5,"pagination":6,"data":7},200,"application\u002Fjson; charset=utf-8",{},{"id":8,"webUrl":9,"mobileUrl":10,"name":11,"dirPath":11,"title":12,"logo":10,"company":12,"address":13,"tel":13,"fax":10,"email":14,"crod":15,"copyright":16,"seoTitle":17,"seoKeyword":18,"seoDescription":19,"sortId":20,"isDefault":8,"status":21,"domains":22},1,"https:\u002F\u002Fwww.virtuamesh.com",null,"default","VirtuaMesh","","sales@virtuamesh.com","陕ICP备16016569号-4","版权所有 © 2026 VirtuaMesh. All Rights Reserved.","VirtuaMesh - 基于 WireGuard 的零信任异地组网平台 · 企业级 Mesh VPN","VirtuaMesh,异地组网,虚拟组网,mesh VPN,WireGuard 组网,零信任网络,内网穿透,NAT 穿透,DERP 中继,虚拟局域网,企业组网,自托管 VPN,MagicDNS,ACL 访问控制,出口节点","VirtuaMesh 是基于 WireGuard 协议的零信任虚拟组网平台，提供跨地域异地组网、NAT 穿透与 DERP 中继、ACL 访问控制、MagicDNS 自动域名、出口节点共享等核心能力。支持 Windows、Linux、macOS、Android、iOS 全平台客户端，可自托管部署，数据自主可控，开箱即用。",99,0,[],"  \u003Cdiv class=\"pg pg-privacy\">\n\n    \u003Csection class=\"hero\">\n      \u003Ch1>Privacy Policy\u003C\u002Fh1>\n      \u003Cp>We understand the importance of your personal information and are committed to protecting your privacy. Please read this policy carefully to understand how we collect, use, and protect your information.\u003C\u002Fp>\n      \u003Cdiv class=\"updated\">Last updated: June 30, 2026\u003C\u002Fdiv>\n    \u003C\u002Fsection>\n\n    \u003Cdiv class=\"content\">\n      \u003Cdiv class=\"toc\">\n        \u003Cdiv class=\"toc-title\">Table of Contents\u003C\u002Fdiv>\n        \u003Col>\n          \u003Cli>\u003Ca href=\"#scope\">Scope of This Policy\u003C\u002Fa>\u003C\u002Fli>\n          \u003Cli>\u003Ca href=\"#collect\">Information We Collect\u003C\u002Fa>\u003C\u002Fli>\n          \u003Cli>\u003Ca href=\"#use\">How We Use Information\u003C\u002Fa>\u003C\u002Fli>\n          \u003Cli>\u003Ca href=\"#store\">Information Storage and Protection\u003C\u002Fa>\u003C\u002Fli>\n          \u003Cli>\u003Ca href=\"#share\">Information Sharing and Disclosure\u003C\u002Fa>\u003C\u002Fli>\n          \u003Cli>\u003Ca href=\"#traffic\">Network Traffic Statement\u003C\u002Fa>\u003C\u002Fli>\n          \u003Cli>\u003Ca href=\"#rights\">Your Rights\u003C\u002Fa>\u003C\u002Fli>\n          \u003Cli>\u003Ca href=\"#children\">Protection of Minors\u003C\u002Fa>\u003C\u002Fli>\n          \u003Cli>\u003Ca href=\"#changes\">Policy Changes\u003C\u002Fa>\u003C\u002Fli>\n          \u003Cli>\u003Ca href=\"#contact\">Contact Us\u003C\u002Fa>\u003C\u002Fli>\n        \u003C\u002Fol>\n      \u003C\u002Fdiv>\n\n      \u003Cdiv class=\"section\">\n        \u003Ch2>1. Scope of This Policy\u003C\u002Fh2>\n        \u003Cp>This Privacy Policy applies to the VirtuaMesh virtual networking software (hereinafter \"the Software\") and its associated control plane service (control.virtuamesh.com).\u003C\u002Fp>\n        \u003Cp>The Software is a private networking tool that helps enterprises establish virtual local area networks within their own infrastructure. The Software is provided as commercial closed-source software, in compliance with applicable laws and regulations regarding the operation of virtual local area networks.\u003C\u002Fp>\n        \u003Cdiv class=\"callout\">\n          \u003Cstrong>Important Notice:\u003C\u002Fstrong> VirtuaMesh positions itself as a \u003Cstrong>private software provider\u003C\u002Fstrong>, not a public network operator. All network traffic is transmitted within your own infrastructure. We do not relay, store, or analyze your business data.\n        \u003C\u002Fdiv>\n      \u003C\u002Fdiv>\n\n      \u003Cdiv class=\"section\">\n        \u003Ch2>2. Information We Collect\u003C\u002Fh2>\n        \u003Ch3>2.1 Information You Actively Provide\u003C\u002Fh3>\n        \u003Cul>\n          \u003Cli>\u003Cstrong>Network Invitation Code:\u003C\u002Fstrong> The invitation code you enter when joining a network, used to identify the virtual network to which you belong.\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Node Name:\u003C\u002Fstrong> The display name you set for this device (optional), used to identify your device in the network member list.\u003C\u002Fli>\n        \u003C\u002Ful>\n        \u003Ch3>2.2 Automatically Collected Information\u003C\u002Fh3>\n        \u003Cul>\n          \u003Cli>\u003Cstrong>Device Identifier Information:\u003C\u002Fstrong> Device hostname, operating system type and version (e.g., \"Android 14\"), and client version number, used for node display and compatibility adaptation.\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Network Endpoint Address:\u003C\u002Fstrong> Your public IP and port (NAT traversal endpoint), used to establish P2P tunnels. This information is temporarily held in control plane memory only and is not persisted to the database.\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Key Information:\u003C\u002Fstrong> WireGuard public key (used for tunnel encryption handshake), node ID, and token (used for identity authentication).\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Traffic Statistics Summary:\u003C\u002Fstrong> Cumulative sent\u002Freceived byte counts (totals only, no content), used for management console display and quota management.\u003C\u002Fli>\n        \u003C\u002Ful>\n        \u003Ch3>2.3 Information We Do Not Collect\u003C\u002Fh3>\n        \u003Cdiv class=\"callout\">\n          \u003Cstrong>Explicit Statement:\u003C\u002Fstrong> The Software \u003Cstrong>does not collect\u003C\u002Fstrong> your network communication content, browsing history, DNS query logs, application usage data, or any data involving business sensitivity.\n        \u003C\u002Fdiv>\n      \u003C\u002Fdiv>\n\n      \u003Cdiv class=\"section\">\n        \u003Ch2>3. How We Use Information\u003C\u002Fh2>\n        \u003Cp>We use the collected information only for the following purposes:\u003C\u002Fp>\n        \u003Cul>\n          \u003Cli>\u003Cstrong>Provision of Networking Services:\u003C\u002Fstrong> Assign virtual IP addresses to your devices and establish encrypted tunnels with other network members.\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Identity Authentication and Authorization:\u003C\u002Fstrong> Verify your node identity to ensure that only authorized devices can join your virtual network.\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Network Management:\u003C\u002Fstrong> Display node online status, operating system type, and traffic summaries in the management console to help network administrators monitor network health.\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Troubleshooting:\u003C\u002Fstrong> Assist in locating connection issues when you actively request technical support (only after you have explicitly authorized such assistance).\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Version Management:\u003C\u002Fstrong> Identify the client version and prompt for upgrade when the version is outdated.\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Security Protection:\u003C\u002Fstrong> Detect abnormal connection behavior and prevent unauthorized access and key abuse.\u003C\u002Fli>\n        \u003C\u002Ful>\n      \u003C\u002Fdiv>\n\n      \u003Cdiv class=\"section\">\n        \u003Ch2>4. Information Storage and Protection\u003C\u002Fh2>\n        \u003Ch3>4.1 Storage Location\u003C\u002Fh3>\n        \u003Cp>Control plane data (node information, keys, network configuration) is stored on the server where you deploy the VirtuaMesh control plane service. Client configuration (virtual IP, network key) is stored on your local device.\u003C\u002Fp>\n        \u003Cdiv class=\"callout\">\n          \u003Cstrong>Key Statement:\u003C\u002Fstrong> VirtuaMesh adopts a \u003Cstrong>private deployment\u003C\u002Fstrong> model, with the control plane deployed and managed by you. As the software provider, we \u003Cstrong>do not host\u003C\u002Fstrong> your control plane data.\n        \u003C\u002Fdiv>\n        \u003Ch3>4.2 Storage Period\u003C\u002Fh3>\n        \u003Cp>Node information is retained for the duration of the network's existence. When you actively deregister a node or a network administrator deletes a node, the relevant information will be purged from the database within 30 days (except for retained audit logs). Temporary information such as NAT endpoints is immediately removed from memory once the node goes offline.\u003C\u002Fp>\n        \u003Ch3>4.3 Security Measures\u003C\u002Fh3>\n        \u003Cul>\n          \u003Cli>\u003Cstrong>Transmission Encryption:\u003C\u002Fstrong> All communication between clients and the control plane is encrypted using TLS (HTTPS\u002FgRPC over TLS).\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Tunnel Encryption:\u003C\u002Fstrong> Inter-node data uses the WireGuard protocol, encrypted with ChaCha20-Poly1305 and AES-256-GCM.\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Key Protection:\u003C\u002Fstrong> Client private keys are stored in the device's secure storage area (Android Keystore \u002F system keychain).\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Access Control:\u003C\u002Fstrong> The control plane API uses JWT token authentication, and the management console supports role-based access control (RBAC).\u003C\u002Fli>\n        \u003C\u002Ful>\n      \u003C\u002Fdiv>\n\n      \u003Cdiv class=\"section\">\n        \u003Ch2>5. Information Sharing and Disclosure\u003C\u002Fh2>\n        \u003Cp>We will not sell your personal information to any third party. In the following circumstances, we may share necessary information:\u003C\u002Fp>\n        \u003Cul>\n          \u003Cli>\u003Cstrong>Sharing Among Network Members:\u003C\u002Fstrong> Your node information (virtual IP, public key, hostname, operating system type) will be shared with other authorized member nodes within your virtual network. This is necessary for the proper operation of the networking service.\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>DERP Relay Service:\u003C\u002Fstrong> When a P2P connection is unavailable, your encrypted traffic may be forwarded through DERP relay nodes. Relay nodes only forward encrypted data and cannot decrypt the content.\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Legal Requirements:\u003C\u002Fstrong> When explicitly required by laws and regulations or by competent government authorities in accordance with the law, we may disclose necessary information.\u003C\u002Fli>\n        \u003C\u002Ful>\n      \u003C\u002Fdiv>\n\n      \u003Cdiv class=\"section\">\n        \u003Ch2>6. Network Traffic Statement\u003C\u002Fh2>\n        \u003Cdiv class=\"callout\">\n          \u003Cstrong>Core Commitment:\u003C\u002Fstrong> VirtuaMesh \u003Cstrong>does not relay, store, or analyze\u003C\u002Fstrong> your business network traffic. All data transmission between nodes is end-to-end encrypted via WireGuard, traveling directly between nodes (P2P) or forwarded through your self-deployed DERP relay nodes.\n        \u003C\u002Fdiv>\n        \u003Cp>Specifically:\u003C\u002Fp>\n        \u003Cul>\n          \u003Cli>In P2P mode, traffic travels directly from one node to another without passing through the control plane.\u003C\u002Fli>\n          \u003Cli>In relay mode, the DERP server only forwards encrypted packets and cannot decrypt or view the content.\u003C\u002Fli>\n          \u003Cli>The control plane only records traffic statistics summaries (total byte counts) and does not record traffic content, destination addresses, or communicating parties.\u003C\u002Fli>\n          \u003Cli>The control plane is deployed by you on your own server, and all data remains entirely within your infrastructure.\u003C\u002Fli>\n        \u003C\u002Ful>\n      \u003C\u002Fdiv>\n\n      \u003Cdiv class=\"section\">\n        \u003Ch2>7. Your Rights\u003C\u002Fh2>\n        \u003Cp>In accordance with applicable laws and regulations, you have the following rights regarding your personal information:\u003C\u002Fp>\n        \u003Cul>\n          \u003Cli>\u003Cstrong>Right to Information:\u003C\u002Fstrong> You have the right to know how we collect and use your personal information (this policy fulfills that obligation).\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Right of Access:\u003C\u002Fstrong> You may view this node's information and traffic statistics through the management console.\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Right to Correction:\u003C\u002Fstrong> You may modify the node display name at any time. To correct other information, please contact your network administrator.\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Right to Deletion:\u003C\u002Fstrong> You may \"Deregister Node\" in the client settings. After deregistration, the node information will be removed from the network.\u003C\u002Fli>\n          \u003Cli>\u003Cstrong>Right to Withdraw Consent:\u003C\u002Fstrong> You may stop using the Software and deregister the node at any time, which shall be deemed as withdrawal of consent to information processing.\u003C\u002Fli>\n        \u003C\u002Ful>\n      \u003C\u002Fdiv>\n\n      \u003Cdiv class=\"section\">\n        \u003Ch2>8. Protection of Minors\u003C\u002Fh2>\n        \u003Cp>The Software is intended for enterprise and professional users and is not directed at minors under the age of 14. We do not knowingly collect personal information from minors. If you are the guardian of a minor and discover that your ward is using the Software, please contact us promptly to have the relevant information deleted.\u003C\u002Fp>\n      \u003C\u002Fdiv>\n\n      \u003Cdiv class=\"section\">\n        \u003Ch2>9. Policy Changes\u003C\u002Fh2>\n        \u003Cp>This Privacy Policy may be updated from time to time. Upon a policy change, we will publish the updated version in the management console and on this page, and update the \"Last updated\" date. In the event of material changes (such as an expansion of the scope of information collection), we will notify you through client notifications or email reminders.\u003C\u002Fp>\n        \u003Cp>Your continued use of the Software constitutes acceptance of the updated Privacy Policy. If you do not agree with the revised policy, please stop using the Software and deregister your node.\u003C\u002Fp>\n      \u003C\u002Fdiv>\n\n      \u003Cdiv class=\"section\">\n        \u003Ch2>10. Contact Us\u003C\u002Fh2>\n        \u003Cdiv class=\"contact-card\">\n          \u003Ch3>Privacy Inquiries\u003C\u002Fh3>\n          \u003Cp>If you have any questions, suggestions, or complaints regarding this Privacy Policy, please contact us via the following:\u003C\u002Fp>\n          \u003Ca href=\"mailto:support@virtuamesh.com\" class=\"btn\">Send Email\u003C\u002Fa>\n          \u003Cp style=\"margin-top: 14px; font-size: 13px\">Email: support@virtuamesh.com\u003C\u002Fp>\n        \u003C\u002Fdiv>\n      \u003C\u002Fdiv>\n    \u003C\u002Fdiv>\n  \u003C\u002Fdiv>",1792740971943]