Western States Law Library  ›  Arizona  ›  Guide 15

Arizona Auto Insurance & Crash Law · Citizen Guide 15

Rideshare Insurance

Arizona rideshare coverage changes with the driver's exact digital-network status. Whether the driver was offline, waiting for a request, en route after accepting a ride, or carrying a passenger can change required liability insurance from an ordinary personal-policy system to $250,000 or $1 million in mandatory commercial coverage.

Current-law review: Sept. 13, 2026 A.R.S. §28-4038 $25K / $50K / $20K waiting $250K accepted ride $1M passenger onboard Digital timestamps control

Arizona rideshare insurance changes by phase

Phase 0 App offline

TNC-specific §28-4038 coverage is not activated merely because the person is a rideshare driver.

Phase 1 Logged in · waiting

Driver is available through the network but has not accepted a ride.

Phase 2 Ride accepted

Transportation network services have begun even though the passenger may not yet be in the vehicle.

Phase 3 Passenger onboard

The highest Arizona statutory TNC liability minimum applies while the passenger occupies the vehicle.

The critical transition occurs when the ride is accepted. Under §28-9551, transportation network services begin with acceptance of the request—not when the passenger enters the vehicle.

The statutory coverage map

Driver status Required liability Required TNC UM Key Arizona rule
App offline Ordinary applicable auto-insurance framework; no special §28-4038 TNC minimum solely because person is a TNC driver. Determine from personal or other applicable policy. Verify all other business activity and policy exclusions.
Logged in · no accepted ride Primary 25/50/20 liability. No separate UM requirement stated in §28-4038(A). Investigate TNC and personal rideshare-endorsed policies.
Ride accepted · passenger not onboard Primary commercial liability of at least $250,000 per incident. Primary commercial UM of at least 25/75 under the current formula. Transportation network services have begun.
Passenger onboard Primary commercial liability of at least $1,000,000 per incident. Same statutory §28-4038(B)(2) minimum formula; actual policy may be higher. Obtain the commercial policy rather than assuming UM matches liability.
Do not use one number for the entire rideshare shift. A driver can move through several legally distinct insurance phases during a single hour.

The passenger does not need to be in the car for commercial-service coverage to begin

Arizona defines transportation network services as beginning when the TNC driver accepts the passenger's request through the digital network.

8:14:53 PM Driver waiting online. No accepted request. Phase 1 · 25/50/20 liability
8:15:02 PM Driver accepts passenger request. Phase 2 · $250K liability + statutory UM
8:20:16 PM Passenger enters vehicle. Phase 3 · $1M liability
8:42:31 PM Passenger exits and trip ends. Service phase ends
A timestamp can be worth hundreds of thousands of dollars in coverage. Preserve the platform data before debating liability.

Arizona's required rideshare UM coverage needs separate attention

Once transportation network services have begun, §28-4038(B) requires primary commercial uninsured-motorist coverage.

Statutory Minimum

$25,000 / $75,000

The current statute requires the greater of 25/75 or §28-4009's bodily-injury minimum. With current ordinary limits of 25/50, the TNC statutory result is 25/75.

Actual Policy

May provide more

Statutory minimums are floors. Obtain the actual TNC commercial policy and declarations before fixing the available first-party limit.

Liability and UM do not necessarily match. Passenger-occupied TNC liability rises to $1 million, but §28-4038 does not raise its UM minimum to $1 million.

Underinsured motorist coverage

Section 28-4038 does not itself establish a parallel TNC-specific minimum UIM requirement.

Investigate:

  • TNC commercial declarations
  • UM/UIM endorsement
  • driver's personal UM/UIM
  • rideshare endorsement
  • passenger's own policy
  • passenger household policies
  • stacking issues under Guide 06

The driver's ordinary personal policy may stop covering the car when the app turns on

Section 28-4038(C) expressly provides that a personal policy is not required to insure TNC risks merely because it otherwise covers the driver or vehicle.

No Express TNC Coverage

Coverage may be excluded

The driver's or vehicle owner's personal policy is not statutorily required to provide coverage while the driver is logged in or providing TNC services.

Rideshare Endorsement

Coverage may be restored or expanded

Arizona expressly allows personal insurers to sell a policy, amendment or endorsement specifically covering the TNC period.

“I have full coverage” is not enough. Obtain the complete personal policy and every rideshare endorsement.

The TNC must warn its drivers about the insurance transition

Under A.R.S. §28-9558, before the driver may accept rides, the TNC must disclose in writing or electronically:

TNC insurance

Coverage and limits the company provides while the vehicle is used in connection with its digital network.

Personal-policy warning

The driver's own insurance might not provide coverage during TNC use, depending on its terms.

Lienholder warning

Using a financed vehicle for rideshare activity might violate the driver's agreement with the lienholder.

Digital evidence determines the insurance phase

Section 28-4038(G) specifically recognizes the importance of digital status.

Coverage investigation: the TNC and insurers providing statutory coverage must exchange the driver's precise log-on and log-off times during the 24 hours immediately preceding the accident and descriptions of their coverage, exclusions and limits.

Preserve more than log-in status

  • exact crash timestamp
  • platform log-in time
  • platform log-off time
  • ride request time
  • ride acceptance time
  • pickup time
  • passenger entry evidence
  • trip cancellation time
  • passenger exit time
  • GPS path
  • driver app screenshots
  • passenger app screenshots
  • electronic receipt
  • platform communications
  • payment information
  • phone metadata
  • other active driving apps
§28-4038(G) is an inter-company disclosure rule. Its text requires cooperation between the TNC and insurers. Do not overstate it as an express unlimited claimant right to obtain every insurance document directly from the platform.

Check every active platform

Gig drivers can potentially use more than one driving, delivery or transportation application.

Platform A

Driver may merely be logged in and awaiting a request.

Platform B

Driver may already have accepted a ride or delivery assignment.

Do not assume one app determines the entire insurance picture. Identify every active platform and then analyze the policies and priority rules applicable to each.

If a rideshare passenger is injured, identify who caused the crash

TNC Driver at Fault

Liability claim

While the passenger occupies the TNC vehicle, §28-4038 requires at least $1 million per incident in primary commercial liability coverage.

Another Driver at Fault

Third-party + first-party investigation

Pursue the tortfeasor's liability insurance while also investigating TNC UM, actual TNC UIM coverage and the passenger's own UM/UIM sources.

Passenger coverage investigation should run in both directions. Find the at-fault liability coverage and every first-party UM/UIM source available to the passenger.

A rideshare driver's own injury claim depends heavily on the phase

Driver status If hit by uninsured driver
Offline Investigate ordinary personal UM and all other applicable policies.
Online · waiting §28-4038(A) does not impose the subsection (B) commercial UM requirement. Investigate rideshare endorsement and actual TNC coverage.
Ride accepted · en route to pickup Required commercial UM under §28-4038(B) is in effect.
Passenger onboard Required commercial UM remains applicable; determine actual purchased limit and all other first-party sources.

The platform has statutory duties separate from the driver's insurance

Arizona requires TNCs to perform specified driver screening and vehicle qualification functions before drivers may accept trip requests.

Driving history

The TNC must obtain and review the applicant's driving-history report.

Background check

Arizona requires specified local and national criminal and registry checks.

Vehicle condition

The TNC must require compliance with state vehicle standards and the statutory brake/tire inspection or qualifying newer-vehicle attestation.

Insurance is not the same as TNC tort liability. A statutory insurance policy can respond even when the platform disputes direct or vicarious tort liability. Analyze those questions separately.

Arizona also imposes a rideshare zero-tolerance system

A.R.S. §28-9554 requires a TNC drug-and-alcohol zero-tolerance policy while the driver is:

  • providing transportation network services; or
  • logged in and awaiting service.

A qualifying passenger complaint requires immediate suspension of the driver's access while the company investigates.

If impairment is alleged, preserve the platform complaint file. Arizona requires specified zero-tolerance enforcement records to be maintained for at least two years after receipt of a passenger complaint.

Send a preservation request early

A.R.S. §28-9556 requires a TNC to retain individual trip records for at least one year after each trip.

Driver records must also be retained until at least one year after the driver's activation on the digital network has ended.

One year is a retention floor—not a litigation strategy. Preserve trip, app, GPS, account, insurance and communication records as soon as the TNC connection is discovered.

Crash-scene evidence can help prove TNC status

A.R.S. §28-9552 requires TNC trade dress while the vehicle is being used to provide transportation network services.

Photograph the vehicle

Capture platform logos or trade dress before the vehicle leaves the scene.

Photograph the phones

When lawfully available, app screens can preserve contemporaneous evidence of the active trip or driver phase.

Trade dress is corroboration, not the final phase proof. Digital timestamps remain the strongest evidence of exactly when a ride was accepted or terminated.

Arizona rideshare crash workflow

Identify the TNC. Determine which platform connected the driver and passenger.
Identify the exact crash time. Seconds can determine the applicable statutory phase.
Determine whether the driver was logged in. Obtain digital status rather than relying only on recollection.
Determine whether a ride had been accepted. Acceptance activates transportation network services under §28-9551.
Determine whether the passenger was physically onboard. Passenger occupancy activates the $1 million minimum liability level.
Obtain the TNC commercial policy. Identify liability, UM, UIM, exclusions, limits and endorsements.
Obtain the driver's personal policy. Look specifically for TNC exclusions and rideshare endorsements.
Identify the vehicle owner. The TNC driver may use a vehicle owned by another person.
Check every active application. Determine whether another platform was also active or had an accepted assignment.
Preserve the 24-hour log history. Section 28-4038 expressly recognizes these timestamps in coverage investigations.
Preserve trip and driver records. Do not rely on the statutory one-year minimum retention period.
Build first-party coverage separately. Passenger and driver UM/UIM rights may extend beyond the TNC policy.
Investigate direct platform conduct. Driver screening, vehicle qualification and impairment issues may create separate factual questions.
Build one coverage ledger. Record each carrier, insured, coverage, limit, phase, exclusion and priority.

Rideshare crash document checklist

  • police crash report
  • exact crash timestamp
  • driver identity
  • vehicle owner
  • vehicle registration
  • TNC identity
  • TNC trip receipt
  • ride request timestamp
  • ride acceptance timestamp
  • pickup timestamp
  • trip completion timestamp
  • cancellation timestamp if applicable
  • 24-hour log-on/log-off history
  • GPS route
  • driver app records
  • passenger app records
  • other active app records
  • TNC commercial policy
  • TNC declarations page
  • TNC UM endorsement
  • TNC UIM endorsement if any
  • driver personal policy
  • rideshare endorsement
  • vehicle owner's personal policy
  • passenger personal policy
  • passenger household policies
  • proof of insurance shown at scene
  • platform terms of service
  • §28-9558 insurance disclosures
  • driver application
  • driving-history records where relevant
  • vehicle inspection records
  • zero-tolerance complaint file if relevant
  • photographs of trade dress
  • coverage correspondence
  • coverage denial / reservation letters

Common Arizona rideshare insurance mistakes

“The passenger wasn't in the car yet, so commercial coverage had not started.”

Wrong. Arizona transportation network services begin when the driver accepts the ride request.

“The app was on, so there is $1 million of insurance.”

Wrong. Logged-in waiting status has a different statutory liability minimum from passenger-occupied service.

“The driver's personal policy must cover the rideshare crash.”

Arizona expressly says personal policies are not required to cover the TNC period unless they expressly provide that coverage.

“The $1 million liability limit means there is $1 million of UM.”

No. Current §28-4038 uses a much lower separate statutory UM minimum.

“Arizona requires TNC UIM at the same level.”

Section 28-4038 specifically mandates commercial UM; obtain the actual policy before stating what UIM protection exists.

“The driver's recollection of app status is enough.”

No. Platform timestamps, trip records and phone/app evidence are central because coverage can change within seconds.

Arizona authority map

Primary Law · A.R.S. §28-4038 Transportation network services financial responsibility

Establishes Arizona's TNC phase-based liability requirements, commercial UM requirement, personal-policy treatment, proof-of- insurance duties and insurer/TNC coverage-investigation cooperation.

Read §28-4038 →
Primary Law · A.R.S. §28-9551 TNC definitions

Defines the TNC, driver, vehicle and transportation network services, including the crucial rule that service begins when the driver accepts the passenger's request and ends at passenger exit or cancellation.

Read §28-9551 →
Primary Law · A.R.S. §28-9558 Driver insurance disclosures

Requires disclosure of TNC insurance limits, warns that personal insurance may not cover TNC use and addresses lienholder-contract concerns.

Read §28-9558 →
Primary Law · A.R.S. §28-9555 Driver and vehicle qualification

Establishes application, driving-history, background-check, license, registration, financial-responsibility and vehicle-condition requirements.

Read §28-9555 →
Primary Law · A.R.S. §28-9556 Trip and driver records

Requires individual trip records to be maintained for at least one year and establishes minimum retention for driver records.

Read §28-9556 →
Primary Law · A.R.S. §28-9554 Zero-tolerance drug and alcohol policy

Requires the TNC to maintain an impairment policy and specified suspension, investigation and record-retention procedures after qualifying passenger complaints.

Read §28-9554 →
Primary Law · A.R.S. §28-9552 TNC permits and trade dress

Requires Arizona TNC permitting and visible platform trade dress while the vehicle is being used to provide transportation network services.

Read §28-9552 →
Primary Law · A.R.S. §20-259.01(C) UM/UIM and public/livery-type insurance

Provides additional statutory context for UM/UIM coverage associated with vehicles used as public or livery conveyances and related commercial uses.

Read §20-259.01 →
2024 Arizona Legislation H.B. 2729 · Chapter 74

Amended §28-4038 to establish the present $1 million passenger- occupied liability minimum and revise the commercial UM requirement.

Source-control rule: start with §28-9551 to establish the exact service phase, then apply §28-4038. Do not determine rideshare insurance merely from whether a passenger was physically inside the vehicle.

Frequently asked questions

When does Arizona rideshare commercial coverage begin?

Arizona's transportation network services begin when the driver accepts the passenger's request through the TNC digital network. The passenger does not need to be in the vehicle yet.

How much liability insurance applies while the driver is online waiting for a ride?

Section 28-4038(A) requires primary liability of 25/50/20 while the driver is logged in but has not yet begun transportation network services.

How much insurance applies after the driver accepts a ride?

During transportation network services, Arizona requires at least $250,000 per incident in primary commercial liability coverage until the passenger-occupied $1 million requirement applies.

How much liability insurance applies while the passenger is in the car?

Current §28-4038 requires at least $1 million per incident in primary commercial liability insurance while the passenger being transported occupies the TNC vehicle.

Does Arizona require rideshare uninsured-motorist coverage?

Yes, during the transportation-network-service period after a ride has been accepted. Current §28-4038(B) produces a statutory minimum of 25/75 under the present §28-4009 bodily-injury limits.

Does the $1 million passenger liability limit mean there is $1 million in UM coverage?

No. The statute uses a separate UM minimum formula. The actual commercial policy may provide higher UM limits, so obtain the policy.

Does Arizona require rideshare UIM?

Section 28-4038 specifically mandates commercial uninsured-motorist coverage and does not itself establish a parallel TNC-specific UIM minimum. The actual policy and other applicable Arizona insurance law must be reviewed.

Does the driver's personal policy cover the crash?

Not necessarily. Arizona expressly provides that a personal policy is not required to cover the TNC period unless the policy or an endorsement expressly provides that protection.

What is a rideshare endorsement?

It is an amendment or endorsement to a personal auto policy providing specified coverage during some or all of the driver's TNC activity. Its actual terms and phases must be read.

What if the driver says the app was off?

Obtain the platform's electronic log data. Arizona expressly recognizes precise log-on and log-off times as part of TNC coverage investigations.

What if the driver had accepted the ride but had not picked me up yet?

The driver is already providing transportation network services under §28-9551. The minimum $250,000 commercial liability and statutory commercial UM framework applies.

How long must the platform keep trip records?

Section 28-9556 requires individual trip records to be retained for at least one year after the trip. Preservation should be requested much earlier.

Does the rideshare company's insurance automatically make the company legally liable for the driver's negligence?

No. Required insurance and the platform's own tort liability are separate issues. Direct or vicarious liability requires its own current-law analysis.

Freeze the digital timeline before analyzing the insurance.

Determine the exact crash time, platform log-in status, ride-acceptance time and passenger-occupancy status. Then obtain the TNC commercial policy, personal policy and rideshare endorsement. In Arizona, those timestamps determine which statutory insurance regime was active.

Public legal education only. VictimsGuide.com provides public-interest legal education. It does not provide individualized legal advice, does not offer or accept legal representation, and does not create an attorney-client relationship. Arizona rideshare claims depend on the exact digital-network phase, platform policy, personal policy, vehicle ownership, UM/UIM provisions, crash facts and current Arizona law. Verify controlling primary authority before legal reliance.