QuietBrowse Privacy Policy

Last updated: July 15, 2026

QuietBrowse collects no personal data. We do not operate servers that receive your browsing history, passwords, or identity. The extension works entirely inside your browser.

What stays on your device

QuietBrowse stores the following locally using Chrome's extension storage APIs (chrome.storage.local and chrome.storage.session):

Your settings (protection on/off, site rules, feature toggles)
Block statistics (estimated counts per day and total)
Trackers learned by the heuristic engine
Elements you manually "zapped" to hide
Cached cosmetic filter data from filter-list updates

Removing the extension deletes this data. We cannot access it remotely.

Network connections

By default, QuietBrowse downloads public ad-blocking filter lists from:

These requests go directly from your browser to easylist.to. QuietBrowse does not proxy, log, or relay that traffic. EasyList's own privacy practices apply to those requests.

If you enable optional lists in Settings, additional requests go to:

Fanboy Annoyance / Cookie / Social — secure.fanboy.co.nz

If you add a custom filter-list URL in Settings, QuietBrowse also downloads that list directly from the URL you provide.

All filter-list downloads go directly from your browser to the respective host. QuietBrowse does not proxy, log, or relay those requests.

What we do not do

No accounts or sign-in
No analytics, crash reporting, or telemetry SDKs
No selling or sharing of data (there is no data to sell)
No remote code execution except filter-list text compiled locally
No affiliation with Microsoft, Google, or antivirus vendors

Permissions

QuietBrowse requests broad host access because blocking ads and trackers requires inspecting network requests on pages you visit. Each permission is used only for the features described in the extension and in our permission documentation. See the source code — behavior is verifiable.

Children

QuietBrowse is not directed at children under 13 and does not knowingly collect information from anyone.

Changes

If this policy changes, the updated version will ship with a new extension release. Material changes will be noted in release notes.

Contact

For privacy questions about QuietBrowse, contact the developer through the Chrome Web Store listing support channel or the project's public repository.