SOURCES / CONTROL
A source proves only what it contains.
Every finding retains product, entity, market, date and source class.
Primary records
We prioritise signed terms, regulator and court records, filings, technical documentation and reproducible observations. Dynamic first-party and regulator records used by the expert files were retrieved again on 16 August 2026; each source row exposes that date.
Provider statements
A provider page proves the provider made a claim; it does not independently prove security, solvency, scale, uptime or global licensing.
Execution evidence
A fee table or API specification defines test inputs. Only archived orders, fills, request timestamps, holds and withdrawals can support a performance finding. Pending tests are never written as observations.
People-first review depth
Each file answers a concrete route from a user's perspective: fit and non-fit, entity and custody boundary, total cost, execution or permissions, privacy, support, incidents, alternatives and what would change the conclusion. The visible HTML and machine index use the same local record.
Proof of reserves
PoR can support inclusion at a snapshot. It is not a financial-statement audit, present solvency opinion or guarantee of legal rights over assets.
Refresh cycle
Fees and restrictions are rechecked before release; terms and registrations at least quarterly; incidents and enforcement records whenever a material update appears.