Chrome again exempts Google from user site data settings
summary
Google Chrome is once again ignoring user-defined site data deletion settings specifically for Google-owned websites. This behavior suggests a failure in quality assurance or a deliberate choice to prioritize Google's own data collection over user privacy preferences. The author argues that such inconsistencies are unacceptable for a company of Google's resources. This pattern of behavior reinforces the need for stricter government oversight and the breakup of the Google Search monopoly.
key points
- Chrome's 'Delete data sites have saved to your device when you close all windows' setting is bypassed by google.com, allowing cookies and local storage to persist after the window is closed.
- The author identifies this as a recurring issue, as a similar bug was previously reported and fixed six years ago, implying a systematic failure in regression testing.
- Google Search results now use opaque URLs that hide the final destination, further reducing transparency and transparency for users who are not signed into the account.
who should read it
Privacy-conscious web users, software testers, and regulators who are concerned about how big tech companies handle user data and privacy settings.
discussion skeptical
consensus
Commenters generally view Google Chrome as an intrusive tool that prioritizes corporate data collection over user privacy. There is widespread agreement that the browser incorporates user-hostile features and that Google's monopoly status allows it to ignore antitrust laws with minimal consequences. Sentiment is largely cynical, with users suggesting alternatives like Firefox or Pipewire to avoid these ecosystems.
top insight
A significant point of contention is whether Chrome's failure to delete Google-specific data is a technical bug or a deliberate design choice to privilege Google's own services. One commenter notes that since closing Chrome doesn't always terminate all background processes (like the system tray process on Windows), cached data may persist, though others argue this specific behavior only affecting Google sites suggests intent.
Generated by an LLM from the article and thread. Check the sources before relying on it.