Search the Play Store for a screen time app and you get dozens of results with the same promise: take back your time, stop scrolling, focus. Install a few and a pattern shows up quickly. A banner at the bottom of the usage chart. A full-screen video ad when you open settings. The one feature you actually wanted, a lock you cannot talk your way out of, sitting behind a monthly subscription.
Some of that is just how free apps pay for themselves. But a screen time app is not a flashlight or a calculator. To do its job it needs more access to your phone than almost anything else you will install, and that changes the math on who you let build it.
What a blocker can see
On Android, nearly every app blocker works through the Accessibility Service. It is the only reliable way for one app to know which other app is on screen at this moment, so it can draw a block screen over it. Website blocking goes further: the blocker reads your browser's address bar to know which page you are on.
Accessibility access was designed for screen readers, so it is broad on purpose. An app holding it can read the text on your screen, including messages, and observe what you type. Pair that with the "display over other apps" permission and the app can draw anything on top of anything. Every blocker needs this pair. Curbox needs it too. That is not the problem.
The question is never whether a blocker has this access. It is who else is inside the app with it.
Why ads change the picture
Ads in an Android app do not arrive by magic. The developer adds an advertising SDK, a library written by another company, and that code runs inside the app, with the app's permissions. It typically ships along with analytics and attribution libraries that report device details, app usage and interactions back to their own servers. For an app with Accessibility access, that means third-party code you have never seen is running in the same process that can see your screen.
That does not mean a given ad SDK is reading your messages. Reputable ones have policies against it. It means you are now trusting the developer, plus every company whose code they bundled, plus whatever those libraries do in their next update. You cannot check any of it.
There is also a quieter conflict. An app paid by ad impressions earns more when you open it more often and stay in it longer. A blocker's whole purpose is to get you to spend less time on your phone, including in the blocker. The incentives point in opposite directions. The same is true, in a softer way, of apps where the strict mode is the premium tier: the version that actually works is the one you have to keep paying for.
What "no ads" should actually mean
"Ad-free" on a store listing can mean anything from "no banners in the paid tier" to "we never added an ad SDK at all." The useful version is stricter: no advertising code, no third-party tracking code, and ideally no way for the app to reach the internet in the first place. If an app has no internet permission, it physically cannot send what it sees to anyone, ads or not. That is a guarantee the operating system enforces, not a promise in a privacy policy.
The checklist below takes about five minutes and works on any app, including ours.