After a California rideshare crash, preserve the trip receipt, in-app timestamps, GPS or route information, driver and insurer details, and any dashcam footage. These records can help establish the applicable Public Utilities Code section 5433 coverage period and reconstruct the collision.
Key Takeaways
- Trip acceptance, pickup, impact, and drop-off timestamps can help identify the applicable rideshare insurance period.
- Save the trip receipt, app messages, support contacts, and any screen information before an account view changes.
- GPS or route data, driver history, and dashcam footage can help test how the collision unfolded.
- A preservation request does not replace a lawsuit deadline or the separate public-entity claim process.
The app screen that seemed routine before a crash can become an important time record afterward. In Los Angeles, an Uber or Lyft passenger may need to preserve the trip receipt, acceptance and pickup times, route information, and the identity of each driver involved. This guide explains how to organize those digital records alongside physical evidence and medical documents. It is intended for people who need to establish both the collision sequence and the insurance period without relying on a later recollection of when the ride began.
Why digital rideshare records can be important
Rideshare coverage depends in part on the driver's app period when the crash occurred. Public Utilities Code section 5433 describes different insurance requirements for the app-off period, the app-on/no-accepted-ride period, and the ride-accepted-through-drop-off periods. A trip record with timestamps can help distinguish those stages. Without it, people may describe the same moment differently, particularly when pickup, cancellation, or drop-off activity happened near the impact.
Digital evidence also helps establish the route and participants. A trip receipt may identify the passenger's ride and approximate times, while a map or GPS record can help locate where the vehicle traveled. App messages may show what the driver or passenger reported after the collision. Those records do not decide fault or coverage by themselves, but they can be compared with a collision report, witness accounts, and the physical scene.
Preserve records before relying on a summary. Save the complete trip receipt, screenshots of visible details, relevant messages, and any claim reference. Keep the original files and note when each was captured. If a record is unavailable in the app, write down what you searched for and when, and save any response from support. A clean chronology can make later requests more focused.
Trip timestamps and app status
Record the time of ride request, acceptance, passenger pickup, collision, and drop-off or cancellation. The app period is not determined by the passenger's recollection alone; a timestamped trip history can help establish whether the driver had accepted a ride and whether the passenger was in the vehicle when impact occurred. If an insurer assigns a period, compare its stated timing to the trip record and note any discrepancy.
Save screenshots that show the trip status and any messages related to an interruption, route change, or report of the crash. Capture the entire screen where possible so that context such as date, time, or trip identifier is not separated from the record. Keep the receipt email or app-generated trip summary as well. Do not edit the only copy or write over the screenshot; make a separate note explaining what it depicts.
Timing details are particularly important because the insurance amounts differ by period. Period 1 coverage under section 5433(c) has specified primary and excess limits, while Periods 2 and 3 use a $1 million primary liability requirement under section 5433(b)(1). Period 3 passenger UM/UIM coverage changed under SB 371 effective January 1, 2026. Preserve trip dates and timestamps accurately so the correct rule can be assessed.
GPS, route, and collision-sequence records
Preserve route maps, pickup and drop-off locations, and any available GPS information that can locate the vehicle at the time of the crash. Write down the intersection or road segment and the direction of travel as soon as possible. A route record may establish where the vehicle was traveling, while a witness or camera may show the actual movement immediately before impact. These sources are strongest when their time and location details can be compared.
Do not treat a displayed map as a precise reconstruction unless the underlying record supports that level of detail. Note the platform, date, and source of each image or export. If the route display changes when a trip is reopened, preserve the original receipt and describe what remains visible. Where multiple vehicles or a public bus are involved, list their positions separately rather than assuming that the rideshare route explains every movement.
Ask promptly that relevant electronic records be preserved, identifying the account, trip date, approximate time, and location. Keep a copy of the request and any confirmation. The facts establish trip and GPS data as useful evidence but do not supply a particular retention period or retrieval process for every record. Avoid stating that data has been erased or withheld unless a source confirms that; document exactly what was requested and what response came back.
Driver history, messages, and other app information
The verified rideshare facts identify driver rating and complaint history as potentially relevant evidence. Preserve any information already visible to you, such as the driver's displayed name, vehicle details, rating if shown, and messages connected to the trip. Keep the trip identification and date with those records so that material from another ride is not mistakenly attached to this collision.
Do not infer misconduct from a rating or an unverified complaint. Such information may provide investigative context, but it does not establish that the driver caused this particular crash. The immediate evidence should describe the actual route, movement, visibility, and timing. If the driver or another party disputes the account, seek records that address the event itself rather than relying solely on a generalized profile entry.
Preserve app support conversations and insurer communications in complete form, including dates and sender details. If a message refers to a coverage period or policy limit, record the exact wording and ask which app status and coverage type it addresses. Period 3 UM/UIM and Period 2/3 liability are distinct. Keeping those conversations together with the trip timeline can help prevent a reduced UM/UIM figure from being confused with the separate liability coverage.
Dashcams, scene photos, and medical documentation
Ask whether the rideshare vehicle, another car, or a nearby camera recorded the collision. If footage exists, request preservation promptly with the date, approximate time, exact location, and relevant camera or vehicle. Save the original file if it is provided and do not replace it with a trimmed excerpt. Note who provided it and whether the recording's time display appears accurate when compared with the trip record.
Photograph vehicle positions and damage, roadway layout, traffic controls if visible, and any physical marks that help explain the sequence. Keep the collision report, witness names, and contact information. If another driver was involved, record that person's insurer and vehicle details as well. A rideshare trip log can show a trip status, while scene evidence can show what the vehicles were doing; neither should be substituted for the other.
Keep medical and treatment records, prescriptions, restrictions, and documentation of symptoms in a separate but linked folder. A dated chronology can connect the time of collision to the onset of care without making assumptions about medical causation. Retain repair or replacement information for damaged personal property. Preserve originals and label each item by date and source so later reviewers can understand when and how it entered the record.
A practical evidence-preservation sequence
Immediately after safety and medical needs: save the trip receipt, screenshot the trip status and messages, note the collision time and location, and gather names for all drivers and witnesses. If another person can help, ask them to capture what they personally observed and the time they did so. Avoid using the app alone as the record; save copies outside the account where practical.
In the next few days: organize GPS or route details, request relevant dashcam or nearby footage, preserve the collision report, and keep insurance communications. Make a timeline for ride request, acceptance, pickup, impact, and drop-off. Note any difference between the time shown in an app and the time shown in a report rather than silently changing one to match the other.
As the claim progresses: keep a record of each data request and response, preserve medical and repair documents, and compare the insurer's coverage-period position against the timestamps. Calendar the lawsuit deadline separately: personal-injury actions generally have two years under Code of Civil Procedure section 335.1, while a public-entity claim generally must be presented within six months under Government Code section 911.2. Evidence requests do not extend either period.
This guide is attorney advertising and general information only. It is not legal advice, and reading it does not create an attorney-client relationship.
Preserving rideshare evidence in Los Angeles County
For a Los Angeles County crash, save the route, intersection, and direction details rather than noting only a neighborhood. Most personal-injury lawsuits arising in the County are filed in Los Angeles County Superior Court and Los Angeles County Superior Court; the exact courthouse assignment should be confirmed for each case. App records can help establish the relevant coverage period under Public Utilities Code section 5433; public vehicle involvement can add a separate written claim due generally within six months under Government Code section 911.2. Keep identifiers for Metro, city, or other public vehicles if present, and record all data requests and replies. A screenshot of a trip receipt is useful, but retain complete correspondence and any original recording too.