AdBloke MVP Preview

Application-level ad and tracker blocking built around local DNS filtering.

Private concept preview

Pick the apps you want protected. AdBloke prepares the blocking policy.

The current Windows MVP discovers running desktop applications, saves a protected-app policy, lets users choose a blocklist level, caches DNS-domain feeds, and previews whether the machine is ready for enforcement.

Protected apps 3
Blocked queries 184
Allowed queries 912
AdBloke Control Center

Protected Applications

Toggle apps into the local blocking policy.

Policy ready

DNS Decision Log

Domain requests are either forwarded upstream or answered locally as blocked.

Feeds cached

Core Flow

The MVP keeps the model understandable and reversible.

1
Discover running appsUsers choose which desktop applications should be protected.
2
Build a DNS blocklistSelected HaGeZi level is merged with tracking and security feeds.
3
Preview readinessAdapter, privilege, policy, and blocklist status are visible before enforcement.
4
Block by domainBlocked DNS names receive local sinkhole responses; allowed names forward upstream.

Per-App Control

Users can select specific applications instead of applying one opaque system-wide mode.

Policy persisted

Transparent Blocking

The app shows readiness, selected level, and request outcomes so protection is visible.

Counters visible

No Traffic Decryption

The DNS model blocks known ad and tracking domains without inspecting HTTPS page contents.

DNS only

A privacy control layer people can understand.

The MVP starts with DNS filtering, but the larger product direction is local, transparent privacy control across apps and platforms.

App-Level Privacy Profiles

Different protection policies per app or context, with visible controls that do not require users to understand network internals.

Transparent Blocking Intelligence

User-readable explanations of what was blocked, allowed, or flagged, and why the decision was made.

Cross-Platform Policy Model

A shared privacy posture across Windows, Android, iOS, macOS, and companion tooling, adapted to each platform's limits.

What a browser integration could unlock.

A trusted browser partner could bring AdBloke's policy model closer to the page: site-level profiles, clearer explanations, and defensive actions that make passive tracking less certain.

01

Extension or App Bridge

AdBloke can act as the policy engine while the browser keeps ownership of the browsing experience, UI, and user trust.

02

Per-Site Privacy Memory

Profiles can follow sites and contexts, so users do not have to choose between one strict global mode and constant manual exceptions.

03

Confidence Reduction

The product story moves beyond blocking: reduce the certainty advertisers and trackers have in linking activity back to one person.

Per-Site Profiles

Assign a posture by site or context.

Retail site

Shopping and ad-heavy pages get stronger tracker separation.

Ghost
Tracker confidence in cross-site identity 28%