A company vehicle GPS tracking policy holds up legally when it does six things: identifies the vehicles and data being tracked, states a legitimate business purpose, defines whether tracking runs only during work hours or around the clock, gives employees written notice they sign before driving, addresses any audio or biometric collection separately, and spells out how tracking data will be used for discipline, tax reporting, and wage calculations. Everything else in a good policy is detail built on those bones.
What the Policy Must Say
Vague references to “monitoring company property” won’t satisfy state notification statutes and won’t hold up in litigation. A policy needs specifics.
Purpose and Scope
State in plain terms why the company tracks its vehicles. Typical reasons include verifying driver safety, optimizing routes, preventing theft, and confirming that vehicles are used only for authorized purposes. Purpose matters legally because courts evaluate whether tracking served a legitimate business interest when privacy claims arise. The scope section should identify which vehicles are covered by VIN or plate number and whether tracking applies only during work hours or continuously.
Data Collected
Employees should know exactly what the system records. Most fleet GPS platforms collect real-time location, speed, engine idling time, harsh braking events, and route history. If the system also logs fuel consumption, diagnostic codes, or driver behavior scores, list those too. If the vehicle carries a dashcam or in-cab camera, the policy has to say so and describe what the camera captures.
Retention and Access
State how long the company keeps GPS data. No single federal regulation mandates a specific retention period, so the right answer depends on insurance requirements, litigation hold obligations, and operational needs. Whatever period you choose, put it in writing and stick to it. Retaining data indefinitely creates unnecessary liability; deleting it too quickly may destroy evidence needed for an accident investigation or wage dispute.
Name the roles authorized to view tracking logs, such as fleet managers, safety directors, or HR. Limiting access prevents misuse of location history and reduces the chance that sensitive movement data gets shared informally within the organization.
Tampering and Consequences
Employees need to understand what happens if they disable, obstruct, or physically remove a GPS device. Most policies treat tampering as a serious offense because a non-functioning tracker defeats the program and may indicate unauthorized use. A common approach is a written warning for a first offense and suspension or termination for repeat violations, though some companies treat any intentional tampering as grounds for immediate termination. Spell out the consequences rather than leaving them to management discretion.
Written Notice and Signed Acknowledgment
A growing number of states require employers to give written notice before electronically monitoring employees, and some specifically address GPS devices in employee vehicles. States with explicit notification requirements include Connecticut, New York, Delaware, New Jersey, California, and Texas, among others. Penalties for skipping notice range from $100 per violation at the low end up to $3,000 per violation for repeat offenses, and New Jersey’s tracking-device statute imposes fines of up to $1,000 for a first violation and $2,500 for each subsequent one.
Any employer running a fleet across state lines needs to check the notification rules in every state where its vehicles travel, because the obligation typically triggers wherever the vehicle operates, not just where the company is based. Designing the policy around the strictest state requirements means fewer headaches when vehicles cross borders. Most of these statutes share the same core features: notice in writing or electronic form, acknowledgment of receipt, and an exemption for criminal investigations or non-targeted system maintenance.
Distribute the finished policy through the employee handbook, a standalone notice, or both. The goal is documentation: you need to prove every driver received the policy and acknowledged it before getting behind the wheel. Electronic signature platforms create a time-stamped audit trail that holds up better than a paper sign-in sheet. For new hires, acknowledgment should be part of onboarding, completed before they receive vehicle keys.
Federal recordkeeping rules vary by document type. The EEOC requires private employers to retain personnel records for one year from the date of the record or the personnel action, and for one year after involuntary termination.1U.S. Equal Employment Opportunity Commission. Summary of Selected Recordkeeping Obligations in 29 CFR Part 1602 The FLSA requires payroll records for three years.2U.S. Equal Employment Opportunity Commission. Recordkeeping Requirements GPS tracking acknowledgments don’t fit neatly into either category, so the conservative approach is to keep signed acknowledgments for the duration of employment plus at least three years to cover the statute of limitations on most employment claims.
Off-Duty Hours and Personal Use
Tracking a company vehicle during working hours is legally defensible in virtually every jurisdiction. Tracking it during an employee’s personal time is where claims gain traction. Courts have drawn a meaningful line between knowing where a company asset is during the workday and surveilling an employee’s movements during evenings, weekends, and vacations.
In Cunningham v. New York Department of Labor, the New York Court of Appeals held that a GPS search was unreasonable in scope because the employer made no effort to avoid tracking the employee outside business hours. The court concluded that when an employer installs GPS without limiting it to work time, the search as a whole must be considered unreasonable. The case involved a government employer and constitutional analysis, but the logic applies broadly: if your policy doesn’t address off-duty hours, you’re collecting data you may not be entitled to.
The practical fix most employment attorneys recommend is to let employees disable the device or stop tracking when they go off the clock, or to configure the system to log only during defined work hours. If the vehicle stays with the employee overnight, the policy should explicitly state whether tracking continues and why. “We track the vehicle 24/7 to prevent theft” is a defensible reason. Silence on the question is not.
Audio, Dashcams, and Biometric Data
Many modern fleet systems go beyond location tracking. Forward-facing and cabin-facing dashcams, AI fatigue detection, and audio recording each introduce legal obligations a basic GPS policy doesn’t cover.
If the system records audio inside the cabin, federal wiretap law requires at least one-party consent, and roughly a dozen states require all-party consent. The safest approach is written consent from every employee who drives a vehicle with audio recording capability. A handbook notice alone may not be enough. Courts construe the federal Wiretap Act strictly against employers, and the burden is on the company to prove the employee received notice and agreed.3Office of the Law Revision Counsel. 18 USC 2511 – Interception and Disclosure of Wire, Oral, or Electronic Communications Prohibited Statutory damages run to $100 per day of violation or $10,000, whichever is greater, plus attorney’s fees.4Office of the Law Revision Counsel. 18 USC 2520 – Recovery of Civil Damages Authorized
Dashcams that use facial recognition or scan facial geometry to detect drowsiness may trigger biometric privacy laws. Illinois, Texas, and Washington have specific statutes governing biometric data collection. Illinois imposes statutory damages of $1,000 per negligent violation and $5,000 per intentional or reckless violation. An employer based in another state can still be reached by these laws if the dashcam collects biometric data while the vehicle operates within a covered state. Any policy governing AI cameras should include a separate biometric notice, a written consent form, a retention schedule, and a destruction protocol.
Tax and Wage Effects the Policy Should Address
GPS data doesn’t just manage the fleet. It also feeds tax compliance and wage calculations, and the policy should acknowledge both uses.
When an employee uses a company vehicle for personal driving, including commuting, the IRS treats the value of that personal use as a taxable fringe benefit that must appear on the W-2.5Internal Revenue Service. Publication 15-B (2026), Employer’s Tax Guide to Fringe Benefits Any use that isn’t substantiated as business use gets included in income. The IRS offers three simplified valuation methods alongside the general fair-market-value approach:6Internal Revenue Service. Publication 15-B (2026), Employer’s Tax Guide to Fringe Benefits
- Cents-per-mile rule: multiply the IRS standard mileage rate by total personal miles driven. For 2026, the business standard mileage rate is 72.5 cents per mile. This method is only available if the vehicle’s value when first made available for personal use doesn’t exceed the IRS maximum automobile value for the year.7Internal Revenue Service. IRS Sets 2026 Business Standard Mileage Rate at 72.5 Cents Per Mile, Up 2.5 Cents
- Commuting rule: value each one-way commute at $1.50 per trip. Available only if the employer has a written policy prohibiting personal use other than commuting and the employee isn’t a control employee (officer or highly compensated).
- Lease value rule: uses IRS annual lease value tables based on the vehicle’s fair market value, multiplied by the percentage of personal use.
GPS logs make substantiation straightforward because the system creates an automatic record of business versus personal miles. Handwritten mileage logs are notoriously incomplete and hard to verify during an audit. State in the policy that GPS records may be used to calculate the taxable value of personal use and that employees are responsible for reporting any discrepancies.
For non-exempt drivers, GPS data can become evidence in wage and hour disputes. Under the Fair Labor Standards Act, travel between work sites during the workday is compensable time. Commuting in a company vehicle is generally not compensable under the Portal-to-Portal Act, but only if five conditions are met: the vehicle is a type normally used for commuting, the employee uses a normal commuting route, the employee doesn’t incur additional costs, the travel is within the employer’s normal commuting area, and the use is subject to an agreement between the employer and employee.8Office of the Law Revision Counsel. 29 USC 254 – Relief From Certain Activities Not Compensable A written GPS policy addressing commuting use helps satisfy that last requirement.
GPS data cuts both ways. It can confirm an employee was on the road during claimed work hours, but it can also reveal unreported hours the employer should have paid. If the system shows a driver leaving the yard at 6:15 a.m. but the timesheet says 7:00, the employer has constructive knowledge of those 45 minutes. Ignoring GPS data that contradicts timesheets is a fast track to a wage claim.
Unionized Fleets
Employers with unionized drivers face an extra step before rolling out GPS tracking. The National Labor Relations Board has held that implementing GPS surveillance is a mandatory subject of bargaining. Introducing tracking without negotiating with the union first can constitute an unfair labor practice, even when the underlying decision to track vehicles is otherwise legal.
The NLRB has also scrutinized selective deployment. In a 2003 memorandum, the General Counsel found that installing GPS units in only two of eight company trucks, both driven by known union organizers, violated the National Labor Relations Act because the selective surveillance interfered with employees’ rights to organize.
Collective bargaining agreements often include GPS provisions that go beyond what statute requires: advance notice before new tracking technology is introduced, restrictions limiting GPS data to safety purposes only and prohibiting its use for discipline or productivity monitoring, and employee rights to access their own tracking data. Any employer with a collective bargaining agreement should review it before installing a single device.
Third-Party Vendors
Most companies don’t build their own tracking systems. They contract with a fleet telematics vendor that hosts data on its own servers, creating a data-sharing arrangement the policy should acknowledge and the vendor contract should address.
At minimum, the vendor agreement should cover who owns the data, what security standards the vendor maintains, whether the vendor can use or sell the data for its own purposes, what happens to the data when the contract ends, and how the vendor will notify the employer of a data breach. If the fleet operates in states with biometric laws and the system includes facial recognition, the contract needs to address biometric data handling separately.
Tell employees in the policy that a third party stores and processes the location data. Some state privacy laws explicitly require disclosure of third-party sharing, but even where they don’t, transparency about who holds the data reduces the chance an employee’s privacy claim survives a motion to dismiss.
Reviewing and Updating the Policy
Review the policy annually. GPS technology evolves, state legislatures pass new privacy laws, and fleet composition changes. A policy written in 2024 that doesn’t address dashcam AI or biometric data is already behind. Each update should trigger a fresh round of acknowledgments for anyone affected by the changes, using the same signed, time-stamped process as the original rollout.