New York electronic monitoring law: notice duties for fleets and warehouses

What does New York's electronic monitoring law require?#

New York's electronic monitoring law requires an employer with a place of business in the state that monitors employees' telephone, email or internet access or usage to tell them in writing. The notice is given at hiring, the employee acknowledges it in writing or electronically, and the employer posts it in a conspicuous place.

The law sits in New York's Civil Rights Law and describes monitoring through any electronic device or system. It carves out certain processes that manage the type or volume of email, voicemail or internet use and are not aimed at a particular person, such as routine system maintenance and protection. Counsel should read the current text against your tools, because the limits of that exception matter.

For fleets and warehouses, the hard part is rarely the email monitoring the law plainly covers. It is the long list of operational tools that also record what employees do on the road and on the floor.

Which fleet and warehouse tools may be in scope?#

Fleet and warehouse tools fall along a spectrum, from systems that plainly monitor communications to devices whose relation to the law needs a legal read. The table sorts common tools by how directly they connect to telephone, email or internet use.

Because the boundaries are not settled for every device, many employers write one monitoring notice that names all of these categories. Over-inclusion costs little; a missing category leaves a notice that does not match practice.

A notice checklist for telematics, cameras and WMS tracking#

A workable notice checklist turns the law's three duties into tasks that HR, safety and IT can each own. Run it when the notice is first drafted and again whenever a new tool goes live or a vendor adds a feature such as in-cab AI alerts.

• 1Inventory every monitoring tool by department: IT, dispatch, safety, warehouse operations and facilities.
• 2Describe each tool by category and purpose in plain words, such as vehicle location, in-cab video or scanner activity.
• 3State that monitoring may cover telephone, email and internet access or usage through company devices and systems.
• 4Deliver the notice at hiring, before or with the first assignment, for drivers, warehouse associates and office staff alike.
• 5Collect an acknowledgment in writing or electronically, and record which notice version was signed.
• 6Post the notice where employees will see it: break rooms, driver lounges, dock offices and the HR portal.
• 7Assign an owner to update the notice when tools change, and decide with counsel whether current staff should acknowledge revisions.
• 8Coordinate with call recording, biometric and camera audio rules, which may impose separate requirements.

How should acknowledgments be stored?#

Acknowledgments should be stored as dated records tied to a specific notice version, in the same system that holds the employee's onboarding file. An unsigned PDF in a shared drive shows nothing about who saw what.

Most employers use the onboarding module of their HRIS or an e-signature tool. Each record should carry the employee ID, the date, the notice version and the delivery channel. For drivers hired at a terminal with paper packets, scan the signed page into the same record so there is one place to look.

Keep evidence of the posted notice as well, such as a facility checklist or dated photo. If a question arises, the employer will want to show that all three duties were met, not only the signature.

Monitoring notice is not permission to reuse the records#

A monitoring notice tells employees that the employer watches certain activity; it does not by itself authorize new uses of what was recorded. Using dashcam events, dispatch messages or WMS logs for analytics, AI tools or data licensing raises separate questions about employee privacy notices, other state laws and contracts.

Employees in other states may have their own rights. California's privacy law, for example, may apply to employee data now that its temporary employee exemption expired on January 1, 2023, and biometric laws can reach some camera features regardless of any monitoring notice. Before any reuse, counsel should compare the employee privacy notice, the monitoring notice and the intended purpose, then decide whether updates or exclusions are needed.

The fleet and warehouse records most useful outside the company rarely need personal detail. Exception notes, dispatch decisions and inventory corrections can usually be prepared with driver and associate identifiers replaced.

Illustrative: a carrier rewrites its notice before a records review#

Illustrative: a fictional regional less-than-truckload carrier runs a cross-dock in upstate New York and a fleet with telematics units and dual-facing cameras. Its onboarding packet still carries an email and internet monitoring notice drafted before the cameras were installed.

As the company starts asking whether its exception and claims records could be licensed, its general counsel lines the notice up against the tools actually in use. Cameras, in-cab messaging and RF scanners are missing. HR issues a revised notice listing each category, collects electronic acknowledgments through the HRIS, posts the notice in the driver lounge and dock office, and on counsel's advice asks current staff to acknowledge the revision.

The licensing review proceeds on its own track. Camera video and call recordings are excluded outright. Shipment exception and OS&D records from the TMS remain in scope, with driver names and IDs replaced before any sample leaves the company.

How SourceX treats monitoring-derived records#

SourceX treats records produced by monitoring tools as high-sensitivity sources that need a rights decision before anything else. In the SourceX five-step transaction, the Rights step reviews monitoring and privacy notices, and the Preparation step removes personal details such as names, driver IDs and location trails tied to a person.

Each approved package carries a SourceX Evidence Packet whose privacy record notes which monitoring sources were excluded and why, giving the supplier's counsel a written trail of the decision.