An Uber crash can produce a passenger receipt, driver app screens, platform timestamps, GPS points, messages, calls, safety reports, insurance exchanges, and device records. Those items may be held by different people and may use different clocks, time zones, labels, and retention periods.

A screenshot records what one screen displayed at one moment; a complete rideshare record connects the accepted request, service interval, route, people, vehicle, platform events, and source metadata.

Save the passenger receipt and ride identity

G.S. 20-280.2 requires a TNC to send an electronic receipt that includes where the service started and ended, the total time and distance, and an itemization and calculation of the fee. Preserve the original email, in-app receipt, account export, and any later correction rather than relying only on a cropped image.

  • Passenger account, ride-request time, acceptance, driver name and photograph, vehicle description, plate, pickup, destination, and receipt
  • Route map, GPS points if available, stops, cancellation, trip-end status, fare adjustment, tip, refund, support ticket, and safety report
  • In-app messages, masked calls, text, email, push notifications, recordings lawfully made, and photographs or video
  • Other passengers, seating positions, pickup or drop-off witnesses, and every related account or device
  • File name, format, source, export method, creation or download time, device clock, time zone, and unchanged storage copy

Preserve precise app-status and service times

G.S. 20-280.4(m) requires a TNC driver, the TNC, potentially covering insurers, and other directly involved parties to exchange specified coverage information and precise log-on, log-off, and TNC-service times for the 12 hours before and after an accident in a claims coverage investigation or accident.

Request the full applicable window, not only the crash minute. Transitions between offline, available, accepted, traveling to pickup, carrying a passenger, unloading, cancelled, and completed status can affect the evidence and coverage analysis. Identify simultaneous rideshare or delivery apps instead of assuming one platform was the only one in use.

Use the statutory record period as a floor, not a reason to wait

G.S. 20-280.5(c) requires the TNC to maintain a record of each North Carolina TNC service for one year and an identified driver record for one year after the driver relationship ends. A targeted preservation request should still be sent promptly because the statute does not say every desired data field is part of the retained service record, and other sources may have shorter ordinary retention.

Build separate requests for separate custodians

  • TNC: account, trip, service, GPS, communication, safety, support, payment, insurance, and driver or vehicle records tied to the event
  • Driver: app data, screenshots, phone, navigation, other platforms, dashcam, vehicle data, receipts, and insurer communications
  • Passenger: receipt, account export, messages, calls, location history, photographs, health-app data, and device backups
  • Insurers: first notice, app-status material, coverage exchange, statements, photographs, estimates, reports, and written positions
  • Independent sources: law enforcement, 911, traffic and business cameras, witnesses, tow, repair, telematics, and other vehicles

A preservation request identifies information at risk; it is not an order compelling production. After litigation begins, North Carolina Rule of Civil Procedure 45 provides a subpoena process with duties and protections for the recipient. The correct procedural tool depends on who holds the information, case posture, scope, privacy, and objections.

Protect authenticity and privacy together

Retain native files and exports, record the source and handling history, and preserve the device or account when proportionate. Create working copies for annotation. Do not edit timestamps, rename away source information, access another person’s account, impersonate a user, evade platform security, or collect unrelated private data merely because a phone contains relevant evidence.

Reconcile the data into one event chronology

Compare platform times with phone, camera, 911, dispatch, vehicle, witness, receipt, and medical records. Record clock offsets and uncertainty rather than forcing every event to the same second. A route point may show where a device reported itself, not who held it or why the vehicle moved. App status may affect insurance evidence but does not by itself prove collision fault.

The related Charlotte rideshare fault guide explains how app activity, road movements, video, vehicle data, witnesses, and contributory-negligence evidence fit into the separate collision analysis. This page owns the trip and app-record preservation process.

Rosensteel Fleishman Car Accident & Injury Lawyers provides information about a North Carolina Uber accident claim involving platform records. Early organization should identify each account, device, custodian, time source, retention risk, lawful request, and unchanged original.

Sources