PassengerPool

Legal

Privacy Policy

PassengerPool is built around trust and safety. This Privacy Policy explains what information we collect, why we collect it, how we use it, and how we protect it.

PassengerPool is a technology platform for verified shared commute coordination. PassengerPool helps users coordinate shared rides. Users remain responsible for verifying ride details, pickup points, travel arrangements, and personal safety.

Who We Are

PassengerPool is operated by PassengerPool (SMC-PVT) Ltd, a company registered with the Securities and Exchange Commission of Pakistan (SECP). It is the company that decides how the personal data described in this policy is used.

Company
PassengerPool (SMC-PVT) Ltd
Company type
Single-member private company limited by shares
SECP registration (CUIN)
0360861
Incorporated
2026
Registrar
Company Registration Office (CRO) Lahore
Registered office
Punjab, Pakistan

Information We Collect

Account Information

  • Full name
  • Phone number (given with your first seat request or when you verify your identity)
  • Email address
  • City (given when you verify your identity)
  • Profile photo, if provided
  • Authentication and login information
  • How you sign in: email and password, Google (website and mobile app), or Apple (mobile app). If you sign in with Google or Apple we receive the name and email address that service shares with us. If you choose Apple's Hide My Email, we receive a private relay address instead of your real one.

KYC and Verification Information

  • CNIC number, CNIC front image, and CNIC back image
  • Selfie image. In the mobile app, document and selfie photos are taken with your phone's camera at the time you verify; the app does not accept photos chosen from your gallery. On the website the photos are taken with your device's camera in the browser; a file picker is offered only on a device where no camera can be used.
  • Date of birth and gender. The date of birth is checked only to make sure you are 18 or older; a date that shows you are younger is refused.
  • Emergency contact name and emergency contact phone
  • Driving license number and driving license images
  • Vehicle registration number and vehicle registration document
  • Vehicle make, model, year, color, and plate number
  • Community, workplace, or university details, if provided

Ride and Route Information

  • Routes, pickup and drop-off areas, ride date, and ride time
  • Seat availability and ride requests
  • Accepted, rejected, cancelled, completed, or no-show request status
  • Platform-calculated fare data including total trip cost, per-seat cost, distance, fuel calculation, wear-and-tear allowance, and toll amount
  • Agreed cost-sharing amount and in-app honour-based payment confirmation status, such as whether the fare was marked as paid by the passenger and confirmed as received by the driver
  • Ride history, ratings, and reviews where supported

Safety and Support Information

  • User reports, complaints, disputes, and support messages
  • Admin review notes and moderation status
  • Emergency or SOS-related information if safety features are enabled

Technical Information

  • Device and browser information
  • IP address if logged by hosting or security tools
  • Cookies or analytics identifiers if used
  • App usage logs and error logs
  • In the mobile app: a push-notification token for your phone, the language and appearance you chose, and your notification and analytics preferences
  • On the website, only if you turn alerts on: a push-notification token for that browser and the language you use
  • In the mobile app: anonymous usage analytics and crash reports (see Cookies and Analytics below)
  • On the website, only if you allow it: anonymous page views and counts of errors (see Cookies and Analytics below)

Location Information

  • Approximate route and location data needed for shared ride coordination
  • Geocoded latitude and longitude coordinates for pickup and drop-off points and route endpoints, collected when a user selects a verified location through the in-app map search
  • Road distance calculations between selected locations and route endpoints, performed via Google Maps Distance Matrix API to enforce safety boundaries
  • The road a driver chooses for a ride, including any places it passes through ("via"): the line of the road, its distance and expected duration, and the towns along it, worked out with Google's routing service
  • In the mobile app: your current position is used as the starting pickup when you request a ride, and to show you rides on your road.
  • In the mobile app: live location, including in the background, only while you are taking part in a ride. For drivers: while available for requests and while a ride of theirs is under way. For passengers: while they have an open ride request and from booking until the ride ends. It is not collected at other times.
  • In the mobile app: to protect users from false locations, the app checks that each position your phone reports is genuine and refuses positions reported by location-faking tools. Our servers also check live positions for movements that are not physically possible. A refused position, and the reason, is recorded with the ride for safety review.
  • In the mobile app: place names and searches are looked up through OpenStreetMap's Nominatim service, and map images are loaded from OpenStreetMap servers. These services receive the text you search for or the coordinates of the pin, and your IP address.

Why We Collect Information

  • To create and manage accounts
  • To verify passenger identity
  • To verify driver identity and vehicle details
  • To allow users to offer and request rides
  • To calculate a transparent, platform-set fare based on route distance, fuel price, wear-and-tear, and toll — split equally among all occupants including the driver
  • To validate pickup and drop-off locations against safety criteria, including place type, keyword filters, and road distance from the route
  • To improve safety and prevent misuse
  • To detect fraud, impersonation, spam, fake accounts, or suspicious behavior
  • To provide support and feedback handling
  • To investigate reports, complaints, and disputes
  • To improve app performance
  • To let you sign in with email, Google, or Apple
  • To send notifications you have not turned off, such as ride requests, decisions on requests, and verification results
  • To detect and refuse false locations and other attempts to bypass safety checks
  • To show a ride request only to drivers on the passenger's road with a free seat, and to show passengers only those drivers
  • To let a booked passenger and driver see each other's position until the ride ends, and to support safety features such as sharing a trip and emergency help
  • To calculate each passenger's fare from the road distance of the part of the driver's road they travel
  • To understand which parts of the app are used and where people get stuck, using anonymous analytics
  • To keep closed accounts closed and prevent spam and repeat abuse (see Deleting Your Account)
  • To comply with applicable legal obligations where required

How We Use KYC Documents

CNIC, selfie, driving license, and vehicle documents are used only for verification, safety review, fraud prevention, dispute handling, and platform integrity.

  • KYC documents are not displayed publicly.
  • Only authorized admin or review staff can access these documents.
  • Public users only see limited trust indicators such as verified badge, rating, display name, city, and ride count where available.
  • Verification is reviewed by a person; it is not decided automatically.
  • You can ask to review your verification data. If you delete your account, verification records and documents are retained as explained under Deleting Your Account.

The PassengerPool Mobile App

The mobile app for Android and iPhone uses the same account and data as the website. It asks for these permissions, each only when needed:

Permissions

  • Camera: to take your verification photos. The app has no access to your photo gallery.
  • Location, including in the background ("Always" on iPhone, "Allow all the time" on Android): to set your pickup from where you are, to match you with rides on your road, and to share live location while you are taking part in a ride (see Location Information). Android shows a notification while location is in use. Without this permission you can browse rides but cannot request, offer, or take part in one.
  • Notifications: to tell you about requests, decisions, and verification results. You can turn them off in the app (Account) or in your phone settings.

Without an account

  • Anyone can browse upcoming rides in the app without signing in.
  • Visitors who are not signed in see the route, date and time, price per seat, seats left, vehicle, the driver's first name and rating. They do not see exact pickup or drop-off points, ride notes, or contact details.

Security of the app itself

  • The app uses Firebase App Check (Play Integrity on Android, App Attest on iPhone) to help confirm that requests come from the genuine app. This involves Google or Apple device attestation services.
  • Accounts with administrator access are for the website only. They are not used for rides in the app.

Sharing of Information

PassengerPool may share limited information only where needed for platform operations, safety, support, or legal compliance. PassengerPool does not sell personal data.

  • With other users only when necessary for confirmed ride coordination. Before a ride is booked, drivers on the same road are shown only as their chosen road and roughly how far along it they are, never an exact live position. After booking, the passenger and the driver of that ride see each other's live position until the ride ends.
  • With the admin or support team for verification and safety review
  • With hosting, authentication, storage, analytics, notification, communication, or infrastructure providers (see Third-Party Services)
  • With Google LLC for location search, place type validation, and road distance calculation via the Google Maps Platform. Location coordinates are sent to Google's Distance Matrix API to check that a selected pickup or drop-off is within a safe road distance of the route. This is subject to Google's own privacy policy.
  • With legal or regulatory authorities if required by law or to prevent harm, fraud, or criminal misuse
  • With emergency contacts if emergency features are triggered and enabled

Third-Party Services

PassengerPool uses the following third-party services that may process data on our behalf. Each service is governed by its own privacy policy.

Google Maps Platform

  • Used for location search (Places Autocomplete), place type validation, road distance calculation (Distance Matrix API), and the road choices offered to a driver when publishing a ride (Routes API). Route requests are sent from our servers with the start, end and any via places only; no personal identity data or live location is included.
  • When a user selects a pickup or drop-off location, the chosen coordinates are sent to Google's Distance Matrix API to verify the road distance from the route. No personal identity data is included in these calls.
  • The Google Maps JavaScript SDK is loaded from Google's CDN when the user opens a form that includes location fields.
  • Google's use of this data is governed by the Google Privacy Policy at google.com/policies/privacy.

Firebase / Google Cloud

  • Used for authentication, database (Firestore), file storage, cloud functions, and hosting.
  • Subject to Google Cloud and Firebase terms and privacy policies.

Google Sign-In (website and mobile app) and Sign in with Apple (mobile app)

  • If you choose to sign in with Google or Apple, that service confirms your identity to us and shares your name and email address. We do not receive your Google or Apple password.
  • Use is governed by the Google Privacy Policy and Apple's privacy policy. If you delete your account after signing in with Apple, we ask Apple to revoke the app's access.

Push notifications (mobile app and, if you turn them on, the website)

  • Notifications are delivered through Firebase Cloud Messaging and, on iPhone, the Apple Push Notification service. Your phone's notification token is stored so we can reach your phone, and removed when you sign out.
  • On the website, alerts in your browser are off until you turn them on (Profile, then Alerts on this device) and allow them when your browser asks. A token for that browser is then stored so we can reach it, and removed when you turn alerts off or sign out. Your browser's own push service delivers the notification.

OpenStreetMap (mobile app)

  • Map images are loaded from OpenStreetMap servers, and place search and place names use OpenStreetMap's Nominatim service. These services receive your IP address and the text or coordinates being looked up.

Firebase Analytics / Google Analytics for Firebase (mobile app and, if you allow it, the website)

  • Used to understand how the app and the website are used. See Cookies and Analytics below for what is collected and how to switch it off.

Firebase Crashlytics (mobile app)

  • Used to receive a report when the app fails, so we can fix it. A report contains the error and where it happened in the app, the app version, the phone model and the operating system version. It does not contain your name, phone number, email address, ID numbers, documents, or location. It is switched off together with usage analytics in Account.

Public Profile and Ride Visibility

Other users may see limited trust and ride coordination details.

May be visible

  • Display name or first name
  • Profile photo, if provided
  • Verified badge
  • City
  • Rating
  • Ride count or ride history summary where supported
  • Basic ride details
  • Basic driver vehicle information relevant to the ride

Visitors who are not signed in (website and mobile app)

  • Anyone can browse upcoming rides. Without signing in they see the route, date and time, price per seat, seats left, vehicle, the driver's first name and rating.
  • Exact pickup and drop-off points and ride notes are shown only to signed-in people. Contact details are not shown.

Accounts that are being deleted or are closed

  • Their profile and their rides, requests, alerts, and ratings are hidden from other users. See Deleting Your Account.

Never shown publicly

  • CNIC number or CNIC images
  • Driving license number or driving license images
  • Vehicle registration document images
  • Emergency contact details
  • Full phone number unless needed after confirmed ride coordination
  • Exact home address
  • Sensitive admin notes

Data Security

  • Restricted admin access for sensitive review surfaces
  • Authentication checks before private account, ride, request, and KYC access
  • Firebase and Storage access controls where applicable
  • Audit logs for verification review activity where implemented
  • No public access to KYC documents
  • Reasonable technical and operational protection measures

No system can guarantee 100% security, but we take reasonable steps to protect user data.

Data Retention

  • Account data is kept while the account is active.
  • Ride history and safety logs may be retained for trust, safety, fraud prevention, and dispute resolution.
  • Live location: the latest position is overwritten as it changes. The track of a booked ride is kept for 30 days after the ride ends for safety and dispute handling, then deleted, unless it is part of an open safety report.
  • KYC data may be retained as long as necessary for verification, safety, fraud prevention, dispute handling, and legal compliance.
  • When you delete your account it is hidden from other users at once and closed after 30 days. Closed accounts are disabled, not erased; the records described under Deleting Your Account are retained.
  • We keep records for as long as they are needed for safety, spam and fraud prevention, dispute handling, and legal obligations, and we review what we hold from time to time.

Deleting Your Account

In the mobile app you can delete your account from Account, then Delete my account; on the website, from Profile, then Delete my account. You are asked to sign in again to confirm. This is what happens:

  • At once: your profile and everything other users could see of you (your rides, requests, alerts, and ratings) is hidden from other users, your pending requests are cancelled, and notifications to your phone stop.
  • For 30 days: you can sign in again and choose Keep my account. Everything comes back as it was.
  • After 30 days: your account is closed. Your sign-in is disabled and cannot be used again, and the account cannot be used to ride, offer rides, or contact other users.
  • You cannot delete your account while you have a live ride: an active ride you offered, or a seat another driver has accepted. Finish or cancel it first.

Closing an account does not erase all of its data. We disable the account and keep certain records, because we need them to keep users safe, to stop spam, repeat abuse, and fraudulent or duplicate accounts, to handle disputes and reports, and to meet legal obligations. The records we keep are:

  • Your profile details and sign-in identity (which also keeps your email address from being used to open a new account)
  • Verification requests, including identity documents and photos, and verification audit logs
  • Ride, request, rating, and alert records, which stay hidden from other users
  • Reports, support requests, and feedback you sent or that concern you

These records are not shown to other users and are used only for the purposes above. If you want to know what we hold about you, or you ask us to erase data, contact us at support@passengerpool.pk. Where the law gives you a right to erasure we will consider your request against the reasons above. We may restore a closed account if you ask, unless it was closed for misuse.

User Rights and Choices

  • Access profile data
  • Correct or update inaccurate information
  • Delete your account in the mobile app or on the website (see Deleting Your Account), or ask support to help
  • Request review of verification data
  • Turn off notifications in the app or on your phone, switch off usage analytics and crash reports in the app (Account), and allow or decline website analytics at any time on this page
  • Contact support for privacy concerns
  • Disable optional public profile fields where supported

Cookies and Analytics

We use analytics to understand which parts of PassengerPool are used and where people get stuck, and crash and error reports to fix failures, so we can improve reliability, safety, and product quality. We do not sell personal data and we do not use advertising cookies or advertising identifiers.

Mobile app

  • Usage analytics and crash reports are switched on by default and you can switch both off at any time in the app: Account, then Help improve PassengerPool.
  • What is collected: simple events such as the app being opened, a ride being viewed, a sign-in method being chosen, verification being started or submitted, a ride being offered, a request being answered or a ride completed, and a seat request being sent. Firebase Analytics also collects standard information such as first open, sessions, screen views, app version, device model, operating system, and approximate region. A crash report contains the error, where it happened, the app version, the phone model and the operating system version.
  • What is not collected in these events and reports: your name, phone number, email address, ID numbers, documents, or location.
  • Development and test builds of the app collect nothing.

Website

  • The website collects nothing for analytics until you press Allow on the notice that appears on your first visit. Until you choose, and if you decline, nothing is collected and no analytics identifiers are stored in your browser.
  • If you allow it: the pages you open (the address without any search words), counts of sign-ups completed, seat requests sent and rides offered, and the text of errors the page hits (shortened, with no web addresses). Firebase Analytics may also store an identifier in your browser and collect standard information such as browser, device type, and approximate region.
  • Not collected: your name, phone number, email address, ID numbers, documents, or locations you enter.
  • You can change your mind at any time with the control below, or by clearing this site's data in your browser.
  • The website does not use advertising cookies.

Children and Minors

  • PassengerPool is not intended for users under 18.
  • Users must be 18 or above to create an account, request rides, or offer rides. The date of birth you give when you verify must show that you are 18 or older.
  • Drivers must hold a valid driving license.

Changes to This Privacy Policy

PassengerPool may update this Privacy Policy as the platform, safety features, verification workflows, and legal obligations evolve. The latest version, with its effective date, will be posted on this website. If a change is significant we will also tell you in the app or by email.

Contact

For privacy questions, data requests, or account support, contact PassengerPool (PassengerPool (SMC-PVT) Ltd) at support@passengerpool.pk.

Website: https://passengerpool.pk

You can also use the Contact / Support page.

Questions or requests?

Contact PassengerPool support for account, privacy, verification, or safety questions.

Website: https://passengerpool.pk