Either someone has asked you to be their accountability buddy, or you are watching a person you care about lose hours a day and wondering what you can usefully do.
The two situations need almost opposite approaches, and getting them mixed up is how well-meant help turns into a strained relationship.
If they asked you
Good news: the job is much smaller than you think, and doing it well mostly means doing less than your instincts suggest.
Your job is to answer, not to watch
In a well-built setup you are not monitoring anyone. You receive a request when they want to unlock something, and you approve or deny it. You do not see their usage statistics, their app list, or their schedule. In Disconnect you see the rule name and whatever reason they chose to write, and nothing else.
Resist the urge to expand the role. Checking in, asking how it is going, or commenting on their phone use converts a clean mechanism into surveillance, and surveillance makes people hide.
Saying no is the whole point
This is the part people find hardest. When a friend sends a request with a reason that sounds perfectly fair, declining feels unkind.
It is not. They set the rule while thinking clearly and asked you to hold it precisely because they knew they would argue later. The argument arriving is not new information — it is the thing they predicted.
If you approve every request, the system is decorative and you have quietly wasted their month.
Agree the terms once, up front
Five minutes at the start prevents most of the trouble. Ask them:
- What counts as a real reason? Get the short list. Everything else is a no.
- What should I do if you push back? Have them tell you now, while calm, to hold the line.
- How long should an approval last? Long enough to do the thing, not the rest of the evening.
Having their own words to point back to makes declining a matter of following instructions rather than a judgement you are making about them.
Do not take it personally
You will occasionally get a short message. It is aimed at the situation, not at you, and it usually evaporates within the hour. If it genuinely bothers you, say so and hand the role back — that is a legitimate move and worth agreeing as an option at the start.
Being a buddy is free
It changes nothing about your own phone. You get a notification, and you answer it with one tap.
Get Disconnect →If they did not ask you
This is the harder case, and the honest answer is that your options are limited and mostly indirect.
What does not work
Commenting on their phone use. Sending them articles about screen time. Setting up an app on their behalf. Pointed remarks about how much they are on it. All of these reliably produce defensiveness, and defensiveness produces more private use rather than less.
What sometimes does
- Change what is available, not what they should do. Suggest the walk, the meal without phones, the activity that occupies hands. Structure beats persuasion.
- Do it yourself, visibly and without commentary. Leaving your own phone in another room, and not mentioning it, is more persuasive than any argument. Announcing it is not.
- Say it once, plainly, and then stop. One honest sentence about how it affects you, delivered calmly and never repeated, does more than a campaign. Repetition converts a real point into background noise they have learned to tune out.
- Offer, once, to be their buddy. Mention that the option exists and that you would be glad to. Then leave it entirely with them.
When it is not really about the phone
Heavy phone use is often downstream of something else — stress, isolation, avoidance, or low mood. If that is what you are actually seeing, no blocker addresses it, and pushing on the symptom can make someone feel more alone with the cause.
In that situation the useful move is the ordinary one: ask how they are, and mean it.