Privacy Policy for Obsidian AdBlocker Pro

This Privacy Policy explains how Obsidian AdBlocker Pro, a Chrome extension by Pascual Labs, handles data while blocking ads, trackers, cookie banners, and unwanted page elements.

1. Single purpose

Obsidian AdBlocker Pro has one purpose: to block ads, trackers, cookie consent banners, distracting page elements, and unwanted cosmetic content on websites visited by the user. It uses local filtering rules, user settings, whitelists, and an optional element picker so users can control what is hidden or blocked in their browser.

2. Data collection

Obsidian AdBlocker Pro does not collect or transmit:

• Personally identifiable information
• Browsing history or visited URLs
• Website content or page text
• User activity across websites
• Authentication information
• Financial, health, or location information
• Personal communications

The extension does not use analytics, tracking pixels, remote logging, advertising identifiers, or user accounts.

3. Local processing

Network request blocking is performed locally by Chrome using the declarativeNetRequest API. Cosmetic filtering, cookie banner cleanup, and the element picker also run locally inside the user's browser. The extension does not send page content, browsing history, or filtering activity to Pascual Labs or to any external server.

4. Local storage

The extension stores a small amount of data locally in chrome.storage.local so it can remember user preferences. This may include:

• Whether blocking is enabled or disabled
• Selected filter categories
• Whitelisted domains
• Custom element-picker rules created by the user
• Local blocked-item counters shown in the extension popup or badge

This information stays on the user's device. Pascual Labs does not receive it.

5. Chrome permissions

Obsidian AdBlocker Pro requests only the permissions needed for ad blocking and page cleanup:

• declarativeNetRequest: used to block unwanted network requests locally through Chrome's native filtering engine.
• declarativeNetRequestFeedback: used to update local blocked-item counters and badge statistics when a local rule is matched.
• storage: used to save user preferences, whitelists, custom rules, and local counters on the user's device.
• activeTab: used when the user interacts with the extension on the currently active tab.
• webNavigation: used to reset per-tab counters and keep the extension badge state accurate when pages navigate.
• scripting: used to inject the element picker and local page cleanup scripts when required.
• Host access (<all_urls>): required so ad blocking and cosmetic filtering can work across websites visited by the user.

6. Third-party services

Obsidian AdBlocker Pro does not send browsing data to third-party services. The extension may include local filter rules derived from public ad-blocking rule lists. These rules are packaged with the extension and applied locally by Chrome.

7. Data sharing and sale

Pascual Labs does not sell, rent, transfer, or share user data from Obsidian AdBlocker Pro. Because the extension does not collect browsing data or personal information, there is no such data for us to sell or share.

8. Children

Obsidian AdBlocker Pro is not directed at children under 13. Pascual Labs does not knowingly collect personal information from children.

9. Changes to this policy

If this Privacy Policy changes, the "Last updated" date above will be updated. Material changes will be reflected on this page.

10. Contact

Questions about this policy can be sent to hello@pascuallabs.com.