School Vahan processes information about students, parents, drivers, attendants and vehicles in order to provide school transport visibility and safety monitoring. This policy explains what is collected, why, who can see it and how long it is kept.
LAST UPDATED
27 August 2026
01Who controls the data
The school is the controller of its transport data and decides what is recorded and who may access it. Telliepact Global acts as the processor, handling that data on the school's instructions in order to run the platform.
02Student information
We process the student details the school provides — name, class, photograph where supplied, assigned stop, bus and route — together with boarding and drop events. This exists so that the school can maintain a transport record and so a parent can see their own child's journey.
03Parent information
We process a parent's name, contact number, email and relationship to the student, in order to authenticate their account and deliver transport notifications. Parents see only the bus, stop and journey relevant to their own child.
04Staff information
For drivers and attendants we process name, contact details, assignment, licence and verification records where the school uploads them, and duty status. This supports assignment, compliance tracking and contact during a trip.
05Vehicle and location data
Tracking hardware records vehicle location, speed and trip events during a school trip. This data drives live tracking, ETA, route-progress and safety alerts, and forms the historical trip record the school can report on.
06Optional sensor and camera data
RFID, CCTV, door and temperature modules are optional. Where a school enables them, the resulting records are processed for the stated purpose only — boarding accuracy, incident review or cabin monitoring — and access is limited to the roles the school authorises.
07Who can see what
Access is role-based. The school's transport team sees fleet-wide operations; a driver sees the assigned trip; an attendant sees the students at their stops; a parent sees only their own child. Our staff access production data only where necessary for support, and that access is logged.
08Notifications
Transport notifications — boarding, drop, delay, ETA and safety updates — are sent to parents only where the school has enabled them, and only for that parent's child. Notification preferences can be adjusted per account.
09Retention
Operational records such as trips, boarding events and alerts are retained for the period the school configures for its reporting and compliance needs. On termination, records are made available for export before deletion within a reasonable period.
10Security
Data is transmitted over encrypted connections and stored with access controls, role separation and audit logging. Hardware is provisioned per vehicle. We review access rights periodically and require support access to be justified.
11Sharing with third parties
We share data only with the connectivity and infrastructure providers needed to operate the platform, with any hardware partner servicing a school's devices, and where required by law or a lawful request from a competent authority. We do not sell personal data and do not use student data for advertising.
12Your rights and requests
Parents and staff can ask the school to correct their details or to explain what is recorded about them. Requests to access, correct or delete data should be raised with the school, which may pass them to us as processor. We will support the school in responding.