LockedIn vs EduShield (2026): purpose-built phone-free campus software for student-owned phones vs EduShield-style school MDM that restricts apps on school-issued devices. Where each one fits and why most U.S. K-12 schools need both layers.
EduShield is a school-MDM-style platform that restricts apps, websites, and screen time on school-issued and managed student devices. It sits in the same category as GoGuardian, Securly, Mobile Guardian, and LanSchool. The crucial detail for U.S. K-12 administrators: school MDMs only control devices the school owns. They do nothing for the student-owned phone in the student's pocket — which is the actual phone problem most schools are trying to solve.
Two different categories solving two different problems
EduShield / school MDM is for the Chromebooks, iPads, or laptops the school issues to students. It can block YouTube during a math class, filter web content for CIPA compliance, and remotely wipe devices that are lost or stolen. That's a real, valuable category — but it's not the same as a phone-free campus.
LockedIn is for the personal smartphone the student brought from home. The school doesn't own it, can't enroll it in standard MDM, and can't push a policy that wipes it. LockedIn locks the personal phone at the OS level during configured school hours and on the campus geofence, without giving the school any other control over the device.
Why most U.S. K-12 schools end up needing both layers
In a typical American district, the Chromebook program and the phone program are run by different people with different goals. The IT department deploys an MDM (EduShield, GoGuardian, Securly, etc.) to keep school-issued devices on-task. The principal's office, in parallel, has a phone policy — and that policy is what fails when students keep their phones in their pockets all day.
LockedIn was built specifically to close the second loop. It is not an MDM replacement. It does not filter web content, monitor browser history, or push apps. It does one thing well: it locks the student-owned phone during school hours so the phone policy is actually enforced.
Where each product fits in your stack
- • School-issued Chromebook or iPad → EduShield / GoGuardian / Securly / Mobile Guardian (MDM + content filtering)
- • Student-owned phone → LockedIn (campus geofence + OS-level lock)
- • Student-owned phone with a school CIPA mandate to filter web content → MDM-class tool with a BYOD module + LockedIn for phone-free campus enforcement
- • Concerts, exams, lockdowns → LockedIn emergency mode + campus geofence overrides
Why MDMs don't work for student-owned phones
Enrolling a personally-owned student phone in a school MDM creates four problems: (1) parents reasonably object to the school having low-level device control over their child's personal property; (2) Apple and Google require user-acknowledged enrollment, which most parents won't grant; (3) any policy you push survives off-campus, which is overreach; and (4) MDM enrollment can be removed by the student at home, defeating the whole purpose.
LockedIn solves this by scoping enforcement to a campus geofence and a school-hours schedule, by leaving the phone fully accessible to parents outside that window, and by being explicit in the privacy policy about exactly what data is collected (device-state and bypass-detection events only — never messages, photos, or browsing history).
See also