Transparency alternatives to Join
Other Applicant tracking vendors we measure, sorted by how much we found at them and not at Join. This is a comparison of disclosure, not of features or fitness.
12 shown of 43 that differ from Join on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Join has 7 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Join” is the one that closes them.
| Vendor | Score | Found there, not found at Join | Found at Join, not found there | |
|---|---|---|---|---|
| Jobvitejobvite.comSee also Transparency alternatives to Jobvite | 83/100 | 6 Subprocessor list, Data location stated, Status page with history, +3 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| SmartRecruiterssmartrecruiters.comSee also Transparency alternatives to SmartRecruiters | 57/100 | 5 Subprocessor list, Status page with history, Certifications named, +2 | 3 Data processing agreement, security.txt (RFC 9116), Named privacy contact | Compare |
| JazzHRjazzhr.comSee also Transparency alternatives to JazzHR | 65/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Workableworkable.comSee also Transparency alternatives to Workable | 61/100 | 4 Subprocessor list, Data location stated, Status page with history, +1 | 2 Data processing agreement, security.txt (RFC 9116) | Compare |
| Bullhornbullhorn.comSee also Transparency alternatives to Bullhorn | 48/100 | 4 Subprocessor list, Status page with history, Certifications named, +1 | 3 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Leverlever.coSee also Transparency alternatives to Lever | 43/100 | 4 Subprocessor list, Status page with history, Certifications named, +1 | 4 Data processing agreement, Public pricing, security.txt (RFC 9116), +1 | Compare |
| Manatalmanatal.comSee also Transparency alternatives to Manatal | 43/100 | 3 Data location stated, Status page with history, Certifications named | 3 Data processing agreement, security.txt (RFC 9116), Named privacy contact | Compare |
| iCIMSicims.comSee also Transparency alternatives to iCIMS | 39/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 3 Data processing agreement, Public pricing, security.txt (RFC 9116) | Compare |
| Ashbyashbyhq.comSee also Transparency alternatives to Ashby | 35/100 | 3 Status page with history, Certifications named, Uptime SLA with a figure | 3 Data processing agreement, security.txt (RFC 9116), Named privacy contact | Compare |
| PrimePROprimepro.netSee also Transparency alternatives to PrimePRO | 48/100 | 2 Subprocessor list, Notice before subprocessors change | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Homerunhomerun.coSee also Transparency alternatives to Homerun | 43/100 | 2 Subprocessor list, Status page with history | 2 Data processing agreement, security.txt (RFC 9116) | Compare |
| Greenhousegreenhouse.ioSee also Transparency alternatives to Greenhouse | 22/100 | 2 Status page with history, Certifications named | 3 Data processing agreement, Public pricing, HTTPS enforced with HSTS | 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.