Transparency alternatives to Stackfield
Other Project management vendors we measure, sorted by how much we found at them and not at Stackfield. This is a comparison of disclosure, not of features or fitness.
12 shown of 77 that differ from Stackfield on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Stackfield has 5 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, Notice before subprocessors change. The column “Found there, not found at Stackfield” is the one that closes them.
| Vendor | Score | Found there, not found at Stackfield | Found at Stackfield, not found there | |
|---|---|---|---|---|
| Airtableairtable.comSee also Transparency alternatives to Airtable | 91/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 1 No third-party tracking before consent | Compare |
| Smartsheetsmartsheet.comSee also Transparency alternatives to Smartsheet | 91/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 1 No third-party tracking before consent | Compare |
| Miromiro.comSee also Transparency alternatives to Miro | 70/100 | 4 Subprocessor list, Status page with history, Uptime SLA with a figure, +1 | 3 No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact | Compare |
| Oraora.pmSee also Transparency alternatives to Ora | 70/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 3 Certifications named, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Plutioplutio.comSee also Transparency alternatives to Plutio | 70/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 3 Certifications named, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| monday.commonday.comSee also Transparency alternatives to monday.com | 61/100 | 3 Data processing agreement, Subprocessor list, Status page with history | 3 Data location stated, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Edworkingedworking.comSee also Transparency alternatives to Edworking | 57/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 4 Data location stated, Certifications named, No third-party tracking before consent, +1 | Compare |
| Avazaavaza.comSee also Transparency alternatives to Avaza | 52/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 5 Data location stated, Certifications named, No third-party tracking before consent, +2 | Compare |
| BigTimebigtime.netSee also Transparency alternatives to BigTime | 52/100 | 3 Subprocessor list, Status page with history, Uptime SLA with a figure | 4 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), +1 | Compare |
| GanttPROganttpro.comSee also Transparency alternatives to GanttPRO | 52/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 5 Data location stated, Certifications named, No third-party tracking before consent, +2 | Compare |
| Linearlinear.appSee also Transparency alternatives to Linear | 70/100 | 2 Data processing agreement, Notice before subprocessors change | 1 Named privacy contact | Compare |
| Breezebreeze.pmSee also Transparency alternatives to Breeze | 61/100 | 2 Data processing agreement, Notice before subprocessors change | 2 No third-party tracking before consent, 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.