Transparency alternatives to Movingimage
Other Video and podcast hosting vendors we measure, sorted by how much we found at them and not at Movingimage. This is a comparison of disclosure, not of features or fitness.
12 shown of 49 that differ from Movingimage on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Movingimage 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 “Found there, not found at Movingimage” is the one that closes them.
| Vendor | Score | Found there, not found at Movingimage | Found at Movingimage, not found there | |
|---|---|---|---|---|
| api.videoapi.videoSee also Transparency alternatives to api.video | 78/100 | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | 1 Certifications named | Compare |
| Simplecastsimplecast.comSee also Transparency alternatives to Simplecast | 78/100 | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | 1 Certifications named | Compare |
| Loomloom.comSee also Transparency alternatives to Loom | 61/100 | 5 Data processing agreement, Public pricing, security.txt (RFC 9116), +2 | 1 Data location stated | Compare |
| JWXjwx.comSee also Transparency alternatives to JWX | 70/100 | 4 Data processing agreement, Subprocessor list, Notice before subprocessors change, +1 | 1 Certifications named | Compare |
| WeVideowevideo.comSee also Transparency alternatives to WeVideo | 70/100 | 4 Data processing agreement, Public pricing, Notice before subprocessors change, +1 | nothing | Compare |
| Transistortransistor.fmSee also Transparency alternatives to Transistor | 57/100 | 4 Data processing agreement, Subprocessor list, Public pricing, +1 | 2 Data location stated, Status page with history | Compare |
| Vidyardvidyard.comSee also Transparency alternatives to Vidyard | 57/100 | 4 Data processing agreement, Subprocessor list, Notice before subprocessors change, +1 | 2 Status page with history, HTTPS enforced with HSTS | Compare |
| Muxmux.comSee also Transparency alternatives to Mux | 52/100 | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | nothing | Compare |
| Tellatella.tvSee also Transparency alternatives to Tella | 48/100 | 3 Data processing agreement, Public pricing, Named privacy contact | 2 Status page with history, Certifications named | Compare |
| Cleanvoicecleanvoice.aiSee also Transparency alternatives to Cleanvoice | 39/100 | 3 Data processing agreement, Public pricing, Notice before subprocessors change | 3 Data location stated, Status page with history, Certifications named | Compare |
| Acastacast.comSee also Transparency alternatives to Acast | 35/100 | 3 Data processing agreement, Public pricing, security.txt (RFC 9116) | 3 Data location stated, Status page with history, Certifications named | Compare |
| Dacastdacast.comSee also Transparency alternatives to Dacast | 43/100 | 2 Public pricing, Uptime SLA with a figure | 1 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.