Transparency alternatives to Culture Amp
Other Performance management vendors we measure, sorted by how much we found at them and not at Culture Amp. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Culture Amp on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Culture Amp has 7 gaps in what we could measure: Data processing agreement, 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 Culture Amp” is the one that closes them.
| Vendor | Score | Found there, not found at Culture Amp | Found at Culture Amp, not found there | |
|---|---|---|---|---|
| Perdooperdoo.comSee also Transparency alternatives to Perdoo | 61/100 | 4 Data processing agreement, Public pricing, Certifications named, +1 | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Profit.coprofit.coSee also Transparency alternatives to Profit.co | 57/100 | 4 Data processing agreement, Status page with history, Certifications named, +1 | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Betterworksbetterworks.comSee also Transparency alternatives to Betterworks | 65/100 | 3 Public pricing, Certifications named, Uptime SLA with a figure | nothing | Compare |
| PerformYardperformyard.comSee also Transparency alternatives to PerformYard | 65/100 | 3 Status page with history, Public pricing, Certifications named | 1 Named privacy contact | Compare |
| Latticelattice.comSee also Transparency alternatives to Lattice | 57/100 | 3 Status page with history, Public pricing, Certifications named | 1 Data location stated | Compare |
| Nectarnectarhr.comSee also Transparency alternatives to Nectar | 48/100 | 3 Data processing agreement, Certifications named, security.txt (RFC 9116) | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Zensaizensai.comSee also Transparency alternatives to Zensai | 48/100 | 3 Data processing agreement, Status page with history, Certifications named | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | Compare |
| Leapsomeleapsome.comSee also Transparency alternatives to Leapsome | 61/100 | 2 Data processing agreement, Public pricing | 1 HTTPS enforced with HSTS | Compare |
| Kudoskudos.comSee also Transparency alternatives to Kudos | 48/100 | 2 Data processing agreement, Status page with history | 2 Subprocessor list, Notice before subprocessors change | Compare |
| WorkBoardworkboard.comSee also Transparency alternatives to WorkBoard | 48/100 | 2 Status page with history, Certifications named | 1 Data location stated | Compare |
| Small Improvementssmall-improvements.comSee also Transparency alternatives to Small Improvements | 43/100 | 2 Status page with history, Public pricing | 2 Subprocessor list, Notice before subprocessors change | Compare |
| 15Five15five.comSee also Transparency alternatives to 15Five | 39/100 | 2 Public pricing, Certifications named | 2 Subprocessor list, 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.