Transparency alternatives to PrimePRO
Other Applicant tracking vendors we measure, sorted by how much they publish that PrimePRO does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 43 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 “publishes and PrimePRO does not” is the one that closes them.
| Vendor | Score | Publishes, and PrimePRO does not | PrimePRO publishes, and they do not | |
|---|---|---|---|---|
| Jobvitejobvite.com | 83/100 | 5 Data location stated, Status page with history, Public pricing, +2 | 1 Named privacy contact | Compare |
| JazzHRjazzhr.com | 65/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 2 Subprocessor list, Named privacy contact | Compare |
| Workableworkable.com | 61/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| SmartRecruiterssmartrecruiters.com | 57/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 2 Data processing agreement, Named privacy contact | Compare |
| Manatalmanatal.com | 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.com | 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.com | 48/100 | 3 Status page with history, Public pricing, Certifications named | 2 Data processing agreement, HTTPS enforced with HSTS | Compare |
| Greenhousegreenhouse.io | 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 |
| Homerunhomerun.co | 43/100 | 2 Status page with history, Public pricing | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Leverlever.co | 43/100 | 2 Status page with history, Certifications named | 2 Data processing agreement, Named privacy contact | Compare |
| Joinjoin.com | 39/100 | 2 Public pricing, security.txt (RFC 9116) | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Comeetcomeet.com | 26/100 | 2 Status page with history, Public pricing | 4 Data processing agreement, Subprocessor list, Notice before subprocessors change, +1 | 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.