DiliBus

Privacy Policy

How DiliBus collects, uses, shares and protects your personal data when you use the DiliBus app, and how you can delete your account.

Last updated: 20 November 2026Effective from: 20 November 2026

Your privacy at a glance

Contents
  1. Who we are
  2. Scope of this policy and your consent
  3. Information we collect
  4. Permissions the app asks for
  5. Information we do not collect
  6. How we use your information
  7. How we share your information
  8. E-tickets, ticket links and profile photos
  9. Notifications and messages
  10. Where your data is stored
  11. How long we keep your data
  12. How to delete your account
  13. Your rights and choices
  14. How we protect your data
  15. Children's privacy
  16. Third-party services and links
  17. Changes to this policy
  18. Contact us and Grievance Officer

1Who we are

DiliBus ("DiliBus", "we", "us" or "our") is an online bus ticket booking platform based in New Delhi, India. With the DiliBus app you can search buses, choose your seats, pay online and manage your tickets. DiliBus does not run buses itself. Every journey is operated by the independent bus operator named on your ticket.

Under Indian data protection law, DiliBus is the Data Fiduciary for the personal data collected through the app. This means we decide why and how your personal data is processed, and we are responsible for protecting it.

Address
RZ-26P/26 GALINO 33, INDRA PARK PALAM COLONY, Indira Park, Palam Police Station, New Delhi, South West Delhi-110045, Delhi, India
Email
dilibus.app@gmail.com
Phone
+91 971 888 2649

2Scope of this policy and your consent

This Privacy Policy applies to the DiliBus mobile app for Android and iOS. It also covers the services we provide to travellers through the app: account and login, bus search, seat booking, payments, cancellations and refunds, e-tickets, notifications and customer support (together, the "Services").

We handle personal data in line with the following laws, to the extent each is in force:

You give your consent through clear actions: logging in with your mobile number, filling in your profile, entering passenger details or allowing notifications. Each of these lets us process that information for the purposes described in this policy.

You can withdraw your consent at any time (see section 13). Withdrawing does not affect processing already done, but some features may stop working. For example, we cannot issue a ticket without passenger details.

Please also read our Terms & Conditions, which govern your use of the Services.

3Information we collect

3.1 Information you give us

3.2 Information created when you use the Services

3.3 Information that stays on your device

This information is not sent to our servers, except your language choice as explained above. You can remove it by clearing the app's data or uninstalling the app.

3.4 Data at a glance

DataWhy we use itShared withRequired?
Mobile numberLogin with OTP, account security, messages about your bookingsSMS provider (to send the OTP)Required
Name, email, age, genderYour profile and tickets; contacting you about bookings and supportRazorpay (your name, pre-filled at checkout)Required
Profile photoShown on your account screenCloud storage providerOptional
Passenger details (name, age, gender, seat, optional mobile)Issuing tickets; seat rules for ladies and gents seats and for childrenPrinted on your e-ticket. Bus operators see seat numbers only, not namesRequired to book
Booking contact mobile and emailPrinted on the e-ticket; messages about that bookingRazorpay (pre-filled at checkout); messaging provider if we send your ticket by SMS or WhatsAppMobile required Email optional
Booking and payment recordsConfirming bookings, refunds, GST and accounts, supportRazorpay; the bus operator (seat numbers, route, date, fare and status only); authorities when required by lawRequired to book
Saved passengersFilling passenger details fasterNot sharedOptional
Support messagesAnswering your questions and complaintsOnly if needed to solve your issue (for example, with the bus operator or Razorpay)Optional
Push token, device OS, app language, notification settingDelivering notifications in your languageExpo, Apple Push Notification service, Google Firebase Cloud MessagingOptional
IP address and technical logsSecurity, preventing abuse, fixing errorsOur hosting providerAutomatic
Recent searches, theme, welcome-screen statusConvenienceNot shared; stays on your deviceAutomatic

4Permissions the app asks for

The app asks for a permission only when a feature needs it, and you can say no. Saying no only switches off that feature. You can change your choice at any time in your phone's settings.

PermissionWhen and why
Notifications OptionalAsked once, after the welcome screens. Used for booking confirmations, cancellations and refunds, trip updates (bus started or running late), replies from support, and offers.
Camera OptionalUsed only when you tap Take photo to set your profile photo.
Photos OptionalUsed only when you tap Choose from library to pick a profile photo. Only the picture you select is uploaded. We do not read or upload any other photo or file.

The app does not ask for access to your location, contacts, microphone, SMS, call logs or calendar.

5Information we do not collect

6How we use your information

We use your information only for the following purposes:

We do not sell your personal data or use it to profile you for advertising. We do not use it to make automated decisions that have legal or similarly significant effects on you.

7How we share your information

We never sell or rent your personal data. We share it only as described below, and only as much as is needed.

7.1 Bus operators

For bookings on their bus, the bus operator can see:

Operators do not get your name, mobile number, email address, user ID or payment details through our platform. At boarding, they check the e-ticket you show.

In exceptional situations, such as a breakdown, accident, medical emergency, lost luggage or a safety issue, we may share the minimum passenger details needed with the operator so that they can help you.

7.2 Service providers

We use trusted service providers who process data for us and only on our instructions:

We require these service providers to protect your data with the same or an equal level of protection as described in this policy. They must keep it confidential and use it only to provide their services to us.

7.3 Legal reasons

We may share information:

7.4 Business transfers

If DiliBus is involved in a merger, acquisition, restructuring or sale of assets, your information may be transferred as part of that transaction. The new owner must follow this policy, and we will inform you of any change in who controls your data.

7.5 When you choose to share

When you tap Share ticket, the ticket summary and the e-ticket PDF link go to the app or person you choose. We do not control how they use it.

8E-tickets, ticket links and profile photos

9Notifications and messages

Stay safe: DiliBus will never ask for your OTP, card details, CVV or UPI PIN by phone, SMS, email or WhatsApp. Do not share them with anyone, including someone who claims to be from DiliBus.

10Where your data is stored

Your data is stored on secure cloud servers. Files such as profile photos and e-tickets are stored in India, in the AWS Mumbai region.

Some of our service providers, such as push notification and map services, may process limited data outside India. When data is processed outside India, we do so in line with Indian law, including any restrictions notified by the Government of India. The protections in this policy continue to apply.

11How long we keep your data

DataHow long we keep it
Account and profile: mobile number, name, email, age, gender, profile photoWhile your account is active. Deleted or anonymised when your account is deleted (see section 12).
Saved passengersUntil you delete them, or until your account is deleted.
Push notification tokenUntil you log out or ask us to delete your account.
Booking, payment, GST and refund records, including passenger and contact details on those bookings, e-tickets and payment referencesUp to 8 years from the end of the financial year of the transaction. GST, income-tax, accounting and other laws require this, and we also need these records to handle refunds, chargebacks, disputes and legal claims. We keep these records even if you delete your account.
Support requests and our repliesAs long as needed to resolve the request and any related complaint. If a request is linked to a booking or payment, we keep it for the same period as booking records.
OTP recordsStored only in hashed form. Each OTP expires 10 minutes after it is sent and cannot be used after that.
Server and security logsOnly as long as needed for security and troubleshooting, plus any period required by law. For example, CERT-In directions require certain system logs to be kept for 180 days.
Information on your device: session, preferences, recent searchesUntil you log out (session), clear the app's data or uninstall the app.

When a retention period ends, we delete the data or anonymise it so that it can no longer identify you.

Account deletion

12How to delete your DiliBus account

You can ask us to delete your DiliBus account and personal data at any time, free of charge. You can do it in the app, or by email or phone if you no longer have the app.

Option 1: Delete your account in the app (recommended)

  1. Open the DiliBus app and log in with your registered mobile number.
  2. Tap My Account in the tab bar at the bottom of the screen. In Hindi it is labelled मेरा अकाउंट.
  3. Scroll to the bottom of the My Account screen.
  4. Tap Delete account (अकाउंट डिलीट करें). It is shown in red, just below Log out.
  5. A confirmation box appears: "Delete account? Your profile, saved passengers and coupons will be removed after review. Booked tickets stay valid. This cannot be undone." Tap Delete account to confirm, or Cancel to go back.
  6. You will see the message Request received, and you will be logged out of the app.

Option 2: Request deletion without the app

If you have uninstalled the app or cannot log in:

What happens after you ask for deletion

What we delete

  • Your profile: name, mobile number, email address, age, gender and profile photo. In our records your name is replaced with "Deleted User", and the account is permanently deactivated.
  • Your saved passengers.
  • Your push notification token.
  • Your coupons and offers. Unused coupons are cancelled and cannot be used again.
  • Your login access. The account can no longer be used.

What we keep, and why

  • Booking, payment, GST and refund records, including the passenger names, ages and genders, the contact mobile number and email used for each booking, e-tickets and Razorpay payment references. We keep these for up to 8 years from the end of the financial year of the transaction for two reasons:
    • Indian tax (GST, income-tax) and accounting laws require it.
    • We need them to handle refunds, chargebacks, fraud checks and legal claims.
  • Support requests linked to those bookings or payments, for the same period.
  • Any information we must keep under a law, a court order or the direction of a government authority, for as long as required.

These records are no longer linked to an active account and are protected by the same security measures. They are used only for the purposes above and never for marketing, and they are deleted or anonymised when the retention period ends.

Good to know

  • Uninstalling the app does not delete your account. Please use one of the options above.
  • After your account is deleted, you can create a new account with the same mobile number at any time. Your old bookings, saved passengers and coupons will not be available in the new account.
  • If you only want to stop notifications, you do not need to delete your account. Turn off My Account → Notifications instead.

13Your rights and choices

Subject to applicable law, you have the following rights:

To use any of these rights, email dilibus.app@gmail.com or use Help → Write to us in the app. We may need to verify your identity first. We will acknowledge your request within 24 hours and respond within 15 days.

14How we protect your data

We follow reasonable security practices and procedures, including:

No method of sending or storing data is completely secure. If a personal data breach happens, we will act immediately to contain it. We will inform affected users, the Data Protection Board of India and CERT-In as required by law.

You can help too: keep your phone locked, never share your OTP, and log out on shared devices.

15Children's privacy

16Third-party services and links

The app uses or links to services run by other companies, such as Razorpay's payment checkout, Apple Maps, OpenFreeMap, the App Store and Google Play. Their own privacy policies apply to the information they collect. You can read the main ones here:

17Changes to this policy

We may update this policy from time to time, for example when we add features or when the law changes. The "Last updated" date at the top shows when it last changed.

If we make significant changes, we will tell you in the app or by notification before they take effect. Where the law requires it, we will ask for your consent again. If you continue to use the Services after an update, you accept the updated policy.

18Contact us and Grievance Officer

For questions, requests or complaints about your privacy or this policy, contact us:

Email
dilibus.app@gmail.com
Phone
+91 971 888 2649
Support hours
Monday to Sunday, 9:00 AM to 9:00 PM (IST)
In the app
Help → Write to us

Grievance Officer

In line with the Information Technology Act, 2000, the rules made under it, the Consumer Protection (E-Commerce) Rules, 2020 and the Digital Personal Data Protection Act, 2023, our Grievance Officer can be reached at:

Name
Grievance Officer, DiliBus
Email
dilibus.app@gmail.com (subject: "Grievance")
Phone
+91 971 888 2649
Address
RZ-26P/26 GALINO 33, INDRA PARK PALAM COLONY, Indira Park, Palam Police Station, New Delhi, South West Delhi-110045, Delhi, India

We acknowledge every grievance within 24 hours and resolve it within 15 days of receiving it.