Encryption
Data is encrypted in transit. Sensitive server credentials stay server-side and are not exposed to browsers or mobile apps.
Trust centerThe details behind
The details behind
the calm trip dashboard.
Flock handles minors, live location, medical context, and emergency workflow records. This page gives school leaders, nurses, technology teams, and counsel a clear starting point for review.
LAST UPDATED — MAY 27, 2026
AVAILABLE DURING PROCUREMENT
Request packet →DPA, privacy policy, security overview, sub-processor list, retention notes, insurance review, and district rollout plan.
Security overview
Tenant isolation
Organizations, trips, rosters, medical records, messages, and billing records are scoped to the school or district that owns them.
Role-based access
Nurses and trip leaders receive the broadest trip access. Chaperones receive only the student and group context needed for their assignment.
Audit logging
Medical access, SOS activity, trip messages, check-ins, and administrative changes are designed to leave reviewable records.
Incident response
If a security incident affects customer data, Flock notifies the affected organization without undue delay and shares what is known.
Student privacy
FERPA posture
For school customers, Flock acts as a school-directed service provider with a legitimate educational interest in operating trip safety workflows.
COPPA posture
Flock is provided through schools and youth organizations, not for independent child sign-up. Schools control parent notice and consent requirements.
No advertising use
Flock does not sell student data, run ads against student data, or build advertising profiles from trip activity.
School control
Schools can request deletion, export, or correction of records through their organization administrator or support channel.
Location and retention
Trip-window sharing
Location is intended for active trip operations and is not a general-purpose student tracking product.
SOS history
SOS events retain enough context for resolution review: time opened, status changes, staff notes, and relevant location context.
Archived trips
Completed trips preserve operational records for school review, then can be deleted or exported according to the school relationship and DPA.
Graduation and account closure
When an organization leaves Flock, records can be returned or deleted on request, subject to legal or contractual retention obligations.
Medical boundaries
Need-to-know access
Full medical details are limited to nurses and trip leaders; chaperones see critical alerts only when they are assigned to the relevant trip or group.
Emergency contacts
Emergency contacts are surfaced alongside an SOS or student profile for staff responsible for that student.
Public confirmation
Parent medical-confirmation pages use one-time verification and access logging before any record is shown.
Volunteer visibility
Volunteer and chaperone access is role-scoped so sensitive records do not become available just because someone is helping on a trip.
Operational limits
Not emergency services
Flock coordinates school staff during a trip. It does not replace calling 911 or following the school emergency plan.
GPS limitations
Location accuracy depends on device hardware, permissions, battery, network conditions, and the surrounding environment.
Connectivity
Staff should keep existing offline procedures for areas with poor service, low battery, or device loss.
Human responsibility
Trip leaders and schools remain responsible for supervision, headcounts, emergency escalation, and final decisions on the ground.