Transparency alternatives to Workr
Other Applicant tracking vendors we measure, sorted by how much they publish that Workr does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 43 that differ from Workr on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Workr has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Certifications named, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and Workr does not” is the one that closes them.
| Vendor | Score | Publishes, and Workr does not | Workr publishes, and they do not | |
|---|---|---|---|---|
| Jobvitejobvite.com | 83/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 1 security.txt (RFC 9116) | Compare |
| JazzHRjazzhr.com | 65/100 | 5 Data processing agreement, Data location stated, Certifications named, +2 | 1 security.txt (RFC 9116) | Compare |
| Workableworkable.com | 61/100 | 5 Subprocessor list, Data location stated, Certifications named, +2 | 1 security.txt (RFC 9116) | Compare |
| PrimePROprimepro.net | 48/100 | 5 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +2 | 1 security.txt (RFC 9116) | Compare |
| iCIMSicims.com | 39/100 | 5 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +2 | 1 security.txt (RFC 9116) | Compare |
| SmartRecruiterssmartrecruiters.com | 57/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | 1 security.txt (RFC 9116) | Compare |
| Bullhornbullhorn.com | 48/100 | 4 Subprocessor list, Certifications named, Notice before subprocessors change, +1 | 1 security.txt (RFC 9116) | Compare |
| Leverlever.co | 43/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | 1 security.txt (RFC 9116) | Compare |
| Homerunhomerun.co | 43/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Manatalmanatal.com | 43/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Joinjoin.com | 39/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Pinpointpinpointhq.com | 26/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Named privacy contact | 1 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.