Telematics, Insurer Driving Apps, and Phone Data as Evidence in Car Accident Injury Claims: Who Holds It, How It Cuts, How to Preserve It

A generation ago, the evidence in a car crash case was mostly skid marks, vehicle damage, photographs, and the memories of the people involved. Today, the cars, phones, and apps in and around a collision can quietly record far more: how fast each vehicle was moving, how hard someone braked, whether a phone screen was unlocked, and where each device was every few seconds. Insurers, lawyers, and courts increasingly treat that information as central evidence.

This guide explains the main types of digital driving data, who usually holds each one, how the data can help or hurt both the injured person and the driver accused of causing the crash, how to preserve it before it disappears, the privacy limits that apply, and how it is obtained in discovery. It is general education, not legal advice. Rules on privacy, evidence, and discovery vary by state and by court, and they continue to change as the technology does.

The main types of digital driving data

"Telematics" is a broad word. In practice, several different sources can matter after a crash, and each has its own owner, format, and lifespan.

• **Usage-based insurance programs.** Many auto insurers offer discounts if a driver installs a plug-in device or a smartphone app that tracks driving behavior. These programs commonly record speed, hard braking, rapid acceleration, time of day, mileage, and in some app-based programs, phone handling while the vehicle is moving.
• **Manufacturer connected-car systems.** Many newer vehicles send data back to the automaker or a connected-services provider. Depending on the vehicle and subscription, this can include location, speed, airbag deployment alerts, automatic crash notifications, and diagnostic codes.
• **Event data recorders.** Often called the "black box," the event data recorder stores a short snapshot of data around a crash or near-crash event, such as pre-crash speed, throttle, brake application, and seatbelt status. It lives in the vehicle itself rather than in the cloud.
• **Smartphone data.** A phone can hold location history, motion sensor data, app usage logs, call and text activity, and screen unlock events. Some of this sits on the device, some with the wireless carrier, and some with the companies that run the phone’s operating system or individual apps.
• **Navigation and rideshare apps.** Mapping apps, rideshare driver apps, and delivery apps often log trip routes, speed estimates, and the status of a trip at specific moments.
• **Fleet telematics.** Employers that run company vehicles frequently use tracking systems that log location, speed, harsh events, and sometimes in-cab video.
• **Dash cameras and in-cab cameras.** Video from personal or fleet cameras often comes with time stamps and sometimes speed overlays drawn from GPS.

Knowing which of these sources exist in your crash is the first job, because each one is preserved and requested in a different way.

Who actually holds the data

A common misunderstanding is that "the data" sits in one place. In reality, it is scattered.

The insurer. If a driver was enrolled in a usage-based program, the insurer or its technology vendor may hold detailed trip data. The program’s terms usually explain what is collected and how long it is kept. Note that this may be the at-fault driver’s insurer, the injured person’s insurer, or both.

The vehicle manufacturer. Connected-car data generally belongs in the first instance to the automaker or its service provider under the vehicle’s terms of service. Retrieval often requires a formal request or legal process.

The vehicle itself. Event data recorder information remains in the vehicle’s modules. If the car is repaired, salvaged, or crushed, that data can be lost permanently. This is why the physical vehicle is often the most time-sensitive piece of evidence.

The wireless carrier. Carriers keep records of calls, texts, and data sessions for billing and network purposes. Content of messages is treated differently from the basic record that a call or text happened, and carriers generally require proper legal process for detailed records.

The phone and its accounts. The device and its cloud backups can hold app activity, screen events, and location history. The owner of the phone controls much of this, which creates both an opportunity to preserve and a risk of loss.

App companies and employers. Navigation, rideshare, delivery, and fleet providers hold their own records under their own retention policies.

How the data can help an injured person

Digital driving data can be powerful for someone hurt by another driver’s negligence.

• **Proving speed.** If the other driver claims they were going the limit, insurer app data, connected-car data, or event data showing a much higher speed can be decisive.
• **Proving distraction.** Phone records showing an active call, a text sent seconds before impact, or screen interaction while moving can support a distraction claim. Many insurer apps also flag phone handling while driving.
• **Answering "you stopped suddenly."** In rear-end crashes, the injured driver’s own data may show gradual, normal braking rather than the abrupt stop the other side alleges.
• **Fixing the timeline.** Precise time stamps can resolve disputes about who entered an intersection first, how long a light had been red, or whether a driver had time to react.
• **Confirming impact severity.** Data showing a sharp change in velocity can counter an argument that a collision was too minor to cause injury, although injury causation still depends heavily on medical evidence.
• **Showing a pattern.** In some cases, a history of hard braking or speeding events may be relevant, though courts often limit evidence of past conduct, and its use varies by jurisdiction.

How the data can hurt an injured person

The same technology can cut the other way, and anyone bringing a claim should assume the defense will look for it.

• **Your own speed and braking.** If you were also speeding or braked late, the data may be used to argue you share fault. In states that use comparative fault, this can reduce the amount recovered. In the few places that still follow strict contributory negligence, even small fault can be a serious problem.
• **Your own phone use.** A text, a notification you tapped, or an app session at the wrong moment can become a central defense argument, even if it had nothing to do with the crash.
• **Activity after the crash.** Location history and fitness data recorded in the weeks after a crash may be used to challenge claimed injuries, for example by showing gym visits or long walks. Context matters, but you should expect the question.
• **Inconsistencies.** If your recorded statement or written account differs from the data, the defense may use the gap to attack your credibility generally.

None of this means injured people should fear the data. It means the data should be gathered and understood early, so there are no surprises and so any misleading reading can be explained.

How the data can help or hurt the accused driver

Drivers accused of causing a crash also have a stake in digital evidence.

A driver who was careful may benefit from data showing a legal speed, normal braking, and no phone activity. Telematics can support a defense that the other vehicle cut in, ran a signal, or stopped without reason. On the other hand, a driver who was enrolled in a usage-based program and was speeding or handling a phone may find that their own insurer already holds the most damaging evidence in the case. That is one reason insurers sometimes evaluate liability differently once they review their own program data.

Accuracy limits and why experts matter

Digital driving data looks precise, but it is not infallible.

• **Sampling rates.** Some apps record a data point every second or less often. A sudden swerve or brake between samples may be smoothed out or missed.
• **GPS drift.** Location and speed derived from GPS can be thrown off in urban canyons, tunnels, and areas with poor signal.
• **Clock differences.** Phone time, carrier time, vehicle module time, and camera time may not match exactly. A difference of a few seconds can change the story.
• **Phone versus driver.** Phone data shows what a device did, not necessarily who was using it. A passenger may have been texting. Some apps try to detect whether the phone owner was driving, but those detections can be wrong.
• **Interpretation.** Raw exports can be confusing, and vendors may use proprietary scoring. A qualified accident reconstructionist or digital forensics expert often has to explain what the numbers mean and what they do not.

Because of these limits, courts and juries usually give the most weight to digital data when it lines up with other evidence such as video, scene measurements, vehicle damage, and witness accounts.

Preservation letters: stopping the data from disappearing

The single most important early step is often a preservation letter, sometimes called a spoliation letter or litigation hold request. It is a written notice asking a party or data holder to keep specific evidence and not to delete, overwrite, or destroy it.

A useful preservation letter typically:

• Identifies the crash by date, time, location, and vehicles involved.
• Lists the specific categories of data to keep, such as event data recorder contents, connected-car data, usage-based insurance trip data, phone records, app logs, and video.
• Defines a reasonable time window, often a period before and after the crash.
• Asks that the vehicle not be repaired, sold, or scrapped until data can be downloaded.
• Is sent to every likely holder: the other driver, their insurer, any employer, fleet operator, rideshare or delivery company, and in some cases the automaker.

A preservation letter does not by itself force anyone to hand over data. What it does is put the recipient on notice. In many jurisdictions, once a party knows or should know that litigation is reasonably likely, it has a duty to preserve relevant evidence. If evidence is then destroyed, a court may impose sanctions or allow the jury to infer the missing evidence would have been unfavorable. The details of that duty and the available penalties vary by state and by court.

Some third parties, such as carriers and app companies, may not be bound by the same duty as a party to the case. Lawyers sometimes ask a court for an early order to preserve data from them when the risk of loss is high.

Privacy rules and their limits

Driving data is personal, and privacy is a real concern. Several layers of law and contract can apply.

• **Policy and program terms.** Usage-based insurance programs come with terms explaining collection, use, and sharing. Many describe use of the data for claims. Reading these terms is a good starting point.
• **Federal limits on carriers.** Federal law generally restricts wireless carriers from disclosing certain customer records without proper legal process or customer consent. Message content receives stronger protection than records showing that a call or text occurred.
• **State privacy laws.** A growing number of states have consumer data privacy laws, and some address vehicle or location data specifically. The protections and exceptions differ widely.
• **Court protections.** Courts commonly allow protective orders that limit who can see sensitive data and how it can be used, and they may narrow requests that are too broad.

Privacy rules usually do not make relevant driving data off limits in an injury case. They tend to shape how it is requested, how much is produced, and who can see it. A request for every location a person visited for a year is more likely to be narrowed than a request for data in the minutes around a crash.

How this data is obtained in discovery

Once a lawsuit is filed, digital evidence is usually gathered through formal discovery tools.

• **Requests for production** ask the other party to hand over documents and electronically stored information they control, such as app exports or downloaded vehicle data.
• **Interrogatories** are written questions that can ask whether the driver was enrolled in a usage-based program, what phone they used, which carrier provided service, and which apps were active.
• **Subpoenas** are used to obtain records from non-parties such as carriers, app companies, and automakers.
• **Depositions** let lawyers question drivers under oath about phone use, app enrollment, and what the data shows.
• **Forensic examination** of a phone or vehicle module may be allowed in some cases, usually under a court-approved protocol limiting what the examiner can look at.

Courts generally weigh relevance against burden and privacy. A showing that phone use or speed is genuinely disputed, for example from a witness who saw the driver looking down, often helps justify a targeted request. Fishing expeditions with no factual basis are more likely to be denied or limited.

The role of insurers before any lawsuit

Most injury claims settle without a lawsuit, so the data often matters during insurance negotiations. An insurer that holds its own policyholder’s app data may use it internally to assess liability, even if it never shares the raw file. An injured person’s own insurer may ask for consent to review their app data, especially in a claim under their own policy such as collision, medical payments, or uninsured motorist coverage.

Before granting broad consent or giving a recorded statement, it is wise to understand what you are agreeing to. You generally have obligations to cooperate with your own insurer under the policy, but the scope of that duty varies. Asking for the request in writing and limiting it to the time of the crash is a reasonable approach to discuss with a lawyer.

Questions to ask about your own driving app

If you are enrolled in a usage-based program or use a driving-safety app, it helps to understand it before the claim gets far along. Useful questions include:

• **What exactly does it record?** Some programs track only mileage and time of day, while others log speed, braking, cornering, and phone handling in detail.
• **Does it record when you are a passenger?** Many app-based programs try to detect whether you were driving, and you may be able to mark trips where you were not. Errors in that detection are common enough to be worth checking.
• **How long is trip data kept?** Retention schedules differ by company and can be short for second-by-second detail.
• **Can you download your own trip history?** Some programs let you view or export trips. Saving a copy of the crash trip, without altering anything, can be a sensible step to discuss with your lawyer.
• **Who else can see it?** The terms may describe sharing with vendors, affiliates, or others, and they may explain what happens when there is a claim or a legal request.

Knowing these answers early lets you and your lawyer judge whether your own data is likely to support your account, and prepares you for questions from the other side.

Step-by-step checklist after a crash where digital data may matter

1. **Get medical care first.** Health comes before evidence, and medical records are essential to any injury claim.
2. **Write down the digital sources you know about.** Note your own and the other driver’s vehicle make and model, any visible dash cameras, whether the other driver was working, and whether you use an insurer driving app.
3. **Do not delete anything.** Keep your phone, apps, messages, photos, and accounts exactly as they are. Avoid factory resets and app uninstalls.
4. **Protect the vehicle.** Tell your insurer and the repair shop that the vehicle may contain evidence, and ask that it not be repaired, sold, or salvaged until data can be downloaded.
5. **Request nearby video quickly.** Businesses and traffic systems often overwrite footage within days or weeks.
6. **Send preservation letters.** Address them to the other driver, their insurer, any employer or rideshare company, and other likely data holders, listing specific data categories.
7. **Review your own program terms.** If you are enrolled in a usage-based program, read what is collected and how it may be used.
8. **Be careful with recorded statements.** Stick to facts you know and avoid guessing about speeds, distances, or seconds.
9. **Consider an expert.** In disputed cases, a reconstructionist or digital forensics specialist can download, interpret, and reconcile data from different sources.
10. **Track the deadline.** The statute of limitations keeps running while evidence is gathered, and it varies by state.

Common mistakes

Waiting too long. Detailed data can be overwritten in weeks. Waiting until settlement talks stall can mean the best evidence is gone.

Assuming the police have it. Police reports rarely include telematics or phone data. Officers may not download vehicle modules except in serious crashes, and even then the data may not be shared automatically.

Letting the car be repaired or scrapped. Once a totaled vehicle goes to auction or the crusher, its event data is usually lost forever.

Deleting apps or messages. Even innocent deletions can look like spoliation and can damage your credibility and your case.

Overstating what the data proves. A single number pulled from an app without context can be misleading. Reading data alongside physical evidence avoids embarrassing contradictions.

Ignoring your own exposure. Before relying on the other driver’s data, understand what your own devices and programs recorded.

Making broad consent agreements without reading them. Signing a sweeping authorization can release far more data than the claim needs.

Posting about the crash. Social media posts and check-ins add another layer of digital evidence that can be taken out of context.

Special situations

Rideshare and delivery drivers. These drivers often run one or more work apps that log trip status. That status can affect which insurance policy applies and whether a company may share responsibility, so app records are often among the first items requested.

Employees in company vehicles. Fleet telematics and in-cab cameras can be very detailed. Employers may also have policies on phone use while driving, which can become relevant to the claim.

Teen drivers. Parents sometimes use monitoring apps for teen drivers. Those apps can hold useful data, and preservation requests should consider them.

Crashes with serious injuries or deaths. Law enforcement may seize phones or vehicles and obtain warrants for data. Coordinating with investigators and requesting copies later can be important.

Key takeaways

• Telematics and phone data come from many sources: insurer apps, connected cars, event data recorders, carriers, apps, fleets, and cameras.
• Each source has its own holder and retention schedule, and some data disappears within weeks.
• The data can help or hurt **both** sides, including the injured person.
• **Preservation letters** sent early, and protection of the physical vehicle, are often the most important first steps.
• Privacy laws usually shape how much data is produced rather than barring relevant data entirely.
• Digital data is most persuasive when an expert reconciles it with physical evidence, video, and witness accounts.
• Rules on preservation, privacy, and discovery vary by state. Talk with a licensed local attorney about your specific situation.

*This guide is general information for educational purposes and is not legal advice. Laws, court rules, and data practices vary by state and change over time.*