How Long Should Fleets Keep GPS Tracking Data?

Why GPS Data Retention Is More Than a Storage Question

The real question is not how much storage your tracking provider includes. The real question is what your fleet may need to prove later.

Deleting GPS data too early can remove evidence needed for an accident investigation, an IFTA audit, an insurance claim, or a customer dispute. Keeping every raw signal indefinitely creates the opposite problem. It increases privacy exposure, expands the records available during discovery, and creates storage costs without necessarily improving fleet decisions.

The volume also creates a management problem. Industry reporting from late 2025 suggested that 68 percent of fleet managers felt overwhelmed by the amount of raw data reaching their dashboards. The solution is not automatically more storage. It is a retention structure that keeps useful information available while removing data that no longer serves a clear purpose.

The Retention Timelines That Actually Apply to Fleet GPS Data

FMCSA and ELD Records: The Six Month Floor

Under 49 CFR 395.8, covered motor carriers must retain records of duty status for at least six months. Supporting ELD records must also remain available in a form that allows officials to review them when requested.

This six month period applies to required ELD and hours of service records. It does not mean every GPS point from a truck only needs six months of storage. A vendor may keep ELD information, location history, and supporting documents on different schedules.

That distinction matters because an ELD account can remain active while older location data disappears. Industry reporting cited more than 500,000 hours of service violations in 2025, which reinforces the need for reliable records and clear access procedures.

IFTA Mileage and Fuel Tax Records: Four Years Minimum

The International Fuel Tax Agreement requires carriers to retain records supporting quarterly fuel tax returns. The IFTA procedures manual states that these records generally must be retained for four years from the date the return was due or filed, whichever applies under the governing rule. See the IFTA record retention requirements.

GPS derived mileage can support distance traveled by jurisdiction, but only when the data is accurate, complete, and connected to the correct vehicle. A tracker that stores only a short window of raw history may not satisfy an audit if the fleet cannot recreate its reported mileage.

For this reason, fleets should preserve mileage summaries, jurisdiction totals, supporting trip records, and fuel documentation for at least four years. Fleets combining IFTA and IRP obligations may choose a longer internal period, often about six and a half years, after consulting their tax and compliance advisers.

Litigation and Insurance: Match the Applicable Limitation Period

FMCSA rules require six months of ELD records, but personal injury claims in many states can remain possible for two or three years. GPS data can show location, speed, route, stopping behavior, and whether a vehicle was operating within an assigned area.

The key legal issue is preservation. A fleet may have a duty to preserve relevant data when litigation becomes reasonably anticipated, not only after receiving a complaint. Once an accident, demand letter, serious injury, or credible dispute creates that possibility, normal deletion rules should be suspended for relevant records.

A practical process should preserve:

• Raw location history for the relevant vehicle and time period
• Driver behavior events connected to the incident
• Trip summaries and route details
• Inspection, maintenance, and repair records
• Camera footage and communications related to the event

A fleet dash camera record may also become important when GPS data cannot explain what happened. Store related records together and document who placed the preservation hold.

Privacy Laws Fleet Managers Cannot Ignore

CCPA, State Laws, and the Consent Requirement

Privacy rules do not usually provide one universal GPS retention period. They focus on notice, purpose, access, protection, and whether the collection and retention of personal information remain reasonably necessary.

The California Privacy Protection Agency explains that data collection, use, retention, and sharing should be reasonably necessary and proportionate to the stated purpose. Its data minimization enforcement advisory warns that keeping unnecessary personal information increases privacy and security risks.

Do not assume that January 1, 2026 created a universal employer GPS risk assessment requirement for every fleet. Instead, document why tracking is used, what information it collects, who can access it, and when it will be deleted. Also review state rules. At least 10 states now have laws or rules that can require employee notice or written disclosure for certain forms of workplace tracking.

California also restricts certain forms of vehicle location monitoring through Penal Code section 637.7. Fleets should review the California vehicle tracking statute and obtain legal advice for their operating locations.

Off Hours Tracking and Data Minimization

Tracking a company vehicle outside working hours can create employee privacy concerns, especially when a vehicle is assigned to one driver or permitted for personal use. A fleet should either pause tracking outside approved work periods or clearly disclose continuous monitoring.

A sound privacy review should answer these questions:

• Is the vehicle used only for business?
• Does the driver receive written notice?
• Can tracking pause during approved personal use?
• Does every manager need access to precise location history?
• Can older raw data be replaced with a less detailed summary?

How Much Data Are You Actually Storing?

A connected vehicle can process up to 25 gigabytes of data per hour, according to McKinsey research. That figure includes much more than GPS location data, but it shows why fleets should distinguish between vehicle generated data and the smaller amount they need to retain.

A 100 vehicle fleet may generate roughly 2 to 5 gigabytes of tracking data each month depending on update intervals, connected cameras, and event settings. Over four years, the volume becomes significant.

Raw pings are valuable during an investigation but often unnecessary for ordinary reporting. A fleet reports dashboard can help managers work from summarized trends while preserving detailed records only when they serve a defined purpose.

Building a GPS Data Retention Policy That Works

Match Retention Windows to Data Type

A single deletion rule rarely works because GPS data supports different jobs. Use three broad categories:

• Operational data: 90 days to one year
• Compliance data: six months to four years
• Litigation sensitive data: the longest applicable limitation period or legal hold

For example, a route history used to resolve a delivery question may not need four years of raw pings. Mileage summaries supporting IFTA should receive a longer period. A collision record should remain preserved until the claim and any related legal risk have ended.

Automate Retention and Deletion Cycles

Manual deletion is easy to forget and difficult to prove. Configure your tracking platform to archive or delete records based on the written schedule.

Centralized fleet software can reduce the problem of managing separate retention settings across GPS providers, inspection apps, maintenance systems, and shared folders. Connect retained trip history with the trip mileage tracking feature and keep supporting vehicle records in a controlled location.

Document Your Policy Before You Need It

A written policy should identify:

• Each data type collected
• The business purpose for collecting it
• The retention period
• Authorized users
• Archive and deletion methods
• Legal hold procedures
• Review dates for updating the policy

A consistent policy gives your fleet a stronger explanation during an audit, insurance review, employee complaint, or lawsuit than ad hoc deletion decisions.

What Happens When You Get Retention Wrong

Deleting too early can cause:

• Missing evidence during accident disputes
• Incomplete IFTA support
• Problems responding to an FMCSA inquiry
• Loss of evidence that could clear a driver
• Spoliation arguments during litigation

Keeping data too long can cause:

• Larger discovery requests
• Increased privacy exposure
• More damage if a breach occurs
• Higher storage and administration costs
• Unclear access responsibilities

Before deleting any GPS data, confirm the following workflow:

1. Confirm that no litigation or reasonably anticipated claim exists.
2. Confirm that the applicable IFTA period has ended.
3. Confirm that the six month ELD minimum has been satisfied.
4. Confirm that the insurance carrier does not require preservation.
5. Confirm that no legal hold applies.
6. Apply the documented privacy deletion schedule.
7. Record what was deleted, when, and under which policy rule.

Final Thoughts

GPS data retention is a risk management decision, not simply a storage decision. Keep enough detail to satisfy audits, defend legitimate claims, investigate incidents, and support operational decisions. Then delete or summarize information that no longer has a clear purpose.

Start by reviewing your current provider settings. Compare them with your IFTA, ELD, insurance, litigation, and privacy requirements. If no written policy exists, create one before the next accident or audit forces the decision.