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