An employee-monitoring framework covering purpose, transparency, proportionality, device scope, screenshots, location, biometrics, productivity scoring and manager access.
Monitoring software can create more security and employee-relations risk than the misconduct it was purchased to detect.
The DPDP framework is phased. The 14 November 2025 commencement notification brought specified institutional and enabling provisions into force immediately; Consent Manager-related provisions follow after one year; most operating duties and Rules follow eighteen months after Gazette publication. As of 22 June 2026, the control should distinguish current obligations from future-state DPDP readiness.
Employment-related processing can fall within specified legitimate use when the relevant provision commences, but purpose, necessity, safeguards and fairness still matter.
Continuous screenshots, keystrokes, webcam, location and productivity scores vary greatly in intrusiveness.
Monitoring on personal devices and homes can capture family, health, union, financial or unrelated personal activity.
| Check | What to examine |
|---|---|
| Purpose | Security, attendance, safety, quality or performance. |
| Scope | Device, app, screen, location, audio and time. |
| Population | Role, remote work, contractor and jurisdiction. |
| Access | Manager, HR, security and vendor. |
| Decision | Alert, review, discipline and correction. |
A productivity tool captures screenshots every minute, including personal banking during a permitted break, and gives every manager access. A narrower application-activity measure may satisfy the security purpose with less intrusion.
Document why the least intrusive alternative is insufficient. Separate security telemetry from performance evaluation.
Give employees clear notice, access to relevant records and a route to challenge inaccurate automated conclusions.
Identify the people, data, systems, purpose, owner, processor, user journey and failure scenario. Review purpose, scope and population together. A policy statement or vendor assurance cannot replace evidence of how the live product behaves.
Apply the 14 November 2025 commencement notification provision by provision. Continue complying with currently operative CERT-In, banking, telecom, insurance, employment, consumer, contract and criminal-law requirements. Build the scheduled DPDP workflow now, but do not describe a future provision as already enforceable.
Run the workflow in the live or controlled test environment. Preserve screenshots, approvals, logs, vendor responses, user communications, exceptions and remediation. Assign a named owner and completion date to every failed control so management can distinguish an operating safeguard from a policy intention.
Privacy and cyber maturity are visible in operating behaviour: what the organisation collects, who can use it, how vendors are controlled, how users exercise choices, how incidents are handled and whether evidence survives scrutiny.
Use the current official instrument, portal or regulator publication before acting. This panel separates the category authority from page-specific references.