This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ripe-list] https://www.ripe.net/ inappropriate javascript
- Previous message (by thread): [ripe-list] https://www.ripe.net/ inappropriate javascript
- Next message (by thread): [ripe-list] https://www.ripe.net/ inappropriate javascript
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard (INEX)
nick at inex.ie
Fri May 3 15:32:31 CEST 2019
Mirjam Kuehne wrote on 03/05/2019 13:30: > We use Google Tag Manager to improve the browsing experience on > ripe.net. We have a lot of content, and with people using our website > for a range of different purposes, it helps us to check that our website > layout is fit for purpose. > > We are not using this to monitor or track individual users, it is purely > to give us insight into how users interact with the website. Hi Mirjam, thanks for the update on this. No-one is suggesting that the RIPE NCC is tracking individual users by using Google Tag Manager, but as data controller for the web site, can the ripe ncc confirm what data Google is collecting via this JS module and how it's processed? CJEU Case Cā673/17 looks like it's heading towards confirming informed opt-in rather than informed opt-out for cookies. The current site configuration has no opt-out. Do you have plans to move this to opt-in for third party cookie collection? Nick
- Previous message (by thread): [ripe-list] https://www.ripe.net/ inappropriate javascript
- Next message (by thread): [ripe-list] https://www.ripe.net/ inappropriate javascript
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]