Criterion · method version 1.2.0
Privacy and data
What this criterion measures in each category, from method version 1.2.0.
Criterion id: privacy · from release method-v1.2.0
What it measures
In Exchanges and brokers
What the platform collects about its customers and what it does with it. Evidence: the scope of identity checks (KYC) beyond what the law requires for the service, the data use and sharing described in the privacy policy (analytics, advertising, data sale), the retention periods, and the jurisdiction where customer data is stored and processed.
In Hardware wallets
How much the device and its companion software reveal about the user. Evidence: telemetry and whether it is off by default or can be disabled, how addresses are handled (reuse, which servers learn them), whether the user can connect to their own node, and which network connections the software makes, from documentation, privacy policies and WhatTheChain's own traffic tests.
In Mobile wallets
How much the app reveals about the user. Evidence: identity checks required to use the app, telemetry and analytics and whether they can be disabled, how addresses are handled (reuse, which servers learn them), whether the user can connect to their own node, and which network connections the app makes, from documentation, privacy policies and WhatTheChain's own traffic tests.
In On-ramps
What the service collects about its customers and what it does with it. Evidence: the scope of identity checks per amount (KYC), the data use and sharing described in the privacy policy, the payment data passed to third parties, and the jurisdiction where customer data is stored and processed.
How the score is built
The sub-criteria an assessor notes on the way to the score. They are not published as scores of their own.
In Exchanges and brokers
Assessors note sub-scores as whole numbers from 0 to 100.
- Scope of KYC
- Which identity data and documents are required, and whether more is collected than the service needs by law.
- Data use
- Uses and sharing of customer data named in the privacy policy, and whether they can be refused.
- Data jurisdiction
- Where customer data is stored and processed, and under which law.
In Hardware wallets
Assessors note sub-scores as whole numbers from 0 to 100.
- Telemetry
- Data sent to the maker or third parties, its default, and opt-out.
- Address handling
- Fresh addresses per receipt, and which servers learn the user's addresses and balances.
- Network connections
- Connections the software makes, and support for the user's own node or Tor.
In Mobile wallets
Assessors note sub-scores as whole numbers from 0 to 100.
- Telemetry
- Data sent to the provider or third parties, its default, and opt-out.
- Address handling
- Fresh addresses per receipt, and which servers learn the user's addresses and balances.
- Network connections
- Connections the app makes, and support for the user's own node or Tor.
In On-ramps
Assessors note sub-scores as whole numbers from 0 to 100.
- Scope of KYC
- Which identity data is required per amount, and whether more is collected than the law requires.
- Data use
- Uses and sharing of customer and payment data named in the privacy policy.
- Data jurisdiction
- Where customer data is stored and processed, and under which law.
Evidence and confidence
Every score of this criterion cites evidence items with their sources, and carries one of four confidence labels.
- high
- Primary sources checked at the assessment date, confirmed by a WhatTheChain test or a second independent source.
- medium
- Primary sources that could not be confirmed independently, or some older than the last scheduled review.
- low
- Only secondary sources, or sources that conflict; the rationale explains which one the value follows.
- estimate
- No direct source: derived from documented properties and comparable designs, and the rationale says how.