Alternatives to Gumlet
Other Video and podcast hosting vendors we measure, sorted by how much they publish that Gumlet does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 28 that differ from Gumlet on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Gumlet has 9 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, Named privacy contact. The column “publishes and Gumlet does not” is the one that closes them.
| Vendor | Score | Publishes, and Gumlet does not | Gumlet publishes, and they do not | |
|---|---|---|---|---|
| api.videoapi.video | 78/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 1 security.txt (RFC 9116) | Compare |
| Loomloom.com | 74/100 | 6 Data processing agreement, Data location stated, Status page with history, +3 | nothing | Compare |
| Vidyardvidyard.com | 57/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| JW Playerjwplayer.com | 48/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Muxmux.com | 52/100 | 4 Data location stated, Status page with history, Certifications named, +1 | nothing | Compare |
| Auphonicauphonic.com | 52/100 | 3 Subprocessor list, Data location stated, No third-party tracking before consent | 1 security.txt (RFC 9116) | Compare |
| Cleanvoicecleanvoice.ai | 48/100 | 3 Data processing agreement, No third-party tracking before consent, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Descriptdescript.com | 48/100 | 3 Subprocessor list, Data location stated, Certifications named | 1 security.txt (RFC 9116) | Compare |
| Brightcovebrightcove.com | 22/100 | 3 Data location stated, Certifications named, Named privacy contact | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Podbeanpodbean.com | 36/100 | 2 Data location stated, Named privacy contact | nothing | Compare |
| Dacastdacast.com | 35/100 | 2 Data location stated, Uptime SLA with a figure | 1 security.txt (RFC 9116) | Compare |
| Captivatecaptivate.fm | 26/100 | 2 Data location stated, Named privacy contact | 2 HTTPS enforced with HSTS, 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.