1. Overview
PaXenger collects information needed to operate a private mobility coordination platform for Dispatchers, companies, Drivers, administrators, and mobile app users.
We use this information to create accounts, verify users, publish and manage ride requests, process platform payments, support payouts, send notifications, improve safety, prevent fraud, and provide support.
2. Information we collect
The exact information collected depends on your role and the features you use.
- Account data: name, email, phone, password hash, role, language preference, account status, email verification, approval status, and login activity.
- Driver data: profile details, Pax ID, service areas, state and city working zones, vehicle information, registration expiration, documents, photos, availability, groups, ride activity, and payout setup status.
- Dispatcher data: company name, tax or business information when provided, contact details, saved passengers, ride requests, payment mode, credit wallet activity, and dispatch groups.
- Ride data: pickup and dropoff addresses, stops, coordinates when available, dates, times, passenger count, luggage, vehicle category, fare, distance, duration, notes, offers, assignments, status changes, cancellation notes, and hourly ride timers.
- Payment data: Stripe payment references, payment status, refund status, dispute status, earnings, payout status, fees, transaction history, and audit logs. We do not store full card numbers or full bank account numbers.
- Device and notification data: app version, device platform, push notification identifiers, OneSignal identifiers, browser user agent, IP address, and notification preferences.
- Location and media data: location may be used for maps, pickup/dropoff context, routing, or future tracking features when permission is granted. Photos or files may be uploaded for profile, vehicle, document, or evidence workflows.
3. How we use information
We use information to provide, secure, support, and improve PaXenger.
- Create and manage user accounts, authentication, OTP verification, password resets, and role-based access.
- Review Driver and Dispatcher accounts, working zones, vehicles, documents, groups, and approval status.
- Publish, match, prioritize, assign, cancel, complete, and audit ride requests.
- Show payment mode warnings, prepaid badges, external payment notices, earnings, wallet credits, payouts, reports, and administrative dashboards.
- Process credit purchases, prepaid ride payments, refunds, disputes, Stripe Connect onboarding, weekly payouts, and Instant Pay when enabled.
- Send service emails, OTP codes, alerts, push notifications, internal notifications, receipts, payout updates, and operational messages.
- Detect fraud, abuse, duplicate payouts, unauthorized access, failed webhooks, and violations of platform rules.
5. Payments and banking information
Payment and payout features rely on third-party payment providers such as Stripe and Stripe Connect. Sensitive card and bank information should be entered only into secure provider flows or secure platform forms that tokenize or transmit data to the payment provider.
PaXenger stores payment references, statuses, last-four indicators when available, account status, payout eligibility, and audit records. PaXenger does not store full card numbers, full bank account numbers, banking passwords, or private payment provider keys in user-facing systems.
6. Location, maps, and mobile permissions
The mobile app may request location permission when a feature needs it, such as showing current location, pickup/dropoff context, routing, or future tracking. You can deny or revoke location permissions in your device settings, but some features may not work correctly.
Camera, photo, file, notification, and share permissions are requested only when needed for related workflows such as profile photos, vehicle images, documents, evidence uploads, push notifications, or sharing permitted links.
7. Retention
We keep information for as long as needed to operate accounts, provide services, meet legal and accounting obligations, resolve disputes, prevent fraud, audit financial activity, and enforce platform rules.
Some records, such as payments, payouts, refunds, disputes, ride history, audit logs, and tax or compliance records, may need to be retained even after an account is closed.
8. Security
PaXenger uses technical and organizational safeguards such as authentication, role permissions, token-based API access, server-side validation, audit logs, rate limits, secure payment provider integrations, and restricted access to sensitive areas.
No system can be guaranteed completely secure. Users must protect their passwords, devices, email accounts, and OTP codes, and must report suspicious activity promptly.
9. Your choices and rights
Depending on your location, you may have rights to access, correct, delete, restrict, or export certain personal information. Some requests may be limited by legal, security, financial, or operational recordkeeping requirements.
- You may update profile information from your account where available.
- You may change language preferences through the platform selector.
- You may manage mobile permissions through your device settings.
- You may request support for privacy questions at support@paxenger.com.
10. Children
PaXenger is intended for professional and business use and is not directed to children. Users must be legally able to create an account and enter platform agreements.
11. Changes to this policy
We may update this Privacy Policy as the platform, laws, providers, payment flows, or mobile features change. The updated date will show when the policy was last revised.
12. Contact
For privacy questions, contact support@paxenger.com. Do not send passwords, full card numbers, full bank account numbers, OTP codes, or private keys by email.
This page explains PaXenger platform rules in practical language. It is not legal advice. If you operate in a regulated market, you should also review these terms with your own legal advisor.