A clearer road
to the right answer.

LibreRide connects riders with drivers through booking, trip, and support tools. The Rider app handles ride requests; the Driver app handles driver duty and trip activity. This website explains access and offers support.

LibreRide is preparing an invited Miami sandbox beta. This is not a general public launch. Service areas, driver availability, vehicle options, and app access depend on your invitation and the options actually shown in your account.

Use the app information on the homepage, or ask about beta access. Tell us whether you use iPhone, Android, or a browser. Do not assume a public app-store listing or production payment access is available.

Check the phone or email entered and the device connection. Use the most recent code and the retry option shown in the app. Never share a verification code or password. If the problem continues, contact support with your device and the time of the attempt; leave the code out.

Review the pickup, destination, ride type, displayed fare, and any conditions before confirming in the Rider app. A request is not a guarantee of driver acceptance. Follow the status shown in the app.

Check the driver and vehicle information shown before entering. If the person or vehicle does not match, do not board. Move somewhere safe and contact support.

Use the options available for your current trip stage. Review any route change and the displayed fare before accepting. A shorter route does not automatically reduce the booked fare. During a ride, an early-end request needs a safe stopping point and driver confirmation; the request alone does not end the trip.

Use the cancellation option displayed for your trip. The current flow has no separate cancellation or no-show fee. A cancellation does not guarantee that a bank hold disappears immediately. See payments and refunds.

Use in-app Help for the trip, or contact rider support with the date, trip reference, and a description. Do not post private contact information or try to track down a driver yourself. Recovery cannot be guaranteed.

No. A payment authorization can reserve the displayed amount before a ride is released. A completed charge is a different payment state. Canceling does not guarantee immediate hold release; provider and bank timing varies.

Use in-app Help or rider support. Include the trip date, receipt or trip reference, disputed amount, and what happened. Report duplicate, incorrect, unrecognized, or charged-but-unprovided rides for review. Do not send full card details. Read the refund policy for the review process.

An approved refund goes to the original payment method. Approval, provider processing, and the bank posting the refund are separate stages. Timing varies; no fixed arrival date is promised here. Follow up with the original support reference.

Review the confirmed trip and payment details in the app. If an email receipt is available, delivery uses the verified receipt address and can take additional processing time. Contact support if a receipt is missing or incorrect.

Tips are optional and require your amount confirmation. Review any charge or calculation method before authorizing it. The current flow has no separate cancellation or no-show fee. This website does not introduce a new fee table or subscription. See the payment information.

Contact your bank promptly and report the concern to support with the transaction reference and date. Never send full card numbers, security codes, or bank credentials. Support review does not remove your payment-provider or legal rights.

Contact driver support about invited access and the approved onboarding process. An invitation or installation is not approval to carry riders. Driver, vehicle, insurance, and operational requirements must be confirmed before live service.

Enabled describes a preference; it does not prove the device is recording. Check the recording status while safely parked. Online duty, device permission, local samples, and confirmed uploads are separate. If it says recording stopped or samples stay at zero during an authorized test, report the status, app version, device, and time to driver support. Repeating permission changes alone may not resolve a collection error.

A dash means the measurement is unavailable. Approval, validation, enough measured coverage, and supported sensors may be required. Completed trips or estimated miles do not by themselves create safety scores. Do not interpret a blank category as a perfect score or a safety violation.

Use your applicable driver agreement and payment statement, and ask driver support for verified insurance disclosures. Test balances and simulated payouts are not live earnings. This page does not set commissions, subscriptions, payout dates, or insurance coverage. See the driver information.

Contact driver support with the account email, the message shown, and relevant dates. Ask for a review and provide factual information. Do not send identity documents through the public contact form. Reinstatement and completion times are not guaranteed.

Call 911 for immediate danger or urgent medical help. Move to a safe place when possible. LibreRide support, this form, and possible-impact detection are not emergency dispatch services. Report the trip concern to support once safe.

Use in-app Help, safety support, or [email protected]. State the nature of the concern and include the trip, time, and observations. Do not confront someone or collect evidence while driving. See the zero-tolerance policy.

Tell support the practical assistance needed or what happened. Use safety support for a denial or discrimination, or email if the form is inaccessible. Do not share unnecessary medical records. See the accessibility and service-animal policy.

No. A signal can be wrong, missed, or unavailable. It needs review and cannot replace emergency services. Optional coaching and possible-impact detection have separate notices and approval requirements. Read the safety monitoring information.

Visit Policies & disclosures. Find website notices and platform policies in one place. Read the full texts on the website; applicable app terms and required consent actions are presented separately in the apps.

Follow the account deletion page or contact privacy support. Verification may be needed. Florida requires ride records for at least one year after the ride and driver records for at least one year after the driver relationship ends. Other obligations may require longer retention. Deletion is not a promise of immediate removal of every record. Read the platform privacy notice for retention details.

For a trip issue, in-app Help keeps the request connected to the trip. Otherwise use the contact center or email [email protected]. Choose rider, driver, beta, safety, or account/data support and include a useful reference. Keep the submission reference if one is provided.

Include the account email, trip or receipt reference, date, device/app version if relevant, what happened, and the help requested. Leave out passwords, verification codes, full payment details, and identity documents. Reply with the original reference for follow-up. The contact center is an inbox-backed service; no live-chat availability or fixed response time is promised.