Transparency alternatives to Sapia
Other Recruiting assessment vendors we measure, sorted by how much we found at them and not at Sapia. This is a comparison of disclosure, not of features or fitness.
12 shown of 41 that differ from Sapia on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Sapia has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Sapia” is the one that closes them.
| Vendor | Score | Found there, not found at Sapia | Found at Sapia, not found there | |
|---|---|---|---|---|
| Bryqbryq.comSee also Transparency alternatives to Bryq | 70/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 1 Status page with history | Compare |
| TestGorillatestgorilla.comSee also Transparency alternatives to TestGorilla | 57/100 | 5 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +2 | 2 Status page with history, Certifications named | Compare |
| Toggl Hiretoggl.comSee also Transparency alternatives to Toggl Hire | 52/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 1 Certifications named | Compare |
| Adafaceadaface.comSee also Transparency alternatives to Adaface | 48/100 | 4 Data processing agreement, Data location stated, Uptime SLA with a figure, +1 | 2 Status page with history, Certifications named | Compare |
| CodeSignalcodesignal.comSee also Transparency alternatives to CodeSignal | 48/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Certifications named | Compare |
| Predictive Indexpredictiveindex.comSee also Transparency alternatives to Predictive Index | 48/100 | 4 Subprocessor list, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Certifications named | Compare |
| Criteriacriteriacorp.comSee also Transparency alternatives to Criteria | 43/100 | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | 2 Status page with history, Public pricing | Compare |
| HireVuehirevue.comSee also Transparency alternatives to HireVue | 43/100 | 4 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change, +1 | 1 Public pricing | Compare |
| Vervoevervoe.comSee also Transparency alternatives to Vervoe | 35/100 | 4 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | 3 Status page with history, Public pricing, Certifications named | Compare |
| CoderPadcoderpad.ioSee also Transparency alternatives to CoderPad | 48/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| Qualifiedqualified.ioSee also Transparency alternatives to Qualified | 48/100 | 3 Data processing agreement, Subprocessor list, Data location stated | 2 Public pricing, Certifications named | Compare |
| Feenyxfeenyx.aiSee also Transparency alternatives to Feenyx | 39/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Named privacy contact | 1 Status page with history | 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.