Privacy notice

Effective date: September 14, 2026.

This notice describes the Boober Tours public website and the Boober Tours: Pedicab Rides mobile app. The platform connects riders, approved pedicab drivers, and authorized operator staff. Available functions depend on your app version and the active service. Version 1.2 is prepared for store review on this date.

Data we use

• Account data, such as your name, email address, phone number, account status, and approved-driver status.
• Ride data, such as pickup, destination, passenger count, quote, fare, ride status, assigned driver, passenger-count approval, receipt, and support records.
• Ride activity, such as a public driver-profile view, a driver cancellation reason, and passenger-count approval.
• Version 1.2 account choices, such as a favorite driver, a completed-ride rating score, a selected tip, and launch-credit grant, reservation, use, release, and refund records.
• Your precise current location when you choose a pickup or use a location-sharing function described below.
• Payment records, such as amount, status, refund, provider reference, and a safe card label. Stripe can store the selected card for later rides. The app does not store the raw card number or card security code.
• Driver financial records, such as earnings, transfer and payout amounts, status, and provider references. Stripe collects identity and bank details in its account setup form. Boober does not receive or store the raw bank-account number.
• App installation and device data needed for secure sign-in, service protection, and provider operation. Version 1.1 and later can register an account-linked installation and push token for ride and active-shift notices.
• Technical data from our service providers. This can include map and payment-screen interaction, request data, an SDK identifier, crash data, performance data, and website usage measurements.
• Beta-list data, such as the email address or US mobile number that you submit, your rider or driver interest, your separate email and text choices, and the time and source of each choice.

How we use data

We use this data to provide accounts, quotes, dispatch, ride tracking and pickup-time estimates, payment, passenger-count approval, receipts, favorite drivers, ride ratings, voluntary tips, launch credit, driver earnings, support, security, fraud prevention, and required records. Google Maps and Stripe also use some technical data to operate, protect, and improve their services. The app does not use this data for advertising or cross-app tracking. We do not sell personal data.

Location limits and choices

Version 1.0 uses location while the app is open. Version 1.1 and later include the separate location choices below. Available choices depend on your app version and the active service.

When rider sharing is available, you can separately choose to share your current location for a ride, from the ride request until completion, cancellation, or expiry. The assigned driver can see this point. You can stop sharing at any time. Sharing when you switch apps or lock your phone requires separate phone permission. A force-close or phone restriction can stop sharing. We keep only the latest rider point, with no movement history or offline queue. Ending or stopping sharing removes that point.

An approved driver can share a current location while Active or serving an assigned ride. Sharing when the app is not open requires explicit consent and separate phone permission. Sharing stops when the driver pauses or ends the shift, signs out, loses approved access, deletes the account, or uses another device for the active shift.

We keep the driver's current point, not a history of exact movement. Authorized dispatch staff can use the current point. After assignment, only the assigned rider can receive that driver's point and pickup-time estimate. An old point is not shown as a current location.

Phone contact

Version 1.1 and later require a driver phone number and contact consent before the driver becomes Active. The assigned rider can call or text this number during the ride. A rider phone number is optional. We show it to the assigned driver only after a separate choice for that ride. In-app access ends when the ride ends, the assignment or number changes, or the rider stops sharing.

Calls and texts use real numbers through your phone and message apps. Before either app opens, Boober explains that the other person can see and save your number, even when in-app sharing is off. Stopping sharing cannot remove a saved number. Carrier charges can apply. Boober does not read your address book or message content.

Notices and driver payouts

You can change notification permission in your phone settings. A push token connects a permitted app installation to ride or active-shift notices. Notification sending is not yet active on the effective date of this notice. Driver payout requests in the app are also not yet active. Stripe account setup can still collect the identity and bank information that you choose to supply.

Sharing

We share data with the rider, assigned driver, and authorized operator staff as needed for a ride, with the providers needed to run the platform, and with authorities when law requires it. Providers include Supabase for accounts and platform data; Apple and Google for optional sign-in; Stripe for payments and driver account setup; Expo Push Service, Firebase Cloud Messaging, and Apple Push Notification service for notices; Resend for service email; Google Maps Platform for maps and routes; Sentry for service monitoring; Render for hosting; and Cloudflare for website delivery and usage measurements. Public driver information does not include private contact data or exact live location.

Control, retention, and deletion

You can manage a saved card, change phone permissions, and sign out. See account deletion instructions to request permanent account deletion or get help if the app cannot complete the request. We must confirm your identity. A received request is not proof of completed deletion. The new secure deletion request service is not yet available on the effective date of this notice.

Required ride or payment settlement can delay cleanup. Deletion does not forfeit driver earnings or automatically request a payout. After completed cleanup, we remove unnecessary profile data, deny old account access, and remove the payment-provider customer and saved card methods when that step applies.

We retain records needed for ride history, payments, refunds, accounting, security, support, and required cases. Some required records can contain personal data. Access is restricted. A name change alone does not make a record anonymous. Current location is kept separately from ride history. Provider data and backups have their own removal limits. Contact us for information about data that remains in a specific case.

If you have a private deletion-status receipt, keep it secure. It is valid for 30 days from issuance. After expiry, a pending request needs a new receipt. Contact us if you cannot renew it. Receipt expiry does not complete or cancel the request.

Beta and launch updates

The version 1.2 launch offer gives one $10 ride credit to each of the first 100 eligible Boober rider accounts that claim it while the offer is active. A rider must save a valid payment method before the credit can be used. The credit is not cash, is not transferable, and does not reduce driver earnings. We keep credit records to prevent a second claim and to apply, release, or refund credit correctly.

Email and text choices are separate. The public form stores your supplied first and last name and the channels that you request. A request is pending, not verified consent. Updates require confirmation that you control the selected email address or phone number. A public request does not cancel an earlier opt-out. Consent is not a condition of a ride. Marketing email will include an unsubscribe method. Marketing text will accept STOP and other reasonable opt-out requests. We will put these controls in service before we send a marketing campaign.

The public signup form uses a one-way hash of the network address for a short rate limit. It does not store the raw network address in the beta list.

When you use a tagged campaign link, we may store its short source, medium, campaign, and content labels with your consent record. We do not use this to store your page-browsing history or a raw referring URL.

Contact

For a privacy question, contact [email protected].