FYI, Chrome’s Identity Consistency Flag has stopped working in version 71

Google has made a significant change in Chrome 68, which now being noticed is the search engine giant has tied user identity on Google Web Services such as Gmail to user’s identity in Chrome. What this means is if you sign into your Google account, you’ll be signed into Chrome browser as well (and data will be uploaded to Google servers, but sync is not turned on by default, unless you choose) and if you sign out of either Google account/Chrome, you’ll be signed out of both.

If you’re happy with this or not, the change is here to stay, meanwhile, Google has marked sync pauses when signed out of Gmail and Chrome 69 breaks multi-sign in bugs as won’t fix.

Account Consistency flag already has stopped working in Chrome 71

There is a flag available to disable identity consistency between Chrome and cookie jar, but that (chrome://flags/#account-consistency) has been already stopped working in Chrome 71 dev when set to disabled.

If you’ve complaints against Chrome rounded UI and you may have enabled a flag to get the previous UI back which isn’t going to stay either.

It’s pretty clear! Stop depending on flags, adapt to the change or switch to another browser, flags don’t last for too long, they’ll be removed eventually from chrome://flags page.

UPDATE: Forget about the flag, we’re able to successfully prevent Chrome from signing into the browser when signed into a Google account, check out this article, working 100% on Mac and Windows, even in Chrome 71 where the flag has failed. Stop Chrome from Signing into browser when you sign into Google service [Registry Trick]

UPDATE 1: Google will address the Chrome sign-in, sync and Google auth cookies getting left when cleared browser data concerns in Chrome 70, read this Google: Chrome 70 will offer a Setting to remove web and browser sign-in linking

Have you got our point?