Skip to content

Wize AdBlock VPN Guide

Privacy Pulse and Weekly Reports: Making a Local Ad Blocker Legible

A privacy report on Android is visibility, not protection. How Wize AdBlock VPN surfaces weekly Privacy Pulse reports and what those numbers really mean.

Privacy Pulse and Weekly Reports: Making a Local Ad Blocker Legible preview

Written by the Fulldive product engineering team, based on direct inspection of the repositories listed below.

A good privacy report Android feature is not a marketing graphic. It is a weekly, honest summary of what a local ad blocker actually saw and blocked on your device. Wize AdBlock VPN ships this as Privacy Pulse, the app’s running log of DNS queries filtered, trackers touched, and weekly highlights delivered as a notification. This post explains what it shows, how it gets there, and what it deliberately does not claim.

Primary context first: Wize AdBlock VPN is a local DNS-filtering app that uses Android’s VpnService API. It is not a remote VPN, and Privacy Pulse reports reflect only what that local filter can see. Everything below flows from that constraint.

Why a weekly report at all?

A local DNS blocker running silently in the background has a communication problem. Users see the VPN key icon in the status bar and, if nothing else happens, have no way to judge whether it is working. That ambiguity leads to two failure modes:

  1. People uninstall because they cannot tell the app is doing anything.
  2. People overestimate what it is doing, because “no visible ads” can have many causes.

A weekly report cuts through both. It tells the user, in plain numbers, what the filter actually did over the last seven days. The design intent is visibility, not protection.

How Privacy Pulse ships on device

Three commits in the AdShield repo trace the Privacy Pulse feature end to end:

  • commit c8f7f968 `` introduces the weekly report notification. This is the Android notification users receive when a new week’s report is ready. It uses the standard notification channel infrastructure, not a floating banner.
  • commit 5daecf90 `` makes the notification a direct entry point into Privacy Pulse. Tapping the notification opens the in-app report, not the generic dashboard. This is a small UX decision with a large effect on whether people actually read the report.
  • commit 8c4a9eca `` aligns the weekly report view with the privacy shield UI so the report and the on-device shield use consistent language, icons, and time ranges. Without this, the weekly report and the live dashboard could disagree and erode trust in both.

What these three commits add up to is a weekly cadence that the app, not the user, remembers to surface.

What the numbers actually mean

A Privacy Pulse report surfaces counts of DNS queries the local filter acted on. Read carefully, a blocked query means:

  • An app on the device asked a DNS resolver to look up a domain.
  • That domain matched an entry on the blocklist currently loaded.
  • The resolver returned a non-routable answer, so the app could not open a connection to that domain.

A blocked query does not mean:

  • “An ad was prevented from appearing.” The same domain can serve ads, analytics, and other resources; only the DNS contact was prevented.
  • “A tracker was stopped from tracking you across the internet.” Tracking uses many channels, including first-party endpoints the filter does not touch.
  • “Malware was blocked.” A domain blocklist is not an endpoint security product.

Reading the report with that framing is the difference between useful visibility and false confidence.

Why aligning with the privacy shield matters

If you open Wize AdBlock VPN while the VPN is active, you see the live “shield” view. It shows queries that happened recently. The weekly report is the same underlying data rolled up over seven days. commit 8c4a9eca `` explicitly aligned these two surfaces so a user who sees “142 blocks today” in the live view and “1,004 this week” in the report can trust that these are the same counts from the same source.

This sounds trivial. It is not. Any time a product shows the same metric in two places computed from two sources, users eventually notice when the numbers diverge and stop believing either.

What the notification does not do

A deliberate design choice worth calling out: the weekly notification is not an advertisement for upgrades or a gamified streak. It is a data surface. The commit history reflects this restraint. There is no “you blocked more than 90% of users this week” line, and there is no engagement-loop framing. The report is useful because it is boring.

If we ever start decorating the report with encouragement or leaderboards, it stops being an evidence document and becomes marketing, and that is the moment the E-E-A-T of this product erodes.

How this fits the Pi-hole lineage

The Pi-hole project has long shipped a web dashboard that shows per-client query statistics on a home network. Wize AdBlock VPN borrows the concept and adapts it to a single device: instead of a dashboard you visit on your LAN, you get a weekly summary that arrives in the Android notification tray. The trade-off is that you cannot drill down to every query the way Pi-hole lets you, but you also do not need to run a server.

Limits: what Privacy Pulse cannot tell you

Specifically:

  • It cannot report ads not served via a blocked domain. If a domain is not on the blocklist, the query passes through and is not counted.
  • It cannot judge tracker severity. The report counts matches, it does not weight them.
  • It cannot see encrypted DNS that bypasses the local resolver. If an app on Android uses its own DoH/DoT endpoint, it can bypass the DNS filter entirely.
  • It cannot retroactively report. Queries that happened before the VPN was active, or while it was stopped, are not in the numbers.

Those four caveats are why the weekly report is a visibility tool, not a guarantee. This is consistent with our general stance laid out in What Wize AdBlock VPN can and cannot block.

Reading your first weekly report

A reasonable way to interpret your first Privacy Pulse:

  1. Check whether the top-blocked domains are ones you recognize from apps you use heavily. That is the filter doing its job.
  2. Do not treat the total number as a quality score. The count reflects both how active your phone was and how many blocklist entries matched.
  3. Compare two or three weeks rather than one. Single weeks vary based on travel, app usage, and network.
  4. If the number drops sharply, check that the VPN service is still running and has not been stopped by the system or by another VPN app taking over.

Where to go next

Sources

Last updated: 2026-04-16. Commit hashes and version numbers are drawn from Fulldive repositories inspected on 2026-04-13.