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