Transparency alternatives to BigTime
Other Project management vendors we measure, sorted by how much we found at them and not at BigTime. This is a comparison of disclosure, not of features or fitness.
12 shown of 76 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 “Found there, not found at BigTime” is the one that closes them.
| Vendor | Score | Found there, not found at BigTime | Found at BigTime, not found there | |
|---|---|---|---|---|
| Airtableairtable.comSee also Transparency alternatives to Airtable | 91/100 | 5 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +2 | nothing | Compare |
| Smartsheetsmartsheet.comSee also Transparency alternatives to Smartsheet | 91/100 | 5 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +2 | nothing | Compare |
| Linearlinear.appSee also Transparency alternatives to Linear | 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.orgSee also Transparency alternatives to OpenProject | 48/100 | 5 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +2 | 5 Subprocessor list, Data location stated, Status page with history, +2 | Compare |
| Oraora.pmSee also Transparency alternatives to Ora | 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 |
| Plutioplutio.comSee also Transparency alternatives to Plutio | 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.pmSee also Transparency alternatives to Breeze | 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 |
| Edworkingedworking.comSee also Transparency alternatives to Edworking | 57/100 | 4 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 4 Data location stated, Status page with history, Certifications named, +1 | Compare |
| Teamworkteamwork.comSee also Transparency alternatives to Teamwork | 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.comSee also Transparency alternatives to Stackfield | 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 |
| monday.commonday.comSee also Transparency alternatives to monday.com | 74/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Named privacy contact | 1 Uptime SLA with a figure | Compare |
| ClickUpclickup.comSee also Transparency alternatives to ClickUp | 58/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change | 1 Status page with history | 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.