Transparency alternatives to Fozzels
Other Product information management vendors we measure, sorted by how much we found at them and not at Fozzels. This is a comparison of disclosure, not of features or fitness.
12 shown of 36 that differ from Fozzels on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Fozzels has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Fozzels” is the one that closes them.
| Vendor | Score | Found there, not found at Fozzels | Found at Fozzels, not found there | |
|---|---|---|---|---|
| Sodasoda.ioSee also Transparency alternatives to Soda | 65/100 | 5 Data processing agreement, Data location stated, Status page with history, +2 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Siffletsiffletdata.comSee also Transparency alternatives to Sifflet | 52/100 | 4 Data processing agreement, Data location stated, Certifications named, +1 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Reltioreltio.comSee also Transparency alternatives to Reltio | 39/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| Alationalation.comSee also Transparency alternatives to Alation | 39/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 2 Public pricing, security.txt (RFC 9116) | Compare |
| data.worlddata.worldSee also Transparency alternatives to data.world | 39/100 | 3 Data location stated, Status page with history, Certifications named | 2 Public pricing, security.txt (RFC 9116) | Compare |
| ATAMYAatamya.comSee also Transparency alternatives to ATAMYA | 39/100 | 2 Data processing agreement, Data location stated | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Castorcastordoc.comSee also Transparency alternatives to Castor | 30/100 | 2 Subprocessor list, Notice before subprocessors change | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| inriverinriver.comSee also Transparency alternatives to inriver | 30/100 | 2 Data location stated, Certifications named | 2 Public pricing, Named privacy contact | Compare |
| Plytixplytix.comSee also Transparency alternatives to Plytix | 30/100 | 2 Data location stated, Certifications named | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Profiseeprofisee.comSee also Transparency alternatives to Profisee | 30/100 | 2 Data location stated, Certifications named | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Syndigosyndigo.comSee also Transparency alternatives to Syndigo | 30/100 | 2 Data location stated, Certifications named | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Tamrtamr.comSee also Transparency alternatives to Tamr | 30/100 | 2 Data location stated, Certifications named | 2 Public pricing, security.txt (RFC 9116) | 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.