Monitoring your team can actually see

Monitoring software is usually sold to the manager and hidden from everyone else. This page is the opposite: it is the one to forward to the team you are asking to install it.

There is no hidden mode

scrin.io cannot be run as spyware, because we never built the switch. Tracking is started and stopped by the person being tracked, from an app on their own machine, and it is visible while it runs.

Every screenshot announces itself

A notification appears near the system tray each time a capture is taken. It is on by default. A screenshot nobody knew about is worth less as evidence and costs far more in trust than it can ever return.

Nothing is keylogged

Activity level records that keyboard or mouse input happened in a ten-second window. What was typed is not captured, not stored, and not available to anyone — there is no keystroke log in the product to read back.

Your team can see their own settings

The desktop app shows each person the rules that apply to them: how many screenshots an hour, whether app tracking is on, whether activity level is measured, the auto-pause delay, any weekly limit. No one has to take a manager's word for what is being collected.

And their own data

Everyone sees their own timeline, their own screenshots and their own reports, and can remove any of the data they have submitted. The same record the manager reads is the record they read.

Screenshots can be blurred

Turn blurring on for the team or for one person, and screenshots show that work was happening and what kind of screen it was, without the content being readable. Enough for a timesheet to stand up; not enough to read someone's messages.

Idle time is not billed as work

Tracking pauses itself when nobody is at the keyboard, and the gap is offered back as a question rather than silently counted. The protection runs both ways: nobody is charged for someone's lunch, and nobody is recorded working through it.

The account itself is protected

Two-factor sign-in is available, including passkeys and hardware security keys, because a timeline of somebody's working day is exactly the kind of thing that should not be behind one password.