WayWink security
Protect transport visibility by controlling who can see and manage it.
WayWink connects information about students, parents, drivers, vehicles and active journeys. Product security begins with making that information available to the appropriate users and transport roles.
Product security
Start with access to the transport operation.
A school transportation platform can contain information about children, parents, drivers, vehicles, routes and live journeys. The usefulness of that information depends on it being visible to the people who need it without making the same information available indiscriminately.
WayWink therefore separates the administrator, driver and parent experiences. Each role participates in a different part of the transportation workflow.
This page focuses on product-level controls that can be stated about WayWink today. It intentionally does not make broader infrastructure or certification claims that have not been established.
Access controls
Controls connected to the way transportation is managed.
Authorized accounts
WayWink transportation information is intended for users who have been given access to the relevant school transport environment.
Role permissions
Administrators, drivers and parents participate in different parts of the product based on their responsibilities.
Parent and student relationships
Parent visibility is connected to the child or children associated with that parent account.
Driver assignments
Driver workflows are connected to the buses, trips, routes and stops assigned for transport operations.
Operational records
Trip, attendance and transport activity can remain available as historical context for authorized review.
Audit history
Audit records can provide additional context around activity within the transport operation.
Role separation
Different responsibilities require different visibility.
A parent should not receive an administrator workspace, and a driver should not need access to the entire school transport database to run an assigned trip.
School administrator
Works with school-side transportation administration including routes, stops, buses, drivers, students, parents, assignments, trips, attendance and reporting.
Driver
Works with information needed for assigned transport journeys, including the vehicle, route, stops, expected students and trip actions.
Parent
Receives child-specific transportation information associated with the parent account and participating school.
Operational records
Security also means preserving useful operational context.
School transport does not stop being relevant when a live trip ends. Attendance records, completed journeys, operational alerts and audit history can provide useful context when an authorized school user needs to understand previous activity.
Maintaining that history can help reduce dependence on informal messages, phone calls or disconnected records when reviewing transport events.
Location information
Live school transport location should not be public by default.
Live vehicle location can reveal information about an active school journey, its route and the movement of students between home and school.
WayWink places that visibility inside authorized administrator, driver and parent experiences rather than presenting the transport journey as a publicly accessible tracking page.
Location information can also be affected by device availability, positioning accuracy, network connectivity and other operational conditions.
Transport information
Information that deserves deliberate access decisions.
Live vehicle location
Student transport relationships
Parent and child associations
Driver and vehicle assignments
Trip activity
Attendance and boarding records
Transport alerts and operational events
Security transparency
Avoid turning security language into claims we cannot support.
Security is broader than a feature list.
Access controls and audit history are useful product controls, but they should not be presented as proof of a broader certification or security standard that has not been established.
Location information requires controlled access.
Live vehicle location is operational information connected to students, families and active school transport. It should not be treated as public tracking information.
Operational security does not replace school responsibility.
Schools remain responsible for transport policies, account administration, user access decisions, supervision and operational procedures.
About this page
This page does not claim specific certifications, encryption standards, penetration-testing schedules, infrastructure architecture, data residency guarantees, backup commitments or authentication features unless those capabilities have been separately established and documented.
Security questions
Need more information?
Schools evaluating WayWink can contact us with questions about product access, role permissions, transport visibility or deployment-specific security requirements.