Doorman App FAQ
Doorman's privacy policy is publicly available on their website, and is included in the app itself.
Doorman has a page dedicated to parents on their website, which answers some FAQs and provides a way for parents to ask additional questions directly to a Doorman team member: https://doorman.school/parents
Answers to some FAQs provided by Doorman:
Eastern is currently utilizing Doorman's on-device blocking “Lockdown” mode, not a VPN.
1. Data collected. In order to provide the service, we store a student’s name, school email, student ID, grade, class schedule and bell schedule; app version, device model, and OS version for troubleshooting; tap-in events; bypass events (emergency unlocks, reboots during class); and standard crash and usage analytics. We do not store device advertising IDs, IP addresses, or network metadata.
We do request camera permission, used only to scan a QR code as a backup to tapping in on an NFC tag or to unlock early. It simply scans QR, so no image is ever stored or transmitted.
Examples of what is NOT accessible or collected: messaging, email, or DM content, photos, videos, contacts, browsing history, web page content, content from other apps, location, microphone, etc.
2. Network access. No VPN, configuration profile, certificate, are used in the district's current deployment. Restrictions run on the device itself through the operating system's own app and content restriction APIs. No student network traffic reaches Doorman servers, so there is nothing for us to see or receive.
3. Location. The app never requests location permissions. Doorman won't appear in the device’s location permission list.
4. Tap-in and unlock records. A tap-in record contains a student, school, and class identifier, NFC tag or QR Code info, and a timestamp. An emergency-unlock record contains the student identifier, the timestamp, and the fact that an unlock occurred.
Access to this information is limited to authorized school staff through role-based permissions the district or school administrators can revoke. Dashboard actions are logged.
Whether violation records factor into discipline is a district and school policy decision, but the assumption would be that they do.
5. Retention. The district directs retention under its agreement with us. When the agreement ends we delete student personal information, and the district can request deletion at any point before that. Students who graduate, transfer, or leave drop out of roster sync and their records can be deleted on the same basis. We retain only aggregated, de-identified metrics that cannot reasonably be re-identified.
6. Third parties. Hosted on Google Cloud Platform in the United States. Beyond hosting, there is the district's own Google SSO for authentication, and Sentry for error monitoring. All are contractually bound to protect the data and use it only to provide services to us. None receive student data for their own purposes, and none may use it for advertising, marketing, profiling, or model training.
7. Data use. Doorman does not sell student data, use it for advertising or marketing, or use it to train AI models. Contractually, we are an approved Student Data Privacy Consortium vendor and the district becomes party to our National Data Privacy Agreement by signing Exhibit E. FERPA, SOPIPA, and COPPA also apply.
8. Privacy and security review. The signed SDPC Exhibit E is the district's Data Privacy Agreement with Doorman, and the NDPA terms are publicly available. On our side we maintain encryption in transit and at rest, role-based access controls, audit logging, and regular internal security assessments.