Alternatives to When I Work
Other Workforce and shift management vendors we measure, sorted by how much they publish that When I Work does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 34 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 “publishes and When I Work does not” is the one that closes them.
| Vendor | Score | Publishes, and When I Work does not | When I Work publishes, and they do not | |
|---|---|---|---|---|
| Timelytimelyapp.com | 65/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 1 Status page with history | Compare |
| Deputydeputy.com | 48/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Named privacy contact | Compare |
| TimeCamptimecamp.com | 48/100 | 3 Subprocessor list, Certifications named, HTTPS enforced with HSTS | 2 Status page with history, Named privacy contact | Compare |
| Timeneyetimeneye.com | 48/100 | 3 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change | 2 Status page with history, Named privacy contact | Compare |
| 7shifts7shifts.com | 43/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change | 1 Status page with history | Compare |
| Time Doctortimedoctor.com | 43/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Data location stated, Status page with history | Compare |
| Hubstaffhubstaff.com | 39/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Data location stated | Compare |
| RescueTimerescuetime.com | 35/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Named privacy contact | Compare |
| Sonagetsona.com | 35/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 3 Data location stated, Status page with history, Public pricing | Compare |
| Kimaikimai.org | 30/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| Findmyshiftfindmyshift.com | 45/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 2 Status page with history, Named privacy contact | Compare |
| Homebasejoinhomebase.com | 43/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 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.