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