Contact support@sagamobility.com. Grievance Officer: Bhuvanesh Kumar. Account deletion keeps completed/cancelled trip and payment records; see Data retention.
Who this policy covers
This policy explains how Konathala Bhuvanesh Kumar, an individual operating as Saga Mobility, handles personal information in the Saga rider app and at sagamobility.com. Our postal address is 35-1-4, Kancharapalem, Visakhapatnam 530008, India. Saga provides all-electric airport taxi journeys, currently focused on Visakhapatnam Airport, with EV Comfort and EV Luxury offerings.
“Saga”, “we” and “us” mean this operator. This notice covers riders, people whose passenger details are supplied for a booking, website visitors and people contacting support. Driver location and contact information are described here where they are used to provide a rider’s journey.
Our Terms & Conditions cover use of the service. Reading this policy or agreeing to those terms does not replace a device permission or other specific consent required by law.
Information we collect
- Account and sign-in: your verified mobile number, name, account and Firebase identifiers, verification status and sign-in/session information. Rider sign-in uses phone OTP verification. Contact email and profile photo are optional.
- Bookings and journeys: pickup and destination addresses and coordinates, requested pickup time, vehicle category, fare quote, assigned driver and vehicle, trip-start OTP, journey timestamps, cancellations, ride status and payment method/status or confirmation records.
- Saved places and preferences: labels, addresses and coordinates you save, profile choices and notification preferences.
- Notifications: ride and service messages, inbox entries and read status. Offers and promotions are optional and off by default; they appear only after you enable that preference. On supported devices, push delivery also requires device permission and uses a device registration and push token.
- Technical information: installation and session identifiers, authentication token hashes, request/error information and security timestamps used to operate and protect the service. Google and Firebase services used by the app may also process app and device identifiers, app version, IP address, user-agent or device information to provide authentication, maps and supported messaging. An installation identifier may remain on your device after sign-out.
- Support and feedback: your contact details, booking reference, message and any relevant evidence you choose to email to support@sagamobility.com. We also use information supplied by an assigned driver or another passenger when investigating the same journey or complaint.
New bookings currently use cash payment. We record fares and payment status. The current rider service does not offer card checkout, UPI checkout or online wallet funding, and does not collect card numbers through those unavailable features.
Location, photos and device permissions
With your device permission, the rider app uses precise or approximate location while the app is in use to position the map, suggest places and help select a pickup. You can decline this permission and enter your pickup manually. The rider app does not request continuous background location tracking.
The pickup and destination you select, including their coordinates, are sent to Saga as booking information even if location permission is off. During an active journey, the assigned driver’s location is used for navigation and trip updates displayed to you.
A profile photo is optional. You choose an image using the device’s image picker and save it to your profile. We remove embedded EXIF/GPS metadata when processing that image; the photo itself is still personal information.
Manage location, photo access and notification permissions in your device settings. Turning a permission off affects features that rely on it and does not erase booking information already stored.
How and why we use information
- Verify your phone number, create your account and maintain secure sign-in.
- Search places, calculate routes and fare estimates, create or schedule bookings, assign vehicles and manage journeys and trip-start verification.
- Show trip updates and history, save your preferences and places, send service messages, and send optional offers or announcements only when you enable the promotion preference.
- Respond to support, lost-item, billing, safety and privacy inquiries, and investigate complaints and service misuse.
- Maintain access controls, troubleshoot errors and protect accounts and service systems.
- Handle applicable legal obligations and valid requests from competent authorities.
Where consent is required, you can withdraw it through device controls or a privacy request. Processing needed to provide a requested journey or meet an applicable legal obligation may continue to the extent permitted by law. Our current retention behavior is explained separately below.
CO₂-saving insights and rewards are coming soon. New features and any new personal-data purposes will be explained before they begin.
Who receives information
- Your assigned driver: pickup, destination and relevant trip details. During an active assigned trip, the driver can access your saved name and verified phone number to arrange pickup. The phone-contact access is limited to that assigned active trip.
- Authorised Saga personnel: relevant account and trip information for service operations, support and complaint handling, subject to access controls.
- Firebase/Google: phone authentication and SMS verification, and push-message delivery on supported devices when enabled. Firebase Authentication may process your phone number, IP address and user agent; Cloud Messaging may use a Firebase installation identifier and device token to deliver a message.
- Google Maps, Places and Routes: mapping requests, place-search text, search-session identifiers, optional location bias and route endpoints. The Maps SDK also sends Google the app name and version, authentication information and an anonymous identifier when it requests map content.
- Hosting and storage services: Google Cloud for backend infrastructure in the United States, MongoDB Atlas for application records, and OpenAI Sites for serving these website pages.
- Authorities and parties to a claim: relevant information where disclosure is required by applicable law or a valid legal process, or is necessary and lawfully permitted to handle a particular claim.
This iOS Rider release includes Firebase Analytics and bundled Google measurement and conversion components. Firebase Analytics collection is deactivated for this release. Analytics storage, advertising storage, advertising personalization and Saga’s optional app-usage event dispatcher are disabled. Google and Firebase may still process technical information needed to provide authentication, maps and other integrated services.
External providers can process information in the locations where their services operate, including outside India. Their own notices explain their service-level processing: Google, Firebase and MongoDB. Contact us for a privacy question about a particular provider or disclosure.
The public website
This website provides company information, rider-app previews, contact information and policies. App Store and Google Play downloads are Coming soon. The website does not accept ride bookings or payments and has no enquiry submission form; an email link opens your own email application.
Serving a page exposes ordinary request information such as IP address and browser headers to the hosting service. These pages load Manrope and icon fonts from Google Fonts, which sends requests to Google. External links lead to the relevant provider’s own service.
These website pages do not install analytics or advertising trackers. This statement does not prevent the hosting or font providers from receiving the technical information needed to serve their resources.
Security
We use HTTPS for app API connections, provider-backed authentication, server-side access checks and hashed authentication token/session identifiers. Access to account and booking functions is restricted by sign-in and service-role checks. These safeguards reduce unauthorised access; no system can guarantee absolute security.
Keep login codes private. Share the six-digit trip-start OTP only with your assigned driver when you are ready to begin the journey. Report a suspected account or data-security issue to support@sagamobility.com.
Data retention
We keep account/profile information, saved places, inbox entries, preferences and sign-in records while they are needed for your account. Account deletion removes the categories described below.
Payment amounts and ride-cost information are retained for cost analysis and future fare calculations. These calculations do not require your name, phone number, email address or profile photo. Removing those profile fields alone does not anonymise a trip record that still contains account identifiers or locations.
Completed and cancelled trip records and associated fare/payment records are currently retained indefinitely, with no automatic expiry. They can include rider and driver account identifiers, pickup and destination addresses and coordinates, journey timestamps, vehicle details and fare/payment metadata. They are not automatically anonymised by account deletion. If the deleted sign-in was also used to provide journeys, related driver-approval records are disabled and retained.
This describes the current service configuration; it does not mean that the law requires every record to be held permanently. You can email support@sagamobility.com with the subject Review retained data to request a review of the records remaining after deletion. We will explain any applicable retention requirement and act on erasure or restriction requests as required by law.
Planned change: We plan to remove account identifiers, trip locations and other user-level details from retained financial records, keeping only unlinked payment and ride-cost statistics for future fare calculations. Those statistics will contain no user-level information once the cleanup has been implemented and verified. Until then, the current retention described above applies.
Operational security/error records and information in provider-managed systems are separate from your app profile. A privacy request can include these records, and we will explain any applicable storage limits or retention requirements in our response.
How to delete your account
- Open the Saga rider app and go to Profile → Delete account.
- Read the explanation of what is deleted and what is retained. Complete or cancel any active ride.
- Verify your sign-in again with a fresh phone OTP when requested, then confirm deletion.
- Follow the status shown in the app. Deletion is processed in a queue; provider or service failures may require retries.
The process removes your Firebase sign-in identity, Saga account and profile (including the profile photo), sessions, saved places, inbox and notification preferences, push registrations and quotes. If you use the same sign-in across Saga applications, that shared sign-in is also removed. Completed/cancelled trip and payment records remain as explained in Data retention.
Outside the app, email support@sagamobility.com with the subject Account deletion and the phone number associated with your account. We will verify your authority through an appropriate secure process and explain the status and any retention limits. Do not email passwords, login OTPs or unnecessary identity documents.
Signing out or uninstalling the app does not delete the server account. Reading this page does not submit a deletion request.
Your choices and privacy requests
You can update supported profile fields, manage saved places and notification preferences, change device permissions, and initiate account deletion in the app. Offers and promotions are off by default; you can enable or disable them in App settings. Push delivery also depends on your device permission where supported.
For access, correction, consent withdrawal, deletion or a complaint about personal information, email support@sagamobility.com with the subject Privacy request. Describe the information or action involved. We may ask for proportionate verification to protect your account; do not send a login OTP.
Bhuvanesh Kumar handles privacy grievances through the process below. Where a request is limited by an applicable legal obligation, we will explain the reason and affected information. Your rights under applicable law are not waived by this policy.
Children and policy changes
You must be at least 18 and have legal capacity to hold a Saga booking account. A child travelling as a passenger must be accompanied by a responsible adult with authority to provide necessary passenger details. The service does not offer accounts for unaccompanied children. Contact us if you believe a child has created an account.
This policy is effective from 29 September 2026. We publish changes here with an updated date and give notice of material changes through available service channels before they take effect where required. A new permission or use requiring consent will be requested separately.
Operator, privacy and grievance contact
- Legal operator
- Konathala Bhuvanesh Kumar, an individual operating as Saga Mobility
- Postal address
- 35-1-4, Kancharapalem, Visakhapatnam 530008, India
- Support, privacy and account deletion
- support@sagamobility.com
- Grievance Officer
- Bhuvanesh Kumar · support@sagamobility.com · postal address above
- Email support@sagamobility.com with the subject Complaint or Privacy request. Include the booking reference if relevant, a way to contact you, what happened and the remedy you seek. Share only information needed to investigate.
- We acknowledge receipt within 48 hours, provide a complaint reference and a copy of the recorded complaint, and identify any further information needed.
- Bhuvanesh Kumar, Grievance Officer, reviews and addresses the complaint, and communicates a reasoned decision and any appropriate remedy within one month of receipt.
- If you disagree with the outcome, or the response is overdue, you may take the unresolved complaint to the National Consumer Helpline or a competent consumer commission or other authority. We will provide the complaint reference and a copy of our response on request. Any internal follow-up does not extend the original one-month redressal period.
Our process does not limit your statutory rights.
Related policy: Terms & Conditions