So it’s basically saying that despite it auto-linking your Chrome browsing and (Google) web-based activity it’s not automatically copying your browsing data to its own servers, where it would then be able to derive all sorts of fresh linked intel about you for its ad-targeting purposes. In its blog post Google claims that being signed in to Chrome does not mean Chrome sync gets turned on. But Google’s change flips that switch - making the default setting hostile to privacy by folding a Chrome user’s browsing activity into their Google identity. Prior to the Chrome 69 update, users had to actively opt in to linking their web-based and browser-based IDs. Matthew Green, a cryptography professor at Johns Hopkins, flagged the change in a critical blog post at the weekend - entitled Why I’m done with Chrome - arguing that the new “forced login” feature blurs the previously strong barrier between “never logged in” and “signed in”, and thus erodes user trust. Now Google is saying there will be an option to prevent it pinning your Chrome browsing to your Google account - but you’ll have to wait about a month to get it.Īnd of course for the millions of web users who never touch default settings being automatically signed into Google’s browser when they are using another Google service like Gmail or YouTube will be the new normal. The update to Chrome 69 means users are automatically logged into the browser when they are signed into another Google service, giving them no option to keep these digital identities separate. Google has responded to blowback about a privacy hostile change it made this week, which removes user agency by automating Chrome browser sign-ins, by rowing back slightly - saying it will give users the ability to disable this linking of web-based sign-in with browser-based sign-in in a forthcoming update (Chrome 70), due mid next month.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |