Freeze the app phase before the insurance layers start pointing at one another.

Record whether the injured person was a passenger, rideshare driver, other motorist, pedestrian, or cyclist. Preserve the ride receipt, pickup and destination, driver and vehicle profile, trip or incident number, cancellation, fare, messages, map, timestamps, and immediate platform communications. A passenger's app may show a different clock or status from the driver's system, so both should be preserved in native or complete export form rather than relying only on cropped screenshots.

The driver's status should be reconstructed from platform data: log-on and log-off, availability, request offer, acceptance, route to pickup, arrival, passenger entry, trip start, route, trip completion, cancellation, and any simultaneous use of another platform. Location and application logs may show activity, but field definitions and time zones need explanation. A platform's business record or witness may be required to authenticate what a status code means.

Actor identity extends beyond the brand. Determine the vehicle owner, driver, personal insurer, transportation network company, platform insurer, other involved drivers, employers, rental or fleet provider, and any delivery or second platform. Oklahoma law defines transportation network companies, drivers, vehicles, digital networks, and prearranged rides. Those definitions and the current version must be matched to the facts before a policy phase or legal relationship is stated.

The platform may hold account, onboarding, driving-history checks, app status, ride and location events, safety reports, complaints, support contacts, deactivation, and insurance-routing information. What exists, who possesses it, retention, privacy, terms, and access procedure require confirmation. A platform summary created for a claim may not be the native event history. Preserve field names, timestamps, time zone, source table, and any later correction.

The driver's phone can contain app data, notifications, navigation, calls, messages, photographs, and other-platform use. Inspection raises the same relevance, privacy, proportionality, possession, privilege, and authentication issues as other digital evidence. The request period should bracket the trip and crash. A targeted protocol can protect relevant app state without authorizing a wholesale search of unrelated personal content.

The vehicle may provide event data, dash or cabin video, infotainment, telematics, driver-assistance alerts, and physical evidence. The owner may be the driver, another household member, a rental or fleet program, or a finance company with no operational control. Identify the specific system and custodian. Federal Part 563 covers defined event-data circumstances for certain light vehicles; it does not establish that every rideshare vehicle stored a complete driving history.

The analysis should identify the operative statute on the crash date and distinguish offline personal use, logged-on availability, an accepted request, travel to pickup, and a prearranged ride. Do not state dollar limits or declare a layer primary until current text and the issued policy are verified. Proposed legislation, platform marketing, and an outdated summary are not substitutes for the enrolled law and declarations applicable to the event.

Driver fault remains an ordinary collision question: speed, lookout, distraction, following, turn, signal, impairment, fatigue, pickup or drop-off maneuver, and compliance with road law. App interaction may supply evidence of distraction or trip status, but it does not establish causation by itself. Another driver may be responsible, and a passenger can pursue the parties supported by evidence without adopting a carrier's preferred account before the evidence is reviewed.

Platform responsibility is separate. Statutory classifications, agreements, control, agency, employment, direct negligence, any federal preemption, and current Oklahoma appellate law may matter. Background-check or safety-policy allegations need records and causation. Routing or insurance alone does not establish every duty or defense.

Develop collision and medical proof independently of coverage. Preserve position, belt, airbag, contact, damage, symptoms, emergency response, diagnosis, treatment, work or school limits, household effect, and future recommendations. A ride record may prove presence, not medical consequence.

Coverage may include driver, platform, other-driver, owner or rental, commercial or employer, uninsured or underinsured motorist, medical-payments, and umbrella policies. Priority, exclusions, insured status, offsets, consent, limits, and phase may be disputed. Obtain policies and endorsements, not a portal summary.

A rideshare driver injured while working may also face workers' compensation or occupational-accident questions depending on employment and coverage facts. A passenger or other motorist may have health-plan liens and subrogation. Multiple claimants and limits can create allocation pressure. Releases should be reviewed for platform, driver, owner, insurer, affiliate, and unknown-claim language before signature, especially when another layer remains disputed.