Privacy Policy

Information and purposes

Account information can include your name, contact details and authentication records. Journey information includes pickup and destination, travel date, selected service and booking reference. These records support account access, booking coordination and service administration.

Payments and location

The booking flow uses a payment-provider integration. Payment references, amounts and transaction states may be retained for reconciliation and support. Enter payment credentials only in the payment provider's secure interface.

Journey locations are used to search and coordinate a trip. If a location feature requests device permission, review the browser prompt; you can decline or change that permission in your device settings.

Cookies and service providers

Authentication cookies and local browser storage support account sessions and essential application functions. The Cookie Policy explains these categories.

Transport providers, payment services, infrastructure providers and authorized personnel may need relevant information to fulfil their roles. Business review must confirm the recipient list, purposes, contractual safeguards and any international processing.

Retention and security

Keep information only for the confirmed operational, contractual and legal purposes for which it is required. The business must approve and document a retention and deletion schedule.

Access controls and authentication help protect information. No website or transmission method can promise absolute security. Report a suspected account issue through a verified support channel.

Choices, rights and grievances

Depending on applicable law and the processing involved, you may be able to request access, correction, erasure, consent withdrawal, grievance redressal or nomination. Identity verification may be necessary before a request can be handled.

Business review required: publish the request method, responsible contact and escalation process. Explain any consequences of withdrawing consent, the treatment of children's data, and any applicable exceptions. A policy page alone does not establish DPDP compliance.

Policy changes

Material changes should be communicated with an approved effective date and a clear explanation. The business must complete legal review against the applicable commencement provisions before final adoption.

Questions and requests

Use verified contact details supplied with your booking or business agreement, where available. Do not share payment credentials or one-time passwords.

Business review required: confirm and publish the responsible legal entity, service address, support channel and privacy/grievance contact before treating these notices as final.