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