DPDP-Compliant Employee Monitoring Vendors for India 2026 — Vendor Risk Matrix

What the five DPDP anchors test

Workplace monitoring data is personal data. The employer is the Data Fiduciary; the vendor is a Data Processor under Section 8(4). The five anchors collapse the DPDP Act 2023 plus the expected Rules into the decisions a procurement team can make today.

• Section 4 consent. Does the vendor surface a per-feature consent record — not a single product-level toggle — so the deployer can demonstrate notified consent or specified legitimate use for each capture surface?
• Section 8 DPIA. Does the vendor ship Section 8(5) security safeguards documentation plus a DPIA template the deployer can adapt? Vendors that hand over a generic DPA without the DPIA section read partial.
• Section 10 SDF obligations. For employers likely to be designated Significant Data Fiduciaries (large IT services, BPO, regulated sectors), does the vendor ship the SDF documentation pack — appointed DPO contract, audit support, periodic DPIA refresh?
• Default surveillance. Are screenshot, keystroke, webcam, and similar capture surfaces switched off by default? Off by default = pass; on by default with role-level toggles = partial; on by default with only org-wide toggle = fail.
• India data residency. Does the vendor offer India-region data storage with a documented residency posture — or at minimum a clear cross-border transfer record that complies with Section 16 once notified?

DPDP penalty bands run up to INR 250 crore per breach for failure to take security safeguards (Section 33 and the schedule), with separate bands for breach-notification failure, SDF-obligation failure, and child-data failure — figures subject to revision in notified rules, verify with counsel.

The 6-vendor DPDP risk matrix

Per-vendor read

gStride — Ready

gStride was built India-first with DPDP as a foundational design constraint, not a bolted-on DPA. Surveillance capture surfaces are off by default; the consent surface is per feature so the deployer can produce a Section 4 record per data principal per capture type. India residency is supported with a documented residency posture. The data-principal rights workflow — access, correction, erasure, grievance — is built into the product rather than a manual ticket queue. Section 10 SDF pack ships with the deployer kit. See the solution stance for cross-deployment EU + India posture.

Keka — Ready (HR scope)

Keka is HR-suite first — payroll, leave, attendance, performance — not a monitoring tool, so it sits outside the surveillance-default question for most of its product surface. India residency and Section 4 consent surface are clean. Where it reads partial is the Section 10 SDF pack (HR suite, not monitoring depth) and the Section 8 DPIA template (generic, not workplace-monitoring-specific). For India SMB and mid-market buyers who need an HR system plus light productivity signal, Keka is deployable; for buyers who need productivity intelligence depth, pair it or consolidate. See gStride vs Keka for the use-both pattern.

Freshteam — Ready (HR scope)

Freshteam scores the same pattern as Keka — HR-suite first, India residency clean, consent surface clean, Section 10 SDF pack and DPIA template partial because the product isn't workplace-monitoring depth. For deployers running Freshteam as the HR backbone and a separate productivity tool on top, score the productivity vendor separately. The DPDP exposure usually concentrates in the productivity layer, not the HR-record layer.

Hubstaff — Patchable

Hubstaff has a global product footprint and DPA architecture but not an India-specific posture. Section 4 consent reads partial — consent toggles exist but are not per-feature granular enough for a clean record. Default surveillance is fail — screenshots, activity score, app/URL tracking are on by default per project. Section 10 SDF documentation isn't published. India residency reads partial because the global tenant doesn't pin to an Indian region. Patchable with deployer-side hardening (per-feature consent, surveillance off at org level, SDF pack from counsel) but the vendor needs to ship the missing pieces for a sustainable Ready.

Time Doctor — Patchable

Time Doctor mirrors the Hubstaff pattern with the same default-on screenshot plus activity rating. Section 4 consent surface is partial, default surveillance is fail, Section 10 SDF documentation is missing, India residency is partial. The patch path is the same: deployer-side consent record, capture off at org level, SDF pack adapted from counsel. Hold renewal on a vendor-side commitment to ship the missing pieces inside 60 days.

Teramind — At-Risk / Halt

Teramind's default product configuration — screenshots, keystroke logging, webcam capture, behavioral analytics — collides with both DPDP consent architecture and the EU AI Act Article 5 prohibition when used in cross-border deployments. Section 4 consent reads fail because the depth of capture cannot be cleanly mapped to a per-feature consent record without disabling most of the product. Default surveillance is fail. India residency is partial. For India deployers where any portion of the workforce sits in EU jurisdiction or the data crosses an EU border, this becomes a halt for the combined matrix, not just at-risk. See our Teramind alternative piece for the enterprise replacement pattern.