Privacy policy

The short version

Freebuff Ad Block has no server and no backend. It does not collect, store, transmit, sell or share personal data, and it never contacts anything operated by us. All of its work happens locally in your browser, on one site: freebuff.com.

What the extension does

It removes the advertising slots that appear inside the freebuff.com web app. It does that in three ways: a declarativeNetRequest ruleset stops requests to known ad and tracker hosts before they leave the tab, a content script clears out slots the page injects while a build is running, and a picker lets you hide anything the heuristics miss. Nothing in that process reads, copies or sends your data anywhere.

What is stored, and where

Two things, both in your browser's own extension storage. We have no way to read either:

• Your on/off setting — one boolean, whether blocking is enabled.
• Element rules you create yourself — the CSS selectors saved when you use Hide an element on the page.

These live under the keys freebuffAdBlockEnabled and freebuffAdBlockSelectors. If you are signed in to Chrome, Edge or Brave, your browser may sync extension storage through your own account (storage.sync). That transfer is between you and your browser vendor, under their privacy policy — it never passes through us, because there is nothing of ours for it to pass through. Signing out or disabling browser sync keeps the data entirely on the device.

A per-tab count of hidden elements is kept in storage.session so the toolbar badge can show it. Session storage is cleared by the browser when it closes, and it is never written to disk by us.

Network activity

The extension makes no network requests of its own. There is no analytics, no telemetry, no crash reporting, no update ping, no remote configuration and no advertising SDK. Every part of it — the ruleset, the content script, the popup — ships inside the package, so there is no remote code to fetch and nothing to execute that did not arrive with the install.

It does change what your browser requests on freebuff.com: the ruleset blocks requests to known ad and tracker hosts when those requests originate from a freebuff.com page. A blocked request is dropped locally. That event is not logged, counted or reported anywhere. A priority-100 allow rule covers freebuff.com's own traffic, so the extension never blocks the site itself.

Permissions, and why each one is needed

• declarativeNetRequest — block requests to known ad-network hosts that originate from freebuff.com pages.
• storage — remember your on/off setting and the element rules you create with the picker.
• Host access: *://freebuff.com/* and *://*.freebuff.com/* — the content script has to read freebuff.com pages to find and hide the ad slots the page renders itself.

That is the whole list. The extension requests nothing else: no access to your other tabs, your browsing history, your bookmarks, your downloads or your clipboard, and no ability to inject anything into a site other than freebuff.com.

Third parties

There are none in the product. No analytics providers, no advertising networks, no data brokers, no affiliates and no SDKs receive anything from this extension. The only third parties involved are the browser vendors: if you install from the Chrome Web Store, Microsoft Edge Add-ons or addons.mozilla.org, that store handles the download and any review under its own privacy policy.

This website

The page you are reading is static HTML, CSS and JavaScript. It sets no cookies, runs no analytics, loads no third-party scripts, fonts or pixels, and does not profile you in any way. Our hosting provider keeps standard server access logs — IP address, user agent, requested path — for security and abuse prevention, as any web host does.

Children

The extension is not directed at children under 13. Because it collects no data at all, there is no personal information from any age group to manage, disclose or delete.

Changes to this policy

If the extension's data behaviour ever changes, this page is updated before that version ships. The extension is built so that a change in data handling would be visible in its source: there is no server to quietly start talking to.

Contact

Questions, or a privacy concern? Email workofma@gmail.com, or open an issue at github.com/developer-mohanaditya/freebuff-ad-blocker/issues.

Last updated: 1 October 2026 · applies to Freebuff Ad Block 1.3.0 and later.