1. Information we collect
Depending on how you use YAVA Ride, we may process account information such as name, mobile number, email, profile details and authentication/security records. Driver onboarding may also require identity and vehicle information such as Aadhaar-related records, driving licence details, RC, insurance, document images, issue/expiry dates and verification outcomes.
Ride and booking information can include search criteria, route, pickup/drop locations, requested seats, published ride details, fares, booking status, cancellations, replacements, trip completion, ratings and support history.
2. Location and route information
Location information may be used for current location, pickup/drop selection, route matching, smart pickup suggestions, maps, navigation and authorized live-trip tracking. Where background location is required for an active driver trip, the Driver App should request platform permission and explain the purpose. YAVA Ride is designed to avoid collecting continuous background location when there is no operational need.
3. Payments
Payment transactions may include gateway order/payment identifiers, method category, amount, status, signature/webhook verification records, reconciliation and refund information. YAVA Ride does not need to store full payment-card credentials; payment processing is handled through configured payment providers.
4. Device, notification and security data
We may process installation identifiers, FCM tokens, platform, app version, device/OS information, last-seen data, IP address, user agent and pseudonymized device-risk signals. These support authentication, notifications, fraud/risk review, security and service reliability.
5. Communications and support
Booking-scoped chat messages, unread/read state, permitted attachments, support tickets and contact-form submissions may be retained to provide communication, safety, abuse reporting and support. Phone numbers are not intended to be exposed publicly in ride listings; authorized contact access is tied to an eligible booking stage.
6. SOS and safety information
If you trigger YAVA SOS features, YAVA may record your location, related booking/ride, user/driver/vehicle context, emergency contact information you provide, time of trigger, evidence you attach and Admin handling status. YAVA’s SOS feature records and escalates information according to configured operations; it does not represent a guarantee of emergency-service dispatch.
7. AI, smart matching and risk review
YAVA may use deterministic scoring and optional AI services to improve ride ranking or assist operational analysis. Smart matching can consider route compatibility, time, seats and location/detour signals. Risk systems can flag suspicious booking/device patterns for human review. YAVA’s design does not permanently ban a user solely because an AI model labels activity suspicious. External AI payloads should be minimized and secrets are kept on the server.
8. Voice search
Voice search can convert speech to text so From/To locations can be interpreted. Normal voice search should use transient processing where practical; microphone audio is not intended to be permanently stored unless a separate feature specifically requires, discloses and lawfully enables that collection.
9. Family Groups and rewards
Family features process membership, invitations, completed-ride events, reward progress and unlock history. Family members must have their own YAVA accounts. Only eligible completed bookings are intended to contribute to Family progress.
10. How we use information
- Provide authentication, profiles, KYC and vehicle verification.
- Search, rank, publish, book and complete rides.
- Process payments, refunds, cancellations and replacement workflows.
- Provide maps, pickup intelligence, trip location and navigation features.
- Enable booking communication, notifications, ratings, support and safety tools.
- Detect abuse, secure accounts, investigate risk signals and maintain audit trails.
- Operate Family progress, promotions, reports and service administration.
- Meet legal, accounting, dispute, fraud-prevention and regulatory obligations.
11. Sharing and service providers
Information may be shared only as necessary with other ride participants (for example authorized booking details), payment processors, Firebase/notification infrastructure, Google Maps/location services, SMS/email providers, configured AI providers, hosting/technical providers, professional advisers or authorities when legally required. Each integration should receive only the data reasonably needed for its role.
12. Data retention
Retention depends on the record type and business/legal need. Short-lived OTPs and temporary security artifacts should expire quickly. Financial, booking, fraud, audit, dispute or legally required records may need longer retention. KYC and sensitive documents should have tighter access controls and documented retention. YAVA should delete or anonymize data when it is no longer needed for a legitimate purpose.
13. Account deletion
You can request deletion from the Passenger/Driver App and through the public Delete Account page. After ownership verification and processing, authentication access and data not required for legitimate retention should be removed or anonymized. Where financial, ride, safety, fraud, audit or legal records must be retained, YAVA may preserve only what is necessary and should separate retained records from active account access.
14. Security
YAVA uses measures such as authentication controls, authorization checks, rate limits, server-side validation, restricted uploads, audit logging, payment-signature/webhook verification and protected secrets. No internet service can guarantee absolute security.
15. Your choices and rights
Subject to applicable law, you may ask about your personal information, request correction or deletion, manage notification/location permissions, disable optional alerts, or contact YAVA about privacy concerns. Some requests may be limited where retention is legally required or necessary to resolve fraud, disputes or financial obligations.
16. Children
YAVA Ride is not intended for children to create independent accounts where applicable age/legal requirements do not permit it. Guardians should contact YAVA if they believe a child’s information has been submitted contrary to applicable rules.
17. Policy changes
This policy may be updated as features, integrations or legal requirements change. Material updates should be communicated through an appropriate website/app notice where required.
18. Contact
Address: India