Rideshare Accidents (Uber and Lyft) Lawyer Near Me in San Marcos, Texas

A location identifier, not an incident conclusion

For an Uber or Lyft crash, the useful starting point is an event-specific record set rather than a general description of the collision. Preserve the trip receipt, app messages, pickup or drop-off details, timestamps, photographs, medical records, and communications with insurers. The relevant evidence may involve the driver, vehicle, platform, passenger, and one or more insurers.

• Identify whether the app showed a requested, accepted, active, completed, or canceled trip.
• Preserve the pickup and drop-off locations and every available time shown in the app.
• Keep names, contact information, vehicle details, insurance information, and any incident or claim number provided.
• Do not edit or discard messages, photographs, receipts, or location information.

Direct answer: point 2

San Marcos is a Texas city listed by the United States Census Bureau with a Vintage 2025 population estimate of 77,830. That identifies the page location; it does not establish where a particular event occurred, which agency handled it, or who may be responsible.

Separate records by custodian

Potential record holders depend on what happened and who created each record. The driver and passenger may hold communications, photographs, receipts, and location information. The rideshare platform may hold trip status, timestamps, route information, account communications, and support records. Vehicle owners, insurers, repair facilities, medical providers, witnesses, and the investigating agency may hold separate records.

• Driver: account details shared after the event, vehicle information, photographs, and communications.
• Passenger: trip receipt, app screens, messages, location history, photographs, and treatment records.
• Platform: trip status, timestamps, route or location records, support communications, and incident records, subject to applicable access and retention limits.
• Insurer: claim correspondence, recorded communications, policy information, and vehicle inspection or repair records.
• Investigating agency: reports or related records created for the event. TxDOT provides statewide crash-report and crash-data starting points, but its resource does not establish that TxDOT investigated a particular scene.

Keep an access log

Do not assume that a trip receipt answers every coverage or responsibility question. Preserve the record in its original form, note when it was obtained, and keep later versions or correspondence separately so changes in the account can be identified.

Keep disputed propositions separate

A rideshare claim may involve disagreement about whether a trip was active, where a pickup or drop-off occurred, which vehicle movement caused the event, what the driver or passenger could see, and whether a later account matches the contemporaneous records. Insurance communications may raise additional questions about the applicable policy or claim handling. The available evidence, not the app label alone, should guide the factual review.

• Trip status: requested, accepted, active, completed, or canceled.
• Timing: app timestamps compared with messages, photographs, device data, and agency records.
• Control and movement: stopping, turning, merging, loading, unloading, or changing lanes.
• Identity and condition: driver, vehicle, passenger, occupants, damage, and witness accounts.
• Coverage records: insurer communications and policy documents connected to the driver, vehicle, platform, or passenger.

Do not import unrelated theories

If a public entity, health-care provider, employer, or product becomes part of the factual picture, different official Texas source chapters may become relevant. The approved sources identify Texas public-entity liability in Chapter 101, health-care liability in Chapter 74, products liability in Chapter 82, and injured-worker claims and coverage through the Texas Division of Workers’ Compensation. The sources do not establish that any such issue exists in this event.