Trust & Compliance
Safety & Compliance
How BlueBird Alerts approaches emergency communication, data protection, and operational reliability for schools and districts.
1Purpose & Scope
BlueBird Alerts is designed to deliver fast, reliable internal emergency notifications to school staff who have the BlueBird app installed. It is a push-notification and in-app alert system — not an emergency dispatch system.
- Sends real-time push notifications to registered iOS and Android devices
- Provides administrators a single activation point for school-wide alerts
- Supports training drills via a dedicated "Training Mode" that does not trigger real notifications
- Scoped to individual school tenants — each school's data and alerts are fully isolated
BlueBird Alerts is intended to augment existing emergency protocols, not replace them. Schools should maintain separate emergency response plans independent of this system.
2Emergency Disclaimer
⚠ BlueBird Alerts does not contact 911 or emergency services.
Activating an alert sends push notifications to registered staff devices only. It does not notify police, fire, or medical services. In any real emergency, call 911 immediately.
When activating a live (non-training) alarm, administrators are required to check an EMS acknowledgment confirming that 911 has been contacted or is not required before the alert is sent.
- Live alarm activation requires an explicit EMS acknowledgment checkbox
- Training mode alarms are visually distinct and never trigger real notifications or SMS
- Safety disclaimers are shown on the admin dashboard, login portal, and alarm activation form
- Administrators cannot bypass the EMS acknowledgment during live alarm activation
3Data Privacy
BlueBird Alerts collects only the data required to deliver its core service. No student data is collected or processed.
- User accounts store name, email, phone (optional), and hashed credentials — no student records
- Device tokens are stored and used exclusively for push notification delivery
- Alert history is retained within the platform for audit and drill-report purposes
- Message content sent via push or SMS is logged for audit trail and troubleshooting
- Data is scoped per school tenant — administrators can only access their own school's data
No data is sold to third parties. Device tokens are transmitted to Apple (APNs) and Google (FCM) solely for push delivery, under the terms of their respective developer agreements.
4Role-Based Access Control
BlueBird Alerts uses a multi-tier role system to ensure users have access only to what they need.
- Staff — can receive alerts and acknowledge them on their device; no admin console access
- Building Admin — can activate and deactivate alarms, manage users, and view reports for their school
- District Admin — oversight access across all schools in their district
- Super Admin — platform-level access; manages tenant provisioning and system configuration
All authenticated active users can trigger emergency alarms. Only Building Admins and above can deactivate an active alarm. TOTP two-factor authentication is strongly encouraged for all administrator accounts.
5Audit Logging
BlueBird Alerts maintains a full audit log of all significant actions within the platform.
- Alarm activations and deactivations — who, when, and message content
- User account changes — creation, role changes, and deactivation
- Admin logins and session events
- Access code generation and redemption
- Push delivery outcomes and acknowledgement events
Audit logs are visible to Building Admins and above in the Admin Console under the Activity section. Super Admins have access to platform-wide audit trails.
6Device Awareness
Real-time push delivery depends on staff having the BlueBird app installed and registered. The platform provides device health visibility to administrators at all times.
- Total registered device count is shown in the System Health panel on the admin dashboard
- Recently active devices (seen within 30 days) are tracked separately from stale registrations
- Device coverage — ratio of active users with registered devices — is a key readiness indicator
- Stale or revoked device tokens are automatically pruned from the delivery pool on the next push attempt
Schools should aim for at least one registered device per active user to ensure full push coverage during an emergency.
7System Reliability
BlueBird Alerts is designed with high availability in mind for critical communication paths.
- Emergency alert delivery is never blocked by billing status or subscription plan limits
- Push delivery uses industry-standard APNs and FCM infrastructure with automatic retry logic
- SMS fallback via Twilio provides a secondary delivery channel when push is unavailable
- Training Mode allows administrators to test the full alert flow without sending real notifications
- The admin console provides real-time alarm state visibility with no polling delay
BlueBird Alerts requires an active internet connection on both the server and registered staff devices. It is not a replacement for hardwired PA systems or offline emergency equipment.
8Training Support
Regular drills are essential for ensuring staff familiarity with the alert system before a real emergency occurs.
- Training Mode activates the full alarm flow on staff devices without sending real push or SMS
- The Drill Readiness panel on the dashboard shows push configuration status and device registration counts
- Post-drill PDF reports are automatically generated and available for download
- The system surfaces a "no recent drill" reminder when no alerts have been sent in the past 7 days
- Access codes allow new staff to self-register before a drill without requiring admin action per-user
It is recommended to run at least one training drill per semester to verify device registrations, delivery paths, and staff familiarity with the alert flow.
