How Rideshare App Status Changes Your Insurance Coverage in Arizona

Rideshare app status changes insurance coverage in Arizona, but it is only one part of the analysis. You also need to know who caused the crash, who was injured, whether a covered ride was accepted, and what the actual policies provide. Arizona law distinguishes waiting, accepted service, and an occupied passenger trip. This guide explains those distinctions and the evidence used to evaluate them.

Updated September 14, 2026

The four rideshare periods, in plain English

The following period labels are a convenient way to describe the sequence. They are not a substitute for the statute or policy. Under A.R.S. § 28-9551, transportation network services begin when a request is accepted and end when the passenger exits or the trip is canceled.

• Period 0: App is off. Driver is just a person in a car.
• Period 1: App is on. Driver is logged in and waiting for a ride request. No passenger, no assigned trip.
• Period 2: Ride request accepted. Driver is on the way to pick up the passenger.
• Period 3: A passenger receiving the arranged service occupies the vehicle; review the actual exit or cancellation circumstances.

Even a short difference in the recorded sequence can matter. Compare acceptance, cancellation, passenger entry and exit, and collision timing. A screenshot taken after the collision may not describe the earlier status.

Related resources: Delivery App Driver Accident Claims in Arizona.

Period 0: App off, review ordinary coverage and the actual activity

Platform rideshare coverage generally relates to rideshare activity. When the app is off and the driver is on a personal trip, review the personal policy and any other applicable coverage. An app label alone does not identify every possible insured party or liability theory.

Arizona’s ordinary auto liability minimums are $25,000 per person and $50,000 per accident for bodily injury, plus $15,000 property damage under A.R.S. § 28-4009. A driver may carry higher limits or another applicable policy. UIM eligibility also requires policy and statutory analysis; it is not automatically stacked on top.

Confirm whether the trip was personal, commercial, or connected to another service. Do not assume that the only possible source of recovery is the minimum policy merely because one platform was offline.

Period 1: App on and waiting, primary coverage is required

A driver logged in and available without an accepted request is in a different statutory category from a driver already providing transportation network services. The lack of a passenger does not mean no insurance requirement applies.

A.R.S. § 28-4038(A) requires primary liability insurance of $25,000 per person, $50,000 per accident for bodily injury, and $20,000 for property damage while logged in but not providing transportation network services. The driver, company, or both may maintain qualifying coverage through the arrangements described in the statute.

This statutory waiting-period liability requirement is primary. Do not describe it as a policy that becomes available only after a personal insurer denies the claim.

Actual platform coverage can exceed the statutory minimum. Uber’s current national rideshare summary lists waiting-period liability limits of at least 50/100/25; the accident-date Arizona policy controls the particular claim. Separate personal-policy coverage or exclusions should also be checked rather than assumed.

Ask each insurer to identify its policy, assigned period, coverage position, and claimed priority in writing. A claim-handling delay does not change the statute’s primary-coverage requirement.

Periods 2 and 3: Accepted service and an occupied passenger trip

Arizona’s statutory liability floor changes during transportation network services. It also distinguishes whether the passenger receiving those services is actually occupying the vehicle.

Under § 28-4038(B), the required coverage includes:

• Primary commercial liability of at least $250,000 per incident while providing services, increasing to $1 million per incident when the passenger occupies the vehicle
• Primary commercial UM coverage of the greater of $25,000 per person/$75,000 per incident or the bodily-injury minimums in § 28-4009
• Any additional benefits supplied by the actual policy. The statute does not establish a universal $1 million UIM benefit or guarantee physical-damage coverage for the driver’s vehicle.

A liability limit covers qualifying liability for harm to others. It is different from UM, UIM, MedPay, or collision coverage. An injured driver cannot treat liability insurance as payment for the driver’s own injuries merely because an accepted trip existed.

Uber and Lyft publish general insurance summaries. Obtain the Arizona certificate, declarations, policy, and endorsements effective on the collision date. Benefits and limits can vary by location, period, and policy year; national marketing language is not the coverage contract.

Personal auto coverage and rideshare endorsements

Section 28-4038(C) provides that the relevant personal policies are not required to cover logged-in or service activity unless coverage is expressly provided or added by endorsement. Read the actual wording. Do not assume every insurer uses an identical exclusion.

The Arizona insurance department’s automobile resources provide general consumer guidance. When reviewing a denial, compare the cited provision with the actual app activity and the policy in force.

An endorsement may add coverage for some rideshare activity, but the scope varies. Ask what it covers while waiting, driving to pickup, transporting a passenger, or making a delivery. An endorsement for one service is not necessarily an endorsement for every commercial use.

Keep any application, endorsement, renewal, and declarations documents. A verbal statement that the policy covers rideshare should be checked against the issued terms. Neither the absence nor presence of an endorsement answers every liability or benefit question by itself.

How the personal policy and the platform policy coordinate

Coverage and payment order depend on the applicable policies, the app period, the injured person’s status, and the facts of the crash.

App off: Review the personal policy and actual activity, plus any other supported coverage source.

Waiting: Identify the primary coverage satisfying Arizona’s 25/50/20 requirement and any additional available policy benefits.

Accepted or occupied service: Identify the primary commercial liability and required UM coverage. Confirm higher actual limits, additional benefits, exclusions, and insured status.

If the period is disputed, ask which records support the insurer’s position. Separate a disagreement about timestamps from a disagreement about policy interpretation. Both can affect the answer.

What happens when the other driver is uninsured or underinsured

When another driver causes the collision, investigate that driver’s liability insurance and any UM/UIM coverage that may insure the injured person. The rideshare driver’s own liability policy is not automatically a replacement for the other driver’s missing or insufficient insurance.

Arizona requires the commercial UM coverage described above during transportation network services. UIM availability and limits require review of the actual policies and applicable law. Do not equate the $1 million occupied-trip liability limit with a $1 million UM or UIM limit.

The waiting-period liability floor in § 28-4038(A) does not itself establish UM/UIM benefits. Check any expressly applicable personal or platform coverage without assuming a standard benefit.

For other applicable auto policies,§ 20-259.01 addresses UM/UIM terms and offers. Current declarations-page rules, exclusions, insured status, and limits on multiple coverages require review. Coverage is not created automatically by inability to find a signed rejection form.

How to prove which period the driver was in

Potential sources for the trip timeline include the following, if available and lawfully obtainable. Each record’s timestamp and meaning must be understood:

• Trip logs and ride receipts from the driver’s and (if applicable) passenger’s Uber or Lyft account
• Driver dashboard screenshots showing app state around the time of the crash
• GPS timestamps built into the platform’s dispatch system
• Backend dispatch records that Uber and Lyft maintain internally
• Push notification logs on the driver’s phone
• Vehicle EDR (event data recorder) downloadscross-referenced with app timestamps

NHTSA’s Special Crash Investigations program illustrates the use of several evidence sources. In a rideshare claim, compare the app record with vehicle, witness, and scene information. EDR data does not itself record the legal app period.

There is no guarantee that every desired field exists or is retained. Section 28-4038(G) requires cooperation and information exchange among the company and insurers in a coverage investigation, including precise log-on and log-off times. That requirement is not unlimited direct access for every claimant.

Preserving app data before it disappears

Identify the actual record custodians and retention settings. Preserve relevant account information, receipts, messages, and original device files available to you. Avoid assuming that a visible trip screen is a complete copy of the platform’s records.

A targeted preservation request can notify the company and relevant custodians about identified evidence. Request confirmation and pursue lawful access when needed. A letter does not itself compel disclosure or automatically establish sanctions if a record is later missing.

Prompt investigation helps identify what exists and what needs protection. Court remedies for lost evidence depend on the actual duty, circumstances, and effect of the loss, not a universal number of days after the collision.

How Arizona’s comparative fault rule interacts with app-period coverage

Under A.R.S. § 12-2505, ordinary comparative negligence reduces damages by claimant fault, subject to the statutory exception for intentional, willful, or wanton conduct.

Fault and insurance are separate questions. Arizona generally allocates liability severally subject to exceptions under § 12-2506. A percentage assigned to a driver does not guarantee that an insurer writes a check for that percentage of all losses. Insured status, limits, covered damages, exclusions, other parties, and collection still matter.

Use the app timeline to identify potentially applicable coverage, then apply the liability findings and policy terms. Do not treat either step as a substitute for the other.

What passengers need to know

A passenger should preserve proof of the arranged trip and occupancy. The statutory $1 million liability minimum applies when a passenger receiving transportation network services occupies the vehicle. An off-app arrangement, cancellation, or disputed pickup requires examination of the actual facts.

That means:

• If the rideshare driver caused the collision, investigate liability coverage applicable to the covered occupied trip.
• If another driver caused it, investigate that driver’s insurance and any UM/UIM benefits that actually cover the passenger.
• Keep the receipt, trip details, and evidence of entry, exit, or cancellation. Passenger status does not eliminate every timing or coverage question.

Your own applicable auto benefits may also require review. Multiple policies do not automatically stack, and a release can affect remaining rights. Check the documents before accepting a settlement described as resolving everything.

What to do right now if you were in a rideshare crash

Practical checklist:

1. Get medical care appropriate to symptoms and follow emergency instructions. Do not seek treatment solely to satisfy an invented insurance documentation deadline.
2. Screenshot everything on the app. The trip screen. The driver’s name. The vehicle info. The receipt. The map showing pickup and drop-off. Do this before you close the app.
3. Ask the driver whether the app was on and whether they had a ride accepted. Note their answer. Don’t argue if they’re vague.
4. Get the police report number. Arizona crash reports become critical when the platform disputes fault or app status.
5. Report the crash to Uber or Lyft through the in-app “help” flow. This creates a timestamped record on the platform side.
6. Identify each insurer’s role before a detailed interview. Seek advice about a voluntary third-party recorded statement while meeting valid notice and cooperation duties under your own policy.
7. Check deadlines: private-party injury suits generally have two years after accrual under § 12-542. Public claims generally require 180-day notice and a one-year suit period under § 12-821.01 and § 12-821, subject to exceptions.
8. UM/UIM claims have separate written-notice and arbitration or suit requirements under § 12-555. Do not assume a tort demand or in-app incident report satisfies every insurance notice requirement.

Frequently Asked Questions

Does Uber’s $1 million policy cover me if I was just walking and got hit by an Uber driver?

Potentially, depending on a covered trip, driver liability, and the accident-date policy. Arizona requires at least $250,000 liability during accepted service and $1 million when the passenger occupies the vehicle. Actual limits may be higher. The waiting-period statutory requirement is primary 25/50/20, not a universal contingent layer.

The Uber driver’s personal insurance denied my claim. Is that the end of it?

Not necessarily. Identify the required primary rideshare coverage and any other applicable policy. Arizona’s waiting-period requirement is not generally conditioned on first obtaining a personal-policy denial. Request the denial and coverage explanation in writing.

How do I find out what app period the driver was in?

Preserve available receipts, screenshots, and messages. Request relevant records through appropriate channels and compare timestamps with other evidence. A preservation request does not guarantee that all desired records exist or grant automatic access to them.

Do I sue Uber or Lyft directly, or do I sue the driver?

The proper defendants depend on the conduct and legal basis for liability. A claim may involve the driver or another responsible party; a claim against a company requires its own supported theory. Contract labels and insurance limits do not alone decide whom to sue.

What if the rideshare driver was speeding or on their phone? Does that change coverage?

Such conduct can be relevant to fault, but it does not answer every coverage issue. Insured status, policy terms, applicable law, and facts still matter. Do not assume every alleged act is covered or that it guarantees payment.

Can I still recover if I was partly at fault for the crash?

Ordinary comparative negligence can reduce damages rather than bar an otherwise valid claim, subject to the statute’s misconduct exception. A hypothetical 40% reduction of $100,000 leaves $60,000 before fees, costs, liens, coverage, and collection. It is not a take-home promise.

Get a Clear Answer About Your Rideshare Crash

Our Uber and Lyft accident practice can review the trip timeline, insurance documents, and unresolved proof questions. Bring the receipt, claim numbers, correspondence, and any proposed release. Driver-specific issues are explained in our guide to being injured while driving for Uber or Lyft.

Call (602) 345-1818 for a free consultation with Impact Legal Car Accident Attorneys. Phone intake is available 24/7.

By Jared J. Pehrson | Impact Legal Car Accident Attorneys