What your child's school already monitors online — and what it quietly does not

At parents' evenings this October, a quiet pattern is showing up: parents assume their child's school is watching far more of the digital world than it actually can. "They told us the school filter catches everything" is a sentence a Designated Safeguarding Lead has been hearing twice an evening since September, and each time they wince, because it is not true, has never been true, and is drifting further from true as children's digital lives move onto their own phones, their own data plans, and their own private messages.

This is not a criticism of schools. The monitoring they do is legally and technically careful, and in many cases excellent. The problem is the gap on the other side of the school day — the 100-plus hours a week when the school's visibility, by design, stops. If you understand the shape of what schools can and cannot see, you can close that gap at home with a handful of calm, boring moves, and stop assuming someone else is covering a shift that nobody is on.

What schools actually monitor in 2026

Across the UK, the US and most of the EU, school monitoring in 2026 looks broadly like this. The specifics vary; the shape does not:

• School-owned devices. School-issued laptops, Chromebooks and iPads usually run a managed profile that filters content, logs activity on specified categories, and sometimes flags keywords. Expect this to be thorough.
• School-network traffic. Any device, personal or otherwise, connected to the school's Wi-Fi passes through the school's filter. On that network, bad categories are blocked and the DSL gets alerts.
• School-issued accounts. Google Workspace for Education, Microsoft 365 for Education and the school's learning platform (Google Classroom, Microsoft Teams, Seesaw, Firefly) have activity logs and keyword flagging on content created inside those accounts.
• Specific safeguarding tools. Many secondary schools run tools like Smoothwall, Senso, Securly or Impero that scan on-device activity on school devices for safeguarding keywords and screenshot risk at the moment of flag.
• Access logs and audit trails. If something is flagged, there is a record of who saw it, when, and what happened next. This is usually robust.

Totalled honestly, this covers roughly 35 of the 112 waking hours in a child's week. It is good, it is lawful, and it does catch real safeguarding incidents. It is also a narrow slice.

What schools quietly do not monitor (and legally often cannot)

This is the half of the picture most parents have never been shown clearly. Across the same jurisdictions, schools typically do not monitor:

• Personal devices on mobile data. The second your child's phone is on 4G or 5G instead of the school Wi-Fi, the school filter sees nothing. For most teenagers, that is 100% of break-time scrolling.
• Any device on home Wi-Fi. School monitoring does not follow a device home. Even a school-issued laptop, on your home network, often operates outside the school filter unless the school specifically configured it to.
• DMs on consumer apps. Snapchat, Instagram, TikTok, WhatsApp, Discord, Telegram, iMessage and in-game chats (Roblox, Fortnite, Minecraft) are not visible to the school filter even on school Wi-Fi, because the content is end-to-end encrypted or stays inside the app's own infrastructure.
• Weekends and holidays. Monitoring software on school devices usually stops or quiets outside school hours. There is no filter alert queue being watched at 11pm on Saturday.
• Private browser sessions on personal devices. Incognito, VPNs and private browsing modes all defeat home-level monitoring unless you have specifically layered device-level tools, which schools do not install on personal devices.
• Content inside apps, as opposed to on the web. A page served inside TikTok's video player, Instagram's reels tab or Snapchat's Spotlight is not visible to a traditional web filter the way a browser URL would be.

None of this is a secret. It is written into every school's acceptable use policy, every safeguarding handbook and every Department for Education guidance document on filtering and monitoring. It just is not usually translated into a sentence a parent would recognise, which is: the school sees school hours, on school kit, on school networks, in school accounts. That is it.

Why the gap exists (it isn't negligence)

The gap between what schools monitor and what parents imagine is not a failure of the school. It is the deliberate output of three forces:

• The law. Schools are limited by data-protection law (GDPR in Europe, FERPA/COPPA in the US) to monitoring that is proportionate to education and safeguarding, on infrastructure they are responsible for. They cannot lawfully reach into a parent-owned device on mobile data at 9pm on a Sunday.
• The technology. Encrypted DMs, in-app content and mobile data are, by design, invisible to a web-filter sitting on a school's network. No amount of budget changes that physics.
• The responsibility model. Schools are responsible for the digital environment they provide. Parents are responsible for the digital environment they provide at home. In 2026 that is a 35/77 split, and the 77 belongs to you.

When a school leader describes their safeguarding setup, they are telling you the truth about their 35 hours. They are not telling you a lie about your 77 hours; they are declining to speak for a thing they cannot see. The quiet mistake is reading their accurate description of the first as a reassurance about the second.

The 77-hour gap, in concrete examples

Four scenarios that illustrate the shape of the blind spot. All four are mundane and common in 2026:

• The lunch-break reel. A pupil opens TikTok on 4G in the dinner queue at 12:30. The school filter is off (not school Wi-Fi), the app is inside its own ecosystem (not the web filter's remit), and the content is a recommender feed. The school sees nothing. If what she watches dents her mood for Period 5, nobody connects the dots.
• The 10pm Snapchat. A 13-year-old on home Wi-Fi receives a Snap from a classmate they argued with earlier. The school filter sees nothing (home network), the app is encrypted (nothing to intercept), and by morning the message has auto-deleted. Monday's playground incident has no visible digital precursor from the school's point of view.
• The weekend Discord server. Three Year 10s join a public Discord server a creator advertised in a TikTok. On a school day they would never have found it; on a Saturday the school's filter does not exist for them. What the server exposes them to over 48 hours is entirely outside the school's view.
• The AI chatbot companion. A lonely tween opens a companion-chatbot app on their own phone each evening. The conversations are private to the app. Any emotional risk builds across weeks, and the school's first signal is a pastoral observation two months later. (The companion-chatbot and other 2026-specific risks are covered in detail in our 10 new online risks post.)

What home needs to do that school cannot

The honest implication of the above is that the school is not failing you. It is covering its 35 hours. You cover the 77. The good news is that you do not need enterprise safeguarding software to cover them. You need four boring, cheap moves:

1. A safe browser on every personal device. This closes the single biggest hole: web content on mobile data and home Wi-Fi, including inside in-app browsers. Our browsers vs apps piece explains which combination catches which gap, but the headline is: start here.
2. Device-level screen time with categories. Caps and schedules that apply regardless of which network the device is on. Short-form video, companion chatbots and gambling-adjacent apps are the categories that most need their own budget separate from creative and learning apps. The screen time vs screen quality reframe is the reasoning behind this one.
3. DM lockdowns on every consumer app. You cannot read your child's DMs (and should not), but you can shut strangers out of them. Set every DM-enabled app to "friends only", filter unknown-sender message requests, and keep disappearing-message timers off.
4. The overnight bedroom-charger rule. The single rule with the largest, most consistent effect on sleep, mood and incident rate. Phones charge outside the bedroom from one hour before bedtime. School cannot enforce this. You can.

Those four moves cover roughly 80% of the 77-hour gap. They are the home equivalent of what a school's filter does for its 35 hours.

Where SafeAnywhere fits the home side of the split

SafeAnywhere is built exactly for the 77-hour slot. It is not trying to replicate what the school already does well on its 35 hours; it is trying to be the clean, calm layer that covers the rest:

• A safe Browser that filters harmful content regardless of network (mobile data, home Wi-Fi, cafe hotspot), closing the "off the school network" hole.
• Guard for device-level control on apps and screen-time, with category budgets rather than one blunt daily number.
• One alert queue, categorised by risk, so you see what matters without reading your child's private messages.
• Open APIs for schools that want unified visibility. If your school is moving toward a unified safeguarding view (covered here), SafeAnywhere can feed signals into it with parental consent.
• Privacy by design. Guard never reads private messages, keystrokes, photos or chats. Safety comes from what your child encounters, not from surveillance of their inner life. The privacy and compliance piece covers how we hold ourselves to this.

The school's filter and the home's safety net are not alternatives. They are two shifts covering the same child, and the handoff happens at 3:30 on Friday and resumes at 8:30 on Monday. The hours in between are yours.

Common questions parents ask

Does my child's school monitor their personal phone?

Only on the school's Wi-Fi, and only for web-level traffic. Mobile data, in-app DMs and home Wi-Fi are outside the school's reach. If the school has not installed a managed profile on your child's personal device (they almost never do), the school has no visibility there.

If the school issues my child a laptop, does the filter follow it home?

It depends on how the school configured it. Some school-issued devices run their monitoring agent anywhere the device is used; many only filter on the school network. Ask your school's IT lead directly — the answer should be in one sentence.

What does the school see if my child gets a safeguarding flag?

Usually: the keyword or category that triggered, a timestamp, the device, and sometimes a short screenshot. The DSL reviews it and decides whether to escalate. The content of private messages on consumer apps is not visible, even post-flag.

Can the school see what my child does on TikTok, Snap or Discord?

No. Those apps are closed ecosystems with encrypted or app-internal content. Even on school Wi-Fi, the school filter sees the app is in use but not what is happening inside it.

Should I ask my school for a full list of what they monitor?

Yes, and politely. Any school's monitoring posture is documented in their acceptable use policy and filtering/monitoring statement. If you cannot find a plain-English summary, ask the DSL. A good school will welcome the question.

If I set up SafeAnywhere at home, does the school get the data?

No, not unless you choose to share it. SafeAnywhere's data belongs to the parent account. Some schools offer an opt-in integration where parents can forward specific safeguarding signals into the school's unified view, but it is explicit and parent-controlled.

The honest bottom line

Your school is doing more than you think, and less than you assume. The 35 hours it covers are usually well covered. The 77 hours it does not cover are the ones where modern harm actually happens, and the only person who can close that gap is the adult who buys the Wi-Fi, pays the phone bill and tucks the child in.

School covers the school day. Home covers the rest. Once you can say that sentence out loud without flinching, the four moves above are the whole job, and the rest of autumn term goes to the children.