You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Videos are always showing, even without explicit consent. Only using the YouTube "no cookie" url is in fact not GDPR conform.
Youtube Nocookie reduces but doesn't eliminate tracking from Alphabet. For youtube (including nocookie) and other external content, explicit consent is mandatory. That consent can not be acquired by a general checkbox or by the TOS. It has to be it's own specific checkbox. And for example if you allow Vimeo and Youtube, each has to be toggleable by the user individually.
Overall the GDPR conformity is not great of daily.dev and you should look through it. But I will open a different ticket for that.
NOTE: The GDPR requires data controllers to take prompt measures to address violations. This means you should act as quickly as possible once you become aware of the violation. I have hereby informed you of the violations of my rights as a citizen of a European Union member state.
Expected Behavior
No response
Steps to Reproduce Issue
No response
Solution Proposed
No response
Screenshots
No response
Environment
No response
Browsers
No response
OS
No response
Version of daily.dev
No response
Additional Context
No response
Code of Conduct
I follow the conditions of this project.
The text was updated successfully, but these errors were encountered:
@marvinpoo Thank you for raising this concern and for engaging with us on such an important topic. We genuinely value feedback from our community and appreciate the effort you’ve taken to share your perspective. Input like yours helps us to identify areas where we can improve and ensures we remain vigilant in maintaining the highest standards for our users. If you have additional suggestions or questions, we encourage you to share them—we’re always open to constructive dialogue.
At daily.dev, user privacy and transparency are at the heart of what we do. We are continuously working to enhance our policies, consent mechanisms, and privacy controls, and we view this as an ongoing journey to align with best practices and regulations.
As part of this commitment, we are also continuously improving the consent mechanisms on our platform to provide users with more granular control. For example, we’re working on implementing clearer, separate toggles for third-party services like YouTube to ensure transparency and allow users to make more informed decisions. These updates are part of a broader ongoing effort to provide an even more robust and user-friendly experience.
We’re actively developing these updates, some of which relate to the concerns you’ve raised above. We aim to release these enhancements in an upcoming version, which is currently being finalized and expected after the holiday period.
We value your input and appreciate your engagement. It plays a crucial role in helping us deliver a better product and experience to our community. Thank you for being part of this process.
What went wrong? 🤔
Videos are always showing, even without explicit consent. Only using the YouTube "no cookie" url is in fact not GDPR conform.
Youtube Nocookie reduces but doesn't eliminate tracking from Alphabet. For youtube (including nocookie) and other external content, explicit consent is mandatory. That consent can not be acquired by a general checkbox or by the TOS. It has to be it's own specific checkbox. And for example if you allow Vimeo and Youtube, each has to be toggleable by the user individually.
Overall the GDPR conformity is not great of daily.dev and you should look through it. But I will open a different ticket for that.
NOTE: The GDPR requires data controllers to take prompt measures to address violations. This means you should act as quickly as possible once you become aware of the violation. I have hereby informed you of the violations of my rights as a citizen of a European Union member state.
Expected Behavior
No response
Steps to Reproduce Issue
No response
Solution Proposed
No response
Screenshots
No response
Environment
No response
Browsers
No response
OS
No response
Version of daily.dev
No response
Additional Context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: