Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I've worked in the sector for years and honestly thought this was well documented, common knowledge: https://developers.google.com/authorized-buyers/rtb/cookie-g...

The only thing Google did in regards to GPRR was limit the number of parties in RTB they're including by default for syncing to a "trusted set" of parties.



I think the silent/invisible nature of cookie sync'ing is what upsets people when they discover it. T

he diagrams in your link show a single hop for the 302, in my experience that can be many hops going between different advertisers. The same thing happens on non-google platforms, like TradeDesk and others.

The sync scenario can make it next to impossible to delete cookies when those cookies can be rebuilt using data from others.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

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

Search: