Tell HN: Android Chrome deletes your browsing history silently

TL;DR

Android Chrome is silently deleting user browsing history, even when "Clear browsing data on exit" is off and history sync is enabled. This results in significant loss of browsing data, both locally and often from synced Google accounts. While Google has reportedly marked a bug report as "WontFix – by design", users are experiencing this as a regression. Workarounds include disabling history sync, using Chrome Beta/Canary (where the issue may not be present), or switching to an alternative browser like Firefox or Brave.

What's Happening?

I've observed that Chrome on Android is silently deleting a substantial portion of my browsing history. These deletions occur without any user interaction, such as tapping "Clear browsing data" or enabling Incognito mode for those sessions. The absence of alerts, error messages, or "History cleared" notifications makes this deletion particularly insidious.

Observations and Details:

• Missing entries: Up to 30% of URLs that should appear in History -> Recent tabs vanish after a relatively short period, often within 24 hours to a few days.
• Silent deletion: No UI notifications, toast messages, or log entries (e.g., in adb logcat or Chrome UI) indicate that data is being cleared.
• Scope of deletion: While one report noted global deletion of all entries, other observations indicate a partial loss of entries rather than a complete wipe. The true loss of data has been verified by comparing exported history databases before and after the events.
• Sync impact: With Chrome sync enabled, the missing entries are also absent from synchronized history on desktop Chrome and Google Activity dashboards, indicating the local deletion propagates to the cloud.
• Affected versions: This issue has been reported on Chrome versions 108.0.5359.157 and 124.0.6367.91 (stable) on Android 12, 13, and 14 (e.g., Samsung Galaxy S23).

Possible Causes:

1. Storage-optimization cleanup: Chrome might be aggressively pruning older entries to remain under a hidden quota.
2. Sync conflict resolution: A truncated history from a desktop client could be overwriting the mobile client's local copy.
3. Bug in the "History" UI: It's conceivable the UI is merely filtering entries that are still present in the SQLite DB, though direct database inspection refutes this in some cases.
4. Google-side policy / "WontFix – by design": This could be an intentional, privacy-focused update that auto-deletes "low-value" history after a certain age, or a bug where an "auto-clear after 24h" feature (intended for Incognito) is mistakenly applied to regular browsing. Google's bug tracker has reportedly marked a similar issue as "WontFix – by design", implying it's an intended behavior.

Workarounds and Solutions:

• Disable history sync: Turning off Sync -> History can prevent local deletions from propagating to your Google account, and in some cases, has been reported to stop the deletions locally.
• Use Chrome Beta/Canary: The issue may not be present in newer beta versions of Chrome (e.g., Chrome 112 beta).
• Switch browsers: Alternative browsers like Firefox for Android or Brave are reported to retain history reliably.
• Report the bug: Continue to file bug reports within the Chrome Help Center or Chromium issue tracker to highlight the user impact.

If you rely on a complete browsing history, consider these workarounds until Google provides a clear statement or a fix.