Privacy Policy
WULLIB LLC
Last updated: October 14, 2026
1. Who We Are and What This Policy Covers
WULLIB LLC (“WULLIB,” “we,” “us,” or “our”) provides the WULLIB ride-hailing website and mobile applications for riders and drivers. This policy explains how we collect, use, disclose, and retain personal information when you use those services or contact us.
Privacy contact: wullib@zohomail.com. You can also contact us at 954-800-5314.
2. Information We Collect
The information collected depends on your role and the features you use.
Account and Contact Information
We collect information such as your name, email address, phone number, account identifiers, profile photo, preferences, and addresses you provide for accounts, trips, or verification. Our authentication provider processes sign-in credentials and verification information.
Trip and Service Activity
We collect ride requests, pickup and destination details, routes, trip times and status, cancellations, driver availability, dispatch and ride-response records, service selections, ratings, and related account activity. These records support rides, customer service, disputes, safety, and operational reports, including trip counts and driver performance.
Payment and Financial Information
We and our payment providers process payment-method information, charges, payment authorizations, receipts, refunds, wallet-credit records, driver earnings, subscription or service-fee records where applicable, and payouts. Payment providers also process information needed for driver payment accounts and identity, tax, and compliance requirements. WULLIB receives transaction identifiers, payment status, and payment-method details returned by those providers.
Location Information
We collect pickup and destination addresses and device location when permission is granted and a location-dependent feature is active. This may include precise GPS coordinates, timestamps, and accuracy information. We use location for nearby-driver availability, dispatch, pickup, navigation, live trip monitoring, safety, and destination-proximity checks. Location can be associated with your account and trip. Granting permission does not, by itself, mean location is continuously collected at all times.
Drivers who go Online may enable background location so WULLIB can update dispatch and live availability while the app is in the background or the screen is locked. Android displays an ongoing location-service notification; iOS may show a background-location indicator. Going Offline or signing out stops this sharing. Nearby riders and other drivers see anonymous available-car positions, not driver names or contact details. Assigned riders can see their own trip's driver, and authorized administrators can see the working fleet. Background location is not required for rider accounts, and device permissions, power saving, network access, or force-closing the app may interrupt updates.
Communications and Support
We collect messages sent through WULLIB, support requests and correspondence, and related delivery and resolution records. This does not mean unrestricted access to your personal email inbox or messages outside WULLIB.
Driver Identity, Eligibility, and Compliance
For drivers, we collect driver-license information, government-ID images, selfies, vehicle details, insurance and registration documents, verification results, and background-check status and related records needed to evaluate eligibility and administer compliance.
Identity verification may submit an ID image and selfie, or a reference selfie and a new selfie, to a face-verification provider. The current implementation compares still images; it does not use an interactive head-movement challenge or environmental or hand scanning. Results may require manual review. Face comparison may involve biometric processing under applicable law. This policy does not replace separate notices or consent required for biometric processing or background checks.
Driver background screening may be conducted by a screening provider under a separate disclosure and authorization process. The provider may collect information directly from the driver; WULLIB receives relevant status and report information for eligibility and review.
Uploaded Images and Documents
We collect profile images, identity images, compliance documents, and other files you submit. Insurance or registration images may be transmitted to an AI-assisted document-processing service to extract information such as document type and expiration date. Images may contain other personal information visible in the document. Uncertain or unsuccessful extraction can require further review.
Device, Technical, and Diagnostic Information
Our services and providers may process IP addresses, device or browser information, request logs, security events, identifiers, and push-notification tokens needed to deliver and protect the service. Some diagnostics remain on your device unless you send them to support. Technical information actually transmitted is used as appropriate for security, troubleshooting, delivery, and reliability. This policy does not mean every possible diagnostic is collected or transmitted.
3. How We Use Information
We use personal information to:
- Create, authenticate, and administer accounts and role-specific profiles.
- Arrange rides, dispatch drivers, and provide navigation and trip updates.
- Process fares, authorizations, refunds, wallet adjustments, driver fees, and payouts.
- Verify driver identity and eligibility, review documents, and administer background checks.
- Provide support, communicate updates, and handle requests and disputes.
- Detect fraud, protect users, enforce service rules, and comply with applicable law.
- Analyze our own trip and account records to improve service operations.
- Send promotional communications where applicable and permitted, subject to available consent and opt-out choices.
Operational reports can include a driver’s name and identifier alongside trip and earnings figures. Information is not anonymous merely because it appears in an analytics report.
4. Who Receives Information
Riders, Drivers, and Authorized Administrators
Assigned riders and drivers may receive relevant trip details, displayed identity/profile details, messages, and live location information appropriate to their roles.
Nearby online drivers may see other available online drivers’ current locations in their local area. Drivers serving a ride are excluded from that peer-location sharing. Before booking, riders may receive approximate, anonymous nearby-driver availability; they receive their assigned driver’s exact location in connection with the ride, not the entire fleet’s exact positions.
Authorized administrators may access account, verification, trip, financial, and fleet information needed for operations, support, safety, compliance, and review.
Service Providers
Relevant services include the following, depending on the feature and enabled configuration:
- Clerk for authentication and account identity.
- Stripe for payments, payment methods, driver payment accounts, and payouts.
- Google Maps and Places for maps, address searches, and routing.
- Twilio for SMS communications and Resend for email delivery.
- Expo and applicable mobile-platform notification services for push delivery where enabled.
- Vouched for image-based driver identity verification; AWS Rekognition is an alternative verification integration if enabled.
- Checkr for driver background screening where used.
- OpenAI-based document analysis through our integration infrastructure for uploaded insurance and registration documents.
- Hosting, database, file-storage, and infrastructure providers supporting WULLIB.
We disclose information relevant to the service provided. Some providers also process information under their own privacy notices and legal obligations. Consult those notices for their independent practices.
Other Disclosures
We may disclose information as required by law or legal process, to investigate fraud or safety incidents, protect legal rights, or resolve disputes. Information may be transferred in a legitimate merger, acquisition, or asset transaction, subject to applicable requirements. Additional disclosures may occur with valid consent where required.
5. Cookies, Advertising, and Tracking
The website and authentication services use cookies or similar storage where needed for functions such as sign-in and preferences. The native app uses local storage for session and application information. These mechanisms are not, by themselves, cross-company advertising tracking. Reporting on WULLIB’s own ride and account records differs from linking information with other companies’ data for targeted advertising or advertising measurement.
WULLIB does not sell personal information or share it for cross-context behavioral advertising. WULLIB does not use information collected through the native app for cross-company targeted advertising or advertising measurement. We disclose information to service providers for the operational purposes described in this policy, rather than to offer it for those advertising purposes.
Providers may also process information under their own privacy notices and legal obligations. Our statements about WULLIB’s practices do not represent that every provider has identical practices across all its products. If our practices change, we will update this policy and provide notices and obtain permissions required by applicable law and platform rules before the relevant processing begins.
6. Retention and Account Deletion
We retain information according to its processing purpose, applicable legal requirements, pending transactions and disputes, fraud and safety considerations, and provider retention arrangements. Relevant categories include accounts, trips, communications, identity and compliance records, background screening, payments, and technical logs.
You can request account deletion through WULLIB’s account settings or by contacting wullib@zohomail.com. One sign-in identity can have multiple profiles; account deletion applies to associated profiles, not just the currently selected rider or driver portal.
Open trips, unsettled payments, wallet funds, payout balances, or other obligations may need resolution before self-service deletion completes. Contact support if a request cannot proceed. Deactivation and deletion are different actions.
Deletion may require coordinated processing by authentication, payment, verification, and storage services. Records necessary for legal obligations, settlement, fraud prevention, disputes, or legal claims may be retained. Deleting a profile does not establish that every associated record or third-party copy has been erased or anonymized.
Retention periods vary by category, purpose, and legal requirements. Contact us for information about your data, retention reasons, and deletion requirements. Any specific notice, retention limit, or destruction schedule required by law applies in addition to this general policy.
7. Permissions, Choices, and Privacy Requests
Manage camera, photo, location, and notification permissions through device settings. Restricting permissions may prevent features from working; turning permission off does not erase information already collected.
Use available account controls to update information or request deletion. For marketing SMS, follow the message’s opt-out instructions, including STOP where supported. For promotional email, use an available unsubscribe option or contact us. Essential account, security, legal, and transaction messages may still be sent as permitted.
Depending on your location and applicable law, you may have rights to access, correct, delete, or obtain a copy of information, restrict processing, or exercise sale/sharing and other opt-outs where relevant. Contact wullib@zohomail.com. We may verify a requester’s identity and apply legally permitted exceptions. Where required, we will explain an available appeal process. This policy does not waive legal rights.
8. Security and International Processing
We use safeguards intended to protect personal information, but no service guarantees absolute security. Information may be processed by WULLIB and its providers in the United States or other jurisdictions. Applicable legal safeguards and provider arrangements must be considered when transferring personal information.
9. Children and Eligibility
You must be at least 18 years old to create a WULLIB rider account. Driver eligibility may impose additional age and other requirements. This account requirement does not by itself define the rules for minors traveling with an eligible adult.
If you believe someone below the applicable minimum account age has provided information through an account, contact us so we can investigate and take appropriate action under applicable law.
10. Changes and Contact
We may update this policy when our practices or services change. We will update the date and provide additional notice or obtain consent where required by applicable law.
WULLIB LLC — wullib@zohomail.com — 954-800-5314.