Privacy Policy — PekBUS

1. Introduction

Peklenc Research Private Limited (“we”, “us”, or “our”) operates the PekBUS mobile application (the “App”) and related services.

PekBUS is a bus and fleet tracking platform used by transport operators, schools, employers, contractors, and other organisations (each, a Transport Provider) to share live bus location, trip progress, and estimated arrival times with their authorised drivers, riders, passengers, parents, guardians, employees, or other end users.

This Privacy Policy explains what data we collect through the App, how we use it, who we share it with, how long we keep it, and what choices and rights are available to users.

This policy applies to the PekBUS mobile application made available through supported app stores and direct enterprise deployment channels. Separate commercial terms, dashboard terms, or customer agreements may also apply between us and a Transport Provider.

By using the App, you acknowledge the practices described in this Privacy Policy. Where required by law or platform policy, we request specific in-app permissions or consent before collecting sensitive data such as precise or background location.

2. Roles and Service Model

PekBUS is typically provided in a B2B2C model:

• We provide the software platform.
• A Transport Provider configures routes, vehicles, and authorised users.
• End users use the App to participate in transport operations, such as driving, tracking, or receiving arrival updates.

In many cases, the Transport Provider determines which users are invited to the service and what routes or vehicles they can access. The Transport Provider may also provide its own notices, internal policies, or employment/transport terms. This Privacy Policy describes how we handle data within the PekBUS platform.

3. Data We Collect

3.1 Location Data (Driver Devices and Other Tracking-Enabled Roles Only)

We collect precise location data from devices that are configured for live trip sharing, such as a driver device or another tracking-enabled operational role.

What we may collect:

• Latitude and longitude
• Speed and heading
• GPS accuracy
• Timestamp
• Altitude, where available
• Battery status or power-related telemetry for operational diagnostics

When we collect it:

• During an active trip after the user starts tracking, or when tracking is otherwise enabled for a trip by the app workflow
• During route recording, calibration, or setup flows where higher-frequency location is needed
• While the app is in foreground or background, if the trip is still active and the relevant permission has been granted

We do not intentionally collect precise location from rider/passenger/guardian devices merely to let them view ETA, unless a separate feature explicitly requires it and the App clearly asks for the necessary permission.

3.2 Registration and Setup Data

• Organisation, operator, school, company, or fleet identifier
• Route number, bus number, or vehicle identifier
• Stop, pickup point, or destination selection
• QR token, invite token, activation token, or similar onboarding credential
• Role selection (for example, driver, passenger, rider, guardian, employee, or authorised viewer)

3.3 Device and Installation Identifiers

• App-generated device UUID or installation identifier
• Push notification token
• Firebase Installation ID or similar service identifier
• Session, authentication, or refresh token metadata

We do not collect hardware identifiers such as IMEI, phone serial number, or MAC address.

3.4 Consent, Permission, and Account State Records

• Acceptance of Terms or Privacy Policy versions
• Permission prompts and responses
• Timestamp of consent or acknowledgement
• IP address, device metadata, or server logs associated with the request

3.5 Diagnostics and Support Data

• Crash reports and stack traces
• Error logs
• Device model, operating system version, and app version
• Performance and stability metrics

3.6 Camera Access

If your deployment uses QR-based onboarding, the App may request camera access solely to scan a QR code. The App does not capture or store general photos or videos.

4. How We Use Data

• Register and authenticate authorised devices and users
• Associate users with the correct organisation, vehicle, route, or stop
• Display live vehicle position and trip progress
• Compute ETA and related transport predictions
• Send notifications relating to approaching arrival or delays
• Detect route progress, stop arrival, detours, or trip completion
• Maintain security, prevent misuse, detect abuse, and investigate incidents
• Diagnose crashes, errors, and performance issues
• Comply with applicable legal obligations

We do not sell personal data. We do not use in-app personal data for third-party advertising.

5. Sharing and Disclosure

With the Relevant Transport Provider: The organisation that authorised you may access data needed to operate the transport service.

With Service Providers: Cloud hosting (AWS), push notifications (Firebase), crash reporting (Sentry, Crashlytics), mapping providers.

For Legal Reasons: Where required by law, regulation, or valid governmental request.

Corporate Transactions: Data may be transferred in a merger, acquisition, or sale of assets.

6. Data Retention

• Raw trip location events: retained for a limited operational period, then deleted or aggregated
• Registration and access records: retained while active and for a limited period thereafter
• Crash and error logs: retained per vendor settings
• Security and audit logs: retained for a longer period where required

7. Security

We use reasonable technical and organisational safeguards including encryption in transit, access controls, role-based restrictions, tenant separation, logging, and monitoring.

8. International Processing

Data may be processed in India and other countries where our service providers operate. We take reasonable steps to ensure appropriate safeguards.

9. Your Choices and Rights

Subject to applicable law, you may have rights to:

• Access information about your data
• Correct inaccurate data
• Delete or request erasure of certain data
• Withdraw consent where processing is based on consent

Deletion Requests:Use the in-app “Delete My Data” setting or contact support@pekbus.com.

10. Children and Minors

PekBUS is intended for authorised users designated by a Transport Provider. If a deployment involves minors, the Transport Provider is responsible for appropriate authorisations. Contact support@pekbus.com with concerns.

11. Background Location Disclosure

Some deployments request background location access for tracking-enabled roles so live trip sharing continues while the screen is off. The App explains this before requesting the permission. Users can disable it in device settings.

12. Third-Party Links and SDKs

The App may integrate third-party SDKs. Those providers process data according to their own terms.

13. Changes to This Policy

We may update this Privacy Policy from time to time. We will update the “Last Updated” date and provide notice where appropriate.

14. Grievance / Contact