ANB Mobility Privacy Policy.
Effective 5 September 2026 · ANB Mobility Pvt. Ltd.
This policy explains how ANB Mobility accesses, collects, uses, shares, protects, retains and deletes personal and device data for the Customer/Rider app and ANB administrative operations.
1. Account and profile information
We process information provided to create and operate an ANB Mobility account, including phone number and OTP identity, name, profile photo, gender, province, district, municipality, ward, account role and account status. Firebase Authentication and Firestore are used for authentication and account records.
2. Rider identity, vehicle and payout information
Rider onboarding may include driver photographs, citizenship documents, driving licence information, vehicle/bluebook and insurance records, approval or renewal status, ratings, earnings, commissions and payout identifiers or QR information. KYC and payout data is restricted to the Rider, authorized ANB staff and service providers where necessary to verify or settle payments.
3. Location and route data
Customer location may be used for pickup selection, route calculation, service-area eligibility, live-trip features and safety. When a Rider chooses to go Online, live GPS location, heading, vehicle type and presence timestamps may be shown to signed-in customers as nearby vehicle availability. ANB does not publish Rider payout, KYC, notification token or other private account fields in the nearby-presence feed.
4. Rides, tickets and transport operations
We process pickup and destination data, trip status, assigned Rider or operator, passenger and contact details, fares, ticket and seat data, trip timestamps, cancellations and invoices. Limited contact and trip information is shared between the matched Customer, Rider or transport operator when needed to deliver the booked service.
5. Payments, commissions and financial records
We process payment method, transaction references, payment proof images where used, commissions, promotions and referrals, rider settlements, wallet transactions and payout requests. When you select a third-party payment provider, information needed to initiate or verify that transaction may be sent to the selected provider.
6. Support, safety and communications
Support tickets, messages, complaints, ratings and reviews, safety incidents and relevant trip or location context may be processed to resolve problems, respond to emergencies, investigate misuse and protect Customers, Riders, operators and ANB Mobility.
7. AI Support
If you choose ANB AI Support, your message and selected ANB account, ride, ticket or support context needed to answer the question may be sent securely through ANB backend services to the AI provider configured by ANB, such as Google Gemini or OpenAI. Human Support is available for sensitive or unresolved issues.
8. Device, notification and security data
We may process Firebase Cloud Messaging tokens, notification preferences, app version and build information, App Check or attestation signals, timestamps and technical service logs. These are used for notifications, compatibility, abuse prevention, debugging and service security.
9. Service providers and sharing
ANB Mobility uses service providers including Google Firebase for authentication, database, storage, functions, messaging and App Check; Google Maps Platform for maps, places, geocoding and routes; configured payment providers such as eSewa; and configured AI providers when AI Support is used. Information may also be disclosed where required by law, regulators, courts, fraud or safety response, or to protect rights and users. ANB Mobility does not sell personal data and the audited app contains no third-party advertising SDK.
10. Security
ANB Mobility uses authenticated Firebase services, Firestore and Storage security rules, restricted administrative access, server-side Cloud Functions and HTTPS/TLS transport. No internet system is risk-free, so access is limited to data needed for each role and sensitive provider credentials are kept server-side where supported.
11. Retention and deletion
Core account, profile and KYC data is retained while it is needed to operate the account and is deleted or de-identified after a verified deletion request when it is no longer required. Ride, ticket, payment, invoice, commission, settlement, tax/accounting and regulatory records are retained for the minimum period required by applicable Nepalese tax, VAT, accounting, transport, safety, fraud-prevention or other law, and only longer where necessary for an active dispute, legal claim, investigation or regulatory obligation. Operational location and device data is kept only as long as needed for service, safety, fraud prevention and troubleshooting, then deleted or de-identified where practicable. Any records that must be retained remain access-restricted.
12. Children's privacy and minimum age
ANB Mobility accounts are intended for people aged 18 or older. Riders must also meet all legal driving, licensing and service eligibility requirements. ANB Mobility does not knowingly permit account registration by children under 18 or intentionally collect their personal data through account registration. A parent or guardian arranging travel for a minor should use their own eligible account and follow applicable service and safety requirements. If ANB learns that an account belongs to a child under 18, we may restrict the account and take appropriate steps to delete or handle the data as required by law.
13. Your choices and requests
You can review profile information in the app, control whether a Rider goes Online, choose whether to use AI Support, sign out, and submit an account and data deletion request. For privacy questions use the in-app ANB Mobility Support Desk or the public request page.
Privacy contact mechanism
ANB Mobility Pvt. Ltd. provides privacy support through the in-app Support Desk and the public privacy/account-deletion request form. Use the form if you cannot access your account.
This policy applies to ANB Mobility Customer/Rider services and ANB administrative processing. The policy should be reviewed whenever data practices or service providers materially change.