Privacy Policy
FleetShield handles children's data. We treat that responsibility as the core of the product, not a footnote.
Categories of Data Processed
FleetShield processes data provided by schools and drivers: (a) Student data: name, roll/admission number, class/section, allocated stop, boarding and deboarding timestamps; (b) Guardian data: name, mobile contact numbers; (c) Crew data: driver/attendant names, phone numbers (used for Firebase Phone Auth verification), driving licence details, police verification records; (d) Vehicle & Telemetry data: vehicle registration, fitness/permit certificates, and smartphone GPS coordinates recorded during active trips.
Data Fiduciary vs. Data Processor
Under the Digital Personal Data Protection Act, 2023 (DPDPA), the subscribing educational institution acts as the Data Fiduciary that establishes the purpose of processing. FleetShield acts strictly as a Data Processor, processing information solely to facilitate safe school transit operations under the documented instructions of the school.
Purpose of Processing
Data is processed exclusively to: (a) operate real-time transit telemetry and route adherence monitoring, (b) authenticate drivers securely using one-time verification codes, (c) maintain driver digital attendance and student manifest registers, (d) manage vehicle and driver compliance expiration tracking, and (e) provide administrative incident logs. Personal data is never monetized, rented, or utilized for profiling or advertising.
Trip Telemetry & Location Privacy
Driver smartphone GPS coordinates, speed, and heading are collected strictly while a scheduled trip is marked as 'Active' in the driver mobile application. To ensure student safety and route monitoring, location is gathered in both foreground and background while a trip is in progress. Telemetry tracking ceases immediately when the trip is closed by the crew or completed by the school dispatch console.
Sub-processors & Infrastructure
FleetShield engages trusted cloud and mapping infrastructure sub-processors: (a) Oracle Cloud Infrastructure (managed cloud hosting in India region & PostgreSQL 17 database), (b) Google Maps Platform (geocoding, tile rendering, and routing API services), and (c) Google Firebase (secure driver phone authentication and push messaging). All sub-processors operate under stringent confidentiality and data security obligations.
Data Retention & Account Deletion
Data is retained for the operational duration of the school's active subscription contract and any statutory compliance audit intervals required under Indian transport regulations. Users and drivers may request account or data deletion at any time by contacting privacy@fleetshield.in or routing requests through their school administration. Upon verified request, personal telemetry and authentication records are securely purged or anonymized within 30 days.
Multi-Tenancy & Access Security
Access to personal and transit records is strictly partitioned by multi-tenant school boundaries and role-based permissions (School Admins, Transport Managers, Dispatchers, Drivers). High-privilege administrative actions, roster edits, and document verifications generate persistent audit logs.
Statutory Grievance Redressal Officer
In accordance with the Information Technology Act, 2000 and DPDPA 2023, queries or grievances regarding data processing may be directed to: Grievance Officer: FleetShield Grievance Cell, Email: privacy@fleetshield.in, Postal Address: FleetShield India, Ahmedabad, Gujarat, India.
Ready to Modernize Your School Transport?
A 30-minute walkthrough with your routes, your buses and your compliance requirements, without generic demo data.
Typical rollout goes live in 4 weeks · No hardware lock-in · Dedicated onboarding lead