Transparency alternatives to Jetti
Other Business intelligence vendors we measure, sorted by how much they publish that Jetti does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Jetti on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Jetti has 7 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, Notice before subprocessors change, Named privacy contact. The column “publishes and Jetti does not” is the one that closes them.
| Vendor | Score | Publishes, and Jetti does not | Jetti publishes, and they do not | |
|---|---|---|---|---|
| Databoxdatabox.com | 52/100 | 3 Data processing agreement, Status page with history, Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Klipfolioklipfolio.com | 48/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Sisensesisense.com | 43/100 | 3 Subprocessor list, Status page with history, Notice before subprocessors change | 3 Data location stated, Public pricing, security.txt (RFC 9116) | Compare |
| Steepsteep.app | 43/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | Compare |
| Modemode.com | 35/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 4 Data location stated, Public pricing, Certifications named, +1 | Compare |
| Cluviocluvio.com | 48/100 | 2 Subprocessor list, Status page with history | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Countcount.co | 48/100 | 2 Status page with history, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| ThoughtSpotthoughtspot.com | 43/100 | 2 Subprocessor list, Notice before subprocessors change | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Lightdashlightdash.com | 39/100 | 2 Subprocessor list, Status page with history | 3 Data location stated, Certifications named, security.txt (RFC 9116) | Compare |
| Lookerlooker.com | 35/100 | 2 Subprocessor list, Uptime SLA with a figure | 3 Data location stated, Certifications named, security.txt (RFC 9116) | Compare |
| Growgrow.com | 26/100 | 2 Status page with history, Named privacy contact | 4 Public pricing, Certifications named, HTTPS enforced with HSTS, +1 | Compare |
| Omniomni.co | 17/100 | 2 Status page with history, Named privacy contact | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | 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.