Rideshare App and Trip Records After a California Crash

This guide is for a California rideshare passenger, driver, or authorized helper who needs to preserve app and trip records after a crash. Its narrow task is to build a source-labeled trip packet: what the rider account shows, what the driver account shows, what the platform may hold, what the phone and email preserve, what the insurer requests or confirms, and what public reports record.

The rideshare accident action guide covers broader first steps. The rideshare service guide explains the wider claim lane. This article does not decide fault or coverage. It focuses on preserving and reconciling the trip-status evidence that can help identify the correct vehicle, driver, platform period, insurer, route, and event sequence.

California Public Utilities Code section 5431 defines a transportation network company as an organization providing compensated prearranged transportation through an online-enabled application or platform that connects passengers with drivers using personal vehicles. That statutory definition makes the app relationship important, but a receipt or app screen by itself does not prove how a collision happened.

Create four parallel clocks instead of forcing every event into one list:

1. Platform clock: request created, driver matched, request accepted, driver en route, arrival, pickup, trip started, trip ended, transaction completed, driver logged off, cancellation, adjustment, and support-case events.
2. Device clock: call log, text, notification, screenshot, photo, location-history entry, Bluetooth event, wallet charge, email receipt, and file creation time.
3. Crash clock: first impact, vehicle stop, emergency call, witness contact, police arrival, medical response, tow, and departure.
4. Claim clock: platform report, insurer notice, claim number, adjuster contact, document request, coverage position, correction, and later correspondence.

Write the displayed time, date, and timezone exactly as shown. If the timezone is not shown, mark it “not displayed.” Preserve an untouched copy before renaming a file. The digital-evidence guide explains why an original export and a labeled working copy serve different purposes.

Do not infer that “trip ended” means the passenger had already exited, that a payment time equals the crash time, or that a support-ticket creation time equals notice to an insurer. Use separate rows until a reliable source connects them.

For each record category, identify both the source and the likely custodian:

• Rider account: trip card, receipt, route view, pickup and destination, driver and vehicle identifiers displayed to the rider, fare adjustment, rating, lost-item or safety report, support messages, and account export.
• Driver account: offer, acceptance, navigation, arrival, pickup, trip completion, earnings detail, cancellation, incident report, app-status history, support messages, and driver export.
• Platform: server-side account, trip, dispatch, status, communication, payment, fraud, safety, and support records. The consumer may not see every field in the ordinary app.
• Phone and cloud account: original photos, videos, notifications, calls, texts, email, wallet activity, location artifacts, backups, and file metadata.
• Insurer or claims administrator: notice, claim intake, recorded communications, coverage correspondence, app-period information received, document requests, and payment records.
• Public source: police or CHP report, dispatch or 911 record where available, DMV SR-1, court record, and CPUC complaint material.

A passenger, driver, pedestrian, cyclist, vehicle owner, and account holder may have different records and access rights. Do not use another person’s login, guess a password, impersonate an account holder, or defeat access controls. Record that a source exists and obtain it through a lawful, authorized route.

Capture the ordinary account view first: full-page screenshots or print-to-PDF where supported, the visible URL or app section, account identifier, trip identifier, export date, and every attachment. Download receipts and account archives in the native format offered. Preserve the original email with headers and attachments rather than copying only its text.

California Civil Code section 1798.110 gives a consumer a right to request categories and specific pieces of personal information a covered business collected about that consumer through a verifiable consumer request. The statute is useful for identifying a formal access lane, but it is not a promise that every requested item will be disclosed. Coverage, identity verification, exceptions, sensitive fields, another person’s information, retention, and other legal obligations can affect the response.

A privacy request, support ticket, insurance notice, preservation letter, subpoena, and civil discovery request are different tools. One does not automatically replace another or stop deletion under every system. Keep each request, verification step, response date, production file, denial, exception explanation, and follow-up in its own lane.

Adapt this factual request to the platform’s designated support, privacy, claims, or legal channel and to your role:

“Please preserve and provide the records available to me for trip [trip identifier] on [date], involving pickup [general location] and destination [general location]. Please include the trip receipt and revisions; request, match, acceptance, arrival, pickup, start, end, passenger-exit or transaction-completion fields if maintained; the times and timezones as stored; driver and vehicle identifiers shown to my account; route or location records available to me; in-app calls or messages and support communications; safety or incident reports; fare, payment, refund, and adjustment records; and an index describing any produced fields. Please preserve the original timestamps, identifiers, and file formats and identify any requested category that is not available through this channel.”

Do not demand another person’s private information or claim a right the requestor may not have. Use the least private location description that reliably identifies the trip. Save the exact submission, confirmation number, attachments, delivery receipt, identity-verification steps, response, export, denial, and follow-up.

Current California Public Utilities Code section 5433, amended effective January 1, 2026, assigns different transportation-network-company insurance requirements to defined app and ride periods. The text distinguishes the time after a driver accepts a ride request through completion of the transaction or ride, whichever is later, from the time a driver is logged on and waiting for a request.

That does not mean a screenshot labeled “on trip” automatically establishes coverage, fault, or damages. It means the stored acceptance, pickup, passenger-exit, transaction-completion, and logon or logoff times can be relevant to a coverage investigation. Preserve the platform source, insurer source, and device source separately so a reviewer can see whether they agree.

Public Utilities Code section 5435 requires a TNC or its insurer, in a claims coverage investigation, to cooperate with involved insurers and facilitate exchange of information including the accident date and time and the precise times the driver logged on and off the platform. The section does not say that every claimant automatically receives the complete platform log, and it does not make exchanged times conclusive. Ask the insurer to identify the source and period information used in its coverage position.

Give each disputed fact one ledger entry with these fields:

• Fact: for example, accepted time, pickup point, passenger exit, crash time, vehicle plate, driver identity, or transaction completion.
• Source: rider receipt, driver screen, account export, original email, device record, police report, insurer letter, or platform response.
• Exact value: copy the value without normalizing the time or spelling.
• Source timestamp and timezone: record what is shown and label anything missing.
• Acquired: who obtained it, by what channel, and on what date.
• Status: agrees, conflicts, incomplete, revised, superseded, or unresolved.
• Next verification: identify the source that could resolve the issue without assuming what it will say.

Example: the receipt may show a 9:18 p.m. trip completion, a phone photo may show the stopped vehicle at 9:16 p.m., and an insurer letter may call the crash time 9:15 p.m. Keep all three. Record whether the receipt time was created later, whether the photo timezone is known, and what source the insurer used. The ledger exposes the gap; it does not invent an answer.

The California DMV’s current SR-1 instructions state that a driver, representative, agent, broker, or legal representative must submit an SR-1 within 10 days when anyone is injured or killed or property damage exceeds $1,000. DMV also says the SR-1 is required in addition to a police, CHP, or insurance report. Confirm the current requirement for the actual event and do not assume the platform files it for a driver.

An SR-1, police report, platform incident report, CPUC complaint, and insurance claim serve different purposes. Record each submission date, reference number, filer, event description, attachments, and later correction. If a report contains an incorrect trip time or vehicle identifier, preserve the original and the correction request rather than replacing the first version.

The CPUC’s current transportation complaint page directs consumers with a complaint about a private passenger carrier, including a TNC, to contact the company first and then submit a complaint with readable supporting documents if the issue is unresolved. A CPUC complaint can document a regulatory complaint; it is not a substitute for emergency reporting, medical care, insurance notice, evidence preservation, or legal advice.

• Trip identifier, account role, general pickup and destination, displayed route, receipt, and every revised receipt.
• Driver name and photo as displayed, vehicle make/model/color, displayed plate, and any mismatch noted without public reposting.
• Request, match, acceptance, arrival, pickup, start, crash, passenger exit, transaction completion, cancellation, and logoff times where available.
• Original photos, videos, dashcam files, notifications, calls, texts, email, wallet activity, location artifacts, and backups.
• Platform safety report, support case, privacy request, account export, claim report, denial, and production index.
• Police or CHP report, dispatch or 911 request, SR-1 copy, witness information, and tow or repair record.
• Personal auto, TNC, platform, and other insurer notices; claim numbers; coverage correspondence; and the source of any app-period statement.
• Medical, expense, income, and daily-function records kept in their own folders and linked to the trip packet by date.

The claim-proof guide offers a broader source-to-element map. The damages evidence resource separates medical, income, property, and daily-life proof. Link those files to the trip index without placing full medical or financial data into a platform support message.

Start immediately because app views, support status, device storage, cloud backups, vehicle data, camera footage, and third-party records can change on different schedules. Preserve what you control before changing phones, deleting the app, clearing messages, repairing a device, returning a rental, or resetting a vehicle system. Do not alter an unsafe device or vehicle merely to obtain data; get qualified help.

Use a redacted working set. Mask full account, payment, driver’s-license, insurance, medical, and contact numbers; access codes; exact home addresses; faces of uninvolved people; and unrelated trip history. Keep the original in controlled storage. A privacy request may require identity verification, but send verification only through the platform’s designated secure process.

Legal and contractual deadlines can depend on the claimant, defendant, public entity, insurance policy, event, injury, and procedure. A platform request or CPUC complaint should not be assumed to pause any other deadline. Seek case-specific advice promptly, especially when the platform period, vehicle, driver, insurer, public entity, serious injury, or evidence-retention issue is disputed.

• Keeping only one screenshot: preserve the full trip view, receipt, original messages, exports, and neighboring events.
• Editing timestamps: record the displayed value and timezone; make calculations only in a separate working field.
• Assuming one account shows everything: rider, driver, platform, insurer, device, payment, and public sources can differ.
• Treating a receipt as a crash report: a receipt documents a platform transaction, not the complete collision.
• Conflating trip completion and passenger exit: preserve both fields if available and note which event the source describes.
• Overstating privacy rights: use the designated request process and document scope, verification, exceptions, and denial reasons.
• Publishing private identifiers: do not post driver photos, plates, addresses, account numbers, or another person’s data to seek help.
• Waiting for a perfect export: preserve current views and confirm separate reporting, claim, and legal deadlines.

1. Write the trip identifier, account role, event date, general locations, vehicle, driver, and crash time as each source shows them.
2. Preserve rider or driver trip views, receipts, messages, notifications, email, payment activity, photos, and videos in original form.
3. Build the four-clock timeline and mark missing timezones or uncertain event labels.
4. Create the platform-and-custodian map and submit narrow requests through authorized channels.
5. Notify the appropriate insurers and ask what platform-period source supports any coverage position.
6. Keep police, DMV, CPUC, platform, and insurer submissions in separate lanes with reference numbers and corrections.
7. Use the source-conflict ledger; never erase an earlier value merely because a later source differs.
8. Ask a licensed California attorney to review disputed access, preservation, coverage, liability, damages, and deadlines.

The attorney rideshare-evidence guide provides a separate attorney-authored perspective. The lawyer-comparison guide lists questions for evaluating independent counsel. Hurt Advice is a lawyer-referral and legal-information service, not a law firm. This article provides general educational information, not legal, privacy, insurance, technical, or medical advice. No attorney reviewed this displayed version. You can use the Hurt Advice contact page to request a referral.