Alternatives to 21 Analytics
Other Crypto compliance and blockchain analytics vendors we measure, sorted by how much they publish that 21 Analytics does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from 21 Analytics on at least one criterion we measured for both. Public transparency score, not a product or security rating.
21 Analytics has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and 21 Analytics does not” is the one that closes them.
| Vendor | Score | Publishes, and 21 Analytics does not | 21 Analytics publishes, and they do not | |
|---|---|---|---|---|
| TaxBittaxbit.com | 48/100 | 3 Data location stated, Status page with history, Public pricing | 1 security.txt (RFC 9116) | Compare |
| CoinTrackingcointracking.info | 39/100 | 2 Data location stated, Public pricing | 1 security.txt (RFC 9116) | Compare |
| Notabenenotabene.id | 39/100 | 2 Data location stated, Public pricing | 1 security.txt (RFC 9116) | Compare |
| Blockpitblockpit.io | 35/100 | 2 Data location stated, Public pricing | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Chainalysischainalysis.com | 35/100 | 2 Data location stated, Status page with history | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Scorechainscorechain.com | 35/100 | 2 Data location stated, Status page with history | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Accointingaccointing.com | 30/100 | 2 Data location stated, Public pricing | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| CoinLedgercoinledger.io | 26/100 | 2 Status page with history, Public pricing | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Bitquerybitquery.io | 22/100 | 2 Data location stated, Public pricing | 4 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | Compare |
| Ellipticelliptic.co | 30/100 | 1 Data location stated | 1 security.txt (RFC 9116) | Compare |
| Integralintegral.xyz | 26/100 | 1 Data location stated | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| AnChain.AIanchain.ai | 22/100 | 1 Data location stated | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.