Private and regular swaps share the same safety checks, but a privacy-focused route adds direct wallet association to the route-selection criteria.
What both routes must verify
Users still need the exact assets, contracts, source and destination networks, receiving address, provider, output, fees, minimum received, and quote window. Privacy does not excuse operational verification.
What the private route changes
Where available, the route is structured to reduce an obvious relationship between the funding and receiving wallets. It does not remove the two chains’ records or guarantee a particular custody or identity model.
Trade-offs are route-specific
Output, fees, timing, wallet requirements, and provider availability can differ. There is no responsible global claim that one route is always faster, cheaper, or more private in every condition.
Choosing from live evidence
Compare the live options and read the privacy status shown for that quote. Use the canonical private and regular route pages to understand the assets and networks before depositing.
How to read the evidence
Read a private-swap claim as a statement about one route property, not as a conclusion about the user, provider, or complete transaction history. Compare the standard and privacy-focused route descriptions, identify both public endpoints, and check the live quote for current support. A defensible conclusion names the exact association the route may reduce and separately lists the records, provider requirements, and later wallet behaviors it cannot control.