Transparency alternatives to BigTime
Other Project management vendors we measure, sorted by how much they publish that BigTime does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 65 that differ from BigTime on at least one criterion we measured for both. Public transparency score, not a product or security rating.
BigTime has 6 gaps in what we could measure: Data processing agreement, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and BigTime does not” is the one that closes them.
| Vendor | Score | Publishes, and BigTime does not | BigTime publishes, and they do not | |
|---|---|---|---|---|
| Airtableairtable.com | 91/100 | 5 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +2 | nothing | Compare |
| Smartsheetsmartsheet.com | 91/100 | 5 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +2 | nothing | Compare |
| Linearlinear.app | 70/100 | 5 Data processing agreement, HTTPS enforced with HSTS, No third-party tracking before consent, +2 | 3 Subprocessor list, Status page with history, Uptime SLA with a figure | Compare |
| OpenProjectopenproject.org | 61/100 | 5 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +2 | 4 Subprocessor list, Status page with history, Certifications named, +1 | Compare |
| Oraora.pm | 70/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 3 Status page with history, Certifications named, Uptime SLA with a figure | Compare |
| Breezebreeze.pm | 61/100 | 4 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 3 Subprocessor list, Status page with history, Uptime SLA with a figure | Compare |
| Teamworkteamwork.com | 57/100 | 4 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 3 Subprocessor list, Public pricing, Uptime SLA with a figure | Compare |
| Stackfieldstackfield.com | 52/100 | 4 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), +1 | 3 Subprocessor list, Status page with history, Uptime SLA with a figure | Compare |
| Miromiro.com | 74/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change | nothing | Compare |
| monday.commonday.com | 61/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Named privacy contact | 2 Data location stated, Uptime SLA with a figure | Compare |
| ClickUpclickup.com | 58/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change | 1 Status page with history | Compare |
| MeisterTaskmeistertask.com | 43/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 3 Subprocessor list, Status page with history, Uptime SLA with a figure | 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.