Resource · Data retention
Worker location data retention: how long to keep it and when to delete it
Keep the time records that prove hours worked for at least the period wage law requires, which is three years under California Labor Code 1174 and the federal payroll rule, and longer where a claim could still be filed. Delete raw location (exact positions and scan data) on a short schedule you can explain, because privacy law expects you to keep personal data no longer than reasonably necessary.
Last updated By ZeroBadge
This is general information, not legal advice. Laws differ by state and change over time. Check the primary sources below and talk to an employment lawyer about your situation.
Is raw location data the same thing as a time record?
No. A time record says that a worker arrived, left and worked a number of hours at a jobsite. Raw location is the material the system used to reach that conclusion: exact coordinates, Wi-Fi scans and cell tower readings, each stamped with a time. The first is the payroll evidence the law tells you to keep. The second is the more sensitive data, and it is rarely needed once a timesheet has been approved and any dispute window has closed.
That difference is what lets you keep two clocks. Time records run on the wage-record clock. Raw location runs on a much shorter clock set by your own purpose for collecting it. Mixing the two, either by keeping every coordinate for years or by deleting the hours along with the coordinates, is the usual mistake.
| Raw location | Derived time record | |
|---|---|---|
| What it is | Exact positions, Wi-Fi and cell scans, each with a timestamp | Arrive time, leave time, hours, jobsite, approved status |
| Why you have it | To work out which jobsite and when | To pay wages and answer a wage claim |
| Sensitivity | High: shows movement through the workday | Lower: shows hours and sites |
| Who needs it later | Almost nobody once hours are approved | Payroll, auditors, the worker, a court |
| Retention driver | Data minimization and your stated purpose | Wage-record rules and limitation periods |
How long does privacy law let you keep worker location data?
Only as long as it is reasonably necessary for the purpose you disclosed. In California, a business may not keep a consumer's personal information or sensitive personal information longer than is reasonably necessary for each disclosed purpose, and it must tell people how long it intends to keep each category or the criteria it uses to decide (Civ. Code 1798.100(a)(3)). California residents who are employees are covered by that law, and precise geolocation is a category of sensitive personal information (CPPA).
The same section says collection, use, retention and sharing must be reasonably necessary and proportionate to the purposes for which the information was collected, and not further processed in a way that is incompatible with them (Civ. Code 1798.100(c)). Proportionate is the word that matters for a retention schedule. If the purpose is paying people for time on site, raw coordinates from three years ago are hard to defend as proportionate.
- Write the purpose first. Retention periods follow from it: verifying hours, resolving disputes, job costing.
- Pick a number for raw data and be ready to explain it. A window long enough to cover pay-period approval and the usual dispute window is easier to justify than a round year.
- Say it in the notice. The worker should be able to read how long raw location is kept and what is kept longer.
- Other states. California is the strictest general statute on this point. Check your own state, and do not assume an exemption for employee data.
What are the minimum retention periods for wage and hour records?
Federal and California rules both set a floor of three years for payroll records, and a shorter federal floor for time cards. The floors are for records of hours and pay. They do not tell you to keep every raw coordinate behind those hours, and the rules say nothing that requires it.
| Source | Records | Minimum period |
|---|---|---|
| 29 CFR 516.5 (federal) | Payroll records containing the employee information the part requires | At least 3 years from the last date of entry |
| 29 CFR 516.6 (federal) | Basic time and earnings cards or sheets showing when each employee starts and stops each day | At least 2 years from the date of the final entry |
| California Labor Code 1174(d) | Payroll records showing the hours worked daily by and the wages paid to employees | Not less than 3 years |
| California Labor Code 226(a) | A copy of each itemized wage statement and the record of deductions | At least 3 years |
| California Labor Code 1198.5(c)(1) | Personnel records an employee may inspect | Not less than 3 years after termination of employment |
Employee access runs on its own clock. When a current or former employee asks to inspect or copy payroll records under Labor Code 226, the employer must respond as soon as practicable and no later than 21 calendar days from the request (Labor Code 226(c)). A record you deleted too early cannot be produced in that window.
Why do some employers keep time records for four years?
Because the period in which a wage claim can be filed can be longer than the record-keeping floor. A federal FLSA claim generally must be filed within two years of when it accrued, or three years for a willful violation (29 U.S.C. 255(a)). California's four-year limit for actions under the unfair competition law (Bus. & Prof. Code 17208) is the reason four years is a common company standard for hours records in that state, because a claim for unpaid wages can be pleaded under it.
Which clock runs out last?
- Federal payroll record floor
- 3 years
- FLSA claim, willful violation
- 3 years from accrual
- California Labor Code 1174(d) floor
- 3 years
- California unfair competition claim
- 4 years from accrual
- A schedule that outlasts all four
- 4 years for time records
Four years is a conservative internal standard, not a statutory requirement. Your counsel may want a different number.
What does a sensible retention schedule look like?
Short for raw location, at least the legal floor for time records, and longer for proof of consent. This is the schedule ZeroBadge applies by default, shown beside the reason for each line so you can set your own.
| Data | Default period | Why |
|---|---|---|
| Raw location (exact positions, Wi-Fi and cell scans) | 30 days, then deleted | Long enough to approve a pay period and settle a short dispute; beyond that it is not needed to prove hours |
| Time records (arrive, leave, hours, jobsite) | 4 years | Covers the 3-year payroll floors and the longer claim windows above |
| Approved timesheets and edit history | At least the same as time records | Shows what was paid and who changed what |
| Consent and acknowledgment records | Life of the account plus 6 years | Proves the worker was told and agreed, including after a worker leaves |
| Access and audit logs | Per your security policy | Shows who viewed location detail and when |
Location readings recorded outside working time should not be kept at all. Working time includes travel while the worker is on the clock, which is paid; readings outside it have no payroll purpose, and a system that never collects them is better than one that collects and later deletes them.
How fast must you answer a worker's deletion request?
Within 45 days of receiving a verifiable request, extendable once by another 45 days when reasonably necessary, provided the worker is told of the extension within the first 45 days (Civ. Code 1798.130(a)(2)). That applies to a covered business responding to a California worker's request under the California Consumer Privacy Act.
The right to delete has exceptions. A business does not have to delete personal information that is reasonably necessary to keep in order to comply with a legal obligation (Civ. Code 1798.105(d)). A wage-record law that requires you to keep hours for three years is such an obligation, so the request can reasonably be handled by deleting raw location and keeping the time record. Say that in your reply, and say why.
- 1
Log the request the day it arrives
Record the date, the worker and what was asked. The 45 days start at receipt.
- 2
Verify who is asking
Confirm the person is the worker or a properly authorized agent before acting.
- 3
Separate raw location from time records
Delete the raw location. Keep the time record that a wage-record rule requires.
- 4
Reply in writing
State what was deleted, what was kept and the rule that requires keeping it. If you need more time, send the extension notice before day 45.
- 5
Check for a hold first
If a claim is pending or anticipated, do not delete data relevant to it. See the next section.
When must you stop deleting?
As soon as a claim, audit or investigation is reasonably anticipated, you should stop deleting the data that could be relevant to it. In federal courts, electronically stored information that should have been preserved in the anticipation or conduct of litigation, and was lost because a party did not take reasonable steps to preserve it, can lead to court-ordered consequences (Fed. R. Civ. P. 37(e)). State courts have their own rules on lost evidence.
- Triggers. A demand letter, an agency inquiry, a wage claim, a threat to sue and a union grievance are all signals. So is a worker disputing a record in writing, if a claim could follow.
- Scope. Hold the data about the people and dates in question, not everything. A narrow hold is easier to defend.
- Suspend the auto-delete for that data. A schedule that keeps running after a claim is anticipated is the failure courts look at.
- Tell the right people. Payroll, IT and your location vendor all need the instruction in writing, with a date.
- Release the hold in writing once counsel confirms the matter is closed, and let the normal schedule resume.
What should you have in place before collecting worker location?
- A written purpose for collecting location, in the worker notice.
- A raw-location retention period, stated in the notice, with automatic deletion.
- A time-record period that is at least the longest wage-record floor in your states.
- A consent record for each worker, kept for the life of the account and after.
- A written procedure for deletion requests with the 45-day and 45-day-extension dates.
- A way to place and release a legal hold that overrides the auto-delete.
- A rule that location is not collected outside working time (scheduled hours plus paid travel while clocked in).
- A log of who viewed location detail, so you can answer who saw what.
Where ZeroBadge fits
ZeroBadge is a company-owned cellular badge worn at work, not an app on a worker's phone. It records which jobsite a worker is at and for how long, and the badge keeps retention short for raw data and longer for the records you need. Raw location (exact positions, Wi-Fi scans and cell scans) is deleted after 30 days. Time records (arrive, leave, hours) are kept 4 years. Consent records are kept for the life of the account plus 6 years. Location readings recorded outside scheduled work hours are discarded automatically unless the worker is still clocked in, such as driving back from a jobsite, which is paid travel time.
Before a badge stores a worker's location, the worker reviews a plain-English disclosure in the worker portal and signs it electronically. That acknowledgment supplements, and does not replace, the signed written consent ZeroBadge strongly recommends each employer obtain. From the portal a worker can see and download their data, dispute a time record, request deletion of raw location data (completed within 10 business days) and withdraw consent, which stops collection for them right away. Every acknowledgment, withdrawal and admin view of location detail is recorded in a timestamped, tamper-evident log. ZeroBadge does not sell the data or use it for advertising. ZeroBadge's tools support compliance. They don't make tracking legal by themselves.
Frequently asked questions
How long should I keep employee GPS data?
Can I delete raw location and still defend a wage claim?
Do federal rules require me to keep location data?
What if a worker asks me to delete their time records too?
Does the 45-day deadline apply to every contractor?
When can I resume deleting after a legal hold?
Sources
- 1.California Civil Code 1798.100 (notice at collection, retention limit, reasonably necessary and proportionate) · California Legislative Information
- 2.California Civil Code 1798.105 (right to delete and its exceptions) · California Legislative Information
- 3.California Civil Code 1798.130 (45-day response, one 45-day extension) · California Legislative Information
- 4.CCPA frequently asked questions (employees covered; precise geolocation as sensitive personal information) · California Privacy Protection Agency
- 5.California Labor Code 1174 (payroll records, 3 years) · California Legislative Information
- 6.California Labor Code 226 (itemized statements, 3 years; 21-day inspection response) · California Legislative Information
- 7.California Labor Code 1198.5 (personnel records, 3 years after termination) · California Legislative Information
- 8.California Business and Professions Code 17208 (four-year limitation period) · California Legislative Information
- 9.29 CFR 516.5, Records to be preserved 3 years · Electronic Code of Federal Regulations
- 10.29 CFR 516.6, Supplementary basic records (time cards), 2 years · Electronic Code of Federal Regulations
- 11.29 U.S.C. 255, Statute of limitations (FLSA) · Legal Information Institute, Cornell Law School
- 12.Federal Rule of Civil Procedure 37(e), Failure to preserve electronically stored information · Legal Information Institute, Cornell Law School
Keep reading
- ResourceWorker location tracking lawsThe pillar guide to the federal and state rules.
- ResourceCCPA and worker location dataWhat California contractors need to know about thresholds, notices and vendor contracts.
- ResourceWorker consent by stateA state-by-state quick guide to consent and notice.
- GuideIs it legal to GPS track employees?The federal baseline and the state laws that matter.
- GuideRolling out time tracking to crewsHow to introduce tracking so crews know what it does and does not do.
