There is something disturbing you should know about Chrome 69 before you update it. S. Bálint pointed out that starting with Chrome 69, logging into a Google Site is tied to logging into Chrome. Matthew Green describes the change as a “forced login policy”, which sounds pretty accurate to me.
The easiest to understand explanation I found about this change comes from S. Bálint’ blog post:
So what changed with Chrome 69? From that version, any time someone using Chrome logs into a Google service or site, they are also logged into Chrome-as-a-broswer with that user account. Any time someone logs out of a Google service, they are also logged out of the browser. Before Chrome 69, Chrome users could decline to be logged into Chrome entirely, skipping the Sync and other features that require a login and they could use Chrome in a logged-out state while still making use of Gmail for example.
I use a Mac, but was using Chrome for a few websites that didn’t work very well on Safari. I noticed that the photo I use on my Gmail account was appearing in the corner of the Chrome browser. I have since deleted Chrome from my computer and the Gmail app from my phone.
Personally, I’m not entirely clear on what, exactly, Chrome 69 wants to Sync from my Gmail account and the Chrome browser. It feels kind of grabby. The impression I got from the blogs I read (and linked above) is that even if Google says that it’s not automatically activating the Sync feature, that doesn’t mean it can’t or won’t do that in the future.
Google started out with a code of conduct that started with the sentence: “Don’t be evil.” The changes coming to Chrome 69 might not technically be “evil”… but they certainly aren’t nice.
One thought on “Chrome 69 has a Forced Login Policy”
Comments are closed.