Clear Site Data

Clear Site Data is a small Chrome extension for quickly resetting the current site in your browser profile.

It is designed for people who need a clean local session without digging through Chrome settings, including SEO testing, web development, QA checks, forum administration, support workflows, and everyday privacy cleanup.

Click the extension icon once to show OK?, then click it again within 3 seconds to clear data for the active site. The extension shows CLR while clearing, then shows OK on the icon badge after Chrome reports that clearing completed. The current tab may need to be reloaded after clearing so the page reads the new clean state.

Clear Site Data uses Chrome's built-in chrome.browsingData.remove() API with the active tab's site origin and, for normal domain names, closely related bare/www plus http/https origins.

It is designed to clear current-site data types that Chrome supports through site-specific browsing data removal:

• Cookies for the broader registrable domain where Chrome's cookie scoping applies
• Local storage (localStorage) for the active site origin and its bare/www sibling origin
• IndexedDB for the active site origin and its bare/www sibling origin
• CacheStorage for the active site origin and its bare/www sibling origin
• Service workers for the active site origin and its bare/www sibling origin
• Site cache for the active site origin and its bare/www sibling origin
• WebSQL and file system storage for the active site origin and its bare/www sibling origin where still supported by Chrome

Cookies are cleared more broadly because login and session cookies are often shared across subdomains. Other storage and cache types are origin-scoped, so Clear Site Data also checks the active site's bare/www sibling and http/https variants for normal domain names without intentionally wiping unrelated subdomains. Localhost, IP addresses, and custom-port origins stay scoped to the exact clicked origin.

These local data types are commonly used for logins, sessions, cached files, offline app data, test states, and tracking identifiers. Clearing them can help reset logins, remove local site identifiers, clear broken test states, and show how a site behaves as a fresh visitor.

Clear Site Data does not currently clear sessionStorage, because Chrome's browsingData API does not expose it as an origin-scoped removal type. Support for clearing sessionStorage may be added later if it can be done cleanly without making the extension feel invasive.

It also does not clear browser-wide data such as saved passwords, browsing history, download history, autofill data, extension data, or fingerprinting/server-side identifiers.

This extension is not a VPN, anonymity tool, anti-fingerprinting system, or guarantee against all tracking. Sites may still recognize visitors through accounts, IP addresses, browser fingerprinting, server-side records, third-party cookies, or other signals. The goal is simple local site cleanup, not identity hiding.

Clear Site Data does not currently clear unrelated third-party cookie domains loaded by the current site. This can matter on a small percentage of websites that use aggressive tracking, anti-adblock, or embedded third-party login/session tricks.

For example, if a website depends on a third-party cookie from a domain such as btloader.com, clearing the current site's data may not remove that external cookie.

Clear Site Data intentionally avoids this for now because removing unrelated third-party cookies would require broader cookie access and host permissions. That would make the extension more invasive, harder to explain, and more likely to clear data the user did not expect. The current goal is simple current-site cleanup, not browser-wide cookie management.

Clear Site Data shows a neutral CLR badge while Chrome is processing the clearing request, then shows a green OK badge only after Chrome reports that the request completed. If the active page is unsupported or Chrome cannot complete the clearing request, the extension shows a red ERR badge instead.

Badge feedback is tied to the active tab when Chrome provides a valid website tab. Unsupported pages such as chrome:// pages, extension pages, or other internal browser pages may show ERR because there is no normal website origin to clear.

Badge cleanup is also tracked per tab, so newer confirmation or result badges are not cleared by older feedback timers. Confirmation uses a neutral OK? badge.

The two-click confirmation is bound to the tab and site origin from the first click. A pending confirmation is single-site at a time. If you switch tabs or sites before confirming, the previous confirmation is canceled and the new active site must be confirmed separately.

During clearing, the extension action is temporarily disabled only for the confirmed tab to prevent duplicate clears while keeping the behavior tied to that tab. Other tabs can still be confirmed and cleared separately after starting a new confirmation.

Clear Site Data does not collect, store, transmit, sell, or share user data. All clearing happens locally through Chrome's built-in chrome.browsingData.remove() API after the user clicks the extension.

Clear Site Data uses only the permissions needed for its single purpose:

• browsingData: clears cookies, cache, local storage, IndexedDB, CacheStorage, service workers, WebSQL, and file system storage for the current site.
• activeTab: reads the active tab's current website origin only after the user clicks the extension icon.

Clear Site Data intentionally does not request the cookies permission or broad host permissions for third-party cookie domains.

• Explicitly keeps normal website origin clearing enabled without clearing protected hosted app data.
• Clears related bare/www and http/https origins for normal domain names.
• Keeps localhost, IP addresses, and custom-port origins scoped to the exact clicked origin.
• Improves cleanup for sites that split storage between example.com and www.example.com.
• Keeps clearing limited to Chrome's browsingData API without adding cookie or host permissions.
• Documents why unrelated third-party cookie domains are not cleared for now.

• Added Manifest V3 support for Chrome.
• Added two-click confirmation before clearing site data.
• Binds confirmation to the original tab and site origin to avoid clearing a different site after switching tabs.
• Documents that pending confirmation is single-site at a time.
• Documents the minimal browsingData and activeTab permission usage.
• Refines the extension description to mention cookies, cache, and storage directly.
• Uses the tab provided by Chrome for the extension click instead of querying the active tab again.
• Claims the confirmed tab before async cleanup to avoid duplicate clear races.
• Tracks running clears per tab to block duplicate clears without blocking unrelated tabs.
• Prevents older badge timers from clearing newer confirmation or result badges.
• Uses neutral, green, and red badge colors for confirmation, success, and errors.
• Shows CLR while Chrome processes the clearing request.
• Logs non-fatal extension errors to the service worker console for debugging.
• Temporarily disables the extension action only for the confirmed tab during clearing.
• Clears cookies for the broader registrable domain where Chrome's cookie scoping applies.
• Clears local storage, IndexedDB, WebSQL, file systems, cache, CacheStorage, and service workers for the active site origin.
• Uses Chrome's built-in chrome.browsingData.remove() API.
• Uses minimal extension permissions with browsingData and activeTab.
• Uses one extension icon with badge-only feedback after confirmation, success, or unsupported pages.
• Does not collect, store, transmit, sell, or share user data.
• Shows ERR when clearing is unsupported or fails.
• Supports split incognito mode.