Tracking only initiates once a driver scans the official trip QR code. No GPS data is transmitted or recorded before this explicit activation sequence, ensuring operational privacy.

Yes. Our "Resilience Protocol" allows a supervisor to authorize a vehicle swap. The trip log remains continuous, but the telemetry source shifts to the backup vehicle to maintain the audit trail.

No. The Navigster architecture physically disconnects location services when no active trip is assigned. Background monitoring is strictly prohibited by the system's core governance framework.

Suspension immediately revokes all authentication tokens. The user will be logged out across all devices and will be unable to initiate new trips or access sensitive data containers until reinstated by an Admin.

Pickup locations are controlled by the Transport Manager. Changes can be made in real-time through the dashboard, but are logged as "Route Exceptions" to maintain institutional accountability.

Access is governed by Role-Based Access Control (RBAC). Only Institution Admins and designated Transport Managers have permission to view historical logs within their specific data container.

Never. We use a multi-tenant Secure isolation model. Every institution operates in a separate data silo, ensuring that student data never leaks across organizational boundaries.

The mobile application stores telemetry data locally using secure, encrypted edge storage. Once a stable connection is re-established, the data is synced with the central governance logs automatically.