Google has taken the liberty of logging Chrome into the user's account whenever logged in to any Google service.
Some time ago, Google introduced the ability to have its browser, Chrome, log into the user's Google account whenever the user authenticated for any Google service. That is, log in to Google Docs, for example, and the browser would be logged in as well.
The pitch was that this relationship between being logged in to a service and the browser also being logged in, can help mitigate confusion when a user logs out of a Google service but fails to realize the browser is still logged in. The mystery can be eliminated if the browser keeps the two in the same state automatically.
There is the added benefit that the browser would be better able to synchronize the user experience across each browser that was also logged into the user's account. For example, Chrome on a mobile device could have access to the history from Chrome on a laptop.
The idea is not novel anymore, since Mozilla has user accounts that Firefox can log into as well. Opera has them, Vivaldi has them, and Brave has them as well. The difference is that Firefox has been overt about its effort to protect privacy.
Users can understand and accept, that while logged in to a service, the owner of that service will be able to aggregate data about their activity. The suspicious among us, might raise an eyebrow to the fact that a company, widely understood to be addicted to collecting all manner of data about its users, is now making a web browser too. The fear is easy to understand too.
The browser can easily be a channel to direct all of a user's browsing history to the company, but at least the traffic could naively be assumed to be anonymous.
By automatically logging the user into the browser, the user is tied directly to the traffic, so the situation isn't, "Chrome just loaded page XYZ from this IP address." Now it's, "Chrome just loaded page XYZ from this IP address, and the user is So-and-so."
The only visible clue is the user icon in the upper right corner of the browser window. It would be a fool's bet to assume that everyone will notice their browser is now logged in to Google, and sign it out immediately. And even if they did, the next time they need any Google service, they'll need to log in again, which will of course, log the browser back in, and the cycle will continue.
Granted, this behavior was introduced a year and half ago, and a quick search will turn up a number of outlets talking about the change. If Chrome isn't a user's daily driver, it can easily go undetected, so maybe the topic is worth another visit.
The behavior can be disabled with the following steps.
Some time ago, Google introduced the ability to have its browser, Chrome, log into the user's Google account whenever the user authenticated for any Google service. That is, log in to Google Docs, for example, and the browser would be logged in as well.
The pitch was that this relationship between being logged in to a service and the browser also being logged in, can help mitigate confusion when a user logs out of a Google service but fails to realize the browser is still logged in. The mystery can be eliminated if the browser keeps the two in the same state automatically.
There is the added benefit that the browser would be better able to synchronize the user experience across each browser that was also logged into the user's account. For example, Chrome on a mobile device could have access to the history from Chrome on a laptop.
The idea is not novel anymore, since Mozilla has user accounts that Firefox can log into as well. Opera has them, Vivaldi has them, and Brave has them as well. The difference is that Firefox has been overt about its effort to protect privacy.
Users can understand and accept, that while logged in to a service, the owner of that service will be able to aggregate data about their activity. The suspicious among us, might raise an eyebrow to the fact that a company, widely understood to be addicted to collecting all manner of data about its users, is now making a web browser too. The fear is easy to understand too.
The browser can easily be a channel to direct all of a user's browsing history to the company, but at least the traffic could naively be assumed to be anonymous.
By automatically logging the user into the browser, the user is tied directly to the traffic, so the situation isn't, "Chrome just loaded page XYZ from this IP address." Now it's, "Chrome just loaded page XYZ from this IP address, and the user is So-and-so."
The only visible clue is the user icon in the upper right corner of the browser window. It would be a fool's bet to assume that everyone will notice their browser is now logged in to Google, and sign it out immediately. And even if they did, the next time they need any Google service, they'll need to log in again, which will of course, log the browser back in, and the cycle will continue.
Granted, this behavior was introduced a year and half ago, and a quick search will turn up a number of outlets talking about the change. If Chrome isn't a user's daily driver, it can easily go undetected, so maybe the topic is worth another visit.
The behavior can be disabled with the following steps.
- Open the Settings
- Under You and Google, choose Sync and Google Services
- Uncheck Allow Chrome sign-in
Comments
Post a Comment