I’ve heard some companies only cover you if you’re actively on a trip, not just chilling in the app.
- Actually, I’ve had a different experience. My regular car insurance did get involved when I was logged into the app but not on a ride.
- It was messy—lots of back and forth—but they didn’t just bail.
- Rideshare insurance add-ons can help, but they’re not always required. Some basic policies still step up, even if they grumble about it.
- Honestly, it depends on your insurer’s fine print... which is a nightmare to read, but worth checking.
- I wouldn’t say it’s always a finger-pointing contest, but it’s never smooth sailing either.
I get what you mean about the fine print being a nightmare. I tried reading through mine and honestly, it felt like they wrote it just to confuse people. I remember seeing something about “period 1” coverage (when you’re logged in but haven’t accepted a ride yet), but it was buried in legal jargon.
Rideshare insurance add-ons can help, but they’re not always required. Some basic policies still step up, even if they grumble about it.
That’s interesting—my agent made it sound like I *had* to get the rideshare add-on or else my regular policy wouldn’t touch anything that happened while the app was on. Maybe they were just trying to upsell me? Or maybe it’s different by state? I’m in California and it seems like every company has their own rules.
I’m also curious if anyone’s actually had to pay out of pocket for damages because both the rideshare company and their own insurance pointed fingers at each other. I keep hearing horror stories about people getting stuck with bills, but I don’t know anyone personally who’s gone through that.
Has anyone here ever had their claim totally denied when they were just waiting for a ride request? Or did your insurance eventually cave after some arguing? I’m trying to figure out if the extra $20/month for the rideshare add-on is really worth it, or if it’s just peace of mind for worst-case scenarios.
Honestly, with gas prices and everything else going up, I’m trying to cut costs wherever I can... but not if it means risking a huge bill later.
I hear you on the fine print—sometimes it feels like they’re counting on us giving up halfway through. From what I’ve seen, in California most regular policies really do exclude anything once the app is on, even if you’re just sitting there waiting for a ping. The rideshare add-on basically plugs that gap, but yeah, $20/month adds up.
Here’s how I’d break it down:
1. Check your policy’s “exclusions” section for any mention of rideshare or “commercial use.”
2. Ask your agent (in writing, if possible) what happens specifically during period 1—sometimes they’ll clarify if you push a little.
3. If you have an older car or one you don’t mind fixing yourself, maybe the risk is worth it... but newer cars or anything with a loan? I’d lean toward the add-on for peace of mind.
I’m curious—has anyone here ever had their classic or collector car involved in something like this? I know most folks wouldn’t use one for rideshare, but stranger things have happened...
Check your policy’s “exclusions” section for any mention of rideshare or “commercial use.”
Totally agree—those exclusions are sneaky. I’d add:
- Even if your agent says you’re covered, get it in writing. Verbal promises mean nothing if you end up in a claim battle.
- Some insurers will drop you after a claim if they find out about rideshare use, even if it’s just “period 1.”
- I wouldn’t risk it with anything newer or financed. Lenders get real picky about gaps in coverage.
Classic car for rideshare? That’s wild. Can’t imagine the headache if something happened...
Honestly, you nailed it—those exclusions are a minefield. I learned the hard way that “my agent said it’s fine” doesn’t mean squat when the adjuster gets involved. And yeah, lenders will freak out if there’s any lapse, especially on something with a loan. Using a classic car for rideshare? That’s just asking for trouble… cool idea in theory, but not worth the risk in my book.
