Your privacy at a glance
- We collect only what we need to book and manage your bus tickets: your mobile number, a basic profile, passenger details and booking records.
- We never sell your personal data. We do not show third-party ads, and we do not use advertising or tracking tools.
- Payments are handled by Razorpay. We never see or store your full card number, CVV, UPI PIN or net-banking password.
- The app does not access your location, contacts, SMS, call logs or microphone. It uses the camera or your photos only if you choose to set a profile photo.
- Bus operators see your seat numbers and booking status. They do not see your name, mobile number or email.
- You can delete your account at any time from My Account → Delete account. See how account deletion works.
Contents
- Who we are
- Scope of this policy and your consent
- Information we collect
- Permissions the app asks for
- Information we do not collect
- How we use your information
- How we share your information
- E-tickets, ticket links and profile photos
- Notifications and messages
- Where your data is stored
- How long we keep your data
- How to delete your account
- Your rights and choices
- How we protect your data
- Children's privacy
- Third-party services and links
- Changes to this policy
- 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
- 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:
- the Information Technology Act, 2000 and the rules made under it, including the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 and the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021;
- the Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025.
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
- Mobile number. Used to create your account and log you in. Your mobile number is your login ID, and we verify it with a one-time password (OTP) sent by SMS.
- Profile details. Your full name (as on your government photo ID), email address, age and gender, added once after your first login. To keep your tickets valid, these details cannot be changed later from the app. Contact support if something needs to be corrected.
- Profile photo (optional). If you choose to add one, you can take it with your camera or pick it from your photos. You can change or remove it at any time from My Account.
- Passenger details. For each seat you book, we collect the passenger's name, age, gender and seat number, plus an optional mobile number. Passengers below 12 years are recorded as children.
- If you enter details of other people, such as family members or friends, you confirm that you are allowed to share them with us.
- For a child, you confirm that you are the parent or legal guardian, or that you are acting with the guardian's consent.
- Saved passengers (optional). You can save up to 20 travellers (name, age and gender) to fill passenger details in one tap. You can delete them at any time from My Account → Saved passengers.
- Booking contact details. The mobile number for a booking (your registered number, unless you enter another one) and an optional email address. They are printed on your e-ticket and used to contact you about that booking.
- Coupon codes that you apply to a booking.
- Support requests. When you use Help → Write to us, we collect:
- the topic you choose: Booking, Payment, Refund, Account or Other;
- your message;
- the related booking, if you write from a ticket.
3.2 Information created when you use the Services
- Booking records. Each booking record includes:
- the booking number, bus and operator details, route and journey date;
- boarding and dropping points and seats;
- seat fare, GST, coupon discount and amount paid;
- booking and journey status, cancellation and refund details;
- your e-ticket (PDF).
- Payment records. When you pay, our payment partner Razorpay sends us the order ID, payment ID, payment signature, amount, currency and status. It also sends transaction details such as the payment method and, where applicable, the bank name, card network and last four digits of the card, or the UPI ID used. We use these to confirm bookings, process refunds and keep our accounts. We never receive or store your full card number, CVV, card expiry date, UPI PIN or net-banking password.
- Account activity. The date you joined, the time of your last login, your notification setting and your preferred app language. We store the language so that notifications reach you in English or Hindi.
- Device information. Your phone's operating system (Android or iOS) and a push notification token that lets us deliver notifications to your device. We do not collect your IMEI, serial number or advertising ID.
- OTP security records. Each OTP is stored only in hashed (one-way encrypted) form. We also store its expiry time, the number of attempts and the number of OTPs sent, so that we can stop misuse.
- Technical information. When the app connects to our servers, they process standard technical data such as your IP address, the time of the request and error details. We use this only to keep the Services secure and working (for example, to block repeated or abusive requests) and to fix problems.
3.3 Information that stays on your device
- Login session. A secure session key and your basic profile, kept in your phone's encrypted secure storage (iOS Keychain or Android Keystore). It is removed when you log out.
- App preferences. Your theme (light, dark or system), your language and whether you have seen the welcome screens.
- Recent searches. The routes you searched recently, so that you can repeat a search quickly.
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
| Data | Why we use it | Shared with | Required? |
|---|---|---|---|
| Mobile number | Login with OTP, account security, messages about your bookings | SMS provider (to send the OTP) | Required |
| Name, email, age, gender | Your profile and tickets; contacting you about bookings and support | Razorpay (your name, pre-filled at checkout) | Required |
| Profile photo | Shown on your account screen | Cloud storage provider | Optional |
| Passenger details (name, age, gender, seat, optional mobile) | Issuing tickets; seat rules for ladies and gents seats and for children | Printed on your e-ticket. Bus operators see seat numbers only, not names | Required to book |
| Booking contact mobile and email | Printed on the e-ticket; messages about that booking | Razorpay (pre-filled at checkout); messaging provider if we send your ticket by SMS or WhatsApp | Mobile required Email optional |
| Booking and payment records | Confirming bookings, refunds, GST and accounts, support | Razorpay; the bus operator (seat numbers, route, date, fare and status only); authorities when required by law | Required to book |
| Saved passengers | Filling passenger details faster | Not shared | Optional |
| Support messages | Answering your questions and complaints | Only if needed to solve your issue (for example, with the bus operator or Razorpay) | Optional |
| Push token, device OS, app language, notification setting | Delivering notifications in your language | Expo, Apple Push Notification service, Google Firebase Cloud Messaging | Optional |
| IP address and technical logs | Security, preventing abuse, fixing errors | Our hosting provider | Automatic |
| Recent searches, theme, welcome-screen status | Convenience | Not shared; stays on your device | Automatic |
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.
| Permission | When and why |
|---|---|
| Notifications Optional | Asked 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 Optional | Used only when you tap Take photo to set your profile photo. |
| Photos Optional | Used 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
- Your location. The app never reads your GPS or network location. The route map on your ticket shows an estimated position of the bus, calculated from the bus timetable. It is not live tracking of you or of the bus.
- Your contacts, SMS messages, call logs, microphone recordings or files, other than a photo you choose for your profile.
- Biometric data, such as Face ID or fingerprints.
- Full card numbers, CVV, UPI PIN or net-banking passwords.
- Advertising identifiers. We do not use advertising networks or third-party analytics or tracking tools. We do not track you across apps or websites owned by other companies.
6How we use your information
We use your information only for the following purposes:
- Account and login. We create your account, verify your mobile number by OTP, keep you logged in and protect your account, for example by limiting OTP attempts.
- Bookings. We use your information to:
- show seat availability;
- hold your seats for 10 minutes while you pay;
- apply seat rules for ladies and gents seats and for child passengers;
- apply coupons;
- confirm bookings and issue your e-ticket in the app and as a PDF.
- Payments and refunds. We create payment orders with Razorpay, verify payments and process cancellations and refunds. If a payment cannot be used for a booking, we refund it automatically.
- Trip updates and service messages. We tell you when:
- a booking is confirmed or cancelled;
- a refund is initiated;
- the bus starts or is running late;
- support replies to your request.
- Offers. We tell you about coupons and discounts. You can turn notifications off at any time.
- Customer support. We answer your questions, resolve complaints and grievances, and investigate payment or booking problems.
- Safety, security and fraud prevention. We detect and prevent misuse, fraud and unauthorised access, and enforce our Terms & Conditions.
- Legal and accounting duties. We keep GST, tax and accounting records, and comply with laws, court orders and lawful requests from government authorities.
- Running and improving the Services. We keep the Services working and fix errors. We also look at overall numbers, such as bookings per route or seat occupancy, to plan better routes and features. These figures are counted on our own systems, not with third-party analytics or advertising tools.
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:
- the booking number, seat numbers and journey date;
- the boarding and dropping points;
- the number of adult and child travellers;
- the fare, and the booking and journey status.
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:
- Razorpay Software Private Limited handles payment processing, refunds and payment security.
- At checkout, we share the amount, the booking reference and your name, mobile number and email address (to pre-fill the payment form).
- The card, UPI, net-banking or wallet details you enter go directly to Razorpay.
- Razorpay is PCI-DSS compliant.
- SMS service provider. Sends OTPs and, where applicable, booking messages to your mobile number.
- Push notification services. Expo (expo.dev) delivers our notifications through Apple Push Notification service on iPhone and Google Firebase Cloud Messaging on Android. They receive your push token and the notification text.
- Cloud hosting and storage. Our servers and database are hosted by cloud hosting providers such as Hostinger. Profile photos and e-ticket PDFs are stored on Amazon Web Services (AWS) cloud storage in the Mumbai (India) region.
- Map services. To draw the route map, the app loads map images from one of two sources:
- Apple Maps, on iPhones running iOS 17 or later;
- OpenFreeMap, with the map software served by jsDelivr, on Android and older iPhones.
- Messaging services. If we send your e-ticket or booking updates by SMS or WhatsApp, we share your contact mobile number and the message or ticket with that messaging provider. For WhatsApp, this means Meta Platforms and its authorised business partners.
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:
- if required by law, regulation or a court order;
- in response to a lawful request from a government or law-enforcement agency, for example under the Information Technology Act, 2000;
- when necessary to protect the rights, property or safety of DiliBus, our users, bus operators or the public, including to prevent fraud.
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
- When a booking is confirmed, we create an e-ticket PDF. It contains:
- the booking number, bus and route details, and journey date and times;
- the boarding and dropping points;
- each passenger's name, age, gender and seat number;
- the contact mobile number and email for the booking;
- the bus operator's contact number;
- the payment summary.
- The PDF is stored in our cloud storage behind a long, random web link that is hard to guess. Anyone who has this link can open the ticket, so share it only with people you trust.
- Profile photos are also stored behind random links, and the app uses them only to show your photo.
- E-tickets are kept for the same period as other booking records (see section 11).
9Notifications and messages
- What we send. We send push notifications for:
- bookings that are confirmed or cancelled, and refunds;
- bookings that could not be confirmed (with an automatic refund);
- a bus that has started or is running late;
- replies from support;
- new offers and coupons.
- Turning them off. The My Account → Notifications switch turns off all DiliBus push notifications for your account, including booking and trip updates. You can still see the latest status in My Bookings. You can also block notifications in your phone's settings.
- Logging out. When you log out, we remove the push token from your account, so that phone stops receiving notifications for your account.
- SMS and WhatsApp. We send your login OTP by SMS. We may also send important booking information, such as your e-ticket, to the booking contact number by SMS or WhatsApp.
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
| Data | How long we keep it |
|---|---|
| Account and profile: mobile number, name, email, age, gender, profile photo | While your account is active. Deleted or anonymised when your account is deleted (see section 12). |
| Saved passengers | Until you delete them, or until your account is deleted. |
| Push notification token | Until 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 references | Up 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 replies | As 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 records | Stored only in hashed form. Each OTP expires 10 minutes after it is sent and cannot be used after that. |
| Server and security logs | Only 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 searches | Until 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.
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)
- Open the DiliBus app and log in with your registered mobile number.
- Tap My Account in the tab bar at the bottom of the screen. In Hindi it is labelled मेरा अकाउंट.
- Scroll to the bottom of the My Account screen.
- Tap Delete account (अकाउंट डिलीट करें). It is shown in red, just below Log out.
- 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.
- 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:
- Email dilibus.app@gmail.com with the subject "Delete my DiliBus account". Include your registered mobile number and the name on your account.
- Or call +91 971 888 2649, Monday to Sunday, 9:00 AM to 9:00 PM (IST).
- To protect your account, we may first check that the request is really from you, for example by calling or sending an OTP to your registered mobile number.
- We will confirm by email or SMS once your account has been deleted.
What happens after you ask for deletion
- Straight away:
- you are logged out;
- push notifications stop, because your push token is removed;
- you cannot log in to the account while the request is being processed.
- Review and deletion: our team checks that the request is genuine and that there are no pending refunds or disputes, and then deletes your account. This usually takes up to 7 days, and never more than 30 days from your request.
- Booked tickets stay valid for travel.
- Before you delete your account, download the e-ticket for any upcoming trip from My Bookings → your ticket → Download e-ticket (PDF). You will not be able to log in after sending the request.
- For help with an upcoming booking after that, contact support.
- Changed your mind? Contact us before the deletion is complete and we can cancel your request, so that you can log in again. Once the account is deleted, it cannot be restored.
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:
- Access. You can see your profile, bookings, payment history, saved passengers, coupons and support requests in the app at any time. You can also ask us for a summary of the personal data we process about you and the service providers we share it with.
- Correction and updating. You can change or remove your profile photo and manage saved passengers in the app. To correct your name, email, age or gender, contact support. Passenger details on a booking cannot be changed after the booking is made.
- Erasure. You can delete your account as explained in section 12. Some records are kept because the law requires it.
- Withdrawing consent. You can turn off notifications, remove camera or photo access in your phone's settings, or delete your account. Withdrawing consent is as easy as giving it.
- Grievance redressal. You can raise a complaint with our Grievance Officer (see section 18).
- Nomination. You can nominate another person to use these rights on your behalf if you die or become unable to act. To do this, write to us.
- Complaint to the Data Protection Board of India. If you are not satisfied with our response after using our grievance process, you may complain to the Data Protection Board of India.
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:
- Encryption in transit. All communication between the app and our servers uses HTTPS (TLS) encryption.
- Secure storage on your phone. Your login session is kept in your phone's encrypted secure storage (iOS Keychain or Android Keystore).
- OTP protection. OTPs are stored only in hashed form and expire after 10 minutes. Each number is limited to 5 wrong attempts per OTP and 5 OTPs per hour.
- Payment security. Payments are handled by PCI-DSS compliant Razorpay, and we verify every payment with Razorpay before confirming a booking.
- Access control. Only authorised DiliBus staff can access personal data, based on their role and only as needed for their work. Bus operators' access is limited as explained in section 7.1.
- Server protection. We use firewalls, secured database access, limits on repeated requests, security headers and regular backups.
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
- You must be at least 18 years old to create a DiliBus account. The app is not directed at children.
- Children can travel as passengers when a parent, legal guardian or another responsible adult books for them. The adult gives the child's name, age and gender only so that we can issue the ticket, and confirms that they are allowed to do so.
- We do not knowingly create accounts for children. We do not track children's behaviour or send them targeted advertising.
- If we learn that a child under 18 has created an account without a parent's or guardian's consent, we will delete it. If you believe this has happened, please contact us.
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:
- Razorpay: razorpay.com/privacy
- Apple: apple.com/legal/privacy
- Google: policies.google.com/privacy
- Expo: expo.dev/privacy
- Amazon Web Services: aws.amazon.com/privacy
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:
- 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
- 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.