Skip to content
Back to all articles

Guard, Browser, extension: how SafeAnywhere Schools stacks across the three device layers in a 2026 Indian school

A 2026 Indian school is no longer a one-device institution. ICT labs still run on Windows desktops; classrooms have shifted to Android tablets (with iPad on the roadmap); a growing share of homework and admin moves through school-issued phones. SafeAnywhere Schools is designed to cover all three layers from a single Principal dashboard. This piece walks through exactly what runs on which device, what the student experiences at each layer, and what the Principal, ICT Lead and Student Welfare Coordinator see from the other side.

THE SAFEANYWHERE SCHOOLS STACK · THREE DEVICE LAYERS INDIA · 2026 Principal, ICT Lead, Student Welfare Coordinator One unified SafeAnywhere Schools dashboard · policies down · signals up DPDP compliant ICT lab Windows / Linux desktops COMPONENTS Guard for Desktops Lab-mode enforcement STUDENT EXPERIENCE Only approved sites and apps during class Student tablet Android (iPad coming soon) COMPONENTS SafeAnywhere Browser Guard for Tablets STUDENT EXPERIENCE One-tap focus mode, per-subject allow-lists School-issued phone Android / iOS COMPONENTS SafeAnywhere Browser Chrome / Safari extension STUDENT EXPERIENCE Filtered search, blocked categories, time windows Policies flow down Signals flow up 3 LAYERS · ONE DASHBOARD COVER ALL THREE LAYERS OR LEAVE THE WEAKEST OPEN
The three device layers a 2026 Indian school actually has, and where SafeAnywhere Schools components sit on each. The Principal's dashboard is the single pane for policy and signal.

At 9:12 AM on a Monday in Bengaluru, a Class 8-B English teacher at an ICSE school in Rajajinagar walks into Lab 2 for a scheduled computer-assisted reading class. Thirty-two students take seats at thirty-two Windows desktops. The teacher opens a portal on the smart board; thirty-two desktops simultaneously enter Lab Mode. A specific allow-list applies for the next forty minutes: the school's reading platform, two approved dictionary sites, the shared drive folder for today's exercise. Nothing else. The teacher signs out at 9:52 AM; Lab Mode lifts. At 10:00 AM a different class (Class 7-A, Social Studies) enters the same lab; a different allow-list is applied, automatically, because the school's timetable is wired into the dashboard.

At 10:30 AM the same Class 8-B students are back in their regular classroom. The lesson has moved to tablets. Each student opens the SafeAnywhere Browser on a school-issued Android tablet. The browser sees that this device belongs to Rhea T., Class 8-B, and applies the Class 8-B per-student policy. During English period the policy allows the LMS, the reading platform and the school's video-notes drive. During Maths period, which starts at 11:20, the policy will allow a different allow-list. The tablet does not need a human to switch modes; the timetable has told the policy engine what to do.

At 3:30 PM the students have gone home. Three of them have school-issued phones for homework and admin (specifically the students whose families opted into the school's phone programme). Rhea opens the SafeAnywhere Browser on her phone, logs into the LMS and finishes her reading exercise. At 4:45 PM she opens Instagram, which is in the "social" category and specifically blocked for Class 8 students between 2 PM and 7 PM under the school's parent-approved homework-hours policy. The block hits; she returns to the LMS; the attempt is logged. Nobody is punished. The Principal sees the attempt on Friday's weekly review, noted as a single data point in a weekly attempt-pattern summary.

Three device layers; one child; one policy that followed her across all three; one dashboard where the Principal and the ICT Lead and the Student Welfare Coordinator see what each layer saw. This is what SafeAnywhere Schools does. The rest of this piece walks through how.

Why three layers, and not one

A 2026 Indian school is not a 2016 Indian school. The useful mental image is that there are three device surfaces the student uses in connection with their schoolwork, each with a different physical form factor, a different operating system, a different usage context, and a different set of risks. A content filter that covers only one of the three does genuinely useful work on that layer and leaves the other two open.

The ICT lab layer is the oldest. Windows desktops (and a smaller share of Linux desktops) in a shared room, used for specific periods of specific subjects, accessed by thirty students in sequence through the day. The risk shape is: shared devices, timed sessions, bursty high-stakes work (practical exams, coding assignments, research for projects). See the ICT lab blind-spots piece for the specific audit.

The student tablet layer is the newest and the fastest-growing. Most well-resourced CBSE and ICSE schools in India have moved to one-tablet-per-student in Classes 6 to 10 over the past three years. The device is Android today (iPad is on the roadmap for most schools in 2027 as the Apple Education pricing becomes real in India). Risk shape: personalised device, follows the student through the day, carries the school's LMS, used for homework and in-class work.

The school-issued phone layer is the mixed one. A subset of students, typically Class 8 and above whose families have opted in, use a school-issued phone for homework, admin, LMS access and sometimes physical-access tokens (library card, canteen UPI). Risk shape: personal device, connects on home Wi-Fi too, has access to the student's social apps unless the school policy restricts.

A school that filters its Wi-Fi at the router (common) covers the ICT lab layer passably and the tablet layer partially. It covers the phone layer almost not at all, because the phone leaves the Wi-Fi the moment the student steps off campus. See the school monitoring piece for the broader gap.

Layer 1: ICT lab desktops

On ICT lab desktops SafeAnywhere Schools runs two components: Guard for Desktops (the agent that lives on each lab machine) and a Lab-mode enforcement module that talks to the school's timetable and the Principal's dashboard.

Guard for Desktops is a lightweight Windows (and Linux) agent that enforces the current period's policy on the machine: which URLs resolve, which applications open, which USB operations are permitted, which network destinations are allowed. It runs as a managed service, cannot be disabled by the student, survives reboot, and does not require the student to log in with anything beyond the school's standard credentials.

Lab-mode enforcement is the piece that reads the school's timetable (uploaded once, kept in sync by the school's academic office) and auto-applies the right policy to the lab at the right time. When Class 8-B English arrives at 9:12 AM, the lab's current policy is Class-8B-English-Lab. When Class 7-A Social Studies arrives at 10:00 AM, the policy changes automatically. The teacher does not need to configure anything at the smart board; the schedule has done the work.

The student experience is: only approved sites and apps open during the period. Attempts to navigate outside the allow-list are shown with a short, child-friendly explanation message ("this isn't on the Class 8 English list for this period") and the attempt is logged as a signal. Nothing punitive; just visibility.

What the ICT Lead sees: a live Lab view in the dashboard showing current period, current policy, current students, current filter events. Useful mostly when something unusual happens; the dashboard's job on the lab layer is to be boring on a normal day.

Layer 2: student tablets

On student tablets the stack is SafeAnywhere Browser plus Guard for Tablets, both running on Android (iPad versions coming in 2027). The Browser is the primary web surface the student uses; Guard handles the device-level controls (app whitelisting, screen-time windows per period, camera/microphone policy per subject, USB and AirDrop/Quick Share controls).

The per-student policy is the piece that matters most here. A single Class 8-B student who is on a focus-support plan (agreed with the Student Welfare Coordinator and the family) can have a tighter allow-list than the rest of the class, without that being visible to the other thirty-one students. A Class 10 student in the six-month board-exam run-in can have a tighter homework-hours policy than their Class 10 classmates (see the board-exam phone protocol piece). The policy engine does not require a class-wide blanket.

The student experience on a tablet is specifically shaped by the per-subject allow-list. During Science practical periods the tablet unlocks the simulation platform and the lab-notes drive. During English periods it unlocks the reading platform and the dictionary. During PE periods it goes into focus-off mode because the tablet is not supposed to be used in PE. The point of the per-subject design is that the tablet is a useful tool during the subject it belongs to and not a general-purpose scrolling device during the subjects it does not.

What the Class Teacher sees: a tablet view per student showing filter events, time-on-platform, submitted work, and (opt-in) attention signals derived from pattern-of-use data. Not keystrokes; not content; signals.

Layer 3: school-issued phones

On school-issued phones the stack is SafeAnywhere Browser plus a Chrome or Safari extension, on Android and iOS. The Browser is the first-party safe web surface; the extension gives SafeAnywhere's filter visibility inside Chrome or Safari if the student (or a school app) opens one of those. On Android the Guard app is also available for schools that want tablet-grade controls on the phone.

The phone's policy is specifically the layer that has to work outside the school Wi-Fi. When the student steps off campus the school Wi-Fi is gone; the policy must still apply. SafeAnywhere's phone stack filters at the content layer (not the network layer), which means the policy travels with the device, not with the Wi-Fi.

Three specific things the phone-layer policy handles that the tablet and ICT lab layers do not have to:

  • Homework-hours windows. The school's homework-hours policy (typically set with family input) specifies when social apps are blocked on the school-issued phone. 2 PM to 7 PM on school days is a common setting.
  • Category-level blocks across apps and web. Short-form video (Reels, Shorts, TikTok where available), gambling, adult content, etc, blocked at the content-category level, not just by domain. This works because SafeAnywhere's filter is category-aware.
  • Off-campus Wi-Fi awareness. The phone knows when it is on home Wi-Fi vs school Wi-Fi vs cellular, and applies the appropriate policy. Families whose children carry school-issued phones can see their child's phone usage shape on the family side; the school sees the school-usage shape on the school side. The parent-school handshake is deliberate and bounded; see the DPDP parent rights piece for the data-handling frame.

The control plane: one dashboard, three roles

Above the three device layers sits a single SafeAnywhere Schools dashboard. The dashboard has three primary roles: Principal, ICT Lead, and Student Welfare Coordinator. Each role sees a different default view of the same underlying data.

The Principal opens the dashboard on Monday morning and sees a five-screen view: campus-wide filter-event summary from the week, incidents by category, class-by-class attention pattern (opt-in), the open items from the Student Welfare Coordinator's queue, and the week-ahead policy changes (new allow-list entries, timetable changes, exam-mode activations). The weekly safeguarding review piece walks the Principal's weekly 20 minutes in detail.

The ICT Lead sees a three-screen view: live lab status, device fleet health (how many desktops, tablets and phones are online and policy-current), and the backlog of allow-list requests from teachers. The ICT Lead's job is the layer-by-layer plumbing; the dashboard is designed to make the plumbing visible in minutes rather than hours.

The Student Welfare Coordinator sees a two-screen view: the per-student concern queue (students whose filter-event pattern has shifted meaningfully this week) and the active case list (students with open support plans). The Coordinator's work is specifically pattern-noticing, and the dashboard's design supports that by surfacing pattern shifts rather than raw event counts. See the teachers' view piece for the broader context of what teachers and coordinators are looking for.

All three roles view the same underlying data; the DPDP posture (SafeAnywhere as Data Processor under the school's Data Fiduciary role, minimum-necessary signal, no message reading or keystroke logging) is the same at every layer. See the DPDP schools compliance piece for the legal frame.

Three composite rollouts

A CBSE school in urban Delhi, ~2,200 students. Deployed the ICT lab layer first in July 2025; added student tablets in October 2025; added the school-issued phone programme for Class 9-12 in April 2026. By November 2026 the Principal's weekly review is 22 minutes, the Student Welfare Coordinator's queue averages 8 active cases, and the per-student policy engine is handling 14 specific-need plans across the senior school.

An ICSE school in suburban Pune, ~1,400 students. Started with the tablet layer only in September 2025 because the ICT lab was already filtered at the router adequately. Added SafeAnywhere's ICT lab stack in June 2026 to unify the dashboard view. No school-issued phones yet; the school prefers that families handle the phone layer directly, and refers parents to the parental-controls guide for the home side.

A state-board school in semi-urban Nashik, ~800 students. Deployed the full stack in August 2026 at a pricing tier adapted for state-board economics. The ICT lab layer is the primary value; the student-tablet rollout is phased (Class 6 and 7 first; Class 8 onwards in January 2027). No school-issued phone programme; the school's view is that the home-phone question is the family's.

The honest bottom line

A 2026 Indian school has three device layers: ICT lab desktops, student tablets, school-issued phones. SafeAnywhere Schools covers all three from a single Principal dashboard, with the components that fit each layer's form factor (Guard for Desktops on the lab; Browser + Guard for Tablets on the tablet; Browser + extension on the phone). Policies flow down; signals flow up. DPDP compliant, India-built, deployed at CBSE, ICSE and state-board schools across the country.

A school that is filtering one layer today is doing useful work on that layer. A school that wants the three-layer picture, with one dashboard, is what SafeAnywhere Schools exists for. A thirty-minute demo on your campus's own hardware mix is the most useful next step. The piece above is the architecture; the demo is the specifics on your own stack.

Three device layers. One dashboard. Three roles. One policy that follows the child. Cover all three layers or leave the weakest open.

Keep reading

More from the SafeAnywhere blog

Education10 min read

The homework interrupter: when study is seven minutes of work plus three minutes of phone, and what it is doing to Class 9 to 12 performance

Most Class 9 to 12 Indian students are not short of study time. They are short of continuous study time. The specific pattern parent-app dashboards show is 7 minutes of work, 3 minutes of phone, 7 more minutes of work, repeating. The same sixty minutes on a clock contain thirty effective minutes of deep work in the fragmented shape and forty-six in the focused shape. The honest fix is not a longer study timetable; it is a structurally different study hour.

Read article
Education11 min read

The pre-boards phone window: the eight weeks between late November and January that most Indian Class 10 and 12 families get wrong

The six months before boards get the attention; the eight weeks of pre-boards and mock exams, late November to mid-January, are where the real calibration happens. Parent-dashboard data from the last three Indian board cycles tells a specific story: intended study time climbs smoothly, but actual phone time climbs faster and peaks at mock exam week as a stress escape. The crossover is predictable; the response is not. Here is the honest pre-boards playbook for Class 10 and 12 parents in India.

Read article
Education12 min read

'Mummy, my school is using AI for everything now': the honest parent response to the AI-ified Indian classroom in late 2026

In the last twelve months AI has moved from the ICT lab into every subject, every worksheet and every evening study session in urban Indian schools. Most parents have not kept up. The problem is not that AI is bad for learning; the problem is that nobody told the parent which parts of their child's day are now shaped by an algorithm, who built it, what it records, and what they can actually do about it. Here is the honest playbook: the ten AI touchpoints in a Class 8 Indian student's day, the three categories of parental concern, and the five questions to put to the school next week.

Read article
SafeAnywhere Schools: 3-layer stack for Indian schools | SafeAnywhere