Free Hardware

Click for details

Why shop with Spytec? Click for details

Most fleet owners ask one question before installing dash cams: "is this legal?" That is the wrong question, and it is why so many fleets get it wrong.

Putting a camera in a work vehicle raises three separate legal questions, governed by three different bodies of law, with three different answers in your state. Video is the easy one. Audio is the one that trips people. And if your cameras face the driver and use AI to flag drowsiness or distraction, there is a third question most fleets have never heard of, and it is the one that has cost other companies millions.

Here is how the three break down in 2026, what changes by state, and the short list of things to do before you record anyone.

This is a practical operations guide, not legal advice. Recording law changes, several states are genuinely contested, and a fleet that crosses state lines can be subject to more than one rule at once. Run your final policy past an employment lawyer in your state.

Spytec GPS is a self-serve GPS fleet tracking platform built for small and mid-size fleets, with free hardware on every plan, no contracts, and transparent pricing from $8.95/vehicle/month on an annual plan. Everything below applies to any driver-facing camera system, including ours.

The three questions hiding inside "are dash cams legal?"

Fleets tend to treat a dash cam as one decision. The law does not. Each of these is a different statute, a different consent standard, and a different penalty if you get it wrong.

The question What governs it How hard is it to comply?
Can I record video of my driver? Privacy tort and reasonable expectation of privacy; a few state monitoring-notice statutes Easy. Company vehicle, written notice, done.
Can I record audio in the cab? Federal Wiretap Act (18 U.S.C. § 2511) plus state consent statutes Harder. About a dozen states require everyone's consent.
Does the camera scan the driver's face? State biometric privacy laws, above all Illinois BIPA Easy to comply, expensive to ignore.

Question 1: video. Almost always fine, with notice

There is no federal law against recording video of an employee driving a vehicle your business owns. The test courts apply is whether the person had a reasonable expectation of privacy, and in a company-owned vehicle during work hours, that expectation is low. Road-facing cameras are essentially never a problem. Cabin-facing cameras are lawful in the great majority of situations, provided you tell people.

Two things narrow this:

  • Off-hours and take-home vehicles. A camera that keeps recording while a tech drives their kid to school on a Sunday is a much weaker case than one recording a Tuesday service route. Define when recording is active, and say so in writing.
  • Personal vehicles. If a tech uses their own truck, you do not own the space you are recording. Do not install a camera in an employee-owned vehicle without separate, explicit, written consent, and expect to negotiate.

A handful of states also impose a general electronic-monitoring notice duty on employers, and this is where a detail catches people out. Connecticut's law (Conn. Gen. Stat. § 31-48d) is written broadly enough to reach video: it covers collection of information about employees "by any means other than direct observation," and requires prior written notice posted conspicuously. New York's much-discussed monitoring law (Civil Rights Law § 52-c) sounds similar but is narrower than most summaries suggest, covering telephone, email and internet usage only. It does not cover cameras or GPS. Penalties in both states run $500 for a first violation, $1,000 for a second, and $3,000 for subsequent ones.

The practical version: post a notice, put it in the handbook, and collect a signature. If you already run location tracking, you likely have most of this built. Our employee GPS tracking policy template covers the monitoring clause set, and cameras want an addendum to it rather than a rewrite.

Question 2: audio. This is where dash cam laws by state actually bite

Audio is a different statute and a much sharper one, because recording a conversation without the right consent can be a criminal act, not just a civil one.

Federal law (18 U.S.C. § 2511) uses a one-party consent standard: recording is permitted if at least one participant in the conversation consents. States are free to be stricter, and roughly a dozen are. The commonly cited all-party consent states are California, Connecticut, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, New Hampshire, Oregon, Pennsylvania and Washington.

Three of those deserve an asterisk, and the asterisks are the reason a blog table is a bad thing to rely on:

  • Connecticut applies all-party consent to phone recordings, while its criminal statute follows one-party consent for in-person conversations.
  • Oregon requires all-party consent for in-person oral communication but one-party consent for electronic communication, which is a meaningful distinction inside a vehicle.
  • Michigan's statute reads like an all-party rule, but Michigan courts have applied a participant exception since Sullivan v. Gray (1982), so it is generally treated as one-party.

Now apply that to a real fleet. Your tech drives from Philadelphia into New Jersey with a helper in the passenger seat and a customer on speakerphone. Pennsylvania is all-party. New Jersey is one-party. The helper never signed anything. The customer certainly did not.

Which is why the sensible operating rule for a 5 to 50 vehicle fleet is not "look up my state." It is one of these two:

  1. Turn cabin audio off. Most of the safety value in a fleet camera is video and telematics data, not sound. If you do not need audio, disabling it removes an entire category of criminal exposure in one click.
  2. Or get written consent from everyone who rides, in every state you operate in. Not a poster. A signed acknowledgment from each driver and each regular passenger, retained.

Passengers and customers are the part fleets forget. Your driver consenting does not cover the plumber's apprentice or the homeowner who climbs in to point out the problem.

Cameras and tracking, without a contract to sign or a rep to call. The Pulse Vision AI dash cam is $33.33/vehicle/month on an annual plan ($399.95/year), hardware included, with a 30-day money-back guarantee. GPS trackers start at $8.95/vehicle/month annual.

See transparent fleet pricing →

Question 3: biometrics. The expensive one nobody warns you about

This is the question that separates a 2026 guide from a 2019 one, and it exists because of AI.

Modern fleet cameras do not just record the cab. They analyze it. Drowsiness detection, distracted-driving alerts and driver identification work by measuring facial geometry. Under Illinois' Biometric Information Privacy Act (BIPA), a scan of face geometry is a biometric identifier, and collecting one without following the statute is actionable.

BIPA requires a private entity to do three things before collection: inform the person in writing that biometric information is being collected and stored, tell them the specific purpose and the length of time it will be collected and stored, and obtain a written release. That is it. It is not hard. It is just easy to skip when nobody told you the camera was doing face geometry at all.

The cost of skipping it is the point. BIPA carries statutory damages of $1,000 per negligent violation and $5,000 per intentional or reckless violation, plus attorneys' fees, and, uniquely among biometric statutes, a private right of action. Individuals sue directly, and they sue as classes.

This is not theoretical for fleet cameras. In July 2025, Samsara agreed to a $3.95 million settlement of a class action alleging its dual-facing dash cameras collected drivers' facial biometric data without the required disclosures and written consent; the class covered drivers in Illinois from December 2016 to June 2025, and included both employees and independent contractors. Samsara denied wrongdoing. Separately, an Illinois appellate ruling in Lewis v. Maverick Transportation and Lytx held that BIPA applies to every capture and use of a biometric identifier, not only the first time a company obtains it, which is what turns a per-driver problem into a per-incident one.

Two other states regulate biometrics directly, and the difference matters more than the similarity:

  • Texas (CUBI) requires notice and consent and carries penalties up to $25,000 per violation, but only the Attorney General can enforce it. No class actions.
  • Washington (RCW 19.375) requires notice and consent for commercial collection, also Attorney General enforcement only.

Colorado and the other comprehensive state privacy laws treat biometric data as sensitive and generally require opt-in consent, but none of them hands an individual driver a statutory damages claim. Illinois does. If you run driver-facing AI cameras and you have a single vehicle that operates in Illinois, treat BIPA as the standard you build to.

The honest version for our own product

The Pulse Vision AI dash cam includes cabin-facing AI that flags distracted and drowsy driving. That is the same category of functionality at issue in the cases above. We are not going to tell you that buying from us makes the question go away, because it does not. What we will tell you is that the compliance step is a one-page written release you collect once per driver, and that any vendor who lets you switch on driver-facing AI without mentioning it is doing you a disservice.

What to do before you record anyone

A working checklist for a small service fleet, in the order it should happen:

  1. Decide whether you need cabin audio at all. If not, disable it and delete an entire risk category.
  2. Find out whether your camera does face geometry. Ask the vendor in writing. "Does this product collect or analyze biometric identifiers, including facial geometry?" If the answer is yes or unclear, you need a BIPA-shaped release.
  3. Write one camera policy. What is recorded, when recording is active, where footage is stored, how long it is kept, who can view it, and what it will and will not be used for.
  4. Collect a signed acknowledgment from every driver. Not a poster, not a handbook page nobody opened. A signature, dated, retained.
  5. Add a separate written release for biometrics if driver-facing AI is on, naming the purpose and the retention period.
  6. Set a retention schedule and actually follow it. Indefinite retention is its own exposure, and BIPA specifically requires a published retention and destruction schedule.
  7. Handle take-home and personal vehicles explicitly. Different rules, different consent, put it in writing.
  8. Have an employment lawyer in your state read it once. An hour of review against $1,000 to $5,000 per violation is not a close call.

Most of this is the same discipline that makes location tracking work without a mutiny. If you have not built that layer yet, start with employee GPS tracking laws by state, which covers the location half of the same problem, and the liability case for commercial dash cams, which covers why fleets take this on in the first place.

Frequently asked questions

Are dash cams legal in company vehicles?

Yes. Recording video inside a vehicle your business owns is lawful in every state, because an employee has a limited reasonable expectation of privacy in a company vehicle during work hours. The conditions are practical rather than legal in most places: give written notice, define when recording is active, and treat take-home and personally owned vehicles as separate cases. Connecticut adds a specific employer notice duty broad enough to cover video.

Do I need employee consent to record audio in a work truck?

Often, yes. Federal law permits recording with one party's consent, but roughly a dozen states require consent from everyone recorded, including California, Florida, Illinois, Massachusetts, Pennsylvania and Washington. Because a fleet crosses state lines and carries passengers who never signed anything, the practical choices are to disable cabin audio or to collect written consent from every driver and regular passenger in every state you operate in.

What is BIPA and does it apply to my dash cam?

The Illinois Biometric Information Privacy Act regulates the collection of biometric identifiers, including scans of facial geometry. It applies to your dash cam if the camera analyzes the driver's face, which is how drowsiness detection, distraction alerts and driver identification generally work. BIPA requires written notice of collection, disclosure of the purpose and retention period, and a written release before collection. It carries $1,000 per negligent violation and $5,000 per intentional violation, plus attorneys' fees, and individuals can sue directly.

Which states have biometric privacy laws that affect fleet cameras?

Illinois, Texas and Washington have dedicated biometric statutes. Illinois is the one that drives litigation, because it is the only one with a private right of action. Texas allows penalties up to $25,000 per violation but is enforced solely by the Attorney General, and Washington is likewise Attorney General enforcement only. Colorado and other comprehensive privacy laws classify biometric data as sensitive and require opt-in consent without creating individual damages claims.

Can I put a dash cam in an employee's personal vehicle?

Not without separate, explicit written consent, and you should expect that conversation to be a negotiation. You do not own the space you would be recording, the reasonable expectation of privacy is far higher than in a company truck, and off-hours recording of a personal vehicle is difficult to justify. Many fleets solve this by tracking company-owned assets instead, or by limiting recording to defined work hours.

Does a poster in the break room count as notice?

For general video monitoring in some states, a conspicuously posted notice is part of what the statute asks for. For audio consent and for biometrics it is not enough. BIPA requires a written release from the individual, and all-party audio consent means each recorded person agreeing. Collect signatures, date them, and keep them.

The bottom line

Dash cam compliance is not one question with fifty answers. It is three questions, and they get progressively easier to get wrong and more expensive to ignore. Video is largely a notice problem. Audio is a state-by-state consent problem with criminal edges, and the cleanest fix is usually to switch it off. Biometrics is the one that produced a multi-million-dollar settlement against a major fleet camera vendor, and it is also the one that a single signed page per driver resolves.

The fleets that get burned here are not the ones that thought about it and chose wrong. They are the ones that installed cameras assuming it was a single yes-or-no question, and never learned their camera was reading faces.

Cameras and GPS on one platform, bought like software should be bought. Free hardware on every plan, no contract, self-serve checkout, 2-day shipping and a 30-day money-back guarantee. No sales calls and no demos required.

Shop fleet trackers and cameras →

Sources: 18 U.S.C. § 2511; 740 ILCS 14 (Illinois BIPA); Tex. Bus. & Com. Code § 503.001 (CUBI); RCW 19.375 (Washington); Conn. Gen. Stat. § 31-48d; N.Y. Civil Rights Law § 52-c; Lewis v. Maverick Transportation and Lytx (Ill. App.); reported terms of the 2025 Samsara BIPA class settlement. Last reviewed September 2026. Not legal advice.

This section doesn’t currently include any content. Add content to this section using the sidebar.