Is It Legal to GPS Track Security Guards?

GPS tracking security guards legal questions answered: on-duty tracking, employee GPS consent requirements, and a policy outline. Get the operator's guide.

Joe Juarez — Co-founder & CEO

Published July 12, 2026 Updated July 23, 2026 6 min read

I run a 400+ employee guard company that GPS-verifies clock-ins and patrols every day across four markets. When operators ask me "is it legal to GPS track guards," what they're really asking is "how do I do this without creating a lawsuit." Here's the frame we use. It's operator guidance, not legal advice.

What's the Legal Frame for GPS Tracking Employees?

The general US picture, stated as the general picture:

• On-duty tracking for business purposes is broadly accepted. Courts and regulators have consistently treated location monitoring of employees during work hours, on employer-provided devices or work applications, for legitimate operational reasons — verifying service delivery, safety, dispatch — as a reasonable exercise of employer authority. In security specifically, location verification isn't surveillance for its own sake; it's the product. Clients pay for proof that patrols happened, and GPS is how that proof exists.
• Consent and disclosure are the best practice everywhere and the requirement in some places. A number of states impose notice or consent obligations around employee monitoring and location tracking, and the trend line is toward more disclosure requirements, not fewer. Rather than maintaining a 50-state matrix, the durable strategy is simple: disclose clearly and get written consent from everyone, in every state. Then variations in state law mostly stop mattering to your day-to-day.
• Off-duty tracking is where the danger lives. The legal and ethical picture changes completely when an employer tracks location outside working hours or on personal devices without tight controls. Nearly every employer GPS controversy you've read about involves off-the-clock tracking. Don't do it, and build your system so it can't happen by accident.

One more distinction worth naming: tracking a company vehicle the employer owns is generally the most settled scenario; tracking through an app on a guard's personal phone is the scenario that demands the clearest consent and the strictest on-duty-only behavior, because the device belongs to the guard.

What Should an Employee GPS Consent Policy Cover?

A good policy is short, specific, and signed. It should answer, in plain language, the five questions a guard (or a plaintiff's attorney) would ask:

1. What is tracked — location via the work app or device, during clocked-in hours, including clock-in/out coordinates and patrol checkpoints
2. When — from clock-in to clock-out only, never off shift
3. Why — verifying service to clients, guard safety, dispatch, payroll accuracy
4. Who sees it — supervisors and management; what clients see (patrol verification, not a live personal feed); how long data is retained
5. What it's not used for — no off-duty monitoring, no tracking on personal time, no collection beyond the stated purposes

Get it signed at hire, alongside the rest of onboarding paperwork, and keep the signed copy in the guard's file — this is one of the personnel records that matters when questions come later. Re-acknowledge if the policy materially changes. At Ranger Guard, GPS consent is simply part of the standard hire packet in all four of our markets; treating it as routine paperwork, explained plainly, is exactly what keeps it uncontroversial.

Why Does "On the Clock Only" Matter So Much?

Because it's the line that separates service verification from surveillance — legally, ethically, and in your guards' minds.

Technically, this means the tracking architecture itself should enforce the boundary, not just the policy document. SNTNL's GPS and geofence clock-in is built on that principle: location verification is tied to the duty period — clock-in confirms the guard is on site, patrol checkpoints verify presence during the shift, clock-out ends it. There is no off-shift tracking to police because there's no off-shift tracking, period.

That architecture answers the question guards actually ask — "can my boss see where I am on Saturday?" — with a structural no instead of a promise. It's the difference between "we won't" and "we can't", and it's why our guards across 400+ employees treat GPS verification as a normal part of the job rather than an intrusion.

How Does GPS Tracking Protect the Guards Themselves?

This is the part operators under-sell to their workforce, and it's the strongest card in the deck. GPS records cut both ways, and in practice they cut in the guard's favor constantly:

• False accusations. "Your guard was sleeping in his car" and "your guard never patrolled the north lot" are accusations every guard company hears. A GPS trail with checkpoint scans is the guard's alibi — time-stamped, third-party, unfakeable in either direction. At Ranger Guard, patrol verification data has repeatedly resolved client accusations in the guard's favor; the record showed the rounds happened, and the conversation ended there.
• Payroll accuracy. GPS-verified clock-in means the hours a guard worked are the hours a guard is paid for — no disputes about arrival times, no supervisor's recollection deciding a paycheck.
• Safety. A lone guard on an overnight post who stops moving or misses a checkpoint generates an alert. For solo overnight work — a huge share of the industry at guard wages commonly $15–20/hr — that's a welfare check built into the workflow.

Frame tracking honestly as mutual protection, and adoption follows. Frame it as surveillance, and you'll fight your own workforce over a tool that mostly defends them.

What Should a Guard GPS Policy Template Include?

The outline we'd hand a new operator to take to their attorney:

• Purpose statement — service verification, safety, dispatch, payroll
• Scope — what devices/apps, which personnel
• Active period — clock-in to clock-out only; explicit statement of no off-duty tracking
• Data collected — location points, checkpoint scans, timestamps
• Access — internal roles who can view; what clients receive
• Retention — how long location data is kept, consistent with your record-keeping schedule
• Personal-device provisions — if guards use their own phones: app permissions, no access to personal data, what happens at separation
• Consent block — signed and dated acknowledgment, stored in the personnel file
• Change process — how updates are communicated and re-acknowledged

Have counsel adapt it to the states you operate in, then make it standard onboarding paper.

GPS verification is the backbone of proof-of-service — done right, it protects the client, the company, and the guard all at once. If you want to see what consent-based, on-the-clock-only tracking looks like running live across four markets, book a demo and we'll show you ours.

This is general information, not legal advice — verify current requirements with the licensing agency and your attorney.