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