Phone Records After a Distracted-Driving Crash: Preservation, Requests, and Subpoena Limits

Phone evidence can be short-lived, distributed across several systems, and protected by privacy law. After an Oregon crash, the practical task is not simply to “subpoena the phone.” It is to identify the records that may exist, preserve them before routine deletion or device replacement, and use the correct legal process to request a narrow crash-time window.

This article is limited to preserving and obtaining phone, app, carrier, cloud, and device records. For the broader proof picture—including witnesses, video, police observations, vehicle data, and crash timing—read Proving Texting and Driving in a Crash.

Start by Identifying Who May Control Each Record

No single source necessarily has a complete account of phone activity. Potential custodians include:

The driver: the physical phone, account credentials, screenshots, downloaded archives, and data within the driver’s possession, custody, or control.
The mobile carrier: call-detail records, SMS or MMS metadata, subscriber information, and some network or data-session records, depending on the carrier and retention policy.
An app or cloud provider: account logs, user-generated content, synchronization records, or activity metadata, depending on the service and applicable law.
The device or operating system: screen-state, notification, battery, application, location, or diagnostic artifacts that may exist on the device or in a linked backup.
A vehicle-linked system: Bluetooth, infotainment, or projection-system data that may show a connection or interaction, depending on the vehicle and system.

The existence, detail, and retention of these records vary. A carrier’s data-session log, for example, usually does not identify what a person viewed or establish that the driver was handling the phone. An incoming text timestamp does not prove that the message was read. The request must match the factual question.

Preservation Comes Before Production

A preservation notice asks a person or organization not to delete specified information while a claim or lawsuit is reasonably anticipated. It does not by itself compel disclosure, create records that never existed, or guarantee that a provider will retain every requested category.

An effective preservation notice should be prompt and specific. Depending on the facts, it may identify:

The driver, phone number, known account identifiers, and device.
The collision date and a focused period before and after the reported crash time.
Call and message metadata, app activity, location information, cloud backups, and device logs actually at issue.
The physical phone, SIM or eSIM information, paired wearable, and linked vehicle system.
Native files, exports, metadata, audit history, and the form in which information should be maintained.
A request to suspend routine deletion, reset, replacement, trade-in, or account closure for the identified material.

Preservation requests may need to go to the driver or the driver’s counsel, insurer, carrier, and relevant app or cloud providers. Each recipient may have a different process. Sending a letter to one custodian does not preserve data held only by another.

Do Not Alter or Informally Search Someone Else’s Device

An injured person should not try to access the other driver’s phone or accounts. Even when a phone is voluntarily shown at the scene, scrolling through it, forwarding content, or changing settings can create privacy, authenticity, and chain-of-custody problems. Device collection and inspection should use consent or formal legal process with a defined scope.

What to Request From the Driver

When litigation is pending, ORCP 43 permits requests for relevant, nonprivileged documents and electronically stored information in a party’s possession, custody, or control. A targeted request to the driver may seek:

Call logs and message metadata for a short crash-time window.
Records identifying whether relevant messages or app actions were sent, received, opened, or created during that window.
A native account export where it is reasonably available.
Information identifying the device, carrier, phone number, accounts, and linked services in use.
Device settings or logs relevant to screen activity, notifications, driving mode, Bluetooth, or app use.
Production of the device for a limited, read-only forensic inspection when less intrusive records cannot answer the issue.

A request should distinguish metadata from communication content. It should also specify the desired production form when native files, timestamps, time-zone fields, or associated metadata matter.

A Focused Inspection Protocol Can Reduce Privacy Intrusion

Turning over an entire phone can expose years of unrelated messages, photographs, health data, financial information, privileged communications, and precise locations. Where device inspection is justified, the parties or court may address:

The examiner and forensic tool.
The exact date and time window.
The applications, artifacts, or search terms covered.
Whether collection is read-only and how the device is protected.
Filtering for attorney-client privilege and unrelated private material.
A process for objections, redactions, and protective treatment.
What the examiner reports and whether unrelated data must be destroyed or returned.

The right scope depends on relevance, burden, available alternatives, and the particular issues in the case.

What a Carrier Subpoena May—and May Not—Produce

ORCP 55 provides procedures for subpoenas to nonparties in Oregon civil litigation. A properly issued subpoena may seek specified records from a carrier, subject to notice requirements, objections, court supervision, the carrier’s retention practices, and other law.

Carrier records may include subscriber information, call-detail records, and metadata showing that an SMS or MMS event occurred. Depending on the system, records may use different time zones or show network processing rather than when a person viewed a communication. Data usage can reflect background synchronization, automatic updates, navigation, or another passive process. It should not be labeled “active app use” without supporting evidence.

A subpoena cannot retrieve records that were never kept or were deleted before preservation. It also does not give a private civil litigant the same access available to law enforcement under criminal-investigation statutes.

App and Cloud Records Face Additional Limits

Applications vary in what they store, where they store it, and whether the user can export it. Some relevant information may be available from the driver’s own account or device even when the provider cannot disclose it in response to a civil subpoena.

The federal Stored Communications Act, 18 U.S.C. §§ 2701–2713, restricts when covered providers may disclose stored communication content. A private-party subpoena is not a guarantee that a provider can produce message content. The statute distinguishes among content, non-content records, governmental demands, user consent, and other permitted disclosures, so the correct route is fact- and provider-specific.

In practice, counsel may consider:

Requesting relevant content or exports from the account holder through party discovery.
Seeking valid consent where appropriate.
Requesting narrowly identified non-content records from the provider, while anticipating statutory or provider objections.
Using device-level collection when the information is stored locally and inspection is proportionate.
Asking for a preservation response without assuming that preservation creates a right to production.

Narrow the Request to the Collision Timeline

The crash time should be anchored as precisely as available before records are requested. Sources may include a 911 timestamp, dispatch records, camera footage, a connected-vehicle alert, or photographs with reliable metadata. The request can then define a reasonable period before and after that time rather than seeking months of phone history.

Useful scope language identifies:

The controlling time zone and whether timestamps are stored in local time or Coordinated Universal Time.
Whether the request concerns sent, received, delivered, opened, unlocked, foregrounded, or background events.
The relevant phone number, account, device identifier, app, and record category.
The requested native format and associated metadata.
Any exclusions for privileged, medical, financial, or unrelated location information.

Precision reduces privacy disputes and makes the resulting timeline easier to interpret.

Authenticate and Contextualize the Production

Obtaining a record is not the end of the analysis. Counsel may need to establish where it came from, how it was maintained, and what its fields mean. Keep production correspondence, custodian certifications, file names, metadata, and an unchanged copy of the material received.

Common interpretation issues include:

A call can be hands-free or handled by a passenger.
A message can arrive without being opened.
An app can use background data without active interaction.
A phone can be connected to a vehicle while locked.
A timestamp can reflect server processing rather than the user’s action.
A shared account or multiple synced devices can complicate attribution.

Those limits do not make phone records useless. They show why the records must be tied to the correct person, device, event type, and clock before a conclusion is offered.

Frequently Asked Questions

Can I subpoena phone records before filing a lawsuit?

Ordinary party discovery and nonparty subpoenas generally operate within a pending legal proceeding. A pre-suit preservation request may ask that records be retained, but it does not compel production. Whether any limited pre-suit court procedure is available depends on its rules and the circumstances.

Does a subpoena provide the text of every message?

No. Carriers often have metadata rather than message content, and the Stored Communications Act can restrict provider disclosure of stored content. Relevant content may instead need to be requested from the account holder or collected from a device, subject to objections, privacy protections, and court supervision.

Can deleted information still be recovered?

Sometimes, but not always. A provider, cloud backup, linked device, recipient, or forensic artifact may retain a copy. Recovery depends on the system, deletion method, overwrite history, and timing. Preservation should begin promptly rather than relying on later recovery.

How long do carriers and apps keep records?

There is no single retention period for every provider or record type. Policies and technical practices change, and different categories may be retained for different periods. A prompt, provider-specific preservation request is more reliable than assuming a generic deadline.

Can the entire phone be inspected?

Not automatically. Relevance does not eliminate privacy, privilege, burden, or proportionality concerns. A court or agreed protocol may limit the time period, data categories, examiner, search method, and disclosure of unrelated information.

Phone-Record Preservation and Request Checklist

Identify the driver, phone number, carrier, device, accounts, and linked systems as accurately as possible.
Establish the best-supported collision time and controlling time zone.
Send focused preservation notices to each likely custodian.
Preserve the physical device and request that it not be reset, replaced, traded in, or altered.
After litigation begins, use ORCP 43 for records within a party’s possession, custody, or control.
Use ORCP 55 where an appropriate nonparty subpoena is needed.
Account for Stored Communications Act restrictions before demanding provider-held content.
Request native data and metadata, not only screenshots or summaries.
Use a narrow forensic protocol and protective measures when device inspection is necessary.
Keep an unchanged production copy and document the source, time zone, and meaning of each field.

This article provides general educational information, not legal advice. Preservation duties, discovery rights, provider restrictions, privacy protections, and admissibility depend on the facts and applicable law.

Phone Records After a Distracted-Driving Crash: Preservation, Requests, and Subpoena Limits