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