For companies, schools and universities
A policy in your own words.
A ruling on every request.
Block the domain and the team loses the talk they were sent. Allow it and the feed is one click away. Write what the machines are for, in your own words, and every page opened on them, in every browser and every app, is judged against it. It runs headless: nothing on anyone’s screen, and nothing ties a ruling to a person.
For IT: how it deploys · For the DPO: what leaves the machine · For schools · the download
9.99 EUR per seat per month · the plan comes back written, from a person at hello@focusing.app
POLICY “engineering work, payments platform, no social media”
-
github.com/verdict: Allowyourco/ payments/ pull/ 812 -
github.com/verdict: Blocktrending -
docs.stripe.com/The API the team is integrating. verdict: Allowapi/ payment_intents -
reddit.com/verdict: Blockr/ all
Same domain. Opposite verdicts, per request.
What you deploy
Written in your words. Held by every machine.
The same app everyone downloads, with your policy in place of the personal session. 9.99 EUR per seat per month.
01
A policy in plain language
You write it in natural language, as short as “engineering work, payments platform, no social media” or as detailed as the machines need. No category trees, no vendor taxonomy, no blocklist for anyone to keep up to date.
02
Per machine or global
One policy across every machine, or its own policy on any single machine. That is the whole targeting model, and you set it.
03
A ruling on every request
The address is judged first, and where the address can’t tell, the content of what was opened is judged too, as the page loads. It covers every browser and every app on the machine, and every block page carries a Re-evaluate link.
04
Headless
No app on the person’s screen. A background service holds your policy, and the next section shows what the desk does see.
05
Nothing recorded about a person
No per-person record exists, nothing ties a ruling to a person or a machine, and nothing is reported to anyone.
06
Next to the gateway you run
A local proxy on the machine, sitting before the gateway you already run. Designed to coexist, and verified against your stack in the pilot before you commit.
On the machine
What the person at the desk sees.
Headless means exactly that: no app window, no session to start, no orb, nothing to configure. The policy you wrote runs underneath, and stays through a reboot.
The pages the work needs load the normal way, in every browser and every app on the machine. An off-intent page never shows up: a block page stands where the site would have been, with the address on it and a Re-evaluate link.
If the ruling was wrong, that link sends the page to a slower, smarter model on the spot, and the block lifts or stands. No ticket, no list to update, no call to IT.
POLICY “engineering work, payments platform, no social media”
-
youtube.com/The talk someone on the team was sent. verdict: Allowwatch?v=… -
youtube.com/The feed underneath it. verdict: Blockshorts -
reddit.com/The thread with the answer. verdict: Allowr/ ExperiencedDevs -
reddit.com/The front page. verdict: Blockr/ all
Nothing to add to a list, nothing to explain at the desk.
9.99 EUR per seat per month.
For schools and universities
The coursework loads in every seat. The feed doesn’t.
A blocklist forces the bad trade. Ban the domain and the lab loses the lecture with it. Allow it and the room is on the feed by the second slide.
A policy in your own words rules one page at a time instead: the article, the channel the class was sent and the recorded lecture load, and the scroll that lives on the same domains never shows up.
It runs headless. A student sees no app and no session to start, only the pages the coursework needs and a block page with a Re-evaluate link where an off-intent page would have been. Nothing ties a ruling to a student: no per-person record, nothing reported to anyone.
One policy can cover every machine, or any single machine can carry its own: a lab desktop, a library desktop, a seminar-room laptop. Changing it means rewriting a paragraph, not rebuilding a list.
9.99 EUR per seat per month. The plan comes back written: the policy, the install steps and the price for your seat count.
POLICY “organic chemistry, coursework and research”
-
en.wikipedia.org/The reaction on today’s handout. verdict: Allowwiki/ Aldol_reaction -
en.wikipedia.org/One click from the article, and gone. verdict: Blockwiki/ List_of_Internet_phenomena -
youtube.com/The channel the class was sent. Its title is judged as it loads. verdict: Allow@… -
youtube.com/The feed underneath it. verdict: Blockshorts
Same site. Different verdict.
For review
For the DPO and the works council.
What a review asks for, in the order it asks. A person answers the follow-ups.
What leaves the machine, and what is kept
The address, the policy in force, and where the address alone can’t decide, the content being judged, such as a video’s title or the text of a post. A verdict comes back. What is kept is the ruling itself: the address, any content that went out with it, the verdict, when it was made and the policy label, with no account, device or person attached.
Who makes the call
An AI model rules on the request and returns the verdict. No profile is built and there is no per-person record to be requested, reviewed or leaked.
Who you would be contracting with
Deeptegrity Kft, Budapest, Hungary. An EU company, so GDPR applies by law.
A human answers
Questions from a DPO, a works council or an IT reviewer go to hello@focusing.app and a person replies to them. The website privacy policy is at focusing.app/privacy.
The pilot
Start with the machines you choose.
What a pilot is
- Scope
- The machines you choose. A handful is enough to see it rule.
- The plan
- Written, and it arrives before any call, built to be forwarded to whoever signs off.
- Ending it
- Uninstall it and it stops there. Nothing to unwind, nothing to export, no record of anyone.
- Who answers
- A person at hello@focusing.app. IT review questions and DPO questions go to the same address.
How to start
- Install it on your own machine and start a Working session. Same engine: you’ll see how the pages your people need get ruled.
- Choose the pilot machines and count them.
- Write the policy for those machines in your own words, as short or as detailed as you like.
- Send the form. Nothing is installed or invoiced until you say so.
The form sends what you type to hello@focusing.app. The website privacy policy has the detail.
Straight answers
What IT, the DPO and the people at the desks ask first.
How do teams and schools use it?
You write the policy in plain language, for example “engineering work, payments platform, no social media” or “organic chemistry, coursework and research”. It is deployed per machine or globally across every machine, and it runs headless: no app on anyone’s screen, just the background service holding the policy, and it holds through a reboot. Send a pilot request and a human replies with a written plan: policy, install steps, and the price for your seat count.
Can our organization see what people browse?
No. Rulings are kept without any account, device or person attached, so no per-person record exists, and nothing is reported to anyone. Your people get a filter, not a supervisor.
We already run a secure web gateway. Will this collide?
It is designed not to. Focusing App is a local proxy on the machine, sitting before whatever gateway you already run: it rules on each request there and hands the allowed ones on. Bring your setup to the pilot and it gets verified against your stack before you commit.
What leaves my computer, and what do you keep?
What leaves: the address, the session or policy in force, and, where the address alone can’t decide, the content being judged, such as a video’s title or the text of a post. What we keep: the ruling itself (the address, any content that went out with it, the verdict, when it was made, and the session or policy label), with no account, device or person attached. No profile is built, no per-person record exists, and nothing ties a ruling to you. A verdict comes back, and that is the whole transaction.
What if it blocks something I need?
Press Re-evaluate on the block page. The page goes to a slower, smarter model, and the block either lifts or stands. No settings dig, no ticket. If the same wrong block keeps coming up, be more specific about what it is judging against: Studying with Law chosen gets fewer close calls than Studying alone, and for a deployed policy, naming the tool gets fewer than naming the department.
Who is behind it, and whose laws apply?
Deeptegrity Kft, based in Budapest, Hungary. EU jurisdiction, so GDPR applies by law. Questions a DPO would ask get answered by a human at hello@focusing.app.
Try it on one machine first.
The same download as everyone else. Free for 7 days, no card.
On your phone? Send yourself the link for your desk.
Focusing App runs on your Mac or PC, not your phone. The link opens the download buttons there.