Photo by FlyD on Unsplash
Most parental control apps say some version of "blocks inappropriate content" — it's easy to assume that's one thing. It isn't. Where the filtering decision happens, on the device or on a server it talks to, changes what data leaves the phone.
Every time an app opens a web address, the device first resolves that address to a server location — DNS resolution. Content filtering almost always works by intercepting that step: check the domain's category, then either let it resolve or block it. True whether filtering is on-device or cloud-based — the difference is where that check happens.
The device sends DNS requests out to a third-party filtering service, which checks and responds. This works, but every domain your kid's device tries to reach passes through an external company's servers first. Not necessarily sinister — but a running log of your family's browsing now exists on infrastructure you don't own and didn't set the retention policy for.
A blocklist lives on the device, gets checked locally, decision made right there — nothing round-trips to an external server for the purpose of filtering. Browsing activity doesn't get routed through a third party as part of how the filter works. Not a promise layered on top — what the mechanism actually does.
Cloud services update centrally and can apply more sophisticated (ML-based) classification; an on-device blocklist is only as current as its last update. For most parents, "which category does this domain fall into" is a solved-enough problem that the currency tradeoff is small — the privacy tradeoff is the one that actually matters day to day.
Content filtering blocks by domain category — it doesn't evaluate posts or messages inside an already-allowed app. That's a fundamentally different, much harder problem than category-level blocking.
Marketing pages rarely say where filtering happens, so ask directly. A trustworthy answer is specific and easy to find.
None of these need a technical background to ask, and the way an app answers usually tells you how seriously it takes privacy.
Paxio's content filtering resolves DNS locally — blocklist on the phone, category check on the phone, browsing activity never routed through a third party as part of how it works. One of Paxio's core controls, alongside screen time, app blocking, and bedtime scheduling.
"Does this filter on the device or in the cloud" is a fair, concrete question to ask any parental control app.
It means the blocklist and the category check both live on the phone, so filtering doesn't depend on sending your family's browsing to a third-party server.
Yes for blocking categories of websites such as adult content or gambling. It doesn't evaluate posts or messages inside an allowed app.
Cloud filtering checks each domain on the provider's servers, so your browsing passes through them. On-device filtering makes the decision locally.
For the full picture of how this fits alongside app blocking and screen time limits, see our guide on what a parental control app is.