Transparency alternatives to GRIN
Other Influencer marketing vendors we measure, sorted by how much we found at them and not at GRIN. This is a comparison of disclosure, not of features or fitness.
12 shown of 29 that differ from GRIN on at least one criterion we measured for both. Public transparency score, not a product or security rating.
GRIN 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, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at GRIN” is the one that closes them.
| Vendor | Score | Found there, not found at GRIN | Found at GRIN, not found there | |
|---|---|---|---|---|
| Modashmodash.ioSee also Transparency alternatives to Modash | 57/100 | 4 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +1 | 1 Certifications named | Compare |
| Storyclashstoryclash.comSee also Transparency alternatives to Storyclash | 39/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Certifications named, Named privacy contact | Compare |
| Influencityinfluencity.comSee also Transparency alternatives to Influencity | 35/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Public pricing, Certifications named | Compare |
| HypeAuditorhypeauditor.comSee also Transparency alternatives to HypeAuditor | 33/100 | 3 Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS | 1 Certifications named | Compare |
| Heepsyheepsy.comSee also Transparency alternatives to Heepsy | 30/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Certifications named, Named privacy contact | Compare |
| CreatorIQcreatoriq.comSee also Transparency alternatives to CreatorIQ | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Public pricing, Named privacy contact | Compare |
| Minisocialminisocial.comSee also Transparency alternatives to Minisocial | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Public pricing, Certifications named, Named privacy contact | Compare |
| Traackrtraackr.comSee also Transparency alternatives to Traackr | 17/100 | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | 2 Public pricing, Named privacy contact | Compare |
| Woomiowoomio.comSee also Transparency alternatives to Woomio | 17/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 3 Public pricing, Certifications named, Named privacy contact | Compare |
| Insenseinsense.proSee also Transparency alternatives to Insense | 22/100 | 1 Data location stated | 2 Certifications named, Named privacy contact | Compare |
| Afluencerafluencer.comSee also Transparency alternatives to Afluencer | 17/100 | 1 HTTPS enforced with HSTS | 2 Certifications named, Named privacy contact | Compare |
| Kolsquarekolsquare.comSee also Transparency alternatives to Kolsquare | 17/100 | 1 HTTPS enforced with HSTS | 2 Certifications named, Named privacy contact | 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.