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