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