Alternatives to First Advantage
Other Background screening vendors we measure, sorted by how much they publish that First Advantage does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 25 that differ from First Advantage on at least one criterion we measured for both. Public transparency score, not a product or security rating.
First Advantage has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and First Advantage does not” is the one that closes them.
| Vendor | Score | Publishes, and First Advantage does not | First Advantage publishes, and they do not | |
|---|---|---|---|---|
| Xrefxref.com | 70/100 | 6 Subprocessor list, Status page with history, Public pricing, +3 | 1 security.txt (RFC 9116) | Compare |
| Zinczincwork.com | 52/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 1 security.txt (RFC 9116) | Compare |
| GoodHiregoodhire.com | 48/100 | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | 1 security.txt (RFC 9116) | Compare |
| Trueworktruework.com | 48/100 | 3 Subprocessor list, Status page with history, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Certncertn.co | 43/100 | 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Asurintasurint.com | 35/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Checkrcheckr.com | 26/100 | 3 Public pricing, HTTPS enforced with HSTS, Notice before subprocessors change | 3 Data location stated, Certifications named, security.txt (RFC 9116) | Compare |
| Verified Firstverifiedfirst.com | 35/100 | 2 Public pricing, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| AuthBridgeauthbridge.com | 26/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Crimcheckcrimcheck.net | 26/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Cisivecisive.com | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Data location stated, Certifications named, security.txt (RFC 9116) | Compare |
| IDfyidfy.com | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Data location stated, Certifications named, security.txt (RFC 9116) | 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.