Transparency alternatives to Blockaid
Other Crypto compliance and blockchain analytics vendors we measure, sorted by how much we found at them and not at Blockaid. This is a comparison of disclosure, not of features or fitness.
12 shown of 32 that differ from Blockaid on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Blockaid has 11 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Blockaid” is the one that closes them.
| Vendor | Score | Found there, not found at Blockaid | Found at Blockaid, not found there | |
|---|---|---|---|---|
| CoinTrackingcointracking.infoSee also Transparency alternatives to CoinTracking | 39/100 | 5 Data location stated, Public pricing, Certifications named, +2 | 1 No third-party tracking before consent | Compare |
| Notabenenotabene.idSee also Transparency alternatives to Notabene | 39/100 | 5 Data location stated, Public pricing, Certifications named, +2 | 1 No third-party tracking before consent | Compare |
| Blockpitblockpit.ioSee also Transparency alternatives to Blockpit | 35/100 | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Scorechainscorechain.comSee also Transparency alternatives to Scorechain | 35/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Ellipticelliptic.coSee also Transparency alternatives to Elliptic | 30/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| TaxBittaxbit.comSee also Transparency alternatives to TaxBit | 30/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| CoinLedgercoinledger.ioSee also Transparency alternatives to CoinLedger | 26/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Crystal Intelligencecrystalintelligence.comSee also Transparency alternatives to Crystal Intelligence | 26/100 | 3 Data processing agreement, Status page with history, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Bitwavebitwave.ioSee also Transparency alternatives to Bitwave | 22/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Chainalysischainalysis.comSee also Transparency alternatives to Chainalysis | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Ledgibleledgible.ioSee also Transparency alternatives to Ledgible | 22/100 | 3 Public pricing, Certifications named, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Request Financerequest.financeSee also Transparency alternatives to Request Finance | 22/100 | 3 Public pricing, Certifications named, HTTPS enforced with HSTS | 1 No third-party tracking before consent | 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.