// LEGAL

Privacy Policy

Last updated: March 2026 · Applies to ClearBrowse Chrome Extension v1.0.0+

// TL;DR — THE SHORT VERSION

✓

We collect zero data about you or your browsing.

✓

No analytics, no telemetry, no crash reports sent anywhere.

✓

Your settings live only on your device via Chrome's local storage.

✓

We have no servers. Nothing you do is ever transmitted to us.

1. Overview

ClearBrowse ("the Extension") is a free Chrome browser extension for clearing browser data — cache, cookies, history, and more. It is developed and maintained by Brutal. Questions can be sent via the contact form.

This policy explains what data the Extension accesses, how it is used, and where it is stored. All processing happens locally on your device and nothing is ever sent to us or any third party.

2. Data We Collect

We collect no data whatsoever.

ClearBrowse does not collect, transmit, store on remote servers, or share any personal information, browsing history, or usage data. There are no analytics, no telemetry, no error reporting, and no usage statistics sent anywhere.

3. Permissions and What They're Used For

The Extension requests the following Chrome permissions. Each one is used solely to provide local functionality:

browsingData — the core permission that enables clearing cache, history, cookies, downloads, form data, local storage, service workers, and passwords via Chrome's native chrome.browsingData API. No browsing data is ever read or transmitted — it is only deleted locally.
cookies — used to implement the domain whitelist feature. When you have domains on your whitelist, ClearBrowse reads the list of cookies to identify which ones belong to whitelisted domains before deleting the rest. Cookie values are never read, logged, or transmitted.
storage — saves your settings (last cleaned time, whitelist entries, auto-clean toggle) locally via chrome.storage.local. Settings never leave your device.
windows — used only to detect when the last Chrome window closes, so the auto-clean on close feature can trigger. The Extension does not read window content or URLs.

      Note on the cookies permission: This permission is required to implement the whitelist — Chrome's browsingData API clears all cookies for a domain without allowing exceptions. ClearBrowse works around this by reading cookie metadata (domain and name only) to re-protect whitelisted cookies after a clear. Cookie values are never accessed.
    

4. chrome.storage.local

Your settings are stored using Chrome's built-in chrome.storage.local API. Unlike chrome.storage.sync, local storage is never synced to Google's servers — it stays on the device where ClearBrowse is installed.

Stored values include: the timestamp of the last clean, your cookie whitelist domain entries, and the auto-clean on close toggle state. None of this data is sensitive and none of it leaves your device.

5. Third Parties

ClearBrowse does not integrate with, communicate with, or share data with any third-party services, APIs, analytics platforms, or advertising networks.

There are no external network requests made by the Extension at any time.

6. Children's Privacy

ClearBrowse does not collect any data from anyone, including children. The Extension is suitable for all ages.

7. Changes to This Policy

If this policy changes in a meaningful way — for example if a future version adds any form of data collection — the policy will be updated with a new date and the change will be noted clearly. We will never introduce data collection silently.

8. Contact

Questions or concerns about this policy can be directed via the contact form.