Driver journey location
Drivers explicitly enable location sharing during active journeys. Only their fleet operator can view the latest position, accuracy and update time. Customers cannot view driver location. Ending a journey clears its stored coordinates. Android drivers start a location service with a visible journey notification. It can continue when the phone locks, but phone settings, force-stop, revoked permissions or lost connectivity can interrupt updates. Web tracking may pause when the app is closed or the phone locks. Operators can see the time of the last update. Driver app login tokens expire after 30 days and can be revoked by signing out. One-time driver codes expire after 24 hours. Driver names and maintenance reports are visible to their operator.
Optional location search
When you click “Use my location” and allow browser access, your coordinates are sent to this portal and stored in your search session to find nearby bus operators. They are not added to a customer profile or placed in search URLs. “Clear location” removes them from the session. We do not track your location continuously or send it to a map provider.
Operators may save their operating base coordinates and service radius at registration or from their dashboard. These help match customers to their service area. Exact coordinates are not displayed publicly, but nearby results show an approximate distance from the customer's location. Distances are straight-line estimates, not driving distances.
Privacy notice.
This portal collects the information needed to manage bus listings and booking requests.
Booking requests
We collect your name, mobile number, optional email, trip dates, passenger count, pickup location, destination and any notes you provide. These details are available to the chosen bus operator and the portal administrator so they can handle your request. We also store the customer terms version, its text and your acceptance timestamp with each new request. Accepting booking terms does not opt you into unrelated marketing.
Operator accounts
We store operator contact details, business information, bus listings and fee records. We also retain Operator Policy acceptance records, including the account, related bus submission where applicable, policy version, policy text and acceptance time. Approved bus details, photographs and the operator’s business name appear publicly. The operator’s mobile number is public on home-page bus listings and individual bus pages, with call and WhatsApp links. It is also shown on accepted booking pages. WhatsApp links open WhatsApp with the bus name and page link prefilled; sending a message is your choice.
Private booking links
Each booking request has a private status link. Anyone with that link can view the request’s trip information. Keep it private and share it only with people involved in your trip.
Cookies and storage
The site uses session cookies for login and form security. If you choose “Keep me logged in,” it also stores a login cookie. On approved blog posts, optional YouTube videos and Google AdSense ads load only after you choose to load them. Those services may receive your IP address and browser information and use cookies. Reloading the page resets that choice.
Customer blogs
Customer accounts store an author name, email, city and phone number. Approved posts, photographs, video links and author names appear publicly. Email and phone numbers are not shown with posts. Drafts and submitted posts are accessible only to their author and the platform admin. AdSense publisher and ad unit IDs are public advertising identifiers; when approved, they appear in ad code and ads.txt. Google handles advertising earnings directly. Removed photos are detached from posts and may be retained privately for recovery.
Payments and contact
No customer payment card or bank details are collected through this website. To correct booking details or request their removal, contact your assigned operator using the contact shown after acceptance; the operator can raise the request with the portal owner.