Where the data goes
Measurements across typical ad-supported apps consistently show: a news app spends 30–50% of its traffic on ads and their measurement; a casual game can spend more on ad preloading than on gameplay; a weather app may download 2–5 MB of ad assets to show a 3 KB forecast. Multiply by every free app on your phone, every day.
The pattern is structural: ad SDKs preload video assets, refresh banners on timers, and fire tracking beacons on events. None of it waits for you to ask.
The math of a month
| Usage profile | Ad & tracker traffic/day | Wasted per month | Saved with blocking |
|---|---|---|---|
| Light (news + 2 games) | ~60 MB | ~1.8 GB | ~1.6 GB |
| Moderate (social + games) | ~150 MB | ~4.5 GB | ~4 GB |
| Heavy (many free apps) | ~300 MB | ~9 GB | ~8 GB |
NULLOG's live counters make this personal instead of statistical: the dashboard tracks blocked requests and estimated bandwidth saved on your actual usage — users commonly see 300–500 MB saved in the first days, gigabytes over a billing cycle. On capped or roaming plans, that is real money.
Why DNS-level blocking beats "Data Saver" mode
Android's built-in Data Saver throttles background transfers but cannot tell an ad from content — apps keep downloading what they can. A blocklist firewall prevents the requests from starting: the banner never loads, the beacon never fires, the radio never wakes. Data is saved because the transfer simply never happens, and battery is saved with it.
Set it up once, forget it
- Install NULLOG and start protection — filtering is automatic for all apps, no per-app configuration needed.
- Check the weekly Sunday briefing for your personal savings tally (requests blocked, MB preserved, threats stopped).
- On limited plans, add Data Saver on top as a second layer for the apps you deliberately bypass.
Put it into practice with NULLOG
NULLOG runs every technique in this guide locally on your Android — ads, trackers and telemetry filtered in device memory. No root. No cloud. No logs.
Download NULLOG APK (v1.0.2)