Self-driving taxis and app-based rideshare cars make up a large share of the traffic moving through San Francisco, and a collision with one is handled differently from an ordinary crash between two private vehicles. Liability doesn’t stop with the person behind the wheel, partly because there may not be a person behind the wheel at all. Companies running driverless fleets hold permits from state regulators, write their own software, and keep detailed records of what the vehicle sensed and decided in the seconds before impact. Those records usually carry more weight than a police diagram or a witness account.
When a human driver is working through an app, the answer turns on what the app was doing at the moment of the collision. Rideshare companies split their coverage into tiers based on whether the driver was offline, waiting for a request, heading to a pickup, or carrying a passenger. Anyone hurt near Market Street, along the Embarcadero, or on the streets below Lombard needs to know which tier applied and who holds the electronic proof. That evidence follows a retention schedule, so the real question is how quickly someone asks for it.
How liability works when nobody is driving
With a fully driverless vehicle, the usual defendant disappears and the claim moves toward the corporation that built, tested, and dispatched the car. California requires permit holders to carry substantial liability coverage for autonomous fleets, and those policies respond when the vehicle’s own decisions contribute to a collision. Fault might rest on software misreading a cyclist crossing at an angle, on a remote operator approving an unsafe maneuver, on a sensor flagged in maintenance logs and never repaired, or on mapping data that routed the car into an active construction zone. Each theory is proved with different records, often held by different departments inside the same company.
Product liability runs alongside ordinary negligence when a component failed rather than a judgment call going wrong, which brings in suppliers of lidar units, cameras, and braking systems. For someone with serious injuries, that reach matters, because claims against a technology corporation and its suppliers touch far deeper coverage than a standard auto policy provides. It also means the other side arrives with engineers and defense counsel almost immediately, and their early work is aimed at building a record that supports how the vehicle behaved.
The insurance tiers behind an app-based trip
Coverage on an app-based trip changes several times over the course of a workday, and the tier in force at the moment of impact controls how much money is available. With the app switched off, only the driver’s personal auto policy responds, and personal policies commonly exclude driving for hire. Once the driver logs on and waits for a request, the rideshare company provides contingent coverage at fairly modest limits. From the moment a ride is accepted until the passenger is dropped off, the commercial policy rises to one million dollars in third-party liability.
Drivers sometimes close the app after a crash, and insurers sometimes describe a waiting driver as entirely off duty, so the timestamped trip record becomes the deciding document. Obtaining it usually takes a written demand from a San Francisco rideshare crash law firm rather than a phone call, since the company treats trip data as proprietary and releases it on its own timetable.
Which records actually decide these cases
Digital evidence in these collisions falls into a few categories, and each one answers a different question about how the crash happened.
Vehicle telemetry: the log captures speed, steering angle, braking input, and the object classifications the software assigned in the final seconds, which explains why the car acted as it did.
Sensor diagnostics: camera, radar, and lidar health reports show whether any unit was degraded, obstructed, or throwing errors on the day of the collision.
App status data: the trip file shows when the driver logged on, when the ride was accepted, and where the vehicle sat at each timestamp.
Regulatory filings: operators report collisions and disengagements to state agencies, and patterns across those filings can support an argument about a known weakness.
Most of this material rolls off on retention schedules measured in weeks rather than years. Preservation demands sent to the operator, its insurer, and any third-party data vendor freeze the material in place, and they need to name specific systems and dates or the company will read them as narrowly as it can.
How shared fault affects what you recover
California applies pure comparative fault, so a percentage assigned to you reduces your recovery without wiping it out. If a jury decides you were fifteen percent responsible for entering a crosswalk against the signal, an award of two hundred thousand dollars comes down to one hundred and seventy thousand. Insurers for technology companies press this rule hard, arguing that a pedestrian moved unpredictably or that another driver’s lane change forced the vehicle’s maneuver. Sensor data cuts in both directions, which is why an independent review of the raw logs matters more than accepting the operator’s written summary of them.
What protects a claim in the first few weeks
Documented treatment comes first, because gaps in medical records are the first thing a defense adjuster points to when disputing an injury. Photograph the vehicle if you can, including company markings, the permit decal, the roof sensor housing, and the license plate, then get the report number from the responding officer. Video from a bystander’s phone often outlives the operator’s own footage, so names and numbers for anyone who stopped are worth collecting at the scene.
Recorded statements are the other early pressure point, since adjusters often call while someone is still on pain medication and ask questions shaped to lock in a helpful account. Working with a rideshare accident lawyer keeps those conversations controlled and puts preservation demands in motion, which is why CA uber accident attorneys treat the first two weeks as the most important stretch of the case. California’s two-year deadline for injury claims sounds generous, but the data that proves fault expires long before the filing date arrives.
When an autonomous or app-based vehicle causes a crash, the proof sits in trip logs and sensor data the operator controls. Karns & Karns Personal Injury and Accident Attorneys can demand that telemetry before it is overwritten and hold the parent company accountable alongside the driver. Reach us at 1-800-4-THE-WIN (1-800-484-3946).
