AB2361 creates a statutory framework for ‘‘personal vehicle sharing’’ in California. It prevents an owner’s private passenger auto from being reclassified as commercial solely because the owner makes it available through an organized personal vehicle sharing program, but only when the owner’s annual sharing revenue does not exceed the vehicle’s annual operating expenses and the owner does not knowingly permit commercial use.
The bill places operational, recordkeeping, and financial responsibilities squarely on the personal vehicle sharing program: the program must supply proof of insurance compliance (REG 5085 or equivalent), collect and maintain verifiable trip records at its own cost, facilitate and pay for necessary hardware/software and signage, and assume legal liability and the duty to defend and indemnify vehicle owners for sharing-period incidents. Insurers may exclude coverage during sharing and the owner’s policy cannot be canceled solely for compliant sharing.
At a Glance
What It Does
AB2361 prevents private passenger vehicles from being deemed commercial solely because they’re used in a personal vehicle sharing program when specific tests are met; it requires sharing programs to provide proof of compliance, collect trip data, pay for sharing equipment, and assume liability for sharing-period losses. The bill also allows insurers to disclaim coverage for sharing-period incidents and bars cancellation of an owner’s policy solely for compliant sharing.
Who It Affects
Registered vehicle owners who list their cars on peer-to-peer sharing platforms, companies that operate personal vehicle sharing programs in California, primary automobile insurers on file with the DMV, and the Department of Motor Vehicles which will receive and rely on records and proof-of-compliance forms. Third-party claimants and courts will be affected by the bill’s reallocation of responsibility and defense obligations.
Why It Matters
The bill creates a clear statutory allocation of operational and legal responsibilities for peer-to-peer car sharing—removing a legal gray area that has caused coverage disputes and insurer cancellations. It shifts risk and compliance costs from individual owners to sharing programs, which will change commercial terms, underwriting, and platform operations in California.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB2361 defines ‘‘personal vehicle sharing’’ and carves out a protected status for private passenger vehicles used in such programs so long as sharing is run through a qualifying personal vehicle sharing program and the owner’s annual revenue from sharing does not exceed annual vehicle expenses. The test ties the owner’s protected status to a financial threshold (expenses ≥ revenue) and to an owner’s intent not to place the vehicle into commercial use as defined elsewhere in law.
The bill obligates the personal vehicle sharing program to provide the vehicle owner with proof of insurance compliance (a DMV REG 5085 form or equivalent) and requires that proof to remain in the vehicle whenever someone other than the owner is operating it through the program. The program must collect, maintain, and make available verifiable electronic trip records—date, time, initial and final locations, and miles driven—at the program’s expense, and it must use only private passenger vehicles and not knowingly allow commercial use by users.Most consequentially for liability and litigation, AB2361 makes the personal vehicle sharing program assume all liability of the owner for loss or injury during the sharing period and treats the program as the ‘‘owner’’ for all purposes during that time.
The program also has the duty to defend and indemnify an owner named as defendant for sharing-period incidents, and it remains liable until the vehicle is returned to a program-designated location and the sharing period terminates under specified conditions. The bill also recognizes insurers’ contractual rights: an owner’s insurer may exclude coverage for sharing-period incidents, and compliant sharing cannot be the sole reason to cancel an owner’s policy.
The Five Things You Need to Know
The bill bars classifying a private passenger vehicle as commercial solely for sharing when the owner’s annual sharing revenue does not exceed the vehicle’s annual operating expenses.
Personal vehicle sharing programs must provide proof of compliance (DMV Form REG 5085 or equivalent) and keep that proof in the vehicle while it’s shared.
Sharing programs must collect verifiable electronic trip logs—date, time, start and end locations, and miles driven—and maintain those records at their own cost.
The sharing program must assume all owner liability for sharing-period losses, be treated as the vehicle’s ‘‘owner’’ for those purposes, and has a duty to defend and indemnify an owner named in a lawsuit related to sharing.
Insurers may exclude coverage for losses that occur during a personal vehicle sharing period, but an owner’s policy cannot be canceled solely because the vehicle was made available through a compliant sharing program.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Protections against reclassification for compliant personal sharing
This subsection sets the baseline: owners who make their private passenger vehicles available through an approved personal vehicle sharing program won’t have those vehicles reclassified as commercial, for-hire, permissive use, or livery vehicles solely because of sharing. The protection is conditional—three tests must be met, including that sharing occurs via a qualifying program, owner revenue from sharing does not exceed annual vehicle expenses, and the owner does not knowingly allow commercial use. Practically, this ties the legal protection to both financial and intent-based limits, limiting the carve-out to casual or expense-offset sharing rather than genuine commercial rental operations.
Definitions: personal vehicle sharing, program, and private passenger motor vehicle
This section supplies working definitions that determine who and what falls under the law. ‘‘Personal vehicle sharing program’’ is an entity qualified to do business in California that facilitates noncommercial vehicle sharing; ‘‘personal vehicle sharing’’ covers use by people other than the owner; ‘‘private passenger motor vehicle’’ mirrors existing auto policy concepts and excludes vehicles with fewer than four wheels. Those definitions will be the first battleground in disputes—platforms and insurers will argue over whether specific activity is ‘‘noncommercial’’ or whether a vehicle qualifies as a private passenger motor vehicle.
Program operational duties: proof, records, equipment, and permissible vehicles
This subsection imposes several affirmative duties on the platform: issuing REG 5085 or equivalent proof to owners and ensuring a copy stays in the vehicle during sharing; collecting and making available detailed trip records (date, time, initial/final locations, miles driven); not knowingly permitting commercial use; using only private passenger vehicles; and facilitating and paying for required hardware, software, signage, and any damage to that equipment or the vehicle caused by its installation. These are concrete, auditable obligations that create compliance costs for programs and provide a paper trail for regulators, insurers, and courts.
Liability allocation: program assumes owner’s liability and duty to defend
These subsections reallocate risk: when the vehicle is under the control of a non-owner via a program, the program ‘‘assumes all liability of the owner’’ for bodily injury and property damage in amounts at least equal to statutory minimums, and for disputes over control the program remains liable unless it’s proven the owner was in control. The program must defend and indemnify owners named in suits arising from sharing-period incidents. This is a strong transfer of legal exposure to platforms and will materially affect their insurance needs and contractual terms with owners and insurers.
Insurer rights and noncancellation protection for owners
The bill allows an owner’s insurer to exclude coverage during a personal sharing period and to notify insureds it has no duty to defend or indemnify for sharing-period losses. At the same time, subsection (i) forbids canceling or nonrenewing a policy solely because the vehicle was made available for sharing under a compliant program. The pair of provisions signals legislative intent to let insurers manage exposure through contractual exclusions while protecting owners from blanket cancellations for participating in compliant sharing programs.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Private vehicle owners who share their cars for modest revenue — they gain a statutory safe harbor against commercial reclassification and a guarantee that compliant sharing alone won’t trigger policy cancellation, reducing the risk that a casual sharer loses personal auto coverage.
- Consumers who rent shared vehicles for noncommercial trips — the bill forces sharing programs to carry liability and to maintain trip records, improving avenues for compensation and post-incident reconstruction.
- Smaller sharing platforms that can meet the operational requirements — they get legal clarity that, if they comply with the statute, owner-vehicles won’t be immediately treated as commercial assets, which can lower owner friction and grow supply.
Who Bears the Cost
- Personal vehicle sharing programs — they assume owner liability during sharing periods, must defend and indemnify owners, pay for installation and maintenance of hardware/software and signage, and bear ongoing records-collection and storage costs.
- Primary automobile insurers — even though owners get noncancellation protection, insurers may face coverage gaps, indemnity disputes, and administrative burden resolving control disputes and coordinating with platforms and will need underwriting guidance for shared-use exposures.
- Regulators and courts — DMV and the judiciary will handle increased records requests, disputes over control and expense calculations, and enforcement of program duties, potentially creating resource strain and complex litigation over definitions and compliance.
Key Issues
The Core Tension
The core dilemma is whether to enable low-friction, expense-offset vehicle sharing by protecting owners and forcing platforms to internalize risk, or to protect third-party claimants and insurers from moral hazard and underinsurance by placing stricter coverage requirements on sharing activity; AB2361 chooses to protect owners and shift risk to platforms, but it does so in a way that raises unresolved questions about enforceability, underwriting, and the real-world adequacy of platform-held coverage.
The bill shifts legal and operational risk from individual owners to sharing programs, but several implementation challenges remain unresolved. The statute ties owner protection to a financial test—annual sharing revenue not exceeding annual expenses—but it does not prescribe how to calculate ‘‘annual expenses,’’ whether documentation must be standardized, or how disputes over reported expenses and revenue will be adjudicated.
That gap invites gamesmanship and will force either regulation or litigation to create workable standards.
The liability reallocation is sharp: treating the program as the ‘‘owner’’ for sharing-period purposes and making it assume the owner’s liability may create downstream consequences not expressly contemplated, including vehicle registration, tax, and lien-holder complications if a program’s legal status conflicts with other statutes or contracts. Allowing insurers to exclude coverage while prohibiting cancellation creates a tension in practice: owners keep their policies but may be left uninsured for sharing-period incidents unless the platform maintains adequate coverage.
Finally, the bill imposes substantial data collection and retention obligations on platforms without addressing privacy standards, data security, or the evidentiary weight of the stored ‘‘verifiable electronic records.”
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.