Is GPS Tracking of Employees Legal? What Crew Owners Should Know
You want to know where your crew clocked in without stepping over a line you cannot see. Here is a careful, general answer on the legality of GPS tracking at work, and how Clox limits location to the punch itself.
You are thinking about turning on location for clock-ins, and a small voice asks whether you are allowed to. Maybe an employee already pushed back. Maybe you just do not want a surprise complaint after you have wired it up. It is a fair question, and it deserves a straight answer instead of a sales pitch.
Here is the short version. In the United States, tracking employees while they are on company time is broadly permitted, but how you do it matters. Consent and notice matter. A handful of states have their own disclosure rules. And the tracking should stay tied to work, not follow people into their evenings. Below is a general walkthrough of those points, followed by exactly how Clox handles location so you can see where it fits.
The general rule in the US
For work done on company time, employers in the US generally have wide latitude to track how and where that work happens. Location tied to a job is treated a lot like other work records. The friction usually is not whether you can track at all. It is whether you told people, whether you had their agreement, and whether the tracking is limited to work rather than sweeping up private life.
Three ideas come up again and again. They are worth understanding before you turn anything on.
Notice: tell people what you collect
A quiet tracker is the fast way to a complaint. Clear notice is the opposite. When your crew knows that a clock-in records location, when it does that, and why, the whole thing reads as a normal part of the job rather than surveillance. Written notice in a handbook or a short policy is a common way to do this, and it is a good habit regardless of what any single state requires.
Consent: get agreement, in writing where you can
Notice tells people. Consent records that they agreed. Some states lean harder on this than others, and a signed acknowledgment is cheap insurance either way. It also tends to lower the temperature of the conversation, because the person knows what they are agreeing to before their first punch, not after.
Limit it to work hours
The strongest position is the narrowest one. If location is captured only when someone is clocking in for work, and never while they are off the clock, you avoid the part that makes people and regulators uneasy. Continuous background tracking that follows a phone around all day is a different animal, with different risks. Keeping location to the work event is both simpler and safer.
How Clox handles location
Clox is built so the honest, narrow answer to the questions above is the default. It captures location at one moment for one reason, and it gives you the switches to make it fit your crew and your state.
Location is captured at the clock-in punch, not continuously
This is the part that matters most for the legal question. Clox does not run a background tracker that follows a phone through the day. It reads location at the moment a worker clocks in or out, checks it against the job site, and that is it. There is no trail of where someone went at lunch, because Clox never asked.
How the geofence itself works is simple. A manager draws a radius around a worksite on a map, with a sensible default around 200 meters that you can adjust. When the fence is enforced for a worker, a clock-in from outside it is blocked at the punch, so the off-site punch is never created. Most tools only warn. Clox blocks.
It can be turned off, and it is per employee
Enforcement is chosen per employee, so a crew that moves between five sites a day is not forced to fight a fence, while a fixed-site crew can be held to one. And if you decide location is not right for your team or your state, you can leave it off entirely. It is a tool you opt into, not a condition of using Clox.
Kiosk punches capture no location at all
If your crew clocks in on a shared tablet with a PIN, that kiosk mode captures no GPS. Identity there comes from the on-site tablet plus each worker's PIN. For teams where personal-phone tracking is a non-starter, this gives you an attendance record with no location data collected.
There is a GPS-consent notice and a privacy policy
Clox includes a GPS-consent notice so your workers see, in plain terms, that a clock-in records location and what that is used for. There is also a published privacy policy covering how data is handled. That does not replace your own state-specific policy or an attorney's review, but it means the notice and consent pieces are not something you have to build from scratch.
The honest limits
Geofencing is a strong deterrent, not a guarantee, and it is worth being clear about why. The location Clox checks comes from the worker's own phone. Clox reads what the device reports. That means a determined person with the right tools can try to feed a phone a false location, the same way they could with any app that trusts the device.
Clox does not pretend otherwise. It leans on that phone-sourced location honestly and adds review flags a manager sees at approval, in priority order: a device that reported a fake or mock GPS provider (mock_location), a punch that is impossibly far from that same worker's previous punch (impossible_travel), and a coarse but in-fence fix (low_accuracy). There is also an accuracy grace so an honest punch just outside the line can still land within the phone's reported accuracy, capped at 100 meters, and those marginal punches are flagged with an off-the-worksite readout for you to review. A fix too coarse to trust is rejected outright.
None of that makes it foolproof, and it is not meant to. It raises the effort required to cheat and puts the odd cases in front of a human. For an honest crew, it quietly confirms people were where they said. For the legal question, the point is narrower and cleaner: location is read at the punch, from the phone, with notice, and nothing is tracked in between.
Common questions crew owners ask
Do I have to tell my crew before I turn it on?
Telling people is the right move regardless of what any single state strictly requires, and in some states it is required. Clear notice up front turns a location feature into a normal part of the timekeeping process instead of something discovered later. Clox's consent notice is designed to be that up-front disclosure, and pairing it with your own written policy is a sound habit.
Can an employee refuse to be tracked?
This is where legal advice and your own policy matter, and it is a question for your attorney rather than a blog post. What Clox gives you is flexibility around it: enforcement is per employee, location can be turned off, and kiosk mode collects none. You are not locked into an all-or-nothing setup while you work out the right policy for your team.
Does Clox track my crew when they are off the clock?
No. Location is read at the clock-in or clock-out punch and not in between. There is no background tracker running through the day. That narrow footprint is the whole design, and it is the main reason the general rules above are easier to satisfy with Clox than with continuous tracking.
Is this just a geofencing tool?
No. Clox is time tracking for field crews in general. You get one-tap clock-in, overtime and breaks calculated automatically, and payroll-ready exports for QuickBooks, Gusto, ADP, and Paychex. Geofencing is one feature you can switch on when it fits, not the entire product. You can see the full picture on the pricing page.
Where this leaves you
Tracking work on company time is broadly allowed in the US, and the way you stay on the right side of it is by giving notice, getting consent, and keeping location tied to work. Clox is built around that narrow footprint by default: location at the punch only, off when you want it, none in kiosk mode, with a consent notice and privacy policy included. Confirm your state's rules and run your policy past counsel, then decide what fits your crew.
If you want to see how it behaves before committing, you can start a trial. It is 14 days free with no credit card to start, backed by a 30-day money-back guarantee. You can start a free trial and try a clock-in from a phone browser at app.getclox.com, with an iPhone app available on a TestFlight beta.