Terms & Conditions

The terms for requesting a ride

These terms describe the transportation request, booking, payment, cancellation, and communication practices currently shown in Singh's Black Car SUV's booking experience. Please review them before you submit a booking or waitlist request.

Effective / last updated: Owner confirmation required — no effective date has been established yet.

1. Service and booking requests

Singh's Black Car SUV provides private black-car and SUV transportation. A request submitted through /book records the trip details for dispatch review. The app currently distinguishes a scheduled booking from later driver assignment or dispatch confirmation; submitting a request does not by itself establish a confirmed driver assignment.

2. Booking details and edit access

The booking form asks for your name, email, phone number, pickup location, drop-off location, pickup time, vehicle class, stops, and wait estimates. After a booking is recorded, the app emails an edit link that uses an opaque token to return to the booking page. Keep that link private and use it to edit or cancel the booking.

3. Fares and payment choices

The booking flow displays a fixed fare of $130 for a car and $145 for an SUV or van. The app says that route details, stops, and wait time do not change that fare. Standard booking copy says there is no upfront payment and that the ride fare is paid to the driver on pickup day. The booking edit flow also contains optional hosted Stripe Checkout paths for a deposit or full prepayment when enabled; see the owner-confirmation list below for the policy wording and payment details that still need approval.

4. Cancellation timing and fee

The current booking flow allows free cancellation until one hour before pickup. A cancellation inside the one-hour window creates a $75 cancellation fee flow. The app may send that fee through hosted Stripe Checkout; a pending fee remains visible on the booking until the payment flow is completed.

5. Dispatch, driver assignment, and trip status

Dispatch reviews the request and may contact you by call or text to confirm pickup. If you choose the optional SMS consent in the booking flow, texts may include ride confirmations and status/ETA updates. Message frequency varies by ride, message and data rates may apply, and you can reply HELP for help or STOP to opt out. Consent is not required to book. When a driver is assigned and the trip is dispatched, the app can show a shareable live-status link with driver, vehicle, ETA, and trip-status updates. The status page is accessed through its link and does not require a login.

6. Customer responsibilities

Provide accurate contact information and accurate pickup, drop-off, time, vehicle, stop, and wait details. Keep emailed edit or live-status links private. If a trip detail changes, use the edit flow as soon as possible so dispatch has the current information.

7. Operational communications

The app uses the contact details you submit for booking, edit or cancellation links, dispatch coordination, and trip-status communication. The waitlist flow collects an email and pickup/drop-off details so the company can contact you when a driver is available. If you choose the optional SMS consent in the booking flow, texts may include ride confirmations and status/ETA updates. Message frequency varies by ride, message and data rates may apply, and you can reply HELP for help or STOP to opt out. Consent is not required to book.

8. Privacy

The information practices observed in the app are described in the Privacy Policy. Read the Privacy Policy before submitting a request.

9. Questions

For booking or policy questions, contact Singh's Black Car SUV at singhs-black-car-suv@polsia.app.

Placeholders to confirm

The following material policy details are not established by the current app and are intentionally not presented as final terms:

  • The legal business name and owner/operator contact identity.
  • The effective and last-updated date.
  • Governing law and jurisdiction.
  • The exact service area, no-show rules, refund rules, and any liability language.
  • Whether a booking becomes final only after operator or driver assignment.
  • Whether deposits and full prepayment are customer-facing, plus the approved payment and dispute wording for hosted Stripe Checkout.
  • The owner still needs to configure the live SMS provider, sender identity, A2P registration, and delivery operations; no sender number or delivery schedule is promised here.
  • The owner-approved privacy contact and process for policy questions or requests.