Transparency alternatives to When I Work
Other Workforce and shift management vendors we measure, sorted by how much we found at them and not at When I Work. This is a comparison of disclosure, not of features or fitness.
12 shown of 83 that differ from When I Work on at least one criterion we measured for both. Public transparency score, not a product or security rating.
When I Work has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at When I Work” is the one that closes them.
| Vendor | Score | Found there, not found at When I Work | Found at When I Work, not found there | |
|---|---|---|---|---|
| Agendrixagendrix.comSee also Transparency alternatives to Agendrix | 70/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Timelytimelyapp.comSee also Transparency alternatives to Timely | 65/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 1 Status page with history | Compare |
| Time Doctortimedoctor.comSee also Transparency alternatives to Time Doctor | 57/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 1 Status page with history | Compare |
| actiTIMEactitime.comSee also Transparency alternatives to actiTIME | 48/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 2 Status page with history, Named privacy contact | Compare |
| Deputydeputy.comSee also Transparency alternatives to Deputy | 48/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Named privacy contact | Compare |
| DeskTimedesktime.comSee also Transparency alternatives to DeskTime | 48/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 2 Status page with history, Named privacy contact | Compare |
| TimeCamptimecamp.comSee also Transparency alternatives to TimeCamp | 48/100 | 3 Subprocessor list, Certifications named, HTTPS enforced with HSTS | 2 Status page with history, Named privacy contact | Compare |
| RotaCloudrotacloud.comSee also Transparency alternatives to RotaCloud | 43/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Data location stated, Status page with history | Compare |
| Tempotempo.ioSee also Transparency alternatives to Tempo | 43/100 | 3 Subprocessor list, Certifications named, HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | Compare |
| Hubstaffhubstaff.comSee also Transparency alternatives to Hubstaff | 39/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Data location stated | Compare |
| Meckanomeckano.comSee also Transparency alternatives to Meckano | 39/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| RescueTimerescuetime.comSee also Transparency alternatives to RescueTime | 35/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Named privacy contact | 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.