Hacker News new | past | comments | ask | show | jobs | submit login

So not only do users need to actually opt-out but site owners have to opt-out too?

Has anyone stopped to consider where laws and regulations should come in to say that tracking like this is far too invasive?




You don’t have to, what happens between a user and their browser is theoretically none of your business. But if you care about your users’ privacy, I see no reason not to send this header as there’s no defined value for you as a business (unless you plan to somehow try to retarget users who’ve visited your site based on guessing which cohort that potentially refers to).


> So not only do users need to actually opt-out but site owners have to opt-out too?

By setting this on the site level, your users won't have to opt-out. You are doing it for them (all of them).

If you don't, then the browser can always ignore it also. But that would only affect that individual user.


Weird question: What if a user actually wants to opt-in but the site has opted-out? Should user opt-in override site opt-out?


The user opts in to being placed into a cohort. The site opts out of providing information to Google to let them generate cohorts based on the site. There’s no overlap.


The reason why FLOC was invented, is to a oid lawmakers getting involved.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: