1. Scope and contact
This Privacy Policy describes how information is handled by Buffalo Cab Rider, Buffalo Cab Driver, Buffalo Cab Fleet Admin, Buffalo Cab Fleet Driver, Buffalo Cab Admin, the websites, partner portal, and shared backend. Buffalo Cab is an independent transportation service. Contact admin@buffalocab.com or 716 559 4690 about privacy, access, correction, or deletion.
2. Information we collect
- Contact and account information: name, email, phone number, saved preferences and addresses you choose to provide, verification events, and account status.
- Trip information: pickup and destination addresses, scheduled times, passenger counts, route estimates, booking references, ride status, driver assignment, cancellations, no-shows, refunds, optional tips, and messages sent in trip chat.
- Driver information: approved sign-in email, name, phone, vehicle details, color and plate, passenger capacity, online/offline status, shift/session expiry, request responses, scheduled claims, releases, transfers, and operational history.
- Partner information: business name, approved sign-in email and phone, registered pickup address and coordinates, request history, passenger details provided with their agreement, and the recorded confirmation of that agreement.
- Fleet information: fleet company and dispatcher contact details, driver and vehicle rosters, owner-operator links, dispatch responses and assignments, agreed wholesale and driver-pay rate snapshots, settlement entries, statements, invoices, and payment-reconciliation notes. A fleet company receives the records relevant to its own work; direct-driver earnings, fleet wholesale, and fleet-driver pay are separate.
- Reviews: star ratings, review text, reviewer display name, driver name, completed-booking association, and moderation records. Published service and driver reviews, their names and ratings are publicly visible. Removal hides a review from public display and retains the original content and moderation audit. Account deletion does not automatically remove a published review; contact support about review removal or retained data.
- Payment records: fare, payment method category, provider transaction identifiers and status, split-share amounts, cash receipt confirmations, refunds, and tips. Card details are entered into Stripe’s checkout, not stored as full card numbers in the Buffalo Cab application database.
- Optional passkey security: public-key credentials, opaque account handles, authenticator labels, signature counters, sign-in/security events and hashed recovery codes. Your device may verify you using biometrics, a PIN or a security key. Buffalo Cab does not receive or store facial images, fingerprints, biometric templates or passkey private keys. You can revoke passkeys and sessions in Account → Security. Your device or passkey provider may separately synchronize credentials under its own settings.
- Technical information: sessions, device notification tokens, app/project identifiers, notification handoff and error records, request timestamps, IP addresses and security logs. Phone and hosting providers may process additional technical information necessary to deliver their services.
3. Location, maps, and phone permissions
Passenger location is optional and helps fill a pickup address. Passengers are not tracked in the background. Buffalo Cab Driver and Buffalo Cab Fleet Driver collect precise location in the background, including when the app is not in use, for nearby ride matching while online and pickup progress, arrival estimates and measured trip mileage during assignments. Approved drivers must allow precise foreground and background location to use driving features. The Fleet Admin and Buffalo Cab Admin apps do not request their users’ device location; authorized dispatchers can view relevant trip and driver location records. While a driver is online, the service keeps their latest operational location to match nearby requests and confirm availability. During current assignments, GPS supports rider tracking, arrival estimates and movement checks. Background permission allows updates while the phone is locked, subject to operating-system limits.
Riders see only their assigned driver's current trip location, from 30 minutes before pickup through the active trip. Rider access ends when the trip ends, is canceled or reassigned. Operational GPS may continue while the driver stays online; it is never exposed to other riders. Going offline clears the availability location but does not stop a current assigned trip. Revoking phone location permission pauses new dispatch, without canceling an existing assignment. Stale availability fixes are removed after ten minutes; no continuous off-duty location history is collected.
During assigned trips, driver coordinates are also used to calculate road routes and arrival estimates. Mapping/routing providers can receive coordinates or the map area needed to deliver that service. Dispatch records aggregate GPS-observed approach/trip mileage, recorded start/completion times, and location-check outcomes or written completion exceptions. These are operational records; they do not form a saved movement trail. Live driver positions and route caches are removed or hidden when a trip ends, access is revoked, or the data becomes stale. Historical measurements may be incomplete when GPS or network service is interrupted.
4. How information is used and shared
We use information to verify access; estimate, arrange, dispatch, and manage rides; communicate about trips; take and reconcile payments; maintain safety and fraud protections; respond to support; and maintain operational records.
Assigned drivers receive the passenger and trip information needed for pickup and service, including contact details while authorized. Drivers considering an unassigned request see route, fare, timing, and passenger count, but not passenger contact details. Scheduled passengers can see the assigned driver’s name, vehicle, color, and plate. Trip participants can see applicable chat messages; departure chat may include other booked passengers. Do not post sensitive information in a shared trip chat.
Approved partner staff can view the requests made through their business account, including trip status, passenger details they submitted, and a trip-management link. The passenger can receive that link directly from the business. Buffalo Cab administrators can access operational records and relevant communications for dispatch and support.
We use Stripe for payments, Render for hosting, configured email providers such as Resend or SMTP services for transactional messages, and Expo/Apple/Google for mobile build, update, and notification services. These providers receive information needed for their functions. We may disclose records to comply with applicable legal obligations or respond to valid requests and to address fraud, security incidents, or safety concerns. This application does not implement advertising-data sales or cross-app advertising tracking.
The Rider Android map uses Google Maps SDK when configured. Google documents collection of device and SDK metadata, IP addresses, a pseudonymous Maps SDK identifier, crash metrics, and map interaction events. Maps and route services may process pickup and destination coordinates. Expo updates send app/runtime/channel and installation identifiers and request metadata to check for compatible app updates. Optional notifications use Expo and Firebase Cloud Messaging (and Apple on iOS) to route messages to installation tokens; Firebase may process device and delivery information. No advertising SDK or ad-personalization feature is configured in this application.
5. Local storage and security
The mobile apps use protected device storage for account sessions and saved trip-access information. Websites use browser storage for saved trip links and preferences; the partner portal uses an HttpOnly session cookie with a limited lifetime and protections against cross-site requests. Server-side session tokens and verification codes are stored as hashes. Admin access is separate from passenger, driver, and partner access.
Trip links are access credentials: anyone you send one to may be able to view or manage the corresponding trip. Share them only with the intended passenger or authorized staff. Sign out on shared devices. No internet service can guarantee absolute security; report suspected account or link misuse promptly.
6. Retention and deletion
Deleting a passenger account clears its identifying profile fields and preferences, signs out its sessions, and replaces its saved booking-management capabilities. It does not automatically erase all contact information in completed ride, payment, support, or operational records. Those records may need to be retained for transaction reconciliation, disputes, safety, fraud prevention, and applicable recordkeeping obligations. Driver and partner records may be disabled or archived while their operational histories remain.
Retention periods vary by record type, purpose, and applicable requirements. Contact support to ask which records are retained, why they are retained, or to request deletion.
Ride-update text messages
Buffalo Cab sends transactional texts only when you actively select the optional ride-update consent checkbox during booking. Messages concern your requested ride, including booking confirmation, driver assignment and arrival, trip status, completion, and cancellation. Message frequency varies with ride activity. Message and data rates may apply. You can leave consent unchecked and provide an email address instead. This consent does not subscribe you to marketing or SMS sign-in codes.
We record your phone number, consent time, message content, and delivery outcomes to provide ride updates and operational support. Twilio, our messaging provider, and telecommunications providers process information needed to deliver these messages. We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes. Operational processing by service providers is limited to providing and supporting the service.
Reply STOP to stop texts. Reply HELP for help, or contact admin@buffalocab.com or 716 559 4690. Messages may contain private ride-management links; do not forward them publicly. Delivery is not guaranteed. Keep your ride link or contact support if an update is missing. See our SMS Terms.
7. Your choices
Passengers can edit supported profile details and saved preferences in Account. Email changes and account deletion require verification. Resolve open trips and checkout holds before using the in-app deletion flow. You can also request account or data deletion through these instructions; identity verification may be needed before information is disclosed or removed. Direct drivers, pending driver applicants, fleet drivers, fleet dispatchers, Buffalo Cab staff, and partner users can open Request account or data deletion in the relevant app or contact support for correction, access, or deletion requests. Account deactivation and archival do not automatically delete associated personal data. Contact support to request deletion or information about retained records.
You can change optional email preferences where offered, revoke location and notification permissions through phone settings, and clear locally saved trip information. Essential verification, payment, and trip messages may still be needed to provide the service. Going offline stops new private requests; it does not cancel a scheduled assignment or existing trip. Depending on applicable law and your circumstances, additional rights may apply; contact support to make a request or raise a concern.
8. Children and policy updates
The service does not provide a child-directed account experience. A person requesting a ride for someone else must have authority to share that passenger’s details and arrange the trip. Contact support before arranging travel for an unaccompanied minor or if you believe a child’s information was submitted improperly.
We may update this policy as our service, providers, and data practices change. Material changes are communicated as appropriate. The date above identifies the latest version.