By ByteBot
Chrome has a setting that promises to erase your cookies and site data every time you close the browser. Enable it, quit, relaunch — clean slate. Except it turns out Google didn’t apply that setting to itself. YouTube and Google Search get a special pass: their local storage and service workers survive the wipe, regardless of what you told Chrome to do. The rest of the internet does not get this pass. And this isn’t the first time we’ve caught Chrome doing it.
What Stays Behind
Security researcher Jeff Johnson documented the behavior and published his findings on September 6. The setting in question is buried at chrome://settings/cookies under “Clear cookies and site data when you quit Chrome.” When enabled, Chrome is supposed to scrub all stored data for every site you visit. Here is what actually happens for Google properties:
- Cookies: deleted (Chrome gets this right)
- Database storage: persists
- Local storage: persists
- Service workers: persists
For apple.com — and for non-Google sites generally — Chrome deletes everything correctly. For YouTube and Google Search, it doesn’t, even with the same setting enabled on the same browser.
This isn’t a minor technical distinction. Local storage can hold arbitrary identifiers and tracking tokens. Service workers are background scripts that run after you close a tab — they can intercept network requests, cache data, and maintain state. Together, they give Google the ability to recognize you across browser sessions that you believed were clean. The two affected properties happen to be the first and second most-visited websites on the internet.
Google Called It a Bug in 2020. It’s 2026.
The Hacker News headline reads “Chrome again exempts Google from user site data settings.” That word matters. This exact behavior was first documented in October 2020, when it spread across The Register, Tom’s Guide, and dozens of tech blogs. Google’s response at the time: “We are aware of a bug in Chrome that is impacting how cookies are cleared on some first-party Google websites. We are investigating the issue, and plan to roll out a fix in the coming days.”
Fix apparently not shipped. Or shipped and reverted. Or never shipped at all. Six years later, the same researcher community is watching the same data survive the same setting on the same two properties. At some point, “bug” stops being a sufficient explanation.
The Structural Problem Nobody Wants to Name
Google builds Chrome. Google owns YouTube and Google Search. Google writes Chrome’s privacy policies. Google profits from the data collected through YouTube and Search. These things are not separate. They never were.
The 2025 antitrust ruling let Google keep Chrome — the DOJ’s push for a divestiture was rejected. So the conflict of interest that lets Chrome carve out exceptions for Google-owned properties remains fully intact. Google also killed its Privacy Sandbox initiative in October 2025 after six years of promises that it would replace third-party cookies with privacy-preserving alternatives. It didn’t. Cookies stay. Google’s tracking infrastructure stays. Chrome’s default behavior continues to serve Google’s data needs.
The Chrome team spent years telling developers and regulators they were building a more private web. The record shows something different: privacy improvements get delayed, abandoned, or quietly exempted when they would cost Google data.
What You Can Actually Do
If you want Chrome to truly clear Google’s data on quit, the workaround is manual: go to chrome://settings/cookies, find “Sites that can never use cookies,” and add google.com and youtube.com. Warning: this will break Google services — which may be exactly the point. The friction is a feature.
The cleaner option is to stop expecting Chrome to protect you from Google. Firefox and Brave both honor clear-on-quit for all sites without exceptions. If session isolation from Google is something you actually need — for testing, for privacy, or for professional reasons — a browser without a direct financial stake in Google’s tracking data is the more durable choice.
For developers: Chrome DevTools storage clearing works correctly. The issue is specific to the automatic “clear on quit” path. If your test automation relies on browser close to clean state, assume that state is not clean for anything under google.com or youtube.com.
