Data We Collect
| Data type | Examples | Purpose | Required |
|---|---|---|---|
| Personal info | Name, phone number, email, customer or driver account identifiers | Account management, OTP login, booking confirmation, support and safety | Required for app account flows; public booking requires mobile number |
| Location | Pickup, drop, route pins, current customer location, driver GPS while tracking | Booking, fare estimate, route planning, driver assignment and customer-visible live tracking | Required for ride and tracking features; precise GPS is permission based |
| Financial info | Payment method choice, transaction reference, wallet activity, refund or settlement records | Ride payment, wallet top-up, driver settlement, refund support and fraud prevention | Required when using online payment or wallet features |
| App activity | Booking actions, ride status updates, notification consent, safety actions, admin review logs | App functionality, security, compliance, support and abuse prevention | Required for live operations |
| Device or other IDs | Firebase installation ID, push endpoint hash, device fingerprint, session metadata | Push notifications, OTP abuse protection, session security and fraud prevention | Required for protected login, push and security features |
Sharing And Service Providers
GO India RIDE uses service providers for infrastructure and app functionality. Data may be processed through Firebase, web push services, payment gateways, email/SMS/WhatsApp providers, hosting, analytics/security tools and maps/geocoding providers as needed for the selected feature.
- Driver GPS is used for assigned ride tracking and admin safety monitoring.
- Payment data is routed through enabled gateways such as Razorpay, PayPal or UPI-compatible payment flows.
- Push notifications are sent only after browser/app permission and are limited to ride, account, safety and service updates.
Security Practices
- Production API traffic is expected over HTTPS with secure backend validation.
- Push subscriptions store endpoint hashes and encrypted push keys; private VAPID keys are not exposed to the browser.
- Razorpay payment verification uses server-side signature validation; PayPal payment completion uses backend order capture.
- Admin operations are separated from public/customer/driver flows and require authenticated access.
- Users can use the public Account Deletion page or contact support for account, ride, payment, privacy or deletion requests.
Deletion And Support
For data access, correction, deletion, refund or support requests, use the Account Deletion page, the contact page, or email privacy@goindiaride.in. Some transaction, safety, tax, security and legal records may be retained where required by law or legitimate operational obligations.