Post by harunur017 on Feb 2, 2024 22:31:15 GMT -6
The above means that data controllers should actually show website visitors a pop-up asking for permission to share IP addresses with Google in the context of the use of Google Fonts, Google Recaptcha or other services (similar to a pop-up cookie). The main problem is that consent must be given "freely" under the GDPR, which means that people must be able to visit the site even without giving permission for Google to process their data (and therefore without Google Fonts or Google Recaptcha )… All of this is obviously pure legal fiction. In practice, data controllers cannot ask for such authorization.
If it were technically feasible, it would undoubtedly compress traffic numbers on a website or your website will be displayed with an Arial font that will have to act as a backup. There is therefore only one possible conclusion: Websites should avoid sharing the IP addresses of their web visitors in the context of Google Buy TG Number Data Fonts (or Google Recaptcha) with Google or other third parties. For Google Fonts, this means local hosting. For Google Recaptcha, frankly, our technical knowledge fails us. Maybe another recaptcha tool that doesn't send IP addresses to external servers will be the only solution there... We are currently investigating further with our developer. Incidentally, the question remains whether these types of discussions are very good for the image of the GDPR and the general level of data protection in the EU.
There are arguably far more pressing privacy issues than Google processing IP addresses to display a correct font on a website... On the other hand, this is a topic that Google could perhaps communicate more openly about, so that marketers and web builders are more aware that even the choice of a font on a website can have GDPR implications. Attention web developers Web developers better be careful about the projects they deliver. It is true that the owner of the website – i.e. the customer – will in principle be addressed as responsible for the processing of personal data by the supervisory authority in the context of checks or sanctions or by users in the context of a complaint for compensation.
If it were technically feasible, it would undoubtedly compress traffic numbers on a website or your website will be displayed with an Arial font that will have to act as a backup. There is therefore only one possible conclusion: Websites should avoid sharing the IP addresses of their web visitors in the context of Google Buy TG Number Data Fonts (or Google Recaptcha) with Google or other third parties. For Google Fonts, this means local hosting. For Google Recaptcha, frankly, our technical knowledge fails us. Maybe another recaptcha tool that doesn't send IP addresses to external servers will be the only solution there... We are currently investigating further with our developer. Incidentally, the question remains whether these types of discussions are very good for the image of the GDPR and the general level of data protection in the EU.
There are arguably far more pressing privacy issues than Google processing IP addresses to display a correct font on a website... On the other hand, this is a topic that Google could perhaps communicate more openly about, so that marketers and web builders are more aware that even the choice of a font on a website can have GDPR implications. Attention web developers Web developers better be careful about the projects they deliver. It is true that the owner of the website – i.e. the customer – will in principle be addressed as responsible for the processing of personal data by the supervisory authority in the context of checks or sanctions or by users in the context of a complaint for compensation.