Transparency alternatives to Databox
Other Business intelligence vendors we measure, sorted by how much we found at them and not at Databox. This is a comparison of disclosure, not of features or fitness.
12 shown of 39 that differ from Databox on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Databox has 5 gaps in what we could measure: Subprocessor list, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Databox” is the one that closes them.
| Vendor | Score | Found there, not found at Databox | Found at Databox, not found there | |
|---|---|---|---|---|
| Sisensesisense.comSee also Transparency alternatives to Sisense | 43/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 5 Data processing agreement, Data location stated, Public pricing, +2 | Compare |
| ThoughtSpotthoughtspot.comSee also Transparency alternatives to ThoughtSpot | 43/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 5 Data processing agreement, Data location stated, Status page with history, +2 | Compare |
| Lookerlooker.comSee also Transparency alternatives to Looker | 35/100 | 3 Subprocessor list, Uptime SLA with a figure, HTTPS enforced with HSTS | 6 Data processing agreement, Data location stated, Status page with history, +3 | Compare |
| Steepsteep.appSee also Transparency alternatives to Steep | 43/100 | 2 Subprocessor list, Notice before subprocessors change | 5 Data location stated, Status page with history, Certifications named, +2 | Compare |
| Lightdashlightdash.comSee also Transparency alternatives to Lightdash | 39/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 5 Data processing agreement, Data location stated, Certifications named, +2 | Compare |
| Modemode.comSee also Transparency alternatives to Mode | 35/100 | 2 HTTPS enforced with HSTS, Notice before subprocessors change | 5 Data location stated, Status page with history, Public pricing, +2 | Compare |
| GoodDatagooddata.comSee also Transparency alternatives to GoodData | 26/100 | 2 HTTPS enforced with HSTS, Notice before subprocessors change | 5 Data processing agreement, Data location stated, Status page with history, +2 | Compare |
| Cluviocluvio.comSee also Transparency alternatives to Cluvio | 48/100 | 1 Subprocessor list | 3 Data processing agreement, security.txt (RFC 9116), Named privacy contact | Compare |
| Countcount.coSee also Transparency alternatives to Count | 48/100 | 1 HTTPS enforced with HSTS | 2 Data processing agreement, security.txt (RFC 9116) | Compare |
| Klipfolioklipfolio.comSee also Transparency alternatives to Klipfolio | 48/100 | 1 Notice before subprocessors change | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| Metabasemetabase.comSee also Transparency alternatives to Metabase | 43/100 | 1 HTTPS enforced with HSTS | 3 Data processing agreement, security.txt (RFC 9116), Named privacy contact | Compare |
| Jettijetti.comSee also Transparency alternatives to Jetti | 39/100 | 1 HTTPS enforced with HSTS | 3 Data processing agreement, Status page with history, 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.