Teacher Command Center (TCC)

Security, Safety, and Data Protection

At Centennial Education Solutions, everything we build for the Teacher Command Center (TCC) is guided by one core principle:

Is this in the long-term best interest of schools, staff, and students

That principle shapes how TCC is designed, built, and operated, with privacy, security, and school control embedded from the start.

Our promises to schools:

  • We do not sell, share, or monetize student or staff data

  • Schools own their data, Centennial does not

  • We collect only what is necessary for daily school operations

  • We do not build surveillance tools

  • We design for calm, safety, and defensibility, not visibility or engagement

Compliance & alignment

TCC is designed to align with common K–12 data protection expectations, including:

  • FERPA-aligned data handling

  • School-controlled access and retention

  • Privacy-first system design

  • Additional compliance documentation is available upon request.

Product security (high-level)

  • Security is built into TCC at the product level, not added later.

  • Encrypted data in transit and at rest

  • Secure authentication and access controls

  • Continuous monitoring for reliability and integrity

  • Logging and alerting for operational and security events

  • We intentionally avoid publishing sensitive infrastructure details publicly.

Audit logging & accountability

  • All actions in TCC are time-stamped

  • Clear attribution of who did what and when

  • Logs are available to authorized school administrators

  • These records exist to protect staff and schools through clarity and documentation.

Photos & media safety (Safe Photo)

  • Photos are captured inside the TCC application

  • Photos are never stored on personal devices

  • Photos are not stored on Centennial servers

  • Photos are delivered directly to school-owned infrastructure

  • Centennial does not retain media copies

  • Media consent, access, and retention policies are managed by the schoolTCC functions as a secure delivery mechanism, not a media repository.

Behavior documentation safeguards

  • Behavior documentation in TCC is intentionally quiet and professional.

  • Factual, time-stamped records

  • No severity scoring

  • No automated conclusions

  • No parent-facing feeds

  • No behavioral analytics or ranking

  • Behavior logs exist to support documentation and institutional memory, not discipline automation.

Attendance & operational data

  • Attendance is entered directly by staff

  • No passive tracking or background monitoring

  • Support and movement requests are role-restricted

  • All operational actions are logged

Emergency & SOS boundaries

  • SOS is a role-routed assistance request, not a command system

  • No GPS tracking

  • No continuous monitoring

  • No automatic lockdowns or drills

  • No parent notifications

  • TCC supports existing school emergency protocols. It does not replace them.

Access control & permissions

  • Role-based access (teacher, front office, admin, nurse, specialist)

  • Least-privilege access by default

  • Substitute mode with restricted functionality

  • Administrative overrides are logged

Wearable interfaces

  • No student names displayed

  • No visible student data

  • Devices automatically lock when removed

What TCC intentionally does not do

  • No surveillance

  • No student tracking

  • No social feeds

  • No advertising

  • No data sales

  • No parent messaging during pilot phase

  • No AI-driven behavioral scoring

  • No use of student data to train AI models

  • Boundaries are a core part of our security model.

Responsible disclosure

If you believe you have identified a security issue or vulnerability, please contact:

security@centenniales.com

We take responsible disclosure seriously.

The Teacher Command Center is designed to make schools safer, calmer, and more defensible, without increasing noise, exposure, or surveillance.