Peer-to-peer car sharing insurance: six state statutes, the host and guest gaps, and what Turo files

In Arizona, Florida, Maryland, Oregon, Utah and Virginia, your own auto insurer is allowed to exclude the whole trip while a guest has the car. Those statutes make the platform ensure that the host and the guest are insured during the “car-sharing period,” and in five of the six the insurance that meets the requirement is primary. Turo’s own filing says hosts’ personal coverage “is not generally expected to cover damage from guests.”

The gaps sit at the edges of a trip, not in the middle. Arizona keeps the platform’s third-party liability running “notwithstanding the car sharing termination time,” but a late return or a handoff nobody recorded can leave a damage claim outside the sharing period, and most of these laws do not require anyone to insure the host’s own car. So the useful question is not whether your policy covers Turo but which policy answers at each moment of the trip, and what nobody is required to cover.

One limit up front. Other states have car-sharing laws too, and Washington shows that such a law can be repealed as well as passed. Only the six states whose statute text was read on the official legislature site appear in the tables here. If your state is not among them, it may still have a law; read your state’s statute or ask its insurance department before relying on any row below.

Estimates and published averages, not a quote. Not insurance advice. State rules and insurer rules vary. Confirm requirements with your state insurance regulator or a licensed agent in your state.

The car-sharing period: the clock every rule runs on

Every peer-to-peer statute read for this page hangs its insurance duties on a defined window of time. Florida calls it the “car-sharing period,” Virginia the “vehicle sharing period,” and the wording is close to identical across the newer laws because most of them follow a model act. Florida section 627.7483(1) defines the period as the time that “commences either at the car-sharing delivery period or, if there is no car-sharing delivery period, at the car-sharing start time and that ends at the car-sharing termination time.”

Each of those three markers is defined separately, and each one matters in a claim. The delivery period, where the host or someone else drives the car to the guest, is inside the sharing period in Florida, Maryland, Utah and Virginia. The start time, in Maryland’s words, is “the time when a shared motor vehicle becomes subject to the control of the shared vehicle driver at or after the time the reservation of a shared motor vehicle is scheduled to begin.” A guest who collects the car early, before the reservation begins, is therefore at the edge of the definition rather than safely inside it.

The termination time is where most disputes start. Florida defines it as the earliest of three events: the agreed rental time expires and the car is back at the agreed location; the car is returned to an alternative location the host and guest agreed through the platform; or the host takes possession and control of the car. Maryland’s version requires the car to be returned to the location the host designated and one of the ending events to occur. A guest who keeps the car past the booking without an extension, or leaves it somewhere that was never agreed in the app, can fall outside the window the platform’s insurance is built around.

The definition also decides which vehicles and uses count. Florida excludes rental car companies, for-hire vehicles, ridesharing, carpools and car-sharing services from the definition, and Virginia excludes daily rental vehicles. A host who rents a car out informally, outside any platform, is not in a car-sharing period at all. None of the statutes below apply to that loan; the ordinary borrowing rules in the guide to whether insurance follows the car or the driver do.

Six state statutes on one table

The table below reads three questions out of each statute: who may supply the insurance the law requires during the sharing period, whether that coverage is primary, and whether the host’s personal auto policy may exclude the trip. Every row comes from statute text displayed on the state legislature’s own site. Where the site prints the enacting session law, it is given; Arizona’s and Maryland’s sites did not print a history line next to the sections read.

The last column is the same in all six states: the law lets the host’s own insurer step out of the trip. That permission is the reason the platform must step in. The first four columns describe the substitute coverage, and that substitute is where the states differ.

Five of the six follow the same structure. The platform “shall ensure” that during each sharing period the host and guest are insured; the requirement can be met by the host’s policy, the guest’s policy, the platform’s policy or a mix; and whichever policy meets it is primary. Oregon is older and built differently, as the next section explains.

Where the six laws actually differ

Four of the laws read almost as one text. Florida, Utah, Virginia and Arizona share the same three-way choice of who may insure, the same “primary during each car-sharing period” phrase and the same exclusion list, the marks of a common model act. The differences are in the details, and the details are what decide a claim.

Maryland narrows who can insure and adds a test. Its subsection (d)(2) lets the requirement be met by the host, the platform, or both; the guest’s own policy is not on the list. Its subsection (d)(1) requires the policy to recognize that the car is shared “and” to provide the minimum security. Florida, Utah, Arizona and Virginia use “or”: the policy either recognizes the sharing or does not exclude the guest. Maryland also writes in the replacement-vehicle rule: the platform’s policy is primary for the guest, but may be secondary to the guest’s own policy when the guest is using the shared car as a replacement vehicle, as the Transportation Article defines that term. If the guest’s own insurance has lapsed, the platform’s coverage is primary again.

Florida asks for more coverage types. Its subsection (2)(a) requires personal injury protection and uninsured and underinsured motorist coverage on top of liability, which matches what Florida requires of any car. It also adds a travel rule, shared with Utah: if a claim happens during the sharing period in another state with higher minimum limits, the coverage satisfies the difference up to the policy limits. Arizona’s required coverage is liability only. Virginia adds uninsured motorist coverage to liability.

Arizona extends third-party liability past the clock. Its section 28-9602(C) says that “notwithstanding the car sharing termination time,” the platform’s assumption of liability applies to bodily injury and property damage to third parties as required by the state minimum. Utah has a similar sentence in 13-48a-301. That matters most in a late return, covered below.

Oregon’s law predates the model. It was enacted in 2011 for “personal vehicle sharing programs,” and instead of letting the host or guest supply coverage, it requires the program to provide its own policy for each car. That policy must carry liability at least three times the limits in ORS 806.070 and no lower than the limits on the host’s own policy as the host reported them, plus personal injury protection, uninsured motorist, comprehensive and collision coverage. While the car is under the program’s control, the program “shall assume all liability of the vehicle owner and shall be considered the vehicle owner for all purposes.”

Virginia reaches the host’s car. Its section 46.2-1409(J) requires the platform to “either provide or offer for sale” collision and other than collision coverage for physical loss to the shared vehicle during the sharing period, in an amount not less than the car’s actual cash value. No other model-act state in the table writes that duty, which leads to the largest gap in the whole arrangement.

The host’s own car: the coverage most of these laws leave out

The model-act duties are about liability to other people. Florida’s subsection (2)(a) lists property damage liability, bodily injury liability, PIP and uninsured motorist coverage; Arizona’s and Utah’s required coverage is liability at the state minimum. Damage to the shared car itself is not in any of those lists. Florida’s statute says the platform “may” own policies that cover “damage or loss to the shared motor vehicle,” and Maryland’s and Utah’s versions have similar permissions, but permission is not a duty.

At the same time, the host’s own comprehensive and collision coverages are on every state’s exclusion list. Put those two facts together and a host in Arizona, Florida, Maryland or Utah can be left with no statutory source of payment for a crumpled fender caused by a guest. What fills the space in practice is whatever the platform’s own plan offers, and that is a contract, not a statute.

This is why the platform’s protection plan matters more to a host than the statute does. A host in a model-act state who declines the platform’s plan, or picks a plan with a high deductible, is choosing how much of their own car they will pay to repair; the state law did not make that choice for them. A host in Virginia at least has a statutory offer to accept or refuse. In Oregon the program’s policy covers the car.

A financed or leased car adds a third party with its own rules. The lien notices in Arizona and Florida exist because loan contracts commonly require collision and comprehensive coverage, and a trip with that coverage excluded can breach the contract even if nothing happens. The financed car guide covers what lenders typically require and the leased car guide the lease version.

What Turo says about its own coverage, in its own filing

Turo is an interested party: its filing describes working with legislators on these laws and opposing rental-industry bills, and it sells the protection plans that fill the gaps above. It reported about 350,000 active vehicle listings and 3.5 million active guests worldwide as of 2024-09-30. Its help pages are revised over time, so this page relies on a fixed, dated public statement of how its coverage works: the registration statement it filed with the US Securities and Exchange Commission. The figures below come from Amendment No. 12 to its Form S-1, filed 2024-11-14. They describe what the company said then; plan terms may have changed since, and the current terms on the platform govern any trip.

On hosts’ own insurance, the filing is direct: “Hosts’ personal existing insurance coverage is not generally expected to cover damage from guests booking their vehicles on our platform.” It adds that hosts “may fail to appreciate the differences between their personal insurance coverage and the protection plans afforded through our platform,” and that some hosts may list cars in violation of their lease, financing agreements or personal auto policies.

On liability, the filing says that in the United States “all trips provided by hosts are automatically insured by one of our third-party insurance providers,” and that all guests in the United States “automatically receive at least the state-required financial responsibility limits (sometimes called ‘state minimum insurance’)” whether or not they pick a protection plan. Where car-sharing statutes or permits require greater limits, the filing says those are provided.

On the host’s car, the filing describes something different from insurance: “varying levels of contractual reimbursement from us for physical damage and theft,” with the level depending on the plan the host chooses, and reimbursement for eligible repairs “up to the actual cash value of the car, or $200,000 (in the United States), whichever is the lesser amount, subject to the terms of each plan.” For guests, plan prices vary with “the level of their capped financial responsibility” for damage to the host’s car.

Two readings follow. First, the third-party liability Turo describes is insurance from third-party insurance providers, which lines up with what the statutes above require. Second, the physical damage protection is described as a contractual reimbursement from the company, which lines up with the gap in the previous section: the statutes mostly do not require it, so its terms are whatever the plan says. A host comparing plans is comparing contracts, and should read the plan’s exclusions, its deductible and its claim deadline the way they would read an insurance policy.

Listing to return: a host and guest coverage-gap timeline

The table walks one trip through seven moments. The middle column shows who is insured under the statutes in the table above; the right column shows where the gap sits. The statute citations are examples from the six states; where a state differs, it is named.

The edges of the timeline are where claims fail. Moments 3 and 6 depend on what the platform recorded, and moment 4 is where the host’s own car drops out of every statutory requirement in four of the six states. A host who reads only the middle row of a platform’s coverage page will see primary liability insurance and assume the whole trip is handled. The statutes say otherwise.

The late return, the disputed handoff and the records that settle them

A late return is the most common way a trip leaves the protected window. Florida section 627.7483(6)(a)3 requires every agreement to tell both parties “that the peer-to-peer car-sharing program’s insurance coverage on the shared vehicle owner and the shared vehicle driver is in effect only during each car-sharing period and that, for any use of the shared vehicle by the shared vehicle driver after the car-sharing termination time, the shared vehicle driver and the shared vehicle owner may not have insurance coverage.” Virginia section 46.2-1414 carries the same warning almost word for word.

Arizona and Utah soften that edge for people outside the car. Both keep the platform’s assumption of the host’s liability, at the state minimum, for injury and damage to third parties notwithstanding the termination time. That protects the person the late-returning guest hits and, through that, the host who would otherwise be sued as the owner. It does not protect the guest’s own injuries or the host’s car.

The statutes also take away one defense a platform might otherwise use. When the host was supposed to be insured but the platform cannot show who had the car, the platform loses. Florida subsection (3)(a)3 makes the insurers or platform that provided the required coverage assume primary liability when there is a dispute over who was in control and the platform “does not have available, did not retain, or fails to provide” the required records. Arizona 28-9602(G) and Virginia 46.2-1409(E) say the same for a platform that provides the insurance in whole or in part. Oregon 742.595(4) goes further: the program assumes liability for any claim where control is disputed, and the host’s insurer indemnifies the program only if it turns out the host was driving.

The records are specified too. Florida subsection (5) requires the platform to collect and verify the times used, pick-up and drop-off locations and the host’s revenues, keep them at least as long as the personal injury statute of limitations, and provide them on request to the host, the host’s insurer or the guest’s insurer. Virginia 46.2-1409(K) lets an insurer, an injured person or their lawyer ask in writing for the identity of any insurer that may have provided coverage and its limits, and whether the car was in a sharing period; the platform must answer within 30 days if it has the information. Oregon 742.590(3) requires electronic records of date, time, start and end locations and miles driven.

• Host: photograph the odometer, fuel level and all four sides at handoff and at return, and make sure the platform logs both times.
• Host: if a guest asks to extend or change the return place, do it inside the app so the termination time in the platform’s records moves with it.
• Guest: if you will be late, request the extension in the app before the booked end time, not by text message to the host.
• Either side after a crash: ask the platform in writing for the trip records and, in Virginia, the insurer identity and limits under 46.2-1409(K).

The guest side: does your own car insurance follow you into a shared car?

Guests ask the mirror-image question: if I book a car on a sharing app, does my own auto policy cover me? The statutes allow the guest’s policy to be part of the answer. In Arizona, Florida, Utah and Virginia, the guest’s own policy is one of the ways the sharing-period requirement may be met. But it only meets the requirement if it actually covers the trip, and many personal policies treat a car obtained through a sharing platform differently from a borrowed car or a counter rental.

The platform may also require the guest to bring coverage. Florida subsection (6)(a)7 requires the agreement to disclose “any conditions under which a shared vehicle driver must maintain a personal motor vehicle insurance policy with certain applicable coverage limits on a primary basis in order to book a shared vehicle,” and Utah’s disclosure list has the same item. If a platform lets you decline its plan on the strength of your own insurance, that decline can put your policy first in line.

Turo’s filing says guests in the United States automatically receive at least state minimum liability whether or not they buy a plan. State minimum liability is a floor, and for a serious crash it can run out quickly; the state minimum liability limits guide shows what those floors look like. Any judgment above the floor is the guest’s personal exposure unless the guest has their own liability coverage that applies.

Damage to the host’s car is the guest’s other exposure, and it is contractual. The platform agreement decides how much the guest owes for damage, and the plan the guest picks caps that amount at the plan’s level. A guest’s own collision coverage may or may not extend to a shared car; ask the insurer in writing before relying on it. Card benefits deserve the same caution. The rental car guide explains how personal policies and card benefits treat counter rentals, and the questions it lists carry over, with the extra step of asking whether the policy treats peer-to-peer sharing as a rental at all.

Guests who do not own a car have a narrower set of choices. A non-owner policy provides liability for a driver who borrows or rents, typically on an excess basis, and its terms decide whether it reaches a car booked through a sharing platform.

Can listing your car get your policy canceled?

Hosts worry less about one claim than about losing their personal policy for listing the car at all. The statutes answer that unevenly. Oregon is the clearest: ORS 742.595(7) says an owner’s policy “may not be canceled, voided, terminated, rescinded or nonrenewed solely on the basis that the vehicle has been made available for personal vehicle sharing” through a compliant program, and 742.600 bars reclassifying the car as a commercial, for-hire, permissive-use or livery vehicle solely because it is shared.

Maryland stops short of that. Its subsection (b)(2) says that, subject to the insurer’s exclusion right, the use of a car through a peer-to-peer program “does not constitute a commercial use solely on the basis that the motor vehicle is available for sharing or used through a peer-to-peer car sharing program.” That speaks to classification, not to cancellation.

Florida and Utah go the other way. Florida subsection (3)(c) says the exclusion paragraph “does not invalidate, limit, or restrict an insurer’s ability under existing law to underwrite, cancel, or nonrenew any insurance policy,” and Utah 13-48a-303 says nothing in the chapter limits an insurer’s ability to underwrite, cancel or fail to renew under other law. In those states, whether a host can stay with the same insurer is a question for the policy and the state’s general cancellation and nonrenewal rules, which the cancellation vs nonrenewal guide explains.

Disclosure is the practical safeguard. A policy application or renewal form that asks about use for hire or sharing should be answered truthfully, and a host who starts listing mid-term should ask the insurer in writing how it treats a car listed on a sharing platform. A misstatement found after a claim is a worse outcome than a premium change found before one.

Worked arithmetic: one crash under three sets of facts

The figures below are assumed inputs chosen to show how the rules interact, not a quote or a typical claim. A guest rear-ends another car at moderate speed. The other driver’s injury and vehicle claim is $40,000. The shared car needs $9,000 of repairs. The host’s personal policy carries liability limits of $100,000 per person, plus comprehensive and collision with a $500 deductible. The host chose a platform plan that, in this illustration, reimburses damage to the host’s car after a $750 host deductible.

The three rows show the pattern from the timeline in money. Inside the window, the injured stranger is protected by statute and the host’s car is protected only by the plan. Outside the window, both depend on records and on wording. In row A the host is out $750; in row B, if the plan and the guest both fail to pay, the host is out the full $9,000 and has the guest’s contract liability as the only route back. A $750 deductible against a possible $9,000 loss is the comparison a host should make when deciding whether to decline a plan.

The host’s own $500 collision deductible never enters the math, because in every row the host’s collision coverage is excluded. That is the single most counterintuitive point for a new host: a cheaper personal deductible does nothing for a car damaged during a trip.

The disclosures the statutes make the platform give you

Several of the statutes require the agreement to spell out the gaps in plain terms, which makes the agreement itself a checklist. Florida subsection (6)(a) and Virginia 46.2-1414 list what must be disclosed to both host and guest; Utah’s list in 13-48a-203 covers the same ground. Before listing or booking, find each item in the agreement and read what it says for your trip.

• Any right of the platform to seek indemnification from the host or guest for economic loss from a breach of the agreement (Fla. (6)(a)1; Va. 46.2-1414(1)).
• That a policy issued to the host or guest does not defend or pay a claim the platform itself brings (Fla. (6)(a)2; Va. 46.2-1414(2)).
• That the platform’s insurance applies only during the sharing period, and that after the termination time the guest and host may not be insured (Fla. (6)(a)3; Va. 46.2-1414(3)).
• The daily rate and any insurance or protection package costs (Fla. (6)(a)4; Va. 46.2-1414(4)).
• That the host’s own liability insurance may exclude or not cover the shared car (Fla. (6)(a)5; Va. 46.2-1414(5)).
• An emergency number for roadside assistance and customer service (Fla. (6)(a)6; Va. 46.2-1414(6)).
• Any conditions under which the guest must hold a personal policy on a primary basis to book (Fla. (6)(a)7).
• In Virginia, that driver’s license financial responsibility requirements still apply, and that sharing without physical damage coverage may violate a lienholder contract (Va. 46.2-1414(7) to (9)).

If an item is missing from an agreement in a state that requires it, that is worth raising with the state insurance department. If an item is present, it tells you exactly where your own coverage stops, in the platform’s own words.

Gig work next door: how car sharing differs from rideshare and delivery

Peer-to-peer sharing is often lumped in with rideshare and delivery work, and the insurance logic is related but not the same. In rideshare, the driver is the owner and the app’s coverage changes with periods of app status, as the rideshare insurance guide shows. In delivery, the driver is also the owner and the platform’s coverage is set by its own policy rather than a dedicated statute in most states, which the delivery driver guide walks through. In car sharing, the owner is not driving at all; the statutes exist because a stranger is in control of the car, and the coverage shifts on the clock of the reservation rather than on app status.

One shared feature is the exclusion. Personal policies commonly exclude using a car to carry people or goods for a fee, and they commonly exclude making the car available for rent or sharing. Florida’s and Arizona’s statutes both say they do not invalidate a policy exclusion for vehicles “made available for rent, sharing or hire or for any business use.” A host who also drives for a rideshare or delivery app in the same car is dealing with two separate exclusions and two separate platform policies, and neither covers the other.

New York’s no-fault law draws the two together in one place: Insurance Law section 5106(d)(2), covered in the New York no-fault guide, deals with disputes over whether a driver was working for a transportation network company or a peer-to-peer car sharing program at the time of the loss.

States not in the table, and how to read your own

Turo’s November 2024 filing does not settle which other states have such laws; it says only that some states and foreign jurisdictions have not adopted laws written for peer-to-peer car sharing. Washington’s legislature site shows that its 2012 personal vehicle sharing chapter, RCW 48.175, was repealed effective 2023-01-01 by 2022 c 67, so a state’s law can be replaced as well as added.

To read your own state’s statute, search the legislature’s code for “peer-to-peer car sharing” or “vehicle sharing,” then find four sections: the definitions (look for the sharing period and termination time), the insurance requirement (who must be insured, in what amounts, and whether it is primary), the exclusions (what your insurer may exclude) and the disclosures. If the law follows the model act, those sections will look much like Florida’s. If it does not, it may look like Oregon’s, where the program carries the whole owner’s liability.

If your state has no such statute, the platform’s terms and your own policy are the only rules. That puts more weight on the policy’s wording about rental and sharing and on what the platform’s plan actually pays. Your state insurance department’s consumer line can confirm whether a statute exists.

Questions readers ask

For lending a car to a friend outside any platform, where none of these statutes apply, read how coverage follows the car or the driver.