Has anyone actually had a claim paid out during that “Period 1” window, or is it all theory?
I’ve been through this with my S-Class. Had a minor fender bender while waiting for a ping—app was on, no passenger. My personal insurer flat-out denied it, citing the app status. Rideshare coverage kicked in, but the deductible was insane and the payout barely covered repairs. It’s not just theory, but don’t expect a smooth process or full compensation. That “little toggle” really does change everything.
My personal insurer flat-out denied it, citing the app status.
That deductible during Period 1 is no joke. I’ve seen a lot of folks surprised when their “full coverage” personal policy suddenly means nothing just because the app’s on. Curious—did they give you any pushback about whether you were really waiting for a ride, or was it pretty straightforward? Sometimes the gray area between periods gets messy, especially if there’s any confusion about timestamps or app status.
Yeah, that “Period 1” gap is brutal. I actually had a buddy who thought his regular insurance would cover him since he hadn’t accepted a ride yet—nope, denied right away once they saw the app was on. In his case, the insurer didn’t even bother with details about whether he was waiting or just driving around; just the app being active was enough. It’s wild how fast “full coverage” turns into “not our problem.” Makes you think twice about those little gaps...
That’s exactly what happened to my neighbor last year. He was just sitting in his car, app on, waiting for a ping—wasn’t even moving—and someone rear-ended him at a stoplight. His regular insurance company took one look at the claim and said nope, not covered, because the rideshare app was open. He tried to argue it, but they pointed right to the policy language about “commercial use.” It didn’t matter that he hadn’t accepted a ride yet.
I always thought “full coverage” meant you were good no matter what, but apparently not if you’re doing anything remotely commercial. I guess the logic is that as soon as you flip that app on, you’re technically available for hire, so it’s a different risk category. Still feels like a technicality, but insurance companies love those.
He ended up having to go through Uber’s (or maybe it was Lyft’s?) period 1 coverage, which barely covered anything—just liability and not much else. His own car repairs came out of pocket. That was a wake-up call for me. I don’t drive for rideshare myself, but I do rent my car out sometimes and had to double-check my own policy after hearing his story.
It’s wild how these little details can make such a huge difference when something actually goes wrong. Makes me wonder how many people are out there thinking they’re covered when they’re really not... Insurance is one of those things where you don’t know what you don’t know until it bites you.
If anyone’s still driving with just their personal policy and hoping for the best during that “waiting for a ride” time, might be worth looking into some kind of rideshare gap coverage or endorsement. Not every company offers it, but some do now—though it costs extra (of course). Just seems safer than rolling the dice and hoping nothing happens during that weird in-between time.
That “full coverage” myth trips up so many people. I can’t tell you how often I hear, “But I have full coverage, isn’t that enough?”
That’s the kicker—just having the app on puts you in a different risk bucket. It’s wild, but insurance companies see that as commercial use, period. Rideshare gap coverage isn’t cheap, but compared to paying out of pocket for repairs, it’s worth considering. The fine print really does matter... even if it feels like a technicality sometimes.“It didn’t matter that he hadn’t accepted a ride yet.”
