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