Privacy, in plain language.
This policy covers BLOKU 2.0 and bloku.app. The extension is designed to keep your browsing data on your device.
Updated November 2, 2026
This policy describes BLOKU 2.0. For earlier extension versions, also read the legacy notes below.
What the extension stores
BLOKU processes website addresses, network request and frame context, and page content locally to filter ads and trackers, hide elements and apply your chosen privacy and focus controls. Its filtering library observes requests and navigation temporarily; persistent request logging and telemetry are disabled. Browser storage holds settings, filter state, site exceptions, saved selectors, local rules, focus profiles and session deadlines. Daily allowances use observed active time only on sites you configure; idle periods, unfocused windows and long observation gaps do not count. By default, only today's counters needed for allowances are kept. Optional local history retains summaries for up to 90 days; turning history off deletes older summaries. The filtering library also temporarily processes request and response headers, which may include Cookie and Set-Cookie values containing session identifiers. These details are processed locally, are not retained as request logs or uploaded by BLOKU, and are not used to change cookies.
What the extension sends
BLOKU 2.0 requires no account or license validation and does not contact the legacy billing backend. It does not automatically send browsing history, request logs, page content, focus activity or settings to Frameless, AdGuard, DuckDuckGo or a telemetry service. Filters, scripts and consent rules are packaged in the extension. Chrome delivers extension updates through its normal Chrome Web Store update service. BLOKU follows the Chrome Web Store User Data Policy and its Limited Use requirements when handling information through Google APIs.
The website
This website does not load Google Analytics or other analytics scripts. It stores your theme preference in your browser. Our hosting provider processes the ordinary request information needed to deliver the site. Links to the Chrome Web Store and other services follow those services' policies. Chrome automatically opens this website’s welcome page after a fresh installation and its goodbye page after uninstalling BLOKU. These separate website visits expose ordinary request metadata, such as your IP address, browser request headers and access time, to the website host. BLOKU does not append identifiers, visited website addresses, settings or local activity to these page URLs. These visits are separate from locally processed browsing history; using BLOKU requires no account or license.
Support and previous payments
If you email us, we receive the information you choose to share so we can respond. Earlier paid versions used Polar for payment and subscription records. These historical records are separate from local extension data; uninstalling does not delete them. Contact support for questions about those records.
Your choices
Cookie-dialog rejection, clicked-link tracking cleanup and YouTube autoplay controls are optional choices. Rejection works only on supported dialogs; unsupported dialogs remain usable. The limited website privacy preference exposes navigator.globalPrivacyControl to page scripts as a do-not-sell/share preference. BLOKU does not send the Sec-GPC HTTP header, so this is not complete Global Privacy Control (GPC) support. BLOKU does not promise anonymity or complete fingerprint protection. In settings, you can export settings or delete local activity. Removing the extension removes its browser-managed local storage; exported files remain wherever you saved them. Clear site data for bloku.app to remove this website's theme preference. Export settings you want to keep before removing them.
Contact and changes
For privacy questions, email support@bloku.app. We update this page when our practices change and keep the effective date visible.
Earlier versions and records
Earlier versions may retain license or device identifiers and attempt requests to the legacy license-validation service. Their counters are estimates. Do not assume that BLOKU 2.0's data practices apply to earlier versions. Previous payment and support records are separate from local extension data. For questions about these records or earlier versions, email support@bloku.app.
Optional support through PayPal
The optional support link takes you to PayPal only when you choose it. No PayPal payment scripts or forms load on this website. PayPal processes the payment under its own policies and may share payer and transaction details with us so we can manage support payments and required records. You choose the amount; fees or currency conversion may apply. Support does not change access to BLOKU features.
PayPal privacy policy