Private Route is intended to reduce an obvious direct association between the wallet funding a supported route and the wallet receiving its output. Its scope is deliberately narrower than anonymity.
The intended benefit
Where the live route offers it, the delivery structure is chosen with direct endpoint linkage in mind. The exact implementation and availability can change with assets, networks, amount, and provider conditions.
What remains public
Source and destination transaction hashes, addresses, amounts, fees, token contracts, gas, timestamps, and later wallet activity can remain observable on their chains.
What remains separate
Private Route does not establish no-KYC, no-account, no-wallet-connect, or non-custodial status. Those properties must be reviewed independently in the named provider flow.
How to verify it
Use the static explainers to understand the route, then check the live privacy status before depositing. Never assume a standard route automatically has a private counterpart.
How to read the evidence
Private Route should be checked alongside, not substituted for, asset identity, address compatibility, provider policy, custody structure, output, fees, and timing. Its claim boundary is intentionally narrow: reducing an obvious direct endpoint association where offered. The user should confirm the live status and preserve the same safety discipline used for a standard route.