Direct answer
Privacy claims should be evaluated as claims, not accepted as outcomes. Strong language that promises absolute privacy, trace erasure, absent review, or impossible attribution needs source support, scope limits, and a clear explanation of what the claim does not prove. In sensitive contexts, safer wording explains limitations and evidence boundaries.
What it means
A claim may refer to technical design, marketing language, user perception, or legal/privacy expectations. Those are different things. This page keeps them separate so a reader does not mistake an assertion for an outcome.
Unsafe claim classes
| Risky class | Safer frame |
|---|---|
| Absolute privacy promise | Replace with: privacy claim with limits |
| Trace-erasure promise | Replace with: public visibility and attribution limits vary |
| Absent-review promise | Replace with: compliance context differs by actor and jurisdiction |
| Universal legality promise | Replace with: legal status is fact-specific and needs review |
| Monitoring-immunity promise | Replace with: risk indicators and source boundaries |
What it does not prove
Even if a privacy mechanism exists, it does not prove the absence of risk, lawful use, sanction safety, successful obfuscation, or immunity from analysis.
Evaluation checklist
- What is the exact claim?
- Who makes it?
- What evidence supports it?
- What scenario is outside its scope?
- Does the wording create a certainty claim?
Source notes
These sources support public context and terminology. They do not turn this page into legal, financial, sanctions, or compliance advice.
- FATF Virtual Assets Red Flag Indicators - Baseline taxonomy for risk indicators and public red-flag framing.
- Chainalysis cryptocurrency mixers research - Benchmark for explaining mixer typologies without service-like UX.
- Elliptic explainer on crypto mixers - Benchmark for public education and limitations.
- TRM Labs research on crypto mixers - Benchmark for sanctions and risk framing.