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