You can’tquietly opt out.
Ways around it.
Checking in on someone else’s phone
Refused
Each student has one linked phone. A check-in from any other phone is refused with “This phone isn’t linked to your account” and waits for the teacher to approve or turn it away, for lost or replaced phones.
The teacher seesNew phones waiting: approve or turn away
Checking in two accounts on one phone
Refused
One phone can check in one student per class meeting. A second account on the same phone is refused, and the attempt is kept.
The teacher seesAnother account tried this phone
Carrying a friend’s phone in and tapping it
Recorded
Face ID or Touch ID runs before check-in, biometrics only, with no passcode fallback. The result is stored with the check-in. LatchIn only learns whether it matched; biometric data never leaves the phone.
The teacher seesVerified: tag + Face ID, or tapped tag
Switching off Screen Time or the Accessibility service
Reported
This can’t be prevented on a phone the student owns. LatchIn checks the lock at check-in, whenever the app comes to the foreground, every 60 seconds while it’s open, and at every spot check. The student sees “Screen Time is off. Your teacher can see this.” with a button to turn it back on.
The teacher seesLock off since 10:12, with how many times
Deleting the app during class
Reported
During class LatchIn asks the phone to block its removal, which holds while Screen Time access does. Revoking access first shows up as above; reinstalling looks like a new phone and needs approval.
The teacher seesLock off, then a new phone waiting
Setting the phone’s clock forward
Ignored and reported
Class only ends when both the clock and the real elapsed time say so. A clock jump is flagged.
The teacher seesPhone’s clock was changed
Using a look-alike app called “Calculator”
Blocked
On iPhone, name matching only applies to Apple’s own apps. Third-party apps must match the teacher’s list by their exact app ID.
The teacher seesNothing to do
Checking in by a texted tag link from outside
Labelled
Tags hold only the room, so a link can be shared. Check-ins are labelled by method (NFC in the app, tag link, or teacher), and a spot check asks everyone to re-tap the tag within 3 minutes from the same phone.
The teacher seesTag link · Missed spot check 10:35
Tapping in, then walking out
Locked anyway
The lock stays on wherever the phone goes. Leaving early through the sign-out tap is the sanctioned route, and the roster tells it apart from a missed spot check.
The teacher seesSigned out 10:40, or Missed spot check
Evidence,labelled.
Nothing shows as locked just because a student checked in. Each roster row says how strong the evidence is, and focus time is marked verified when the phone reported it, or estimated when it didn’t.
- Locked
- The phone reported the lock engaged and nothing tampered with since. Shows when it was confirmed.
- Lock off
- The phone reported the lock missing or access revoked.
- Not confirmed
- Checked in, but no lock report yet: no permission, an unsupported phone, or it hasn’t reported.
- Released
- Signed out, or class ended.
Limits, stated plainly
- A switched-off lock is noticed the next time LatchIn runs or at the next spot check, not the instant it happens.
- Lock reports come from the student’s own phone. A modified app could lie about them.
- A second device, like a laptop or tablet, isn’t something LatchIn can see. That’s a classroom policy question.
- Only school-managed devices can make the lock impossible to remove. LatchIn is built for the phones students already own.
Roadmap
Planned, not built yet.
- Signed NFC tags that produce a one-time link on every tap, so a shared link stops working
- Silent push wake-ups so a switched-off lock is noticed sooner
- App Attest on iPhone, so the server only counts reports from the genuine app
- Android, planned after iPhone, with Play Integrity and its own safe-mode handling
- A Bluetooth beacon in the room to notice a phone leaving
What LatchIn collects to do all this is in the privacy policy.