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