ZENO / PRIVACY
Privacy policy
Last updated: October 27, 2026
1. Scope and service operator
This policy explains how the Zeno website, dashboard, clients and supporting services handle information. “We” means the Zeno service maintenance team. Processing depends on your platform, enabled features and service deployment. If you use a separately operated signaling service or peer, that operator is responsible for its own processing.
2. Information stored on your device
To restore your preferences and connections, the dashboard stores settings such as language, daemon host addresses, saved host access passwords and the selected host in browser or operating-system storage. Native clients and daemons also store device identity and network configurations on the device. Access to the device, browser profile or backups can affect the security of this data.
3. Signaling and configuration synchronization
The signaling service registers a device using its signing public key and Peer ID, and records registration and last-active times. Depending on the client, it also receives app or daemon version, operating system and version, public IP or connection-candidate addresses and reachability information. Peer connection candidates may be shared with connection partners or nodes assisting connectivity probes. Daemon configurations submitted for synchronization, including peer IDs, listener and target addresses, forwarding rules and virtual-network settings, are stored by the signaling service so they can be restored.
4. Traffic and system permissions
Proxy, forwarding and private networking process traffic according to the peers, listeners, targets and routes you configure. SOCKS5 is an application access method for Proxy. Exit peers, gateways and destination services process the traffic needed to provide the selected connection; their visibility depends on the application protocol and its encryption. Choose peers you trust and use the destination service’s own authentication and transport protection.
On supported mobile platforms, Zeno uses the system VPN or network-extension capability to create a local tunnel and apply your network configurations. The operating system requests permission when needed. You can disconnect Zeno or revoke the permission in system settings; the corresponding networking features will then stop working.
5. Diagnostics and website delivery
Clients, daemons and services may produce operational logs containing connection states, peer identifiers, addresses, ports, timestamps and errors for troubleshooting and reliability. Information you voluntarily send to support is processed to investigate your request. Visiting the website or dashboard, downloading resources or checking for updates also sends normal web-request information to the hosting or CDN provider, such as IP address, requested resource, request time and browser or client information. The current public website and dashboard use Cloudflare for delivery.
6. Recipients and third-party services
Information is processed by the Zeno service team, the infrastructure providers involved in delivering the service, and the peers or target services required by your configuration. Using a support community shares the information you choose to send with that platform and, for group messages, other members. External services apply their own policies. Any disclosure required by applicable legal obligations is handled within the scope of those obligations.
7. Retention and your choices
Manage local settings through the dashboard, browser site-data controls or your operating system. Server-side node registrations and synchronized configurations are retained to maintain node identity and restore configuration; disconnecting or uninstalling a client does not automatically delete these records. Log retention depends on the deployment’s rotation and storage settings. Contact support to ask about access, correction or deletion of server-side information. We will verify the relationship to the relevant node and explain the processing scope and any information that must be retained.
8. Protecting your configuration
Protect your host access passwords, private keys and device access. Only configure peers, services and network resources you are authorized to use. Network and device protections reduce risks but cannot guarantee that every transmission or storage environment is free from unauthorized access. If you suspect a credential has been exposed, restrict the affected access and contact support with a redacted description.
9. Contact and policy updates
We update this policy when relevant features or processing practices change. The date on this page identifies the current revision. For questions about this policy or requests concerning your information, contact the Zeno team through the support center. Ask for an appropriate private channel before sharing personal information or evidence of node ownership.