EduBB Driver — Privacy Policy
Applies to the EduBB Driver app for Android
(package com.edubb.driver) and iOS
(bundle ID com.edubb.driver).
Last updated: 22 September 2026
1. Who we are and who uses this app
EduBB is a school-bus and fleet management platform operated by
TechBySoul (“we”, “us”). The EduBB Driver app is a workforce
application used by drivers employed by or contracted to organisations —
schools and fleet operators — that subscribe to EduBB.
This policy covers both the Android and the iOS versions of the app. Where the two
behave differently, the difference is called out below.
Accounts cannot be self-registered. A driver signs in with an organisation
domain, a mobile number and a password issued by their organisation. The
organisation is the controller of the data recorded through the app; we
process that data on the organisation's behalf as its service provider.
2. Information the app collects
Account and profile information
- Driver name, mobile number and email address
- The organisation the driver belongs to
- Licence and employment details entered by the organisation
Location information
-
Precise and approximate location of the device is collected
only while a trip is active — that is, after the driver taps
Start Trip and until the driver taps End Trip.
-
Each reading includes latitude, longitude, accuracy, speed and bearing, and is
written to the organisation's live-tracking database so the vehicle's progress
can be followed in real time.
-
The location at which each passenger pick-up and drop-off is marked is stored
with the trip record.
-
Android: while a trip is running, the app displays a persistent
“Trip in Progress” notification. The app does not request
background location permission, does not track the driver outside an active trip,
and does not collect location when no trip is running.
-
iOS: the app asks only for “While Using the App”
location access. It reads the device's position when the driver starts or ends a
trip, marks a stop, pick-up or drop-off, centres a geofence, or views the trip
map — only while the app is open on screen. The iOS app does not run background
location tracking.
-
The location of the vehicle may also be reported by a GPS tracking device fitted
to the vehicle by the organisation. That device is not part of this app.
Passenger and trip data entered by the driver
- Rider names, class, roll number or admission number shown on the trip list
- Boarding and alighting events, absence reasons and trip notes
- Route, schedule and odometer / daily running entries
This information is supplied by the organisation and recorded by the driver on the
organisation's behalf. Drivers should record only what the organisation requires.
Camera and photos
-
The camera and photo picker are used to attach a fuel receipt,
an odometer reading or a vehicle document image to an expense,
trip or certificate record. This is optional — a fuel entry can be saved without
a photo.
-
Where the organisation uses student ID cards, the camera is used to
scan a student's QR code at pick-up or drop-off. The scan is read
on the device; no image of it is stored.
-
The app does not browse, index or upload any other images from the device.
Device, diagnostic and usage data
- Device model, operating system version and app version
- A push-notification token, so the organisation's notifications can reach the
device (Firebase Cloud Messaging, and on iOS the Apple Push Notification
service)
- Android only: crash reports and performance diagnostics
(Firebase Crashlytics), basic in-app interaction events (Firebase Analytics), and
the installation identifiers these services generate
The iOS app does not include crash-reporting or analytics SDKs. Neither version
uses an advertising identifier, tracks the driver across other companies' apps or
websites, or contains advertising.
Notifications
With permission, the app sends notifications about assigned trips, schedule changes
and messages from the organisation.
3. How the information is used
- To show the driver their assigned trips, routes and rider lists
- To share the vehicle's live position during a trip with the driver's own
organisation, and — for school routes — with the parents of the riders on that
trip
- To record attendance, pick-up and drop-off events for the organisation
- To record fuel, maintenance, expense and vehicle-certificate entries
- To send operational notifications
- To keep the service secure, diagnose crashes and improve reliability
- To meet legal obligations and enforce our terms
We do not sell personal data, and we do not use location data for advertising or
for any purpose unrelated to transport operations.
4. How the information is shared
-
With the driver's employing organisation: transport
coordinators and administrators of that organisation can see trip location,
attendance, fleet and expense records.
-
With parents and guardians: during an active school trip, the
vehicle's live location and their own child's pick-up / drop-off status are shown
to the parents of riders assigned to that trip.
-
With service providers: Google Firebase (real-time location
database, push notifications, and on Android crash reporting and analytics);
Google Maps Platform (maps and route display on Android); Apple (Maps and push
notifications on iOS) — each under their own data-protection terms; and our
hosting provider.
-
For legal or safety reasons: where required by law, or to
protect the rights and safety of users, students or the public.
5. Data security
All traffic between the app and our servers, and between the app and Firebase, is
encrypted in transit using HTTPS/TLS. Access to an organisation's data is limited
to authenticated users of that organisation. No system is completely secure —
drivers should keep their password confidential and report any suspected
unauthorised access to us.
6. Data retention
Trip, attendance, location-history and fleet records are retained for as long as
the employing organisation's subscription requires them, and thereafter for any
period required by law or contract. Live location readings are retained as trip
history; they are not kept as a continuous record of the driver outside trips.
When retention ends, data is deleted or anonymised where reasonably possible.
7. Your rights, and how to request deletion
Driver accounts are created and controlled by the employing organisation, so
account and data deletion is requested through that organisation's EduBB
administrator, who can deactivate the account and remove the driver's records.
If you cannot reach your organisation, or you want to raise a request directly,
write to edubb@techbysoul.com from the
email or with the mobile number on the account. We will act on the request, or pass
it to the controlling organisation, within 30 days.
You can also revoke location, camera, photo or notification permission at any time:
- Android: Settings → Apps → EduBB Driver → Permissions
- iOS: Settings → EduBB Driver (or Settings → Privacy &
Security → Location Services / Camera / Photos)
Revoking location permission stops trip tracking and location-stamped stop
marking, which are core functions of the app.
8. Children's data
This app is intended for adult drivers only and is not directed at children. It
does display rider details — including children's names and classes — supplied by
the organisation, so that the driver can carry out the route. That data is
controlled by the school and is not used for profiling or advertising.
9. Third-party services
10. Changes to this policy
We may update this policy from time to time. When we do, the “Last updated” date
above changes. Continued use of the app after an update means you accept the
revised policy.
11. Contact us
EduBB / TechBySoul
Email: edubb@techbysoul.com
Phone: +91 8089890401
Website: edubb.in
