Ruby Wilson’s Urban Ride Share Service
pilot terms & privacy notice
This is a registration pilot. No rides are being dispatched, no drivers are authorized to work by this signup, and no subscription or payout fee is being charged. City-specific operating arrangements and final ride terms require review before launch.
1. What you are registering for
Ruby Wilson’s Urban Ride Share Service is a proposed service connecting passengers with drivers. Registration creates a separate Urban profile for Louisville, Los Angeles, Dubai, Tokyo, London or Atlanta. It is not an offer of employment, a guarantee of income, a transport licence or confirmation that a ride is available.
Registration is for adults. Driver minimum ages and other requirements vary by city. Operators, drivers and vehicles must satisfy applicable licensing, insurance, screening and local operating requirements before any activation. Describing the service as a broker does not remove mandatory duties.
2. Proposed commercial terms for launch
- Driver subscription: USD $5 for the first paid month, then USD $20 per month until cancellation. No minimum term or exclusivity is proposed. The paid period does not start during this pilot.
- Passenger signup is free. Each completed ride payment includes a $1.00 passenger processing fee, displayed separately from the driver fare before checkout. No passenger subscription is configured by these pilot terms.
- Proposed driver gross fare: USD $5 per ride plus $1.50 per mile, with zero CLACK ride commission. These figures are planning terms, subject to local currency, tariff, worker-protection and payment requirements. They are not a bookable quote or guaranteed take-home pay.
- Drivers remain responsible for their applicable vehicle expenses and taxes. Refunds, disputes and legally required adjustments may affect settled earnings; final payment terms must explain them before launch.
- Proposed cash-out: one successful withdrawal per driver per local calendar day, with a USD $1.99 processing fee. Only eligible, settled funds can be withdrawn. A failed or unavailable payout will not incur this proposed fee. Bank arrival times depend on the provider and banking system.
- No funds are held in an Urban wallet during this pilot. No real cash-out or automatic bank transfer is enabled.
3. Limited release; protected rights
To the extent applicable law permits, a participant releases ClackMusic.com and its operating entity from civil claims arising solely from the independent conduct of another participant or third party, rather than conduct for which CLACK is legally responsible. Participation involves ordinary travel risks, which may include traffic, delays and third-party conduct.
This provision does not exclude or limit liability that cannot lawfully be excluded, including applicable liability for death or personal injury caused by negligence, fraud, intentional misconduct, gross negligence where protected by law, mandatory insurance duties, statutory consumer rights or other non-waivable obligations. It does not make CLACK immune from lawsuits or determine employment status. Enforceability has not been established for any test city. Final ride and driver agreements must be reviewed for the relevant jurisdiction before rides open.
4. Device verification and photos
Urban requires a platform passkey with user verification. A device may use Face ID, a fingerprint or its PIN/password. Web passkeys cannot guarantee which method the device uses. Biometric templates stay with the device; CLACK stores the public credential, not your face scan or fingerprint.
Both drivers and passengers must provide a recent profile photo. A photo is not proof of identity and is not automatically compared to a government ID. Photos remain private during this pilot. Additional verification and any necessary sharing with an assigned trip participant require a later, disclosed operational flow.
5. Data and privacy
We collect the information you enter: name, contact details, selected city, role, signature and acceptance time, public passkey credential, profile photo, and driver vehicle details if applicable. Email and phone ownership are not verified during this pilot. Do not submit government identification, licence scans, payment card details or bank details through the signup form.
We use these records to provide your requested Urban pilot profile, secure access, record consent and prepare eligibility review. Account records and photos use server-side storage on the site's hosting infrastructure. Photos are accessed only through the signed-in profile endpoint and are not placed in a public directory. The service does not promise that uploaded information has been verified or that future provider review has occurred.
Profiles are retained while the pilot account exists or until the operator ends the pilot and removes its records. You can view your profile, replace your photo and request immediate deletion using the signed-in account controls. Profiles without payment records may use immediate deletion. Payment-enabled accounts require support-assisted closure, preserving financial records where required; payment records are not removed by the instant profile deletion control.
Operational hosting may process data outside your country. Country-specific privacy notices, lawful transfer arrangements, controller contact details and any required provider agreements must be finalized before city activation. Do not register if you do not want your entered information processed on this basis.
6. Maps and trip location
The optional street map loads only after you enable it. It requests the visible map tiles from OpenStreetMap, which receives your IP, site origin and the viewed map area. Read the OpenStreetMap privacy policy. No map account is created. Tiles are best-effort and are not navigation guidance.
GPS preview begins only after your browser permits access and displays your location on your device. If you enable street tiles, the viewed area reflects that location. The preview does not upload coordinates to CLACK. It stops when you press Stop, hide or leave the tab.
For an actual accepted trip, the assigned driver enables GPS sharing and keeps Urban open. The latest fix, its timestamp and accuracy are stored by CLACK and visible only to that trip’s authenticated participants. Passenger updates refresh every five seconds from acceptance through pickup and the trip. A fix over 30 seconds old is stale. The map displays an estimated accuracy circle, and locations with accuracy worse than 100 metres are labelled approximate. You may pan independently and choose Recenter & follow to resume following GPS. Coordinates are not a public driver feed. Only the latest fix is stored, not a location history. Ended or cancelled trips do not expose a location; a complaint cancels active trips involving the reported account and clears their location. No rides are dispatched in this prelaunch pilot.
Phone lock, backgrounding, poor reception and permissions can stop web location updates. Continuous tracking cannot be guaranteed by a phone browser. Do not rely on this site for emergency response or turn-by-turn navigation.
7. Electronic acceptance
Your typed full name, explicit checkboxes, terms version and server timestamp record acceptance of these pilot terms and processing choices. Creating a profile does not authorize a subscription charge, create a booking or approve a driver. No licence, insurance, payment approval or blanket liability protection should be inferred from registration.
8. Required etiquette, ratings and complaints
Drivers and passengers must follow the Urban etiquette protocols whenever using Urban. Drivers must maintain a clean, fresh-smelling, roadworthy vehicle, remove litter, ventilate and avoid overpowering fragrances. Both parties must use seat belts, respect boundaries, avoid harassment, discrimination and impairment, obey safety rules and leave the vehicle clean. Drivers must not handle their phones while driving. Pickups and drop-offs must be safe and permitted. Passengers must verify the assigned car, plate and driver before entering. Neither party may pressure the other into private off-platform rides or payments, or photograph, record or share the other person’s details without appropriate permission. Trip communications and payments must stay within Urban when operational.
Each participant may submit one rating of one to five stars after a completed trip. Ratings must reflect the actual trip and are not complaints. Your account shows the average and count of ratings you receive; no invented ratings are displayed.
An authenticated trip participant may report the other participant for safety, cleanliness, conduct or other issues. Any such complaint immediately suspends the reported account and cancels its active trips pending review. A suspension is precautionary, not a finding of guilt. Review may lead to reinstatement or termination, including termination for verified serious or repeated violations. False reports, retaliation and misuse are prohibited. Suspended users can sign in to view their profile and report issues from their own trips.
Complaints record the trip, parties, category, details, review status and submission time; ratings record the trip, parties, stars and time. These private records support safety review and feedback. No automated system independently verifies a complaint. Human review and operational support must be staffed before city launch. For profiles without payment records, pilot deletion also removes associated trip, feedback and location records. Payment-enabled accounts require support-assisted closure; an operational retention policy must be finalized before rides open.
New signup records acceptance of these protocols. Existing profiles must explicitly accept this version before trip features; earlier signatures are not treated as acceptance of changed terms. Read version 3, version 2 or version 1 of the pilot terms.
9. Payment processing and driver payout details
When payments are activated for an approved US city, the assigned passenger reviews the final completed-trip fare and pays through Stripe Checkout from CLACK. Eligible debit cards and bank accounts appear according to processor availability and verification. Drivers submit payout bank or eligible debit-card details directly through Stripe’s hosted onboarding form, complete its identity requirements and accept its applicable agreements. CLACK stores processor identifiers and payment status, not raw card or bank account numbers.
Verified processor notifications confirm a successful payment. A bank payment can remain processing or fail after checkout. A confirmation screen is not proof of settled funds. The driver’s processor balance distinguishes pending settlement from available funds; payout eligibility, bank processing times, refunds, disputes and required adjustments may delay or reduce availability. There is no guarantee of immediate withdrawal.
The proposed CLACK ride commission is zero. CLACK absorbs payment processing fees rather than deducting them from the quoted driver gross fare. Each successful driver cash-out includes a $1.99 fee, deducted in addition to the amount delivered to the driver. No more than one cash-out per local calendar day is allowed. Failed or cancelled payouts do not retain this fee; any fee collected for such a payout must be refunded. Payouts remain disabled until eligibility and the exact fee configuration are verified. Passenger-fee profits and driver cash-out-fee profits are tracked separately and reserved for 60 days from collection after processor costs and applicable refunds or disputes. Unreconciled costs and disputes prevent release. This accounting hold applies to CLACK fee profits, not driver ride earnings. Bank segregation of reserves must be configured before live payment activation; a ledger alone is not a separate bank account or escrow. Rides and payments remain inactive during this registration pilot. Required payment records are retained through support-assisted closure rather than immediate deletion.