Why Watchly has no device agent — and what to pair it with

Most parental-control products install a device agent — software with elevated permissions that can enforce rules across the whole device. Some go further and use enterprise browser policies to lock themselves in place, disable private browsing, and block alternative browsers, so a child cannot remove or route around them.

That approach is genuinely effective at what it does, and if bypass-resistance on a device you fully own is your main concern, it is the right tool. We want to be straightforward that we do not do it, and why.

An agent has to be installed, which means you need administrative rights on the device. On a school-managed Chromebook you do not have them — the district’s policy governs what may be installed, and a parent has no standing in that domain. That is the device a great many children use most, and it is the one an agent-based tool cannot reach.

An agent also has broad permissions by construction. Once that surface exists, the product can see far more than the problem required: browsing across every app, and in many products messages and location too. We would rather not hold that data, and the cleanest way not to hold it is to have no technical means of collecting it.

So the trade is: we work everywhere a browser works, including devices you do not administer, and we know nothing about your child beyond what they watched inside Watchly. In exchange, we do not restrict the rest of the device. On an unrestricted device, a child can open a browser and go to YouTube directly.

For younger children — roughly under ten — pair Watchly with the operating system’s own controls. The OS handles the device: which apps exist, when the screen locks, whether a browser is available at all. Watchly handles the video. Neither duplicates the other, and the setup guides in this section cover the OS half for every major platform.

For older children, the calculus usually changes. A twelve-year-old with a locked-down device tends to do their watching somewhere you cannot see, which is a worse outcome than a boundary they understand and accept. Here the curated library plus the approval-request flow does more work than any enforcement layer, because it gives them a legitimate way to ask.

On a school-managed device the question is settled for you: you cannot install anything, so a browser-based library is what is available. The realistic arrangement is to let the school device be the homework machine under the school’s rules, and keep leisure viewing on a device where you set them.