Transparency alternatives to Ravelin
Other Fraud prevention and identity vendors we measure, sorted by how much we found at them and not at Ravelin. This is a comparison of disclosure, not of features or fitness.
12 shown of 46 that differ from Ravelin on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Ravelin has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Certifications named, 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 Ravelin” is the one that closes them.
| Vendor | Score | Found there, not found at Ravelin | Found at Ravelin, not found there | |
|---|---|---|---|---|
| Socuresocure.comSee also Transparency alternatives to Socure | 39/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 1 Data location stated | Compare |
| Veriffveriff.comSee also Transparency alternatives to Veriff | 35/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| IDnowidnow.ioSee also Transparency alternatives to IDnow | 43/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | nothing | Compare |
| PXL Visionpxl-vision.comSee also Transparency alternatives to PXL Vision | 43/100 | 3 Certifications named, HTTPS enforced with HSTS, Notice before subprocessors change | nothing | Compare |
| Vouchedvouched.idSee also Transparency alternatives to Vouched | 43/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Alloyalloy.comSee also Transparency alternatives to Alloy | 39/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Feedzaifeedzai.comSee also Transparency alternatives to Feedzai | 39/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 1 Data location stated | Compare |
| Sumsubsumsub.comSee also Transparency alternatives to Sumsub | 37/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Firmcheckfirmcheck.comSee also Transparency alternatives to Firmcheck | 35/100 | 3 Data processing agreement, Public pricing, HTTPS enforced with HSTS | 2 Data location stated, security.txt (RFC 9116) | Compare |
| iDenfyidenfy.comSee also Transparency alternatives to iDenfy | 35/100 | 3 Public pricing, Certifications named, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Signifydsignifyd.comSee also Transparency alternatives to Signifyd | 35/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Yotiyoti.comSee also Transparency alternatives to Yoti | 35/100 | 3 Status page with history, Certifications named, 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.