Transparency alternatives to 21 Analytics
Other Crypto compliance and blockchain analytics vendors we measure, sorted by how much we found at them and not at 21 Analytics. This is a comparison of disclosure, not of features or fitness.
12 shown of 32 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 9 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, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at 21 Analytics” is the one that closes them.
| Vendor | Score | Found there, not found at 21 Analytics | Found at 21 Analytics, not found there | |
|---|---|---|---|---|
| CoinTrackingcointracking.infoSee also Transparency alternatives to CoinTracking | 39/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Notabenenotabene.idSee also Transparency alternatives to Notabene | 39/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Blockpitblockpit.ioSee also Transparency alternatives to Blockpit | 35/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Scorechainscorechain.comSee also Transparency alternatives to Scorechain | 35/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 2 Certifications named, security.txt (RFC 9116) | Compare |
| CoinLedgercoinledger.ioSee also Transparency alternatives to CoinLedger | 26/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Ellipticelliptic.coSee also Transparency alternatives to Elliptic | 30/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| TaxBittaxbit.comSee also Transparency alternatives to TaxBit | 30/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Crystal Intelligencecrystalintelligence.comSee also Transparency alternatives to Crystal Intelligence | 26/100 | 2 Data processing agreement, Status page with history | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Bitwavebitwave.ioSee also Transparency alternatives to Bitwave | 22/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Chainalysischainalysis.comSee also Transparency alternatives to Chainalysis | 22/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Cryptiocryptio.coSee also Transparency alternatives to Cryptio | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Ledgibleledgible.ioSee also Transparency alternatives to Ledgible | 22/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 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.