Alternatives to Treasure Data
Other Marketing attribution vendors we measure, sorted by how much they publish that Treasure Data does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 34 that differ from Treasure Data on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Treasure Data has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Treasure Data does not” is the one that closes them.
| Vendor | Score | Publishes, and Treasure Data does not | Treasure Data publishes, and they do not | |
|---|---|---|---|---|
| Cometlycometly.com | 65/100 | 4 Data processing agreement, Subprocessor list, Notice before subprocessors change, +1 | 1 Status page with history | Compare |
| Supermetricssupermetrics.com | 65/100 | 4 Subprocessor list, Public pricing, security.txt (RFC 9116), +1 | nothing | Compare |
| Analyzifyanalyzify.com | 57/100 | 4 Data processing agreement, Public pricing, security.txt (RFC 9116), +1 | 2 Status page with history, Certifications named | Compare |
| Factors.aifactors.ai | 57/100 | 4 Data processing agreement, Public pricing, Notice before subprocessors change, +1 | 2 Status page with history, Certifications named | Compare |
| Northbeamnorthbeam.io | 52/100 | 3 Subprocessor list, Public pricing, Notice before subprocessors change | 2 Status page with history, Certifications named | Compare |
| HockeyStackhockeystack.com | 48/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 2 Status page with history, Certifications named | Compare |
| Tealiumtealium.com | 48/100 | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | 1 Data location stated | Compare |
| Elevargetelevar.com | 39/100 | 3 Data processing agreement, Public pricing, Notice before subprocessors change | 3 Data location stated, Status page with history, Certifications named | Compare |
| Improvadoimprovado.io | 30/100 | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | 2 Data location stated, Status page with history | Compare |
| Stapestape.io | 30/100 | 3 Data processing agreement, Uptime SLA with a figure, Named privacy contact | 3 Data location stated, Status page with history, Certifications named | Compare |
| Swydoswydo.com | 30/100 | 3 Public pricing, No third-party tracking before consent, Named privacy contact | 3 Data location stated, Status page with history, Certifications named | Compare |
| DashThisdashthis.com | 43/100 | 2 Data processing agreement, Public pricing | 2 Status page with history, Certifications named | 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.