Alternatives to Sifflet
Other Product information management vendors we measure, sorted by how much they publish that Sifflet does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 36 that differ from Sifflet on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Sifflet has 6 gaps in what we could measure: Subprocessor list, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “publishes and Sifflet does not” is the one that closes them.
| Vendor | Score | Publishes, and Sifflet does not | Sifflet publishes, and they do not | |
|---|---|---|---|---|
| Reltioreltio.com | 39/100 | 3 Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS | 4 Data processing agreement, Public pricing, Notice before subprocessors change, +1 | Compare |
| Alationalation.com | 52/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 2 Data processing agreement, Public pricing | Compare |
| Ataccamaataccama.com | 43/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data processing agreement, Notice before subprocessors change | Compare |
| data.worlddata.world | 39/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Data processing agreement, Public pricing, Notice before subprocessors change | Compare |
| Akeneoakeneo.com | 35/100 | 2 Status page with history, security.txt (RFC 9116) | 3 Data processing agreement, Public pricing, Notice before subprocessors change | Compare |
| Castorcastordoc.com | 30/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 5 Data processing agreement, Data location stated, Public pricing, +2 | Compare |
| GoDataFeedgodatafeed.com | 30/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 5 Data processing agreement, Data location stated, Certifications named, +2 | Compare |
| Atlanatlan.com | 26/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 5 Data location stated, Public pricing, Certifications named, +2 | Compare |
| Monte Carlomontecarlodata.com | 26/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 5 Data location stated, Public pricing, Certifications named, +2 | Compare |
| Salsifysalsify.com | 22/100 | 2 Status page with history, HTTPS enforced with HSTS | 5 Data processing agreement, Data location stated, Public pricing, +2 | Compare |
| Collibracollibra.com | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 5 Data processing agreement, Data location stated, Public pricing, +2 | Compare |
| inriverinriver.com | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 5 Data processing agreement, Data location stated, Public pricing, +2 | 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.