Is this a VPN? +
No. A VPN routes your traffic through someone else’s servers. The Focusing App is a local filter, a proxy that runs on your machine. Pages you’re allowed to visit load directly, the normal way. Nothing detours through us. What leaves is only what the ruling needs: the URL, your intent, and, where the address alone can’t decide, the content being judged.
What data leaves my device? +
The URL being checked and the intent in force: your session, or your organization’s policy. For pages where the address alone can’t decide, the content being judged too, analyzed on your machine or in the cloud. A verdict comes back, and that’s the whole transaction. Your browsing history isn’t stored or sold, there are no ads, and no profile of you is built. Verdicts, not surveillance.
What if it blocks something I actually needed? +
Ask for a second look. Any block can be re-evaluated on the spot: a smarter model takes the case and the verdict either flips to allow or stands. No settings dig, no support ticket, no waiting on a list update. And if the same edge keeps coming up, tighten the intent itself: a session rules cleaner in a narrower lane (Studying tuned to STEM beats Studying alone), and an organization policy rules cleaner as a sharper sentence (“writing my thesis, Fourier analysis, lectures allowed” beats “thesis”).
Can it keep me away from gambling sites, or anything else I’d rather avoid? +
Yes. Flip the block once, in daylight, when you mean it, and from then on the page simply never loads: a pause, placed exactly at the moment of impulse, every time. Betting sites, adult content, doomscrolling: the same door-holding works for anything you’d rather keep at arm’s length. You decide what’s off-limits, the filter holds the line, and nobody is watching over your shoulder while it does. No judgment, just distance.
Is there a mobile version? +
No. The Focusing App runs on macOS and Windows: the desktop is where focused work happens, so that’s where the filter lives. If you’re reading this on your phone, the band above will email you the download link for later.
Will it slow my browsing down? +
No. The checks are placed where you can’t feel them. The URL is ruled on in the gap between your click and the page starting to load. Where the content itself needs judging, one video against the next, that happens asynchronously, alongside the load rather than in front of it. On-intent browsing feels like browsing. The only thing designed to be slow here is the doomscroll.
We’re a school. How do we actually deploy this? +
Two modes, your call per rollout. Headless: users see no app at all, just the background service enforcing the policy you deployed. Or the full desktop app, interface included, where the person at the machine sees the session. Either way it installs like any desktop software, and the policy is plain language (“coursework and research for this class”): one policy across every machine, or different policies for different rooms. Volume licensing and pilot support are one email away at hello@focusing.app.
Can we monitor what our students or employees browse? +
No, by design. There is no dashboard, no browsing report, and no log for anyone to review, because none of that exists. The app rules on each request at the machine and keeps no diary. Your students and your team get a filter, not a supervisor. If you’re shopping for monitoring software, we’re the wrong vendor.
Who’s behind this, and whose laws apply? +
Deeptegrity Kft, based in Budapest. The address matters: we’re under EU jurisdiction, so GDPR applies to us by law. Questions a DPO would ask get answered by a human, at hello@focusing.app.
How can it allow one YouTube video and block the next? +
Because it doesn’t only read the address. It reads the content. The URL is ruled on first. Where the address alone can’t decide, say two videos on the same site or two threads on the same subreddit, the content itself is judged against your intent while the page loads, asynchronously, so nothing waits on it. If the verdict is block, the content either never appears or is replaced by a plain notice that it was blocked. Same site, different verdict: that’s the machinery behind it.
We already run Zscaler or another secure web gateway. Will this collide? +
It’s designed not to. The Focusing App is a local proxy on the machine itself. It rules on requests before they leave the device, then hands them on to whatever gateway or inspection setup you already run, sitting between the layers rather than fighting them. Where your stack inspects traffic, the app can be configured to align with the trust setup you already use, so the two don’t fight over the connection. Bring your stack to the pilot conversation and we’ll verify it against your setup before you commit.
Can content analysis run entirely on our own infrastructure? +
For enterprise deployments, yes. By default, classification runs on the machine or in the cloud: the URL and intent are judged first, and where the address alone can’t decide, the content too. Enterprise pilots can route that evaluation to local inference instead: models running inside your network, so content analysis never has to leave your infrastructure. If that’s a requirement, say so in the pilot conversation and we’ll scope it with you.