-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Youtube Embeds GDPR compliant #2980
Comments
Vimeo immediately comes to mind, as their business model is based on paid memberships for the video hosting itself as oppose to collecting user data, and they have an embedded player parameter called The free Basic plan's primary limit to us is an upload space limit of 500mb per week and 5GB total. The cheapest paid plan, Plus, bumps that up to 5GB per week and 250GB per year (and assumedly unlimited total aside from that). |
Dailymotion is another alternative that claims to be GDPR compliant, and they have a more generous free plan than Vimeo. |
We could definitely use a different video platform, but we would be forced to copy over any youtube videos we want to post on our website over to that platform. And we would less traffic on our youtube channel 🤔 Maybe we should consider turning our youtube embeds into links to youtube? We could use the youtube API and CSS to make it look like a video (allowing us to not have to update our website layouts), but when you click on it opens a new tab to youtube. @iterative/websites, what do you think? |
Agreed, would be a rough time to port all videos we want to embed as well as trying to enforce no youtube embeds throughout the site.
I don't think this is quite what we'd want, I get the impression most people like to have the embeds within the site instead of bringing the user to another site which makes it more likely they'll bounce after. Maybe we could re-tune our youtube-embeds such that the iframe src is not loaded until the user clicks a button? I found some inspiration from this article and threw together a little demo: youtube-delayed-load-demo.mp4We'll have to provide our own background image if we want one, but this method of loading ensures that the child iframe can't even load if we don't want it to, ensuring that no user info can be stored and we stay GDPR compliant while keeping videos embedded in the website. PR created at #3136 |
That would definitely be an improvement but I believe to be GDPR compliant, we would need to notify the user that clicking on the button sets trackers. If we want to keep youtube embeds on the site, maybe we could notify the user by showing a tooltip so the user wouldn't need to make extra clicks 🤔 |
Tooltip when I hover the play button? One option to consider - open it the new window on the youtube domain? |
Yes! If we want to keep youtube embeds on our site, we would need to notify the user that clicking on the youtube video would add trackers to their browser. One way that came to mind was adding a tooltip when you hover over the play button, letting the user know that clicking play would add trackers, keeping things GDPR compliant.
Yes, I mentioned this option earlier! We can have the site open a link to youtube when a user clicks on the video. It keeps our site tracker free and we won't have to notify the user of anything :) |
I think tooltip like that works. We would need to take care of the blog and docs for the embedded videos I think. |
Sounds good! We'll need a design for the tooltip and as for the video background... We could keep it a dark screen (like in @rogermparent's example) , design a custom image, or even use the youtube api to fetch the the videos` thumbnail (though that method would add extra requests for the website).
I can think of a way to do this with the docs engine. As for the blog, it may need some kind of custom plugin 🤔 |
Did some further research about using Looking outside of Google/Youtube, I'm reading mixed opinions. Some say that Personally, I don't think it's GDPR compliant. Even if the data that its setting in the local storage doesn't track anything from the user, we still need to let the user know that clicking on the youtube videos activates youtube's cookies :( |
To be GDPR compatible (in a sense that you don't have to show the message) doesn't mean that you could not use cookies at all. It depends on how those cookies (and local storage) are being used. Google mentions briefly that they do not use them to personalize. We would need to check what do they actually do with them. May be we would need to check their privacy policy and terms of use. Can we create a PR to research this a bit? It seems it would be beneficial anyway to switch to the nocookie domain. |
Sure, I'll open an issue!
Agreed! |
Looked into and tested the |
Currently, we use Youtube embeds for videos on the site. But Youtube is using cookies to track user's info. If we don't want to have to ask a user's permission to play Youtube videos, we'll need to find an alternative to youtube. Youtube does offer
youtube-nocookie.com
, but that just places tracking info in local storage and adds cookies once the user presses play.cc @shcheklein @rogermparent
The text was updated successfully, but these errors were encountered: