Privacy Policy

This Privacy Policy explains how Rydar collects, uses, stores, protects, shares, and deletes user data in connection with the Rydar mobile application, website, ride-hailing platform, driver tools, passenger tools, verification tools, wallet/ledger features, support tools, and related services.

Last updated: 18 May 2026

1. Introduction

Rydar respects the privacy of passengers, drivers, applicants, visitors, support users, and other platform users. This Privacy Policy explains what information we collect, why we collect it, how we use it, when it may be shared, how long it may be retained, and how users may request access, correction, or deletion.

2. Developer and Privacy Contact

Rydar is operated under the Rydar name and related business operations.

Website: https://rydar.pk/

Privacy contact email: rydartechnologies@gmail.com

Support page: https://rydar.pk/support/

3. Scope of this Policy

This Policy applies to the Rydar app, website, support pages, verification processes, passenger features, driver features, wallet/ledger features, bonus/promotional features, operational controls, and any related digital or operational service provided under the Rydar name.

4. Information We Collect

Depending on the user role and feature used, Rydar may collect the following categories of information:

Account information: name, phone number, email address, password or authentication information, account role, account status, profile information, language or user preferences.

Passenger and driver profile data: passenger profile, driver profile, selected role, vehicle category, vehicle information, driver availability, and related eligibility records.

Verification data: CNIC or identity document details, face image, profile photo, driving license, vehicle registration documents, character certificate, vehicle photos, document images, verification status, review notes, approval/rejection/resubmission records, and verification history.

Location data: pickup location, drop-off location, live ride location, driver online location, route, distance, ETA, operating-area eligibility, geofencing status, and location records needed for ride tracking, fare estimation, safety, dispute review, and driver availability.

Ride data: ride requests, accepted rides, rejected rides, cancelled rides, completed rides, early-finish/manual-finish records, route information, fare preview, negotiated fare, counter offers, waiting time, pickup/drop-off details, vehicle category, driver/passenger ride status, and ride history.

Payment, wallet, ledger and bonus data: fare amount, cash/wallet/bonus usage, driver balance, passenger balance, platform fee, adjustments, refunds, reversals, bonus/referral/promotional credit, campaign usage, and transaction/settlement records.

Device and technical data: device model, operating system, app version, device identifier where permitted, IP address, session information, login history, device-change records, crash logs, diagnostics, security logs, network information, and app performance information.

Support and complaint data: support requests, complaints, feedback, screenshots, call/email/chat support records, safety reports, dispute evidence, and communication history.

Notification and communication data: notification tokens, SMS or email delivery status, operational alerts, ride alerts, security alerts, policy updates, and support messages.

5. Sensitive Data and Permissions

Rydar may request access to permissions only where required for app functionality, safety, verification, support, or platform operation. These may include location, camera, notifications, internet/network access, and storage or media access where applicable.

Location permission: used for pickup/drop-off selection, route calculation, fare estimation, operating-area validation, driver online/offline eligibility, receiving ride requests, active ride tracking, safety review, and complaint/dispute review.

Background location: for drivers, where approved and enabled, Rydar may use background location while the driver is on duty, online, receiving ride requests, moving toward pickup, or completing an active ride. Background location is intended for driver-duty and active-ride functionality, not unnecessary tracking.

Camera permission: used for profile photo, CNIC/identity document capture, face capture, driving license capture, vehicle document capture, vehicle photo capture, verification, complaint evidence, and support-related image submission.

Notification permission: used to send ride requests, ride status updates, driver/passenger alerts, security alerts, verification messages, wallet/ledger alerts, support updates, and policy notices.

6. How We Use Information

Rydar may use collected information to:

1. Create, authenticate, secure, and manage user accounts.

2. Verify passengers, drivers, documents, vehicles, phone numbers, email addresses, devices, and account activity.

3. Connect passengers and drivers for ride-hailing services.

4. Calculate fare previews, final fare, negotiated fare, platform fee, distance, time, ETA, and route information.

5. Support driver online mode, driver availability, dispatch, ride requests, and operating-area/geofencing rules.

6. Track active rides, improve safety, support dispute resolution, and review complaints.

7. Maintain wallet, ledger, bonus, referral, promotion, adjustment, refund, and settlement records.

8. Prevent fraud, fake rides, duplicate accounts, GPS manipulation, payment misuse, bonus abuse, security threats, and platform misuse.

9. Provide customer support, complaint handling, legal notices, user communication, and operational messages.

10. Improve app performance, reliability, user experience, diagnostics, security, and business operations.

11. Comply with legal, regulatory, tax, accounting, safety, and law-enforcement requirements where applicable.

7. Sharing of Information

Rydar does not sell personal information. However, information may be shared where necessary for platform operation, safety, legal compliance, or service delivery.

Passenger-driver sharing: during a ride, limited information such as name, vehicle details, pickup/drop-off information, ride status, and contact or support-related ride information may be shared between passenger and driver to complete the ride.

Service providers: data may be processed by technical service providers, hosting providers, cloud/database providers, authentication providers, map/routing/geocoding providers, notification providers, analytics/crash-reporting providers, payment or wallet service providers where enabled, and support tools.

Legal and safety sharing: information may be shared with law-enforcement agencies, courts, regulators, tax authorities, emergency services, or other lawful authorities where required by law, safety needs, dispute handling, fraud prevention, or legal process.

Business operations: information may be shared with authorized Rydar staff, administrators, contractors, auditors, legal advisers, technical teams, or operational partners under appropriate confidentiality and access controls.

8. Third-Party Services

Rydar may use third-party or external services for maps, routing, geocoding, hosting, database, authentication, notifications, analytics, crash reporting, payment processing, app distribution, cloud storage, and customer support. These services may process limited data required to provide their services and may have their own privacy policies.

9. Data Security

Rydar uses reasonable administrative, technical, and organizational measures to protect user data. These may include access controls, authentication, encrypted communication where applicable, role-based access, server security, database security, logging, review controls, and limiting access to authorized personnel. No digital system can be guaranteed to be completely secure, but Rydar works to reduce unauthorized access, misuse, loss, or alteration of data.

10. Data Retention

Rydar retains data for as long as reasonably required for service operation, account management, ride records, safety, fraud prevention, dispute handling, legal compliance, tax/accounting requirements, technical logs, and business purposes.

Some records, such as completed ride records, wallet/ledger entries, verification history, complaints, safety reports, tax/accounting records, and legal records, may be retained even after account deletion where required for lawful, safety, dispute, fraud-prevention, accounting, or regulatory reasons.

11. Account and Data Deletion

Users may request account deletion through the Rydar app where available, or through the account deletion page at https://rydar.pk/account-deletion/.

After receiving a deletion request, Rydar may verify account ownership before processing the request. Account data may be deleted, deactivated, anonymized, or restricted according to applicable policy and legal requirements. Some limited records may be retained where required for safety, fraud prevention, dispute handling, completed ride records, tax/legal compliance, accounting, security, or lawful business purposes.

12. User Rights and Choices

Subject to applicable law and verification, users may request access to their information, correction of inaccurate information, deletion of account data, withdrawal of optional permissions, or clarification about privacy practices by contacting Rydar support.

Users can control certain permissions from their device settings. However, disabling required permissions such as location or notifications may limit or prevent important Rydar features, including booking rides, driver online mode, live tracking, verification, and safety alerts.

13. Children and Minors

Rydar is not intended for unsupervised use by children. Minors may use Rydar only through, under the supervision of, or with the consent of a parent, guardian, school, institution, or lawful responsible person where applicable. Rydar may restrict or remove accounts where unlawful or unsafe use by minors is identified.

14. International or Cross-Border Processing

Depending on hosting, cloud services, technical providers, or support tools, user data may be processed on servers located in Pakistan or other countries. Rydar takes reasonable steps to ensure that data is handled according to this Privacy Policy and applicable legal requirements.

15. Legal Compliance and Safety

Rydar may preserve, review, disclose, or use information where necessary to comply with law, protect users, prevent fraud, investigate misuse, respond to legal process, enforce Terms and Conditions, protect Rydar systems, or address safety, emergency, or security issues.

16. Changes to this Privacy Policy

Rydar may update this Privacy Policy from time to time for legal, operational, technical, safety, or business reasons. Updated versions will be published on this page. Continued use of Rydar after the updated Privacy Policy is made available means that the user acknowledges the updated policy, unless applicable law requires another consent process.

17. Contact Us

For privacy questions, support requests, complaints, account-deletion requests, or legal notices, please contact:

Email: rydartechnologies@gmail.com

Support page: https://rydar.pk/support/

Website: https://rydar.pk/