Transparency alternatives to Socure
Other Fraud prevention and identity vendors we measure, sorted by how much we found at them and not at Socure. This is a comparison of disclosure, not of features or fitness.
12 shown of 47 that differ from Socure on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Socure has 6 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Socure” is the one that closes them.
| Vendor | Score | Found there, not found at Socure | Found at Socure, not found there | |
|---|---|---|---|---|
| PXL Visionpxl-vision.comSee also Transparency alternatives to PXL Vision | 43/100 | 2 Data location stated, Notice before subprocessors change | 2 Status page with history, Public pricing | Compare |
| Feedzaifeedzai.comSee also Transparency alternatives to Feedzai | 39/100 | 2 Data processing agreement, Notice before subprocessors change | 3 Status page with history, Public pricing, Certifications named | Compare |
| Wyllowyllo.aiSee also Transparency alternatives to Wyllo | 30/100 | 2 Data processing agreement, Notice before subprocessors change | 5 Status page with history, Certifications named, HTTPS enforced with HSTS, +2 | Compare |
| Truliootrulioo.comSee also Transparency alternatives to Trulioo | 26/100 | 2 Data processing agreement, Notice before subprocessors change | 5 Status page with history, Public pricing, HTTPS enforced with HSTS, +2 | Compare |
| IDnowidnow.ioSee also Transparency alternatives to IDnow | 43/100 | 1 Data location stated | 1 Public pricing | Compare |
| Vouchedvouched.idSee also Transparency alternatives to Vouched | 43/100 | 1 Data location stated | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Alloyalloy.comSee also Transparency alternatives to Alloy | 39/100 | 1 Data location stated | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Firmcheckfirmcheck.comSee also Transparency alternatives to Firmcheck | 35/100 | 1 Data processing agreement | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| iDenfyidenfy.comSee also Transparency alternatives to iDenfy | 35/100 | 1 Data location stated | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | Compare |
| InScope-AMLinscope-aml.comSee also Transparency alternatives to InScope-AML | 35/100 | 1 Data location stated | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| Yotiyoti.comSee also Transparency alternatives to Yoti | 35/100 | 1 Data location stated | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| ComplyAdvantagecomplyadvantage.comSee also Transparency alternatives to ComplyAdvantage | 30/100 | 1 Notice before subprocessors change | 3 Status page with history, Certifications named, security.txt (RFC 9116) | 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.