TCS Denies Tracking Employees On Company Laptops: What DEM Tools May See And Can Performance Be Tracked Without Spying?
Tata Consultancy Services has rejected a report claiming it deployed a Digital User Experience Monitoring, or DEM, tool on employee laptops to track individual activity. The company says the software is used only for “ma
लेखक Debashis Sarkar··17K पढ़े गए
TCS Denies Tracking Employees On Company Laptops: What DEM Tools May See And Can Performance Be Tracked Without Spying?
Tata Consultancy Services has rejected a report claiming it deployed a Digital User Experience Monitoring, or DEM, tool on employee laptops to track individual activity. The company says the software is used only for “macro-level network and security monitoring”, not to watch individual employees. Here is what is known, what DEM tools can technically do, and whether performance can genuinely be tracked without invading privacy.
What TCS Has Said
TCS has called the surveillance reports “baseless and inaccurate”
The company’s official line: “TCS does not track individual employee activity on laptops and respects their privacy. We use tools to monitor macro-level network performance, to ensure security, availability and enhanced user experience for our employees”
TCS has not named the software vendor, disclosed the tool’s precise technical capabilities, specified what categories of data it collects, or said which teams or individuals inside the company can access that data
The company’s public security policy states that protecting business-sensitive information, including personal information, is core to its and its clients’ interests, and that its security framework covers information security, cybersecurity and personnel security globally
What The Report Alleged
Media reported that TCS had deployed a Digital User Experience Monitoring tool across company-issued laptops
Sources cited in that report said the software can show which applications employees access and how much time they spend on each one
The report did not establish whether the tool captures on-screen content, keystrokes or communications, only application-level usage data, according to what has been made public so far
The scale is significant regardless of intent: TCS employs close to six lakh people globally, so any laptop-level deployment affects one of the largest single workforces of any company anywhere
What A DEM Tool Actually Is, Technically
This is the part missing from most coverage of the story. Digital Experience Monitoring is an established, named category of enterprise IT software, not something TCS invented or something inherently sinister. Understanding its real architecture separates the legitimate use case from the surveillance concern.
Endpoint monitoring: tracks the health of the physical device itself, CPU load, memory usage, battery, disk health, whether hardware or software issues are degrading performance
Application performance monitoring: measures how individual applications behave, load times, crash rates, error frequency, response lag
Network performance monitoring: tracks latency, packet loss and connectivity quality, particularly relevant for remote and hybrid staff
Real user monitoring: captures live data from actual user sessions as they happen, rather than simulated tests
Synthetic transaction monitoring: uses scripted bots to simulate user actions and flag problems before a real employee encounters them
Mainstream DEM platforms from vendors such as Nexthink, Aternity and Cloudflare are generally sold on this proposition: identify and fix technical problems, slow logins, dropped VPN connections, lagging applications, before employees have to complain about them. That is a materially different objective from productivity surveillance, even though the underlying telemetry can sometimes support both.
The feature that turns monitoring into surveillance
Some advanced DEM and adjacent “digital employee experience” platforms include a feature called session replay, along with AI-driven sentiment analysis and behavioural scoring. Session replay can reconstruct what a user actually did on screen. That is the line separating infrastructure monitoring from behavioural surveillance, and it is precisely the distinction TCS has not clarified for its own deployment. A tool that only logs which application was open and for how long is fundamentally different from one capable of showing what was inside it.
Five Facts
TCS denies individual tracking. Its official position is that monitoring happens at the network and infrastructure level, not at the level of a named employee’s screen activity.
The alleged capability, if accurate, is application-level, not content-level. Seeing that an employee had a browser or a spreadsheet open, and for how long, is different from seeing what they typed or viewed inside it. Reports so far describe the former, not the latter.
The company has disclosed almost nothing about the tool’s specifics. No vendor name, no defined data categories, no access list. That absence of detail is itself driving much of the concern, independent of what the tool actually does.
TCS has a legitimate, well-documented reason to monitor devices. As a company holding sensitive client data across sectors and countries, device-level cybersecurity monitoring is a standard and defensible practice, not an unusual one.
The controversy reflects a much broader shift. Employee monitoring has expanded significantly since remote and hybrid work became routine, and TCS is far from the only large employer navigating this exact tension.
Can Performance Actually Be Tracked Without Spying?
The honest answer is yes, but only if an organisation deliberately designs for it, because the same underlying telemetry can be configured either way. The difference is not the software category. It is how narrowly the collection is scoped and how transparently it is governed.
What privacy-preserving monitoring looks like
Aggregate over individual. Reporting that “40 percent of laptops in a region experienced VPN latency above 200ms this week” protects infrastructure without identifying anyone. Reporting that “Employee X spent 47 minutes in Excel on Tuesday” does not.
Anonymised or pseudonymised telemetry by default. Performance data tied to a device ID or team cohort rather than a named individual, with identification only unlocked through a documented, auditable process, for example an active security incident.
Collect only what serves a stated purpose. If the goal is detecting malware or unusual network behaviour, the tool does not need to log which productivity apps someone uses for routine work.
No content capture by default. Application-level usage statistics do not require screen recording, keystroke logging or session replay. Those are separate, more invasive capabilities that should require separate, explicit justification.
Defined retention limits. Data kept only as long as needed for its stated security or performance purpose, not indefinitely.
A restricted, named access list. Specific security or IT teams with a documented need, not open visibility across HR, management or reporting managers.
Disclosure to employees. What is collected, why, how long it is kept and who can see it, ideally including whether monitoring continues outside working hours on a company device used at home.