The registered operator, official contact details and final operational policies are awaiting confirmation. This page needs owner approval and legal review before it is used for the public app launch.
Who this policy covers
This review draft describes personal-data practices implemented for the Saga rider app and Saga Mobility’s public website. Saga is an all-electric airport taxi service, currently focused on Visakhapatnam Airport, with EV Economy and EV Premium offerings.
“Saga”, “we” and “us” refer to the Saga Mobility service brand. The legal operator, official privacy contact, production retention schedule and final processor details must be confirmed before this becomes the approved privacy notice. Last updated: 14 September 2026; no final effective date has been set.
This page is separate from our Terms & Conditions. Agreeing to terms or viewing this page does not replace any specific permission or consent required for processing personal data.
Information used by the rider app
- Account and sign-in: account/provider identifiers, name, sign-in email or phone number where supplied, verification status, optional profile image and authentication/session information.
- Journey information: pickup and destination addresses and coordinates, scheduled pickup time, selected vehicle category, fare quotes, ride status, assigned driver/vehicle, trip-start OTP, trip timestamps and payment status.
- Saved places and preferences: place labels, addresses and coordinates, profile choices and notification preferences.
- Notifications: push-delivery identifiers where enabled, notification content, inbox entries and read status.
- Technical information: installation/session identifiers and security-related timestamps or token hashes used to maintain authenticated access. Some device-local identifiers can remain after an ordinary sign-out.
- Support communications: information you choose to send through an official support channel once that channel is published.
Current new bookings support cash payment. The app records fare and payment status; this draft does not describe a live card checkout, wallet or online payment-provider integration.
Location, photos and device permissions
With device permission, the rider app uses precise or approximate location to help position the map and pickup point. Its rider location implementation includes updates while the app is in use; this draft does not describe continuous background rider tracking.
A pickup or destination you select, including its coordinates, is part of the booking record even when it is not your current device location. Trip records can therefore contain location information independently of the device’s location permission.
You can manage location and notification permissions in your device settings. Disabling a permission may limit the feature that needs it and does not delete information already held in a booking record.
If you choose a profile photo, the app uses a gallery/image picker. The backend processes the selected image and strips embedded image metadata, including EXIF/GPS metadata. This does not mean the image itself becomes anonymous.
Why information is processed
The app uses the information described above to authenticate accounts, provide fare estimates, create and schedule bookings, assign and manage trips, support trip-start verification, show available trip updates, maintain saved places and deliver service notifications.
Authentication and session information also support access controls and account-deletion processing. Journey and payment-status records support the service’s trip history and operational records. Final purposes and lawful retention reasons for records kept after deletion must be confirmed in the approved notice.
CO₂-saving insights and rewards are coming soon. This draft does not describe an active carbon tracker or reward ledger; any future feature must explain its calculation, data use and programme rules before launch.
Who receives information
- Your assigned driver: pickup/destination and relevant trip details. The implemented contact flow can provide your saved name and mobile number to the assigned driver during an active assigned trip.
- Authorised Saga operations: relevant booking/account information for access-controlled service operation.
- Authentication providers: Google/Firebase Authentication, Apple/Firebase Authentication on supported devices, and Firebase phone/SMS authentication where enabled.
- Google mapping services: Maps, Places and Routes. Place searches can include search text, session identifiers and an optional location bias; route requests include route endpoints.
- Infrastructure providers: the providers identified for backend hosting and database services are Google Cloud and MongoDB Atlas. Production regions, processor arrangements and backup practices are awaiting confirmation for the final notice.
Any disclosure required by a valid legal request must be handled under applicable law. Any additional processors or marketing/data-sharing arrangements must be confirmed and described in the final notice.
Provider information: Google Privacy Policy, Firebase privacy information, Apple Privacy Policy and MongoDB Privacy Policy.
The public website
The website provides company information, rider-app previews and these policy pages. It does not currently provide a live booking form, account sign-in, payment checkout or a working enquiry submission form. Rider download buttons remain Coming soon.
Visiting the site involves ordinary requests to its hosting service, which can expose technical request information such as IP address and browser headers to that service. The pages also load Manrope and icon fonts from Google Fonts; those requests reach Google. Following an external link takes you to the relevant provider’s own service.
The website does not currently add analytics or advertising trackers. Hosting logs, font-provider processing and any future cookie/analytics configuration still require operational confirmation.
Security and storage
The app implements provider-backed authentication, authenticated API access, server-side access checks and hashed session/token identifiers. These measures reduce unauthorised access but cannot guarantee that every system or transmission is risk-free.
Production hosting locations, access procedures, incident handling and provider protections are awaiting confirmation before the final policy is approved.
Keep login codes private and share the six-digit trip-start OTP only with your assigned driver when you are ready to begin the journey.
Data retention
Account/profile data, saved places, notification inbox entries, preferences and related sign-in/session records are removed through the implemented account-deletion process. Completed and cancelled trip records can remain, including pickup/destination coordinates and fare/payment metadata.
The current implementation allows retained trip records to remain without a fixed expiry when no positive retention period is configured. The live retention setting has not been verified for this draft. Do not assume that these records are automatically anonymised or deleted when you close your account.
Final retention periods, reasons and backup/log schedules are awaiting confirmation. Where applicable law requires a record to be retained, that obligation may limit an erasure request.
How to delete your account
- Open the Saga rider app and go to Profile → Delete account.
- Read the confirmation, then sign in again using the relevant Google, Apple or phone-verification method when requested.
- Complete or cancel any active ride before continuing.
- Confirm deletion and follow the status shown in the app. The deletion process is queued and may retry if a provider or service is temporarily unavailable.
The process removes the sign-in identity and account/profile data, related sessions, saved places, inbox entries, preferences and quotes. If the same Saga sign-in account is used across Saga applications, deleting it also removes that shared sign-in. Completed/cancelled journey records can remain as described in Data retention.
Uninstalling the app or signing out does not delete your server account. Outside-app deletion request contact: awaiting confirmation before launch. This page provides instructions only; it does not submit a deletion request. An official outside-app request channel must be published before the app’s public distribution.
Your choices and privacy requests
You can manage device permissions, update profile information supported by the app, manage saved places and use the in-app account-deletion flow. Withdrawing a device permission does not retrospectively erase trip records.
Depending on applicable law, you may seek information about, correction of or deletion of personal data, raise a grievance or withdraw a consent that a feature relies on. Some requests may need proportionate identity verification. We will not ask you to publish a login OTP or sensitive identification on this website.
The official privacy/grievance contact for requests outside the app is awaiting owner confirmation. These request channels, applicable response periods and any lawful limits must be completed in the approved notice; statutory rights are not waived by this draft.
Children and policy changes
A booking account should be used only by someone with the legal capacity to make a booking agreement. If an adult arranges travel for a child, they must have authority to provide the necessary passenger information and follow applicable consent and safety requirements. Arrangements for children’s data and any required parental consent must be confirmed before launch.
The approved policy will set an effective date and explain material changes before they apply. A new data use, processor or permission may require an updated notice and additional consent.
Privacy and grievance contact
- App and service brand
- Saga rider app · Saga Mobility
- Registered operator and address
- Awaiting owner confirmation before launch
- Privacy, deletion and complaints email
- Awaiting owner confirmation before launch
- Grievance contact and response process
- To be confirmed under applicable law
Confirmed channels will be published here and on the Contact page.
Related policy: Terms & Conditions