_________
/````````_\ S N I F ~ e2e TLS trust for IoT
/\ , / O\ ___
| | | \__|_____/ o\ e2e TLS SNI Forwarder
| | | ``/`````\___/ e2e TLS CA Proxy
| | | . | <"""""""~~
| \___/ `` \________/ https://snif.host
\ ''' ``` /```````` (C) 2021-2026 VESvault Corp
\_________/
https://github.com/vesvault/snif
This page states the terms of the Public SNIF Relay, what it records and its subprocessors. For what SNIF is and how to run a SNIF Connector, see the SNIF home page.
Compatibility. The Public SNIF Relay's certificate authority API and relay protocol are those of the published Internet-Draft. They change by addition: new headers, fields or messages may be added, and what existing SNIF Connectors send and receive keeps working. A change that would stop an existing SNIF Connector working comes only with a new revision of the draft and a new SNIF Connector release, and is announced on the relay's status page before the relay makes it.
A device's hostname. A SNIF Connector whose certificate is a wildcard derives the device's hostname from its private key, on the device. Since version 1.01 it derives the same hostname on every platform: the container image does so, and so does the sample snif.conf (SNIF_CONN_HOSTNAME_PORTABLE=1). A connector set up before 1.01 keeps its older hostname, so that its name does not change. That older hostname depends on the platform: if its private key is moved to a platform with a different byte order or word size, the device gets a different hostname.
The relay forwards each connection by the hostname it is addressed to. It never receives the content of a connection, which stays encrypted end to end, and never receives a device's private key.
Questions about these records, and requests to see or delete them, go to snif@vesvault.com.
When use of the Public SNIF Relay ends. Whether a device stops using the Public SNIF Relay or VESvault Corp restricts its access, the device keeps its private key, which never leaves it, and the certificates it has downloaded. A device's hostname is in a domain of VESvault Corp and works only through this relay; a device that moves to another relay gets a new hostname there. The relay's records about the device are deleted on the schedule above, whatever ended its use, unless the law requires VESvault Corp to keep them longer. Until they are deleted, requests to see or delete them go to snif@vesvault.com. This paragraph does not apply if VESvault Corp discontinues the Public SNIF Relay as a whole.
The Public SNIF Relay uses three subprocessors:
Certificates. Let's Encrypt issues each device's certificate from the request the device makes, except under *.mesh.ves.world, where VESvault Corp's own certificate authority issues it. The device's private key never leaves it. Let's Encrypt's certificates, like every public certificate, are recorded in public certificate transparency logs; the mesh certificates are not.
Last updated: November 21, 2026.