MENLO PARK — Meta has suspended an internal artificial-intelligence project that monitored employees’ mouse clicks and behavior to measure productivity, after a data leak inside the company raised privacy concerns, according to reports from Mint and Business Standard. The program, which analyzed how workers interacted with their computers, has been halted while the company reviews its data-handling practices.
The project was part of Meta’s broader effort to apply AI to internal operations, the same machinery it uses to analyze user behavior on its platforms. The version aimed at employees tracked the rhythm of their workdays: which applications they opened, how frequently they clicked, and how their activity correlated with output. The data leak, whose scope has not been fully disclosed, exposed the program’s existence and its collection practices to a wider internal audience, and the backlash was immediate.
Employees raised concerns that the monitoring crossed a line that internal tools had historically respected, according to people familiar with the discussions. Workplace surveillance has been a sensitive subject at Meta since the pandemic, when the company’s return-to-office policies and productivity tracking drew criticism from staff. The leak turned a background project into a visible issue, and the suspension was announced days after the incident became known inside the company.
The episode lands at a moment when the boundaries of workplace AI are being tested across the technology industry. Software companies sell tools that monitor keystrokes, screen time and application usage to employers, and the market for such products has grown as remote and hybrid work made managers less certain about what employees are doing. Meta’s internal project was, in effect, an experiment in applying the same logic to its own workforce, and the company has now discovered how its employees feel about it.
The privacy questions are distinct from the productivity questions. Monitoring software can identify patterns that help teams work more efficiently, and Meta’s project was justified internally on those grounds, but the collection of behavioral data about employees creates risks that ordinary metrics do not: the data can be misused, leaked or interpreted in ways that harm individuals. The leak demonstrated the risk in the starkest terms, and the company’s suspension acknowledges that the collection itself carried a cost.
Regulators are paying attention. The European Union’s AI Act includes provisions on workplace AI, requiring transparency when systems are used to assess employees, and the California Privacy Protection Agency has been examining employer surveillance practices. The Meta episode gives regulators a concrete case to cite, analysts said, and could accelerate rulemaking that constrains how companies deploy AI internally.
For Meta, the suspension is an acknowledgment that its internal AI ambitions must account for its own workforce’s expectations. The company has invested heavily in AI across its products and has said it wants to use the technology to improve operations, but the employee-tracking project shows the limits of that ambition when it touches the people who work there. The company has not said whether the program will be redesigned or abandoned.
The episode also feeds a broader debate about AI and workplace power. Unions and labor advocates have argued that employers use monitoring tools to pressure workers, and that AI systems trained on behavioral data encode assumptions that penalize certain working styles. Meta’s own unionization history, including organizing efforts at its offices, makes the internal reaction unsurprising, analysts said, and the suspension may be the beginning of a longer negotiation about what the company may observe.
Other large employers are watching the fallout closely. Most of the major technology companies run some form of internal analytics, and the boundaries of acceptable practice are being drawn in real time. A company that quietly monitored employees and got caught has now provided a case study in what happens when the tools of surveillance are turned inward, and the lesson is being absorbed in HR departments across the industry.
The suspension does not resolve the underlying question of what Meta’s internal AI can observe. The company runs analytics across its engineering and product organizations, and its tools track far more than mouse clicks: they measure code shipped, features launched and incidents resolved, metrics that employees generally accept as part of working at a large technology company. The line that was crossed, according to people familiar with the internal reaction, was behavioral: monitoring how people click and work, rather than what they produce, felt like surveillance of effort rather than measurement of output. That distinction, between watching the work and watching the worker, is the boundary that the project crossed and that the company is now trying to re-establish.
The industry is watching how Meta handles the aftermath. A company with Meta’s engineering resources could rebuild the program with better privacy protections, or it could abandon employee monitoring entirely, and either choice would set a precedent for the rest of the technology industry. Labor groups have said they will treat the suspension as a starting point for a broader conversation about the limits of workplace AI, and regulators have taken note of the episode as an example of the risks they have been warning about. The program is dark for now, but the questions it raised are being litigated in public, in meetings, in the press and, soon, probably in the rules that govern how companies may use AI on their own employees.
Meta said in a statement that it takes the privacy of its employees seriously and is reviewing the project’s data practices before deciding how to proceed. For now, the program is dark, and the questions it raised are not. The episode shows that the AI tools companies build for their workers are subject to the same scrutiny as the ones they build for their users, and that the people who write the code have opinions about the code that watches them.
