Alternatives to Join
Other Applicant tracking vendors we measure, sorted by how much they publish that Join does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 24 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 “publishes and Join does not” is the one that closes them.
| Vendor | Score | Publishes, and Join does not | Join publishes, and they do not | |
|---|---|---|---|---|
| Jobvitejobvite.com | 85/100 | 5 Subprocessor list, Data location stated, Status page with history, +2 | 1 security.txt (RFC 9116) | Compare |
| JazzHRjazzhr.com | 65/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Workableworkable.com | 65/100 | 4 Subprocessor list, Data location stated, Status page with history, +1 | 2 Data processing agreement, security.txt (RFC 9116) | Compare |
| Ashbyashbyhq.com | 55/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 2 Data processing agreement, security.txt (RFC 9116) | Compare |
| iCIMSicims.com | 52/100 | 4 Subprocessor list, Data location stated, Certifications named, +1 | 3 Data processing agreement, Public pricing, security.txt (RFC 9116) | Compare |
| Bullhornbullhorn.com | 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.co | 43/100 | 4 Subprocessor list, Status page with history, Certifications named, +1 | 4 Data processing agreement, Public pricing, security.txt (RFC 9116), +1 | Compare |
| SmartRecruiterssmartrecruiters.com | 50/100 | 3 Subprocessor list, Status page with history, Uptime SLA with a figure | 2 Data processing agreement, security.txt (RFC 9116) | Compare |
| Manatalmanatal.com | 43/100 | 3 Data location stated, Status page with history, Certifications named | 3 Data processing agreement, security.txt (RFC 9116), Named privacy contact | Compare |
| Greenhousegreenhouse.io | 35/100 | 3 Data location stated, Status page with history, Certifications named | 3 Data processing agreement, Public pricing, HTTPS enforced with HSTS | Compare |
| Homerunhomerun.co | 43/100 | 2 Subprocessor list, Status page with history | 2 Data processing agreement, security.txt (RFC 9116) | Compare |
| Teamtailorteamtailor.com | 26/100 | 2 Status page with history, Certifications named | 3 Data processing agreement, Public pricing, 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.