← All posts

HOW IT WORKS

Why We Added a Camera to a Focus App

March 2026 · 4 min read

The presence check is the feature people ask about most. The reaction is always some version of: "Wait — it uses my camera?" Usually skeptical. Sometimes alarmed. So here's the full explanation of what it does, why we built it, and why the privacy story is actually stronger than it sounds.

The problem it solves

You can block every website. You can lock down every distraction. And you can still spend the session making coffee, folding laundry, or staring out the window while the timer counts down.

Website blocking solves the browser problem. It doesn't solve the presence problem. A session where you're physically absent isn't a focus session — it's a running clock. And for some people (particularly those working from home, where the couch is twenty steps away), the absence problem is just as real as the distraction problem.

We needed a way to verify that someone was actually at their desk. The only sensor that can do that without being invasive is the one already built into the laptop.

What the camera actually does

The presence check takes a low-resolution frame sample every few minutes during a session. It runs a lightweight on-device model that answers a single binary question: is a person present in frame, yes or no?

That's all it does. No video is recorded. No frames are stored. No images ever leave your device. The model runs locally, produces a boolean, and discards the frame immediately. The result — present or absent — is what the app acts on.

If you step away briefly, nothing happens. If you're absent for an extended stretch, the session pauses and you get a prompt to confirm you're back before it resumes. The session clock doesn't keep running while you're gone.

Why it's opt-in

The presence check is not on by default. You enable it deliberately, in settings, knowing what it does.

We made it opt-in for two reasons. The first is obvious: not everyone needs it. If you work in an office and stepping away from your desk is genuinely rare, the check is unnecessary overhead. The feature is for people who work remotely, or who know from self-experience that physical distraction is a real pattern for them.

The second reason is more important. A tool you've chosen to use works differently than a tool that was imposed on you. When you turn on the presence check, you're making a deliberate commitment — you're telling yourself that you're serious enough about this session to be held accountable even when no one is watching. That decision has psychological weight that a mandatory check would undermine.

The constraint only works if you put it there yourself. Surveillance imposed from outside creates resentment. Constraints chosen voluntarily create commitment.

The privacy architecture

We're aware that "we use your camera" is a sentence that requires trust. So let's be specific about what that trust is actually based on.

Everything happens on your machine. The model is embedded in the app — there's no API call, no frame upload, no remote processing. The frame is captured, analyzed, and discarded in the same pipeline, entirely locally. When the app closes, there is nothing related to the camera check on any server anywhere, because nothing related to the camera check ever left your laptop.

For teams specifically: the presence check data isn't part of what we report to admins. The aggregate sprint count we expose to team administrators tells them nothing about whether any individual used the camera feature. It's not in the data model at all.

The people who actually use it

Based on what users tell us, the presence check gets enabled by a specific type of person: someone who has identified that physical absence — not digital distraction — is their primary failure mode. They start a session, get up to get something, and twenty minutes later realize they're in another room doing something completely different.

For that person, the presence check is the feature that makes the app work. Not because it catches them (there's nothing to catch — no data, no report, no record), but because knowing it's on changes their behavior before the session starts. They sit down. They stay seated. The accountability is to themselves, not to anyone watching.

That's the only kind of accountability that actually works in the long run anyway.

See it for yourself.

Download 45 and try a session. The presence check is in settings if you want it.

Download for Windows