K KLEAN
Get KLEAN
Privacy Policy

Privacy, without the fine print.

KLEAN is built to block ads and trackers locally in your browser. This policy explains what KLEAN accesses, what it stores, and what it does not collect.

Read the policy Back to KLEAN
klean.app / privacy
Request filter Blocked locally
About KLEAN

Built for a calmer browser.

KLEAN is a Chrome extension designed to reduce ad and tracking noise by filtering known advertising and tracking network requests directly in the browser.

KLEAN is not a general-purpose cloud service, account dashboard, or ad-tech platform. The product is focused on making supported browsing cleaner and less distracting while keeping the core filtering work local to the browser.
Data practices
No.

KLEAN is designed around local browser-based filtering. Its core filtering functionality operates directly in the browser using bundled rules. KLEAN does not require a user account to perform its core blocking functionality.

What KLEAN does not intentionally collect
  • Names
  • Email addresses
  • Passwords
  • Payment information
  • Health information
  • Personal communications
  • GPS or location data
  • Browsing history sent to a remote server
KLEAN may access page and network information only insofar as it is needed to perform its filtering functions or respond to browser events when the user invokes extension controls.
Permission overview

Chrome Web Store Privacy Disclosure

KLEAN’s Chrome Web Store privacy declarations describe the extension’s actual handling of user data and permissions. The permissions below are used to enable webpage and request filtering as part of the extension’s purpose.

Permission Why KLEAN needs it
declarativeNetRequest Block known advertising and tracking network requests using bundled filtering rules.
activeTab Allow extension controls to interact with the currently active webpage when invoked by the user.
storage Store extension preferences and applicable local statistics.
webNavigation Respond to page navigation events required by the extension’s site-specific behavior.
Host permissions Apply filtering and site controls across HTTP/HTTPS webpages.
declarativeNetRequest
Why KLEAN needs it Block known advertising and tracking network requests using bundled filtering rules.
activeTab
Why KLEAN needs it Allow extension controls to interact with the currently active webpage when invoked by the user.
storage
Why KLEAN needs it Store extension preferences and applicable local statistics.
webNavigation
Why KLEAN needs it Respond to page navigation events required by the extension’s site-specific behavior.
Host permissions
Why KLEAN needs it Apply filtering and site controls across HTTP/HTTPS webpages.
Local by design

Your browser. Your rules. Your data.

KLEAN performs its core filtering locally using bundled rules. The browser decides what request is blocked, what is allowed, and when an extension interaction is invoked.

Browser
Network request
KLEAN filter
Allowed / Blocked
What KLEAN does

Single-purpose browser filtering.

KLEAN’s core purpose is to reduce ad and tracking noise by filtering known advertising and tracking requests while leaving the rest of the page available to the user.

declarativeNetRequest

Request filtering

KLEAN may use Chrome’s declarativeNetRequest API and bundled filtering rules to block known advertising and tracking network requests before they complete.

activeTab

Active webpage interaction

KLEAN may use activeTab for interactions with the currently active webpage when the user invokes extension controls, such as toggling site behavior or applying a current-page action.

storage

Preferences and local stats

Chrome storage may be used to retain extension preferences and local statistics where applicable. This is for user configuration and extension behavior, not for remote user profiling.

Host permissions

Page-level enforcement

Host permissions give KLEAN access to HTTP/HTTPS webpages so it can enforce page-level filtering and site controls where the extension is designed to operate.

Third-party resources

Included filter lists.

KLEAN may use third-party filtering resources where applicable, including EasyList and EasyPrivacy. Those resources are provided by their respective third-party maintainers and are subject to their own licensing and attribution requirements.

KLEAN does not claim ownership of EasyList or EasyPrivacy. Applicable third-party licenses and attribution notices are included with the extension distribution where required.
User controls

Controls stay with the user.

KLEAN provides user controls for its protection features where supported by the extension. These controls are designed to let a user manage browser filtering behavior without requiring an external account or server-side profile.

✓
Browser-local settings

Settings are stored locally in browser storage where applicable so the extension can remember the user’s chosen preferences.

✓
Site-specific controls

Where supported, KLEAN may expose page- or site-level controls to allow the user to manage how filtering applies on a particular site.

Security

Minimize unnecessary handling.

KLEAN is designed to minimize unnecessary data handling and keep its core filtering functionality local. It does not rely on a remote executable code path for its main functionality.

KLEAN does not use remote executable JavaScript to perform its core filtering. In the current implementation, executable JavaScript is bundled with the extension rather than downloaded and executed remotely. This means the product’s main functionality is not built around a server-side processing pipeline.
Updates

We may update this policy.

We may update this Privacy Policy when KLEAN’s functionality, data practices, or applicable requirements change. The latest version will always be published on this page.

Last updated: September 2026
Privacy contact

Questions about privacy?

Placeholder: replace with the real KLEAN privacy contact email before publishing.