Privacy policy

Nothing to collect, so nothing is collected

Last updated: 2026

No data collection
No analytics
No remote code
No third-party services

1. Overview

FlameBlock is an ad, tracker and anti-adblock blocking browser extension for Chrome and Opera. It also includes optional, opt-in protection against browser fingerprinting and WebRTC IP leaks. It is designed to improve the browsing experience without ever reporting anything back about who is using it.

2. Data collection

FlameBlock does not collect, store, or transmit any personal data — to us or to anyone else.

  • No personal information is collected
  • No browsing history leaves your device
  • No analytics or tracking SDKs are built in
  • No data of any kind is sent to a server, because FlameBlock has none

3. Local processing

Every feature runs entirely inside your browser:

  • Network requests are filtered using the browser's built-in declarativeNetRequest engine
  • Ad and tracker elements are hidden using local content scripts and CSS-pattern matching
  • Fingerprint noise (Canvas, WebGL, audio, font metrics) is generated and applied locally, and never logged
  • Your settings, whitelist, and block counters are stored using the browser's local storage APIs, on your device only

4. Permissions and why FlameBlock needs them

declarativeNetRequest

Blocks network requests to known advertising and tracking domains, entirely on-device.

scripting

Injects the local scripts that hide ads, gate popunders in stealth mode, and apply fingerprint noise.

storage

Saves your preferences locally — language, whitelist, custom rules, toggle states.

tabs

Identifies the active tab so per-site settings (like an allowed site) apply to the right page.

webNavigation

Detects page navigation so filtering rules are (re)applied as you browse.

webRequest

Used only to observe and count blocked requests for the numbers shown in the popup — never to read or store their content.

<all_urls>

Host access is required across sites so ads and trackers can be blocked wherever they appear — not just on a fixed list of domains.

5. Optional and experimental features

A few features are off by default because of trade-offs worth knowing about before turning them on:

  • iFrame size heuristic — hides third-party frames sized like standard ad units; can occasionally hide non-ad content, which is why it's opt-in.
  • WebRTC leak protection — hides your real IP address behind a VPN or proxy, but can interfere with in-browser video calls on sites that don't route media through the proxy correctly.

Both run entirely locally, exactly like every other feature in FlameBlock.

6. Remote code

FlameBlock does not use remote code. No scripts are downloaded from external servers at runtime — all logic ships inside the extension package and is reviewed as part of each store submission.

7. Third-party services

FlameBlock does not use any third-party analytics platforms, crash reporters, or external APIs of any kind.

8. Filter lists

Ad and tracker filtering uses the same community-maintained lists used by other major blockers, along with FlameBlock's own additions and fixes as gaps are found. Applying these lists happens locally; fetching list updates does not involve any personal or browsing data.

9. Security

Because processing happens entirely on-device and nothing is transmitted, there is no server-side store of user data to secure or breach.

10. Changes to this policy

This page is updated whenever the extension's data practices change. Check back here for the current version — it's the same policy linked from the extension's store listing.

11. Contact

Questions about this policy or the extension can be sent to tidesluck@icloud.com, or via the developer contact listed on the store page.