Short answer
Yes, the Digital Personal Data Protection Act, 2023 covers the attendance, selfie and location data you hold about employees. Section 7 allows processing for the purposes of employment without asking for consent, so you do not need a consent form for every punch. It does not remove the other duties: keep data accurate when it decides pay, protect it, report breaches, erase it when its purpose ends, and name someone employees can ask.
This article is about those duties and what they mean for HR. It does not repeat the question of whether GPS tracking is allowed, which we answer in Is employee GPS tracking legal in India?
Which dates matter
The Act was passed in 2023 and the Rules were notified in November 2025. Rule 1 phases them: the administrative rules start on publication, Rule 4 one year after, and Rules 3, 5 to 16, 22 and 23 eighteen months after. Notice, security safeguards, breach intimation and erasure sit in that last group, which puts the start of employer duties at around mid-May 2027.
Eighteen months is not long for changes to access, retention and vendor contracts. Start now.
The employment ground in section 7
Section 7 lists legitimate uses for which personal data can be processed without consent. Clause (i) covers processing "for the purposes of employment or those related to safeguarding the employer from loss or liability", and includes providing a service or benefit an employee has asked for.
What that comfortably covers for a field team:
- Punch times and the location of a punch, to record attendance and verify a site
- Duty-time routes, to verify visits and calculate distance for km claims
- Records needed to run payroll and answer an employee's own request
Where it gets uncertain is anything the job does not need: movement outside duty, data kept long after payroll and audit have no use for it, or data used to profile people. Tie each data type to a work purpose in writing, and drop the ones you cannot explain.
A data map of attendance and field data
Start here. Add your own columns for owner and retention period.
| Data | Why you hold it | What to watch |
|---|---|---|
| Punch in and out times | Attendance, paid days, overtime | Low. Keep for payroll and audit periods, and keep corrections with who approved them. |
| Location at the moment of a punch | Verifying a punch at a site | Medium. Needed only where a site check is part of the job. Do not use it to follow people outside it. |
| Live route during duty | Field work, visits, distance for km claims | High. Limit to working hours, limit who can open it, and decide how long trails are kept. |
| Selfie at punch | Proof that the person punched | High. A face image is sensitive in practice. Keep it for a stated, short period. |
| Device identifiers | Stopping punches from another person's phone | Medium. Say plainly that a device is bound to an account. |
| Photos and notes from visits | Proof of a customer visit | Medium. They may show customers and third parties, so access should follow the reporting line. |
| Odometer readings | Km claims | Low. Keep with the claim. |
Duties that still apply
Keep attendance accurate when it decides pay
Section 8(3)
Where data is likely to be used to make a decision that affects the person, the fiduciary must ensure its completeness, accuracy and consistency. Loss of pay and late marks are such decisions. A correction workflow with a reason and an approver is the practical answer.
Take reasonable security safeguards
Section 8(5) and Rule 6
Rule 6 lists minimums: securing personal data through encryption, obfuscation, masking or virtual tokens; controlling access to computer resources; logs and monitoring of who accessed data; backups; retaining such logs and personal data for one year unless another law needs longer; contracts with processors that require safeguards; and technical and organisational measures that make these work.
Report breaches to the Board and to each affected person
Section 8(6) and Rule 7
Intimation goes to each affected person and to the Data Protection Board without delay, with a fuller report to the Board within seventy-two hours of becoming aware, or a longer period the Board allows. A breach of a location history or selfie store is exactly the kind of event to plan for.
Erase data when its purpose is served
Section 8(7), 8(8) and Rule 8
Data must be erased once it is reasonable to assume the purpose is no longer being served, unless a law requires you to keep it. Rule 8 adds that people must be told at least forty-eight hours before erasure in the cases it covers. The time periods sit in a schedule to the Rules that we did not verify, so confirm them with counsel.
Say who answers questions and how to complain
Section 8(9) and 8(10)
Publish the business contact information of a person who can answer questions about the data, and run a working way to handle grievances. Name an HR contact for tracking and attendance questions in your policy.
Penalties
The Schedule sets ceilings, not standard fines. The Data Protection Board decides an amount after looking at the breach and what the organisation did about it.
- Failing to take reasonable security safeguardsUp to Rs 250 crore
- Failing to notify the Board or affected people of a breachUp to Rs 200 crore
- Any other breach of the Act or RulesUp to Rs 50 crore
Read the first row as the one that matters for attendance and location data. The largest ceiling attaches to weak safeguards, so access control and logs deserve more of your time than wording.
Questions for your software vendor
Rule 6 asks fiduciaries to put safeguards into contracts with the companies that process data for them, so your attendance or field tracking vendor is part of your compliance. Ask in writing:
- Where is our attendance, selfie and location data stored, and who at your company can open it?
- How is it protected at rest and in transit, and do you keep access logs?
- How long do you keep punch records, route trails and selfies, and can we change that period?
- How would you tell us about a breach, and how fast?
- Can an employee's data be erased or exported when they leave?
- Will you sign a data processing agreement that carries the safeguards above?
- Which of your sub-processors touch our data?
The same questions are fair to ask Zeba.
A 30 day readiness plan
- Week 1
Map the data
List every attendance and field data type you hold, where it lives and who can open it. Use the table above as the starting list.
- Week 2
Write and publish the policy
One page: what is collected, when, why, who sees it, how long it is kept, who to ask. Our field staff tracking policy template has wording to copy.
- Week 3
Fix access and retention
Cut live map and selfie access to reporting managers and HR. Set a retention period for each data type and write it down.
- Week 4
Ask your vendors
Send the vendor questions, collect answers in writing, and file them with the contract.
Tools that help: live location tracking that runs only during working hours, geofenced attendance for roles that do not need a trail, and the field staff tracking policy template for the written part.
Check before you rely on this
This is general information for HR teams, not legal advice. We worked from the text of the Act and Rules as published on a third-party reference site, because the official copies were not reachable when we wrote this, so check section numbers, rule wording, schedule amounts and dates against the Gazette or with your counsel before acting on them. The erasure periods in the Rules' schedule and the exact notification date are the two items we did not confirm.
Last reviewed 2026-11-22. Sector rules, client contracts and your own standing orders can add duties.
FAQ
Does the DPDP Act apply to employee attendance data?
Attendance, selfie and location data about identifiable employees is digital personal data, so processing it falls under the Act when the processing happens in India. Employment-related processing has its own ground in section 7, but the other duties of a data fiduciary still apply.
Do I need consent from employees to track attendance?
Section 7 lists processing for the purposes of employment as a legitimate use that does not rest on consent. That covers what the employment actually needs, such as attendance and pay. It does not mean anything collected from an employee is covered, so keep collection tied to a work purpose and ask counsel about edge cases.
Is a notice still needed if I rely on the employment ground?
The statutory notice duty in section 5 is written around requests for consent. Even so, a written policy that tells people what is collected, when and why is the practice that holds up with employees and with regulators, and it is the basis for the contact and grievance duties.
When do the DPDP obligations start for employers?
The Rules were notified in November 2025. Rule 1 brings the administrative rules into force on publication, one rule after a year, and most of the rest, including those on notice, security, breaches and erasure, eighteen months after publication. That points to around mid-May 2027. Confirm the exact date against the Gazette.
Is a GPS trail more sensitive than a punch time?
In practice yes, because a trail shows a person's movements over time. The same law applies to both, but risk, access and retention should be tighter for trails and selfies than for punch times.
What happens to attendance data when an employee leaves?
Keep what payroll, statutory records and audits need, for the period those require, and erase or anonymise the rest once its purpose is served. Write the periods into your policy so the answer is the same for everyone.
Next: copy the field staff tracking policy template, or read how field staff tracking works during working hours.
