RideWave Privacy Policy
Your trust and privacy are paramount to RideWave. This comprehensive policy explains how we collect, use, protect, share, retain, and delete your personal information across our ride-sharing and carpooling platform.
Introduction and RideWave Services
Welcome to RideWave (accessible at https://ridewave.muzamal.site), operated by RideWave Technologies(“RideWave”, “we”, “our”, or “us”). RideWave is an AI-powered ride-booking, intercity carpooling, and urban mobility marketplace connecting independent drivers (“Riders” or “Captains”) who have empty vehicle seats with verified travelers (“Travelers” or “Passengers”) traveling along matching routes.
This Privacy Policy describes our practices regarding the collection, storage, use, disclosure, retention, and deletion of personal data when you access or interact with our web application, APIs, customer support, and related mobility services (collectively, the “Platform”).
Our Core Commitment:
We believe in complete transparency. We never sell your personal data or Google account information to data brokers or third-party advertising networks. Data collected is strictly used to deliver, secure, and improve your transportation experience.
Personal Information We Collect
Depending on how you use RideWave (as a Traveler seeking a ride, a Driver offering rides, or a visitor browsing routes), we collect the following categories of personal information:
Profile & Identity Data
- Full Name and Display Name
- Email Address and Email Verification Status
- Phone Number
- Profile Picture / Avatar URL
- Date of Birth, Gender, Address, City & Country
- Emergency Contact details (Name, Phone Number, Email)
- Travel Preferences & Languages spoken
Driver & Vehicle Data
- Government ID (CNIC/National ID) and Driving License numbers
- Document Scans (ID front/back, selfie, driving license photo)
- Vehicle Make, Model, Year, Registration Number, and Color
- Vehicle Type (Car, Bike, Van, Bus), Fuel Type, Transmission
- Total Passenger Seat Capacity and Vehicle Photos
- Insurance Registration details
Trip, Route & Telemetry Data
- Pickup Address, Destination Address, and intermediate stops
- Precise GPS Coordinates (Latitude and Longitude)
- Real-time driver GPS tracking (speed, heading, accuracy, timestamps)
- Departure Date, Time, Distance (km), and Estimated Travel Duration
- Seat reservation counts and customized pickup notes
Financial & Transaction Data
- Transaction references, invoice URLs, and payment amounts
- Payment Methods (Stripe Card, JazzCash, EasyPaisa, Cash, Wallet)
- Promotional discount codes and referral credits
- Note: Raw card numbers and CVCs are processed by Stripe; RideWave never stores credit card credentials.
Account Registration & Authentication
RideWave supports two secure methods for account creation and authentication via NextAuth.js:
1. Email & Password Authentication
Users may register with their email address and a self-selected password. All passwords are salted and hashed using industry-standard bcrypt (10+ salt rounds) before database storage. Plaintext passwords are never logged, never stored, and cannot be viewed by RideWave staff.
2. Google Sign-In (OAuth 2.0 Single Sign-On)
Users can sign in seamlessly using their existing Google Account. When you select Google Sign-In, Google handles password validation and returns an authorized OAuth token. No Google password is ever exposed to or collected by RideWave.
User sessions are maintained through encrypted JSON Web Tokens (JWT) signed with a high-entropy secret key and transmitted over HTTPS-only cookies.
Google Sign-In and Google User Data
Compliance with Google API Services User Data Policy
RideWave complies strictly with Google's verification and disclosure requirements for apps using Google OAuth 2.0. This section explicitly documents how Google user data is accessed, utilized, stored, shared, retained, and deleted.
A. What Google Data We Access
When you choose to register or log in to RideWave using Google Sign-In, we request access only to your basic Google profile identity (via standard OAuth openid, email, and profile scopes). Specifically, we receive:
- Google Account Email Address: Used to uniquely identify and link your account.
- Full Name / Display Name: Used to personalize your profile and display your name to fellow travelers or drivers on confirmed rides.
- Profile Picture URL: Used as your initial public avatar on RideWave.
- Google Provider Subject ID (
sub): A unique numeric identifier returned by Google to verify authentication across sessions.
We do NOT request access to Google Drive, Gmail, Google Contacts, Google Calendar, or any sensitive or restricted scopes.
B. How We Use Google User Data
Data received from Google Sign-In is used exclusively to:
- Authenticate your identity and grant access to your account without requiring a separate password.
- Create your verified user profile and assign your platform role (default: Traveler).
- Send you essential booking receipts, driver arrival alerts, and security notifications via email.
- Display your first name and profile photo to confirmed co-passengers and drivers for boarding verification.
C. How Google User Data Is Stored & Protected
Google profile data is stored in our secured MongoDB cluster hosted within isolated virtual private cloud (VPC) subnets. Data is encrypted in transit using TLS 1.3 and encrypted at rest using AES-256 encryption. Access to database instances is strictly restricted to authorized production processes.
D. Sharing & Transfer of Google Data
Zero Third-Party Advertising Sharing: We do NOT share, transfer, or disclose Google user data to data brokers, third-party advertisers, market researchers, or advertising networks under any circumstances.
Google user data is shared solely with other registered users on RideWave to the minimal extent necessary to coordinate rides (e.g., displaying a driver's photo to a traveler waiting at a pickup stop).
E. Retention & Deletion of Google Data
We retain Google user data only for as long as your RideWave account remains active. You may delete your account and all associated Google user data at any time by visiting your Account Settings or emailing muzamalfarooq111@gmail.com. Upon account deletion, all Google-derived identifiers, emails, names, and avatar references are permanently erased from our active databases within thirty (30) days.
Google API Services User Data Policy: Limited Use Disclosure
RideWave's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy , including the Limited Use requirements.
GPS Location and Google Maps Platform
Accurate location information is essential for ride-sharing. We integrate the official Google Maps JavaScript API, Google Places Autocomplete API, and Distance Matrix API to deliver map features:
1. Traveler Location Collection
When a passenger searches for a ride or sets a pickup point using our interactive map or Places autocomplete, we collect approximate or precise latitude and longitude coordinates. This data is used solely to match you with drivers traveling along your route and compute pickup walking distances.
2. Real-Time Driver GPS Tracking
When a driver begins an active ride, the RideWave application collects device GPS coordinates, heading, speed, and accuracy via the browser/device Geolocation API (navigator.geolocation.watchPosition). These updates are transmitted over encrypted WebSockets (location:update) and broadcast exclusively to confirmed passengers on that specific ride via ride:{rideId} rooms.
3. User Permission & Control
Location access always requires your prior consent via standard device/browser permission dialogues. You can disable location tracking at any time in your device settings. Real-time driver GPS tracking automatically terminates the moment a ride is marked as completed or cancelled.
By using Google Maps within RideWave, you are also bound by the Google Maps/Google Earth Additional Terms of Service and the Google Privacy Policy.
Rider, Driver, Vehicle & Booking Data
To maintain platform safety, prevent fraud, and verify identity:
- Driver Verification: Drivers must submit identity documentation (CNIC, driving license, vehicle photos) for review before publishing rides. Verification documents are stored in private Cloudinary media buckets and accessed solely by authorized trust & safety personnel.
- Vehicle Information: Make, model, year, registration number, and seat capacity are displayed publicly on published rides so passengers can locate their designated vehicle safely.
- Booking Passes & QR Codes: Each confirmed booking generates a unique reference number (
bookingRef) and an encrypted boarding QR code scanned by the driver upon passenger pickup. - Reviews & Ratings: Following ride completion, travelers and drivers may submit 1-to-5 star ratings and reviews. Reviews are displayed publicly on user profiles to build community accountability.
Data Usage, Storage & Security
We implement comprehensive technical, operational, and organizational security measures to protect your information against unauthorized access, destruction, loss, or alteration:
Cryptographic Safeguards
All web communication is encrypted using Transport Layer Security (TLS 1.2 / TLS 1.3). Database collections are protected by AES-256 encryption at rest. Passwords use bcrypt hashing with salted rounds.
Access Controls & Boundaries
Role-Based Access Control (RBAC) separates administrative permissions from general user access. Strict server-side route guards verify JWT session validity before executing any database mutation.
Third-Party Service Providers
We partner with trusted third-party cloud infrastructure providers who process data on our behalf under strict confidentiality agreements:
OAuth single sign-on authentication, geolocation, mapping, route planning, Places autocomplete.
Secure payment gateway processing credit/debit card transactions under PCI-DSS Level 1 compliance.
Encrypted media asset storage and content delivery network (CDN) for avatars and vehicle photos.
Enterprise cloud database hosting user accounts, ride reservations, and platform data.
Automated dispatch of transactional email receipts, ride reminders, and password resets.
Data Retention & Account Deletion
We retain your personal data only for as long as necessary to provide RideWave services, comply with legal obligations (such as tax, accounting, and transport safety regulations), and resolve platform disputes.
How to Request Full Account & Data Deletion:
You have the right to request the permanent deletion of your RideWave account and all associated personal data (including Google OAuth tokens, vehicle documents, profile photos, and trip history). You can exercise this right through:
Upon receiving a deletion request, we permanently purge or anonymize your personal records within thirty (30) calendar days, retaining only non-identifiable records required by statutory law.
Your Privacy Rights & Choices
Depending on your location and jurisdiction, you enjoy the following privacy rights:
Children's Privacy
RideWave is strictly intended for individuals who are at least 18 years of age (or the legal age of majority in your jurisdiction). We do not knowingly solicit, collect, or store personal information from children under 18 years of age. If we learn that personal data of a minor has been collected without verifiable parental authorization, we will promptly delete that data from our systems. Parents or guardians who believe their child has registered an unauthorized account may contact us at muzamalfarooq111@gmail.com.
Policy Updates & Contact Information
We may periodically update this Privacy Policy to reflect enhancements in our mobility technology, legal mandates, or operational workflows. When modifications are made, the revised “Last Updated” date at the top of this document will be updated. Continued use of RideWave following posted revisions constitutes acceptance of the updated terms.