Frequently Asked Questions
Q: Is InSchool.me safe for our kids?
A: YES. In fact, a huge difference between InSchool.me and something like Roblox or Snapchat is this:
• On those open platforms, people can search, friend-request, or randomly message kids.
• InSchool.me has no discovery, no search, no way for an outsider to even know a child exists.
• An outsider would only succeed if a child willfully hands them their parent email and the parent then somehow approves the link request.
Q. I have multiple kids, can I have them all in one chat? What about my spouse / relative / babysitter?
A: Yes. Parents will have the option to add additional siblings and or spouses / guardians / relatives.
Q: Is InSchool.me in the App Store or Google Play?
A: Right now, InSchool.me is a web app, (But the app is coming!) which means you don’t need to download it from the App Store or Google Play just yet. Just open your browser (Safari, Chrome, or Edge), sign in, and you’re ready to go.
It can behave like an app, you can add it to your home screen:
On iPhone/iPad: Open Safari, tap the Share button, then scroll down and choose “Add to Home Screen.”
On Android: Open Chrome, tap the ⋮ menu, then select “Add to Home screen.”
Once added, InSchool.me launches full-screen, just like any other app.
Q: Will this distract students from learning?
A: No. InSchool.me is designed to be the opposite of social media. There are no feeds, no images, no games, just short, direct messages between parents and their children. Schools can also set limits, such as muting notifications during class hours.
Q: Could parents use this to help kids cheat during tests?
A: Schools already provide students with internet-connected devices, which offer far greater opportunities for misuse than InSchool.me. Our system can be paused during testing hours, and all communication is auditable. Unlike texting or social media, there are no disappearing messages, everything is transparent, accountable and recoverable.
Q: My kid says the app is kind of boring?
A: HAHA. Yes it is. That’s our goal, simple and safe parent to child communication! We had too many ride mixups and last minute plan changes with our kids, we wanted it simple!
Q: What about safety and privacy?
A: InSchool.me is built with safety at its core:
Only verified parents can message their child.
Two-step authentication ensures security.
Students cannot message other students.
All communications stay within a closed, COPPA-compliant system.
Q: Will teachers or staff have to monitor messages?
A: No. InSchool.me is a direct line between parents and students. It does not require teacher involvement or extra work. Administrators can set global policies, but day-to-day use does not burden staff.
Q: Why should schools adopt this if it’s mainly for parents?
A: Schools benefit as well. InSchool.me:
Reduces interruptions from parent calls to the front office.
Reduces interruptions from parent emails to teachers for minuscule problems.
Provides a district-wide tool for announcements, reminders, and emergency alerts.
Offers a safe, uniform alternative to students sneaking phones or relying on multiple, inconsistent communication methods.
Q: What if parents or students misuse InSchool.me?
A: InSchool.me includes built-in protections:
Schools can set messaging limits.
Administrators can review flagged conversations.
No peer-to-peer messaging means no risk of student-to-student bullying.
Q: How does this fit with our existing technology?
A: InSchool.me is a lightweight, web-based platform. It requires no downloads, no new hardware, and works on the Chromebooks, tablets, and laptops schools already provide. It can also complement existing parent portals by focusing on short, timely communication rather than replacing broader systems.
Q. Is a PWA “easier to hack” than a traditional app?
A: No. A PWA (Progressive Web App) is built on the same web technologies (HTTPS, TLS encryption, secure APIs) that banks, healthcare portals, and government services rely on.
Security depends on how it’s built, not the label “PWA” vs. “native app.”
A poorly coded iOS or Android app can be just as vulnerable (or more so) than a properly secured PWA.
The real difference:
Native apps are distributed through app stores, which provide some vetting.
PWAs run in the browser sandbox, which actually limits what they can access on a device (they can’t dig into contacts, SMS, or photos unless explicitly allowed).
So in some ways, a PWA is more locked down by default.
