Privacy policy.

1. Who this policy covers

This policy describes information handled by the GoBla website and shared rider/driver application. Contact GoBla at City.Connector@rythmbara.in, 9951515160 or 9848914180 for privacy questions, operator details or business-address enquiries.

2. Information you provide

We store your mobile number, name, account role, email address and verification status. Driver applications include identity, licence, vehicle and insurance-document images submitted for review. We also process trip routes and departure times, vehicle details, prices or cost contributions, bookings, pickup/drop details, fare offers, ratings, messages, saved ride alerts and support requests. If a driver supplies direct-payment details, these can include a UPI identifier and QR image.

3. Device, maps and location information

Technical infrastructure may process request details such as IP address and browser information for delivery, security and troubleshooting. Our app uses browser storage for sign-in and saved screen preferences. A service worker stores only public offline branding; it does not store authenticated API responses or bookings for offline use.

Maps and driving routes use Google Maps services; fallback map providers may be used when Google Maps is unavailable. Map providers receive requests and technical information when their maps load. Location access is requested when needed. The application supports driver location sharing for active trips, with access limited by booking or share-link permissions. The Android client does not provide continuous background tracking. Closing the application must not be treated as continued tracking.

4. Why we process information

We use information to create and secure accounts, verify phone/email ownership, review driver documents, publish and match journeys, manage bookings, deliver trip updates and chat, show maps, prevent abuse, handle support and investigate disputes. Email OTP delivery is awaiting configuration; we do not mark an email verified without the inbox-code check. Saved ride alerts currently appear in the app and do not imply email or SMS marketing.

5. Who can see information

Ride searches show relevant driver, vehicle, route, contribution and rating details. Driver contact information and supplied direct-payment details are available to confirmed participants under the app’s access controls. Confirmed trip participants can access permitted live-trip information; a person given a trip-sharing link may see the information authorised by that link. Account email addresses and driver-document images are not part of public driver details. Pickup codes are visible only to the confirmed rider; only the trip’s driver submits the code for server verification. Authorised administrators can review documents and support cases. Admin password recovery uses the service owner’s designated recovery contacts. After a password reset, the system stores a password hash and revokes previous admin sessions.

Infrastructure and service providers process information necessary to operate the service, including hosting, maps and account communications, according to the features you use. We may disclose relevant information when required by law or when reasonably needed to investigate abuse or protect rights and safety. No sale of member information is part of the current service.

6. Retention and protection

Account, trip, booking, message and support records are stored to operate the service and handle security, support, disputes and legal obligations. Backups may contain older records. There is no promise of an automatic deletion period for all records. Email OTPs are stored as keyed digests, expire after ten minutes and are subject to retry limits. Expired codes cannot verify an address. Access controls, HTTPS and restricted document endpoints help protect data, but no system can guarantee absolute security.

7. Your choices and requests

You can edit supported profile fields, change notification/search preferences, revoke device location permissions and stop using the app. Keep your email address accurate and up to date. To request access, correction, erasure, account deletion, consent withdrawal or help with a privacy concern, email us or submit an in-app support request using the Privacy category. We may need to confirm your identity and explain any record we must retain. Requests are reviewed by support; an in-app request does not instantly delete an account or backups.

Request account and data deletion

The current Android app does not read your address book or request contacts, microphone or broad storage access. Images are selected through the system picker. Foreground GPS requires your permission.

8. Age, third parties and updates

Account holders must be at least 18. Do not upload children’s identity information or another person’s documents without proper authority. External map, payment, email and website services have their own policies. We will update this page when relevant practices change. Contact the privacy support channel above if you have questions or a complaint.