Kent BrewsterSep 9, 2023

Infosec friends are unanimous: if you're using Chrome, you want to visit chrome://settings/adPrivacy and turn off Ad Topics, Site-Suggested Ads, and Ad Measurement.

IMPORTANT: you must do this for each of your Chrome profiles, since it's not a global setting.

#chrome #privacy #enshittification

Show threadDon Marti
@kentbrew good point. Also IT staff who support desktop Google Chrome can turn these off for all users: https://chromeenterprise.google/policies/#PrivacySandbox
Chrome Enterprise Policy List & Management | Documentation

Chrome Enterprise policies for businesses and organizations to manage Chrome Browser and ChromeOS.

Chrome Enterprise
Sep 9, 2023 at 4:31amWeb
Show threadKent BrewsterSep 9, 2023
@dmarti ooooh, okay, thanks! Surely every government sysadmin or government contractor sysadmin would want to do this immediately.
Show threadDon MartiSep 9, 2023
@kentbrew yes, also set the Permission-Policy header on web servers you manage, in case a 3rd party script is updated to harvest user info on your site (my checklist so far: https://blog.zgp.org/google-chrome-checklist/ )
Google Chrome ad features checklist

Show threadKent BrewsterSep 10, 2023

@dmarti whoa, your "Browser Topics Tracking and the Prejudiced Landlord Problem" is really good! Especially this:

"Won’t members of protected groups just avoid discrimination by blocking certain topics from being shared, or turning off the topics tracking feature? Well, no, because people who don’t expect to be discriminated against will be less likely to take that action, and the ML system will learn to discriminate that way."

https://blog.zgp.org/prejudiced-landlord/

browser topics tracking and the prejudiced landlord problem

Show threadDon MartiSep 11, 2023
@kentbrew Thank you (that's why imho the people who can have the most impact by choosing privacy settings are people who would otherwise get the *good* ads, not people most likely to be discriminated against)