Turo is a car-sharing marketplace rather than a conventional rental company that owns a standardized fleet. Founder Shelby Clark developed the idea in 2009 and the service began under the RelayRides name; after early market testing, RelayRides announced a nationwide U.S. launch in 2012 and adopted the Turo name in 2015. The platform connects hosts who make eligible vehicles available with guests who book those vehicles for a defined trip. That marketplace structure is central to understanding the customer experience. The specific car, pickup method, mileage rules, delivery arrangements and host communication can differ from booking to booking, while Turo provides the marketplace, payment flow, trust-and-safety systems, trip rules and region-specific protection-plan framework.
Turo Inc. operates the U.S. service, and the official domain is turo.com. IAC has disclosed a meaningful minority investment in Turo, but that should not be rewritten as if IAC were Turo's parent company or sole owner. Turo's commercial terms are highly location- and trip-dependent. Guest fees, host earnings, protection-plan costs, airport delivery rules, young-driver charges, cancellation rules and eligible vehicles can change and can differ among the United States, Canada, the United Kingdom, France and Australia. A professional profile should therefore avoid hard-coding fee percentages or protection limits that may become stale.
Protection plans also are not a substitute for reading the current trip-specific terms: responsibilities after damage, roadside assistance, claims handling and third-party insurance relationships depend on the country, role and circumstances. Guests should document the vehicle condition at pickup and return using the required photo process, while hosts remain responsible for listing an eligible, safe and properly maintained vehicle. Turo's current Help Center is the correct starting point for account, booking, payment, host and claims questions. Its Contact Turo guidance routes users first through the website's conversational support flow and then, when appropriate, to customer service by chat, email or telephone.
The company publishes different phone numbers by market, including a U.S. Turo also publishes specific anti-fraud guidance: it says it will not ask users for passwords, login information or verification codes, and it provides dedicated channels for suspicious account activity and phishing reports. Those security contacts should be labeled for their specific purpose rather than shown as general booking support. The company's San Francisco contact address appears in its terms, but current office arrangements can change and are less useful to most customers than the official Help Center.
The stable story is Turo's evolution from RelayRides into a multi-market vehicle-sharing platform, its marketplace relationship between hosts and guests, and the need to use the live regional terms for protection, fees, eligibility and support. That framing is more accurate than treating Turo as a traditional rental fleet or relying on old RelayRides-era policies.
