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