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