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