> ## Documentation Index
> Fetch the complete documentation index at: https://gerfaut-wallet.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Tor
> Reach a backend on a .onion address through the Tor client built into Gerfaut or the one already on your device, then test the route.
Gerfaut reaches a backend whose address ends in `.onion` through Tor, with a Tor client built in, so a hidden service works with nothing else to install. Open **Settings** > **Network** and find the `Tor` card under the backend.
## Pick which Tor Gerfaut uses
**Android**
* **`Automatic`:** Only the built-in Tor, because any app on a phone can answer on the Tor port. This is the default.
* **`System Tor`:** Only a Tor app running on the phone, such as Orbot.
* **`Built-in`:** Only the built-in Tor.
**Desktop**
* **`Automatic`:** The Tor already running on this machine if it answers, the built-in one otherwise. This is the default.
* **`System Tor`:** Only the Tor on this machine, at the `SOCKS address` you enter. Empty means `127.0.0.1:9050`. The Tor Browser listens on `9150`.
* **`Built-in`:** Only the built-in Tor.
## Test the route
**1. Point the backend at your node's .onion address**
Follow [Backend](/docs/settings/backends-and-your-own-node) and enter the `.onion` address of your node.
**2. Select Test the connection**
The built-in Tor takes up to about a minute and a half to start the first time. Meanwhile, the card counts up in steps of ten, such as `Starting the built-in Tor… 40%`.
**3. Read the result**
The card reads `Reached through the built-in Tor.` or `Reached through the system Tor.`, or says what failed. The test stops at Tor, so the next sync shows whether your node answers.
**Android**
**Desktop**
## Route other requests through Tor
With a `.onion` backend, Gerfaut sends these requests through Tor too, and never around it:
* **Update check:** It goes through Tor as soon as one of your backends is a `.onion` address. When Tor cannot be reached, Gerfaut sends nothing. The daily check never starts Tor for itself and waits for a Tor that already runs, such as the built-in one once a sync or Live started it. Until then, it tries again each time you come back to Gerfaut on Android, and at each unlock or within the hour on desktop.
* **Notifications:** The live connection goes to the backend itself, through Tor.
* **Price:** The fiat value, and the price chart on desktop, go through Tor as soon as one of your backends is a `.onion` address. When Tor cannot be reached, the price line reads `Tor is not available, so no price was asked.` Amounts then show without fiat.
* **Price widget on Android:** It never starts Tor for the price alone. While Gerfaut is closed, it fetches the price only through a Tor that already runs, such as the built-in one a sync started, or Orbot under `System Tor`. Otherwise it keeps the last price, with its date.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.