The goal is not to declare an exchange safe. The goal is to create a source trail that shows what is clear, what is missing and what requires deeper review before a user, publisher or team relies on a claim.
01 Custody and asset-control clarity
Understand who controls assets, when funds can be held and what happens during a dispute.
Custody wording
Users need to know whether the platform takes custody, uses a partner, or routes through a liquidity provider.
- Terms of service
- Help-center custody page
- Partner disclosures
Refund and failed-transaction handling
Unclear refund language is a major visible risk signal when swaps, deposits or withdrawals fail.
- Refund policy
- Support article
- Transaction failure examples
02 Withdrawal, limit and settlement rules
Find the practical constraints that change the user experience after funds are committed.
Minimums, maximums and delay triggers
Hidden limits and settlement delays can change the risk profile of a transaction.
- Limits page
- Fee table
- Settlement timing notes
Manual review language
Manual review can be normal, but it must be described clearly and tied to current source pages.
- Risk review policy
- Terms update date
- Account restrictions page
03 Identity review and jurisdiction caveats
Map when additional checks, restrictions or documents may be required.
Identity-check triggers
Broad privacy marketing can mislead users if identity checks may still appear by amount, asset, region or risk review.
- KYC or account-verification page
- Restricted countries page
- Risk controls page
Geo availability
Availability often changes by jurisdiction and can invalidate generic comparison claims.
- Supported countries list
- Sanctions policy
- Terms jurisdiction section
04 Privacy-claim discipline
Separate narrow, sourced privacy statements from broad marketing claims.
Logging, retention and data-sharing disclosures
Privacy claims need operational details, not just slogans.
- Privacy policy
- Cookie or logging note
- Data processor list
Marketing claim consistency
Comparison pages should not repeat claims that official terms do not support.
- Homepage copy
- FAQ
- Terms and privacy policy comparison
05 Fees, spreads and quote transparency
Check whether the final user cost can be understood before a transaction.
Fee table and spread language
A low fee claim can be misleading if spread, network fee or partner fee is not visible.
- Fee page
- Quote screen copy
- Network-fee disclosure
Price refresh and slippage rules
Fast-moving crypto markets need clear quote-expiry and price-change language.
- Quote expiry notice
- Terms on price changes
- Order confirmation copy
06 Support, incidents and source freshness
A useful review checks whether users can resolve problems and whether claims are current.
Support path and escalation
Users need a visible way to handle stuck transactions, account review or refund questions.
- Support page
- Status page
- Escalation policy
Source trail freshness
Old or unsourced pages should not be treated as current evidence.
- Last updated date
- Versioned terms
- Official source links