Accountability vs surveillance: four tests

Accountability is mutual, informed, revocable and designed to start a conversation. Surveillance is one-sided, hard to escape and used to issue a verdict. If a phone-sharing arrangement fails those tests, calling it accountability does not make it safe.

The distinction is not about whether data exists. It is about power.

The four tests

1. Is it symmetric?

Do both people reveal the same kind of information and live under the same rule? One person receiving reports about another is monitoring, even if the intention began as support.

Symmetry is not sufficient — a mutually visible leaderboard can still become hostile — but asymmetry deserves scrutiny.

2. Is consent informed and ongoing?

Both people should understand what will be visible before joining. “You agreed once” is not permission for a feature to expand its reach quietly.

Consent also needs room for a genuine no. If refusing the tool carries punishment, the tap is not meaningful evidence of willingness.

3. Can either person leave?

An accountability arrangement should not require the observer’s permission to end. Revocability is a safety property, not a settings convenience.

Ask a plain question: if this feels wrong tomorrow, can I stop sharing without persuading the other person?

4. Does the data begin a conversation or deliver a verdict?

“We used more than we planned; what happened?” invites context. “You failed again” turns the same number into evidence for prosecution.

No interface can guarantee kindness. It can avoid building punishment, rankings and private administrator powers into the default.

Run common models through the tests

One-way lapse alerts fail symmetry. Parent controls are intentionally asymmetric and can be appropriate for a child, but reproducing that hierarchy between adults is risky. Leaderboards are symmetric yet adversarial. Software marketed for secret monitoring fails consent and usually revocability too.

A shared pool can be symmetric and cooperative: both people contribute to one balance and see the same aggregate state. That still requires a willing pair and an easy exit. Architecture cannot repair coercion outside the app.

Share the stake, not the log

Our design principle is simple: let another person feel the consequence of a shared choice without giving them a detailed receipt.

In Scrollmates, a scrollmate can see daily covered minutes, each person’s share of the pool, whether covered scrolling is happening now, and bond events. They do not receive app names, messages, URLs, notification contents or a general phone-activity history. The company receives the aggregate data needed to keep the two-person pool in sync, not a browsable app log. The technical details are explained here.

Both people opt in. Either can start breaking the bond with a hold-to-confirm action. A one-hour cooling window follows; only the person who confirmed can cancel it, the other person is told, and they cannot keep someone in the bond. Scrollmates’ Terms forbid using the service to monitor, stalk or control someone against their will.

That mutual visibility is the product, not a side effect. If you do not want another person seeing those aggregate numbers, do not bond with them. Solo mode remains available.

“But I want my partner to lock my phone”

The request is understandable. At a calm moment, transferring power can feel like the most reliable way to protect a future decision.

The problem is that relationships contain contexts no rule can pre-authorise: work, care, safety, travel and conflict. A credential that controls another adult’s phone can outlive the agreement that justified it. Prefer the least power necessary: a narrow schedule, self-owned friction, an aggregate shared stake or a time-limited arrangement with a tested exit.

Notice, too, what experienced people reach for before any of this. When someone asked r/relationships in 2020 how to deal with a partner’s phone use — a thread that drew several hundred upvotes — the single most upvoted reply was not a tool, a rule, or a lock. It was a question back: what does he say when you tell him it bothers you? The next most upvoted answer suggested asking for “specific, narrow windows where he’s not on the phone,” with sample sentences for a show and for the dinner table.

The pattern is worth taking as guidance. The first move is a conversation, the second is a narrow shared rule, and control does not appear on the list. A tool that arrives before those two steps is usually being asked to do a job that is not technical.

One more caution from that thread, because it cuts against easy diagnosis: a commenter with ADHD explained that a mindless game genuinely helps them retain what they are hearing. Parallel phone use is not automatically absence. Ask before deciding what someone else’s attention is doing.

If this feels like coercion, treat it as a safety question

If someone checks your device without permission, prevents you from leaving an arrangement, threatens you over usage or uses phone data to isolate you, this is bigger than screen time.

If it is safe to do so, seek help from a device the other person cannot monitor. In the US, the National Domestic Violence Hotline explains technology-safety precautions and offers phone, text and chat support. Outside the US, HotPeachPages lists domestic- and sexual-violence agencies by country. If you face immediate danger, contact your local emergency service.

Be aware that internet and phone activity may be monitored and may not be completely erasable. A specialist advocate can help you plan around your circumstances.

Frequently asked questions

Is mutual screen-time sharing always healthy?

No. Symmetry helps, but pressure, punishment or fear can make a mutual-looking system controlling.

What information is enough for accountability?

Usually the smallest aggregate that supports the shared decision: minutes, remaining budget and agreed events — not an app-by-app activity log.

Can my partner stop me leaving Scrollmates?

No. Either participant can initiate the exit without the other’s approval.

The interface should limit power

Trust is not a privacy policy pasted over a control system. It is visible in who knows what, who can act, and who can leave.