Privacy Policy

Nayar Drive

Effective Date: 2025-10-08

This Privacy Policy explains how Nayar Drive ("Nayar Drive", "we", "our" or "us") collects, uses, discloses, and safeguards information when you use the Nayar Drive rider and driver applications and related services (the “Service”).

This policy is designed to satisfy disclosure expectations outlined in Google Play’s User Data & Privacy policies and applicable data protection principles. By using the Service, you agree to the practices described.

1. Information We Collect

We collect information in the following broad categories:

  • Account & Profile Data: Name, phone number, email address, profile photo (optional), language preference, driver license / vehicle registration (drivers only).
  • Location Data (Precise & Background): Real‑time GPS location for trip routing, pickup & drop-off accuracy, safety monitoring, fraud prevention, service quality metrics, and regulatory reporting. Background location is accessed only while you are marked “Online” (drivers) or during an active trip (riders) to support continuous navigation & safety.
  • Trip & Usage Data: Ride history, route traces, distance, timestamps, payment method metadata (tokenized), in‑app interactions, referral codes, support tickets.
  • Device & Technical Data: App version, device model, OS, network status, crash logs, performance diagnostics, push notification tokens.
  • Communications: Support inquiries, feedback, incident reports, optional ratings & reviews.
  • Safety & Compliance Data: Fraud flags, abnormal route or speed patterns, unsafe driving events (e.g. sudden braking if enabled), account status, law-enforcement/legal request metadata.
  • Optional / Permission-Based Inputs: Camera (ID / vehicle photo), gallery (upload receipts or documents), microphone (future voice features), contacts (only if you use a share / invite feature; otherwise not accessed).

2. How We Use Information

  • Enable ride matching, navigation, pricing, and trip completion.
  • Improve route accuracy and ETA prediction.
  • Authenticate users; prevent duplicate / fraudulent accounts.
  • Protect rider & driver safety (real‑time tracking, anomaly detection).
  • Provide in‑app support, resolve disputes, investigate incidents.
  • Analyze service performance and optimize features.
  • Comply with legal, tax, audit, and regulatory obligations.
  • Send transactional notifications (trip status, receipts, safety alerts).
  • Optional marketing (only with consent or as permitted by law; opt‑out available).

We do not sell personal data.

3. Permissions & Justification

Permission/DataPurposeOptional?
Location (Foreground)Real‑time trip routing & pickup accuracy.No (core feature)
Location (Background)Continuous navigation & safety while driver online or trip active.No (drivers); Yes (riders—only active trip)
CameraProfile, vehicle, document, incident evidence.Yes
Photos/MediaUpload documents / receipts.Yes
PhoneAccount verification (OTP), safety callbacks.No
Push Notification TokenTrip status, safety, receipts.No
Contacts (if used)Share trip / invite feature.Yes
Microphone (future)Voice command / support call.Yes

Background location is never collected when the user is fully signed out or the driver status is Offline.

4. Legal Bases

Depending on jurisdiction: performance of a contract (providing transport), legitimate interests (security, fraud prevention, service improvement), compliance with legal obligations, and consent (where required for marketing or certain device permissions).

5. Sharing of Information

  • Riders & Drivers: Mutual limited disclosure (first name, vehicle info, pickup/drop-off, anonymized contact relay).
  • Service Providers: Hosting, mapping, payment processing, analytics, communication APIs under contract & confidentiality.
  • Regulators / Law Enforcement: When required by law or for safety / fraud investigations.
  • Business Transfers: In a merger, acquisition, or asset sale with notice.

6. Data Retention

Trip, payment, and safety records are retained for periods required for accounting, tax, dispute resolution, fraud prevention, and regulatory compliance. Location traces are minimized or aggregated after operational necessity ends. Where deletion is requested and permitted, we securely remove or anonymize data.

7. Security Measures

  • Transport-layer encryption (HTTPS, TLS).
  • Scoped access tokens & role-based access control.
  • Hashing of sensitive credentials.
  • Monitoring, anomaly detection, and audit logging.
  • Least-privilege infrastructure and periodic reviews.

8. Your Choices & Rights

  • Access, correction, deletion (subject to legal constraints).
  • Withdraw consent (where processing is consent-based).
  • Disable certain permissions (may reduce functionality).
  • Request data portability where applicable.
  • Lodge a complaint with a supervisory authority (if applicable in your region).

9. International Transfers

Data may be processed in jurisdictions with different data protection standards. We implement appropriate safeguards (contractual clauses, access controls) aligned with applicable law.

10. Children

The Service is not directed to children under 16. If we learn we have collected data from such a child without verified consent, we will delete it.

11. Changes to This Policy

We will post updates with a revised Effective Date. Material changes may also be communicated via in‑app notice or email.

12. Contact Us

Nayar Drive Privacy Team
📞 Phone: +95 9770 333 373
📧 Email: [email protected] (or support channel in app)
🌐 Website: www.nayar-drive.com
📍 Address: R22, B2, MICT Park, Hlaing, Yangon

13. Data Safety Summary

This summary aligns with Google Play’s Data safety form:

  • Data Collected: Precise location, name, phone, email, device IDs, trip details, diagnostics.
  • Data Shared: Only with service providers & partners for core functionality, safety, compliance, and analytics; not sold.
  • Security: Encryption in transit; restricted internal access.
  • Data Deletion: User request workflows & scheduled minimization of old location traces.
  • Purpose Limits: Navigation, safety, fraud prevention, compliance, feature improvement.
  • Optional Data: Contacts, camera, microphone only when user invokes related features.