Transparency alternatives to IDScan.net
Other Fraud prevention and identity vendors we measure, sorted by how much they publish that IDScan.net does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 46 that differ from IDScan.net on at least one criterion we measured for both. Public transparency score, not a product or security rating.
IDScan.net has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and IDScan.net does not” is the one that closes them.
| Vendor | Score | Publishes, and IDScan.net does not | IDScan.net publishes, and they do not | |
|---|---|---|---|---|
| PXL Visionpxl-vision.com | 43/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Public pricing | Compare |
| Feedzaifeedzai.com | 39/100 | 4 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 2 Public pricing, Certifications named | Compare |
| IDnowidnow.io | 39/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 2 Public pricing, Certifications named | Compare |
| Sumsubsumsub.com | 39/100 | 4 Status page with history, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | 2 Certifications named, Named privacy contact | Compare |
| Vouchedvouched.id | 43/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 1 Certifications named | Compare |
| Alloyalloy.com | 39/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 1 Public pricing | Compare |
| Socuresocure.com | 39/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| Signifydsignifyd.com | 35/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Certifications named | Compare |
| VAARHAFT Fraud Scannervaarhaft.com | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent | 2 Public pricing, Certifications named | Compare |
| Yotiyoti.com | 35/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 2 Public pricing, Named privacy contact | Compare |
| Sardinesardine.ai | 30/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Public pricing | Compare |
| Incodeincode.com | 26/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Public pricing, 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.