Insurance is a total headache with this stuff. I’ve read the fine print on my policy and there’s a whole section basically saying “nope” if you’re logged into a rideshare app, even if you’re just waiting around. The companies love to advertise “you’re covered,” but as you said, it’s a gray area and they drag their feet when you actually need help.
People think you’re covered just because you’re “on the clock,” but it’s a gray area and the companies don’t make it easy.
I’ve always wondered—if you get hit and it’s clearly not your fault, like you’re rear-ended, why should you be the one paying the deductible? Seems like the other driver’s insurance should step up, but it always turns into a blame game between the companies. Anyone ever actually get the other party’s insurance to pay out without a fight, or is it always a mess? I’m starting to think the only way to avoid this is to never turn the app on unless you’re literally about to pick someone up… but that kind of defeats the point.
I hear you on the deductible thing—it’s super frustrating. Last year, my wife got rear-ended while she was waiting for a rideshare ping, and our insurance still made us pay the deductible upfront. Took months before we got reimbursed, and only after a ton of calls and paperwork. The other driver’s insurance kept dragging their feet, blaming “unclear liability” because she was logged into the app but had no passenger. Honestly, it feels like they look for any excuse not to pay out. Makes you think twice about even bothering with these apps unless you really need the extra cash...
Honestly, I get where you’re coming from, but I’ve seen it work out a little differently too.
That “Period 1” gray area is a pain, but in my case, when I got sideswiped between trips, Uber’s insurance at least covered part of the repairs after my regular policy tried to dodge it. Still had to front the deductible, yeah, but at least there was *some* backup. Not saying it’s perfect—definitely not—but sometimes the app insurance does kick in if you push hard enough. Just wish the process wasn’t such a maze...“blaming ‘unclear liability’ because she was logged into the app but had no passenger.”
Yeah, that whole “Period 1” thing is such a headache. I’ve heard stories all over the place—some people get denied flat out, others get partial coverage like you did. I had a friend who had to go back and forth with both insurance companies for months before anything got sorted. Honestly, it feels like you have to be your own lawyer just to get basic coverage sometimes. Wish they’d make it more straightforward, but I guess that’s wishful thinking...
Honestly, it feels like you have to be your own lawyer just to get basic coverage sometimes.
That’s exactly how it feels. The whole “Period 1” situation is just unnecessarily complicated. I’ve read through a few policy documents and it’s almost like they’re written to confuse you on purpose. One thing I noticed is that some insurers will quietly exclude rideshare driving unless you buy a specific add-on, but even then, the coverage during Period 1 (just waiting for a ride request) is usually way less than what you’d expect.
I get why they want to limit their risk, but it’s not like drivers are trying to game the system—they just want to know they’re protected if something goes wrong. It’s wild that you can be covered one minute, then as soon as you log into the app, your regular insurance steps back and the rideshare company’s policy only half-steps in. No wonder people end up in endless back-and-forths.
Honestly, I wish there was a more transparent way to see exactly what’s covered at each stage. The current setup just seems designed to trip people up.