AdBloPrivacy Policy
AdBlo does not collect, transmit, store or sell any personal information. There is no analytics code, no account system and no server to send anything to. This page explains what that means in detail.
Everything AdBlo stores lives in your own browser. Nothing leaves your device. We could not identify you or reconstruct your browsing if we wanted to, because we never receive any of it.
1. What we collect
Nothing. AdBlo contains no telemetry, no analytics library, no crash reporter, no advertising identifier and no unique installation ID. The extension makes no network requests of its own at any point.
This is verifiable rather than a promise: AdBlo is open source under GPL-3.0, and the extension package contains no networking code outside the filter list compiler, which runs on the developer's machine at build time and is not shipped to users.
2. What AdBlo stores on your device
The extension keeps the following in Chrome's local extension storage. None of it is transmitted anywhere, and all of it is deleted when you uninstall.
| Stored | Why |
|---|---|
| Which filter lists are enabled | To apply your choices on the next page load. |
| Your own custom filters | To compile them into blocking rules. |
| Paused and trusted sites | To keep blocking off where you asked for it to be off. |
| Block counts and estimated bandwidth | To show the numbers in the popup and dashboard. |
| Your settings | Cosmetic filtering, badge, stealth mode and so on. |
| Recent blocked requests | For the Logger. Held in session memory and cleared when the browser closes. |
You can export all of it as a plain JSON file from the dashboard, inspect it in any text editor, and reset the statistics at any time.
3. Permissions, and why each is needed
Chrome shows a permission list at install time. Here is what each one is actually used for.
| Permission | Used for |
|---|---|
| declarativeNetRequest | Applies the blocking rules. Chrome matches them internally — the extension never sees your requests. |
| storage | Saves the settings listed above, locally. |
| tabs | Reads the current tab's address so the popup can show which site you are on and scope a pause to it. |
| scripting | Applies element hiding and injects the element picker when you ask for it. |
| contextMenus | Adds "Zap this element" to the right-click menu. |
| alarms | Ends a timed pause on schedule. |
| Access to all websites | Element hiding must work on whichever sites you visit. AdBlo does not read, record or transmit page content. |
Optional permissions
Three permissions are not requested at install. Chrome asks
for them only at the moment you switch on the feature that needs them, and
you can revoke them at any time from chrome://extensions.
- declarativeNetRequestFeedback — only if you turn on detailed logging in the Logger.
- contentSettings — only if you turn on Stealth mode, to block camera, microphone and location.
- privacy — only with Stealth mode, to set the WebRTC policy and disable hyperlink auditing.
4. Third parties
There are none. AdBlo uses no third-party SDKs, no advertising networks, no analytics providers and no cloud services. No data is shared with anyone, because no data is collected in the first place.
AdBlo's filter lists are compiled from public sources including EasyList and EasyPrivacy. That compilation happens before release, on the developer's machine. Your browser never contacts those projects.
5. This website
These pages load no third-party scripts, no web fonts, no trackers and no advertising. Standard server access logs may record your IP address and browser for security and diagnostics, as with any website; they are not used to build a profile of you.
6. Children
AdBlo is suitable for all ages and collects no data from anyone, including children under 13.
7. Your rights
Regulations such as the GDPR and CCPA give you rights to access, correct, export and delete personal data held about you. We hold none, so there is nothing to request. The data on your own device is yours: export it from the dashboard, or remove it entirely by uninstalling the extension.
8. Changes
If this policy ever changes, the date at the top of this page changes with it. Should a future version of AdBlo ever collect anything at all, it will be opt-in, stated plainly here, and announced before release.
9. Contact
Questions about this policy: sent message to BunkLyf LinkedIn Page. Security issues: sent message to BunkLyf LinkedIn Page.
Template notice: replace the contact addresses and the domain above with your own before publishing, and have a lawyer review this if you operate in a jurisdiction with specific disclosure requirements. It describes AdBlo's actual behaviour accurately, but it is not legal advice.