What in the W3C EME standard cannot be freely implemented? As far as I know, EME is just a communications standard between the browser and components that are not part of the browser to allow those components to provide media data for the browser to display.<p>EME can be used to communicate with proprietary DRM components, but those DRM components are not part of the standard, and there is nothing that I&#x27;ve seen in EME that makes DRM the only thing it can be used for.<p>For instance, couldn&#x27;t EME be used to make a system to protect the privacy of people sharing personal videos? Encrypt the video and upload to a web server that all the parties sharing have access to. Distribute the decryption keys to the people intended to share the video. Use EME to interface the browser to a component that uses that key to decrypt the video on the fly.<p>From the browser&#x27;s point of view there is not really any significant difference between a video that is encrypted for DRM and one that is encrypted for privacy. In the former case those who encrypted it want to keep the key secret from the viewer, whereas in the latter case they want to keep the key secret from third parties. To the browser, these look the same: there is encrypted video, and the browser needs something to decrypt that and hand it the decrypted data for it to display.