The Privacy page in Envoy allows you to customize the privacy of your Envoy experience. Here you can connect Envoy to your own node, toggle Tor on or off, and also choose to require additional authentication to open the app.
Envoy's connection setting can be adjusted here.
For those users wanting to operate Envoy without Tor, read more about the tradeoffs here.
Envoy represents its Tor connection with the blue shield at the top of the screen:
The node Envoy connects to is the one providing the app with the current state of any connected accounts. It is the connected node's responsibility to ensure each account's transaction history is accurate and up to date. This setting allows you to switch Envoy's between the default server, ran by Foundation, or connect to your own personal node.
Once a custom node is specified, Envoy will not fall back to the default backend, even if it cannot successfully connect to the custom node. If this is the case, the Envoy shield will turn red to indicate a connection problem.
The expected URL format is
tcp://youronionaddress.onion:50001 if connecting via Tor. If connecting via clearnet or local connection, the expected format is either
ssl://yournodeIPaddress:port, depending how your node is configured.
Envoy is known to successfully connect with all popular node implementations that ship with an Electrum Server. This includes Citadel, myNode, Nodl, RaspiBlitz, RoninDojo, Start9, and Umbrel.
Since the release of Envoy v1.1.0, you can now secure access to Envoy using any of the following options: