There's more, let me enrich the list of data a bit: (1) Minimal data (as per your comment): - Your IP address (hence, your location and the internet provider y

There's more, let me enrich the list of data a bit: (1) Minimal data (as per your comment): - Your IP address (hence, your location and the internet provider you use) (2) Inevitably collected data (you can't avoid not giving this data for things to operate): - The website domain (goes to DNS and your internet provider / VPN) - The page URL you access (goes to your website and Cloud/CDN provider they use) - Timestamp of the request (goes to all) - Cookies, user agent, referral and other headers your browser typically sends (goes to your website and Cloud/CDN provider they use) (3) Client-side collected data (arbitrary JavaScript and what blockers typically block): - Same data as above (but let's say, instead being fed to a third party like Google) - Some client-only data (screen dimensions, session duration) - Behavioral data (page element clicks, cursor moves, etc) - Whatever the website itself wants to collect (typically, ad conversions, attribution, purchases etc) It's absolutely valid (3) can be misused and it's fair to be minimized. But to same extent (2) can. It all just narrows down to giving less data, to less third parties. A random ad-heavy site on the internet still has a little chance to know you've purchased a new pair of shoes in some random store. There are truly genuine and legit cases when website owners would like to use (3) for whatever purpose, but they can't get accurate data (and with some blocker extensions, even after the consent has been granted). Like, you may want to see how many scroll it down, read and to what extent. There's value. Each website decides this for themselves – they are the builders.