The simplest way to protect student data is to collect almost none of it. Here's exactly what MorningCount stores, what it doesn't, and how it's protected.
A production-planning count for the kitchen. Not the point-of-service count your program claims for federal reimbursement.
Students and teachers never create accounts or type passwords. A district master code unlocks each classroom screen once, and it stays unlocked for about six months. Cafeteria reports can carry a separate password per school. Administrators can revoke every device in one click, which also clears every cafeteria unlock.
Unlock attempts are rate-limited. Access cookies are signed and inaccessible to page scripts. All codes are managed from one admin screen.
Platform pages make zero requests to outside services. No analytics scripts, no fonts from a CDN, no embedded anything. Every page is marked off-limits to search engines, and crawlers are blocked at the root. Student names never appear in server logs.
MorningCount runs on managed hosting that maintains a SOC 2 report, in US data centers, behind Cloudflare. Site files, databases, and backups are encrypted at rest. Every connection is encrypted in transit. Backups run automatically.
Rosters, picks, and history belong to the district. Export trends to CSV anytime. When an agreement ends, your data is returned or deleted at your direction.
