How to escape Google’s forced logins on Chrome 69 | Tech Industry

According to security researcher S. Bálint, any time someone using 69 logs into a Google service or site, they are also logged into Chrome-as-a-browser with that user account. Essentially, Google is forcefully logging users into Chrome.

Chrome browser’s privacy policy notes that if you are is not signed in, all the information is locally stored on your system. However, all the data – including your browser history and password autofill information –is sent to Google servers once you’re signed in. That leads users to believe that Chrome 69’s forced login policy is sharing user data with Google.


However, Adrienne Porter Felt – an engineer and manager on the Google Chrome team – said that the user data is not getting uploaded to Google servers. But if that’s true, then why is Google is forcefully logging people in?

Automatically logging people into browsers potentially creates an unsafe environment on shared devices: Others who use the device may be able to access your account, even when you think you’ve logged out of the services you just used.

Felt said that the new version of Chrome’s UI now uses a profile icon to the right of the address bar to indicate that you’re signed into any of Google’s services. Apparently, this change was made so that users don’t forget to sign out on shared machines. But its effectiveness may be limited, as people may not realize they’re logged into the browser – especially if they don’t notice this change.

You can change this behaviour by going to  ‘chrome://flags/#account-consistency’ and disabling ‘Identity consistency between browser and cookie jar’ flag. Some developers have also built a privacy centric fork of Chrome called Ungoogled-Chrome.