Private routing, identity verification, and custody describe separate properties and should never be used as interchangeable marketing claims.
Private Route
This concerns reducing an obvious source-to-destination wallet relationship where the live route supports it. Public transactions remain.
No KYC
This concerns whether a provider requests identity verification. Requirements can vary by underlying tool, route, amount, region, or eligibility controls.
Non-custodial
This concerns control of funds during the workflow. Wallet transactions, contracts, solvers, and provider deposit addresses can create different custody models.
Review each field independently
A route can have one property without the others. Sasquatch uses qualified language when provider-level evidence is incomplete.
How to read the evidence
Privacy vocabulary should be decomposed into testable questions: what is public on-chain, what a provider observes, whether identity verification can apply, who controls funds, when a wallet must connect, and which endpoint association the route changes. A responsible article answers each independently. Combining them into a single “anonymous” label creates both technical errors and misleading search claims.