Transparency alternatives to SecureSheet
Other Financial planning and close vendors we measure, sorted by how much we found at them and not at SecureSheet. This is a comparison of disclosure, not of features or fitness.
12 shown of 45 that differ from SecureSheet on at least one criterion we measured for both. Public transparency score, not a product or security rating.
SecureSheet has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at SecureSheet” is the one that closes them.
| Vendor | Score | Found there, not found at SecureSheet | Found at SecureSheet, not found there | |
|---|---|---|---|---|
| Leapfinleapfin.comSee also Transparency alternatives to Leapfin | 61/100 | 4 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 1 Certifications named | Compare |
| Venavenasolutions.comSee also Transparency alternatives to Vena | 52/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Named privacy contact | 1 Public pricing | Compare |
| Alephgetaleph.comSee also Transparency alternatives to Aleph | 39/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Named privacy contact | 3 Public pricing, Certifications named, Notice before subprocessors change | Compare |
| Martusmartussolutions.comSee also Transparency alternatives to Martus | 30/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Named privacy contact | 3 Data location stated, Public pricing, Notice before subprocessors change | Compare |
| Planfulplanful.comSee also Transparency alternatives to Planful | 30/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Named privacy contact | 3 Data location stated, Public pricing, Notice before subprocessors change | Compare |
| Anaplananaplan.comSee also Transparency alternatives to Anaplan | 26/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 3 Data location stated, Public pricing, Notice before subprocessors change | Compare |
| Pigmentpigment.comSee also Transparency alternatives to Pigment | 39/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 1 Notice before subprocessors change | Compare |
| BlackLineblackline.comSee also Transparency alternatives to BlackLine | 38/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 2 Data location stated, Public pricing | Compare |
| Cubecubesoftware.comSee also Transparency alternatives to Cube | 35/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Public pricing, Notice before subprocessors change | Compare |
| FloQastfloqast.comSee also Transparency alternatives to FloQast | 30/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Public pricing, Certifications named, Notice before subprocessors change | Compare |
| IDUidusoft.comSee also Transparency alternatives to IDU | 30/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 3 Public pricing, Certifications named, Notice before subprocessors change | Compare |
| Heluhelu.ioSee also Transparency alternatives to Helu | 26/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 3 Public pricing, Certifications named, Notice before subprocessors change | 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.