Google says that in Chrome 70, coming mid-October, it will allow users to disable linking Google website and Chrome sign-ins
We recently made a change to simplify the way Chrome handles sign-in. Now, when you sign into any Google website, you're also signed into Chrome with the same account.
Context & Ripple Effects
Two days before this announcement, coverage flagged that Chrome 69 had made signing into any Google site automatically sign you into the browser, with no way to separate the two. The change read as a quiet expansion of Google's logged-in footprint, and it landed badly enough that Google is now shipping a toggle in Chrome 70 to undo it.
The episode previews a longer fault line: in 2021 Google went further and moved to strip Chromium browsers of access to Chrome bookmarks and sync features entirely, drawing a harder line between the open-source browser and Google's account-bound services.
First-order effects
- Users who resented being silently signed into Chrome after logging into Gmail or another Google site get an explicit off switch when Chrome 70 ships mid-October, though linked sign-ins remain enabled by default.
- Google converts its loudest privacy critics' complaint from a forced behavior into a settings choice, defusing the backlash without changing the default funnel into signed-in browsing.
Second-order effects
- Rival browsers can now position themselves against Chrome's default-on account linking, since Google has effectively conceded that silent sign-in needed an escape hatch.
- The opt-out keeps privacy-sensitive users inside Chrome who might otherwise have switched browsers over the Chrome 69 behavior, protecting Google's share of signed-in sessions that feed its ad business.
Third-order effects
- If the pattern holds, browser makers will keep defaulting to identity-linked browsing and rely on post-hoc toggles as pressure valves — defaults set the behavior, options absorb the criticism.
- The eventual walling-off of sync features from Chromium points toward a structural split: Google's browser surface consolidating around proprietary, account-tied services while the open-source base becomes a thinner compatibility layer.
The trend: Browser vendors are binding web identity to the browser by default, then managing the resulting trust backlash with opt-out switches rather than changing the defaults.