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