Transparency alternatives to ViewFoo
Other Digital asset management vendors we measure, sorted by how much they publish that ViewFoo does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 36 that differ from ViewFoo on at least one criterion we measured for both. Public transparency score, not a product or security rating.
ViewFoo has 11 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, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and ViewFoo does not” is the one that closes them.
| Vendor | Score | Publishes, and ViewFoo does not | ViewFoo publishes, and they do not | |
|---|---|---|---|---|
| Frontifyfrontify.com | 61/100 | 7 Data processing agreement, Data location stated, Status page with history, +4 | 1 Public pricing | Compare |
| Cloudinarycloudinary.com | 64/100 | 6 Subprocessor list, Data location stated, Status page with history, +3 | nothing | Compare |
| Bynderbynder.com | 39/100 | 5 Status page with history, Certifications named, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Imgiximgix.com | 43/100 | 4 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Massetgetmasset.com | 43/100 | 4 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Brandfolderbrandfolder.com | 39/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Airair.inc | 36/100 | 4 Status page with history, Certifications named, Uptime SLA with a figure, +1 | nothing | Compare |
| Sitecore Content Hubsitecore.com | 35/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 1 Public pricing | Compare |
| Censharecenshare.com | 30/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Public pricing | Compare |
| Uploadcareuploadcare.com | 30/100 | 4 Status page with history, Uptime SLA with a figure, security.txt (RFC 9116), +1 | nothing | Compare |
| ResourceSpaceresourcespace.com | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| Aprimoaprimo.com | 30/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 1 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.