Does a crypto mixer make transactions private?
No universal privacy result follows from the mixer label. A route may make one input-output relationship harder to establish, while the underlying ledger entries, timing, amounts, counterparties, device records, and later exchange interactions can remain available to different observers.
Privacy is therefore a bounded question: private from whom, against which signals, during what period, and with what independent evidence? The mechanism guide explains traceability; this page turns that explanation into a claim-assessment framework.
Linkability is not identity
An observer may infer that transactions are related without knowing who controls them. Conversely, an off-chain account record can identify a person even when the public transaction path is complicated.
Observer-to-signal matrix
Start with the observer instead of an absolute slogan. Each observer sees a different slice of the route, and no single row proves a complete identity or transaction history.
Public-ledger observer
May inspect: addresses, token contracts, amounts, timestamps, transaction structure, and confirmations.
Cannot establish alone: the person controlling every address or all off-chain records.
Exchange or custodian
May inspect: account records, deposit and withdrawal history, screening results, and linked identifiers.
Cannot establish alone: control of every external address or another service's internal handling.
Route operator
May inspect: incoming and outgoing instructions, timing, support records, and data described by its current policy.
Cannot be assumed: collection and deletion behavior without dated, route-specific evidence.
Network or device observer
May inspect: connection metadata, session behavior, device signals, or traffic patterns within its scope.
Cannot establish alone: the purpose of a transfer or every event outside that observation point.
Counterparty
May inspect: its own messages, invoices, addresses, amounts, and settlement records.
Cannot establish alone: the complete route before or after its direct interaction.
Later analyst
May inspect: preserved ledger history plus future labels, clustering methods, or lawfully obtained records.
Cannot be ruled out: by a claim based only on what is linkable today.
Stablecoin public-ledger checklist
USDT, USDC, and other stablecoins can exist as different token-contract-network combinations. A privacy statement about one route cannot be transferred to another combination by ticker alone.
- 01
Name the exact asset
Record the token contract and network, not only the ticker or logo.
- 02
Inspect the visible history
Note which addresses, amounts, timestamps, and contract events remain public.
- 03
Map off-chain observers
List exchanges, custodians, route operators, support systems, and counterparties that may hold separate records.
- 04
Keep attribution separate
Distinguish a transaction relationship, an address cluster, and evidence that identifies a person.
Privacy claim worksheet
A defensible claim names its scope and limitation. If any field is missing, leave the privacy outcome unresolved.
- Observer
- Who is the claim supposed to protect against: a public-ledger analyst, operator, exchange, counterparty, or network observer?
- Signal
- Which exact relationship becomes harder to establish, and which ledger or off-chain signals remain?
- Time boundary
- Is the claim limited to current methods, or does it incorrectly imply protection against future attribution?
- Evidence
- Which dated method, policy, technical record, or independent analysis supports the narrow statement?
Harder to link directly
Names the relationship, observer, mechanism, and residual signals.
Privacy enhanced
Requires a threat model, evidence, time boundary, and stated limitations.
Anonymous or untraceable
Absolute language exceeds the evidence and ignores other observers and future analysis.
What this assessment cannot prove
It cannot establish that an operator follows its policy, that no undisclosed records exist, that a particular transfer will resist attribution, or that use is lawful in a specific situation. Churn Money has not tested a route or verified any operator's collection, retention, screening, or deletion behavior.
Use the observer matrix before comparing an operator's privacy language.
Start mixing