Direct answer
Mixer privacy claims should be treated as statements that need context, not as verified outcomes. A claim may describe a design goal, marketing language, user expectation, or public risk issue. The safer analysis asks what is being claimed, what source supports it, and what the claim leaves unresolved.
Claim types
| Type | Boundary |
|---|---|
| Design claim | Describes an intended mechanism or architecture |
| Marketing claim | Describes a promise made to readers or users |
| Evidence claim | Describes what a source says can be observed |
| Legal claim | Requires qualified review and is not provided here |
Why wording matters
Privacy language can create misplaced confidence. Mixer Explained uses limitation-first phrasing so readers see uncertainty before relying on a claim.
Evidence questions
- Is the claim sourced?
- Is the claim limited by date, design, or context?
- Does the source have a commercial incentive?
- Does the page explain what remains unknown?
Safer framing
Use phrases such as privacy claim, public visibility limit, attribution limit, or source-supported statement. Avoid language that turns a privacy claim into a certain result.
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.