Honestly, this is what freaked me out when I started looking into it. I had the app on, just waiting for a ping, and got rear-ended at a light. My personal insurance straight-up asked if I was “working”—I said yes since the app was open, and they immediately tried to deny the claim. The rideshare company only wanted to pay part of the damage because I didn’t have a passenger yet. Ended up fighting both sides for weeks. That gray area is real, and it’s a headache.
The rideshare company only wanted to pay part of the damage because I didn’t have a passenger yet.
That part really confuses me. I get there's a difference between waiting for a ride and actually having a passenger, but isn’t the whole point of their insurance to cover us when we’re “on the clock”? I’ve read some companies do offer limited coverage during that period, but it seems inconsistent. Maybe it depends on local laws or even your specific policy? It just feels like there should be clearer rules here—otherwise, drivers are left in the lurch.
It’s honestly a mess. The insurance coverage “gap” when you’re just waiting for a ping is real—most companies only offer basic liability then, not full collision or comprehensive. Once you’ve got a passenger or are en route, the coverage usually kicks up a notch. But yeah, it varies by state and even by company. I’ve seen folks get burned because they assumed they were fully covered the whole time. Reading the fine print is a pain, but it’s kind of necessary with this stuff...