Overview
A private route may reduce an obvious connection between a sending wallet and received assets where supported. It does not make activity anonymous, invisible, or impossible to track.
Understand privacy-focused routing, its limits, and the checks to complete before depositing.
A private route may reduce an obvious connection between a sending wallet and received assets where supported. It does not make activity anonymous, invisible, or impossible to track.
1. Check whether private routing is available for the selected assets and networks. 2. Review the expected amount, fees, estimated timing, destination address, and route requirements. 3. Use the active deposit details and confirm the SQUATCH Guard checks before sending. 4. Keep the receipt and avoid publishing route details that you do not need to share.
Public blockchains can still expose addresses, amounts, timing, token movements, and contract interactions. Treat private routing as exposure reduction, not a guarantee of anonymity.
Assuming private means untraceable; Reusing an unverified destination address; Sharing a transaction receipt publicly.
Confirm the official site, selected networks, exact asset, receiving address, current quote, and any wallet prompt before sending or signing.
Save the order ID, receipt URL, source transaction hash, route, amount, networks, and timestamp. Never save or send a seed phrase or private key.
Use the Help Center for general questions or contact support with the order ID and public transaction details for a route-specific issue.