In crashes involving Uber or Lyft, the most important detail often isn’t who was at fault. It’s whether the app was on. That one factor can flip the entire insurance process upside down. Here’s what you need to know when coverage hinges on a few seconds of app activity.
Coverage doesn’t apply when the app is off
Uber and Lyft provide no insurance coverage if the driver wasn’t logged in at the time of the crash. During that offline window, the vehicle is treated like any personal car, meaning the driver’s private insurance is the only option, and many of those policies exclude accidents that happen while working for a rideshare company.
Limited coverage applies when the app is on but no ride is active
Once the app is running and the driver is waiting for a ride request, rideshare companies offer a small layer of liability coverage, but only for third-party injuries or damage. This doesn’t protect the driver or any future passenger and often caps out below what’s needed in a serious crash. If you’re hit during this window, you’re dealing with limited options and narrow payout ceilings.
Full coverage starts when a ride is in progress
The moment a trip is accepted, whether the driver is en route to a pickup or already transporting a passenger, full rideshare coverage takes over. This includes up to $1 million in liability and other protections like uninsured motorist coverage. But to access those benefits, it must be clear that the ride had officially started through the app at the time of the crash.
When insurance gaps put you at risk
If no coverage applies, you’re left figuring out which policy, if any, can help you recover. That’s why it’s critical to understand how app status affects liability, especially when rideshare companies and insurers push the blame back and forth. Sorting through that gray area often takes more than paperwork, and getting clear answers early can make the rest of the process less overwhelming.
