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