Meta Backtracks on Employee Monitoring After Internal Revolt — A Signal for Workplace AI Governance
The News
Meta has scaled back plans to collect employee mouse movements, keystrokes, and clicks for AI training after weeks of internal pushback that saw staff liken the company to an “Employee Data Extraction Factory,” Reuters reported June 2. Employees complained the tracking software drained battery life, spiked home internet usage, and invaded privacy on personal devices used for work.
The company introduced a 30-minute pause option and exemption requests, but the episode reveals deep tensions around workplace AI data collection — even at a company whose business model is built on user data. The tool was originally installed on U.S. employees’ computers in April without an opt-out mechanism, and the protests followed a broader restructuring that included layoffs.
Meta VP Stephane Kasriel acknowledged the concerns in an internal memo, saying the company had “heard your concerns about personal data on work devices” while maintaining confidence in the privacy protections at launch. The episode could deepen Meta’s regulatory challenges in the EU, where the data collection was already described as on a “collision course” with privacy rules.
Why It Matters
This matters to TA leaders because the same dynamics will hit hiring tools. If Meta — arguably the most data-forward company on the planet — couldn’t roll out employee monitoring without a crisis, the vendor selling your team an AI productivity tracker or candidate engagement scoring tool will face similar trust issues with your workforce. The episode is a preview of the privacy pushback awaiting any organisation that collects employee or candidate behavioural data without transparent opt-in and clear boundaries.
The EU regulatory dimension matters too. Any AI hiring tool that processes behavioural data from candidates in the European Union will face the same scrutiny — and the EU AI Act’s August 2 enforcement deadline adds teeth to those concerns. If a major technology company cannot navigate these waters, the vendors selling into your enterprise almost certainly cannot either without your procurement team asking the right questions.
Taking Action
All action is situated in your corporate context. These are starting points, not prescriptions — choose what fits.
Connect
Who to talk with in your enterprise
Chief Privacy Officer or Data Protection Officer. If you have one, they need to know which tools in your TA stack collect behavioural or interaction data beyond basic application information. If you don’t have a DPO, that’s worth a conversation with legal — especially if you hire in the EU.
IT Security / Enterprise Infrastructure. They likely already block or flag tools that perform suspicious data collection. Loop them into any new vendor evaluation early. Their risk playbook exists for a reason.
Inspect
What to take a closer look at
Audit your current TA tech stack for any tool that collects candidate or recruiter behavioural data — mouse movements, time-on-page, keystroke patterns, facial expression analysis, or engagement scoring. Request each vendor’s data collection disclosures and AI training data policies. You’re not looking for gotchas; you’re looking for vendors who can clearly articulate what they collect, why, and how candidates or employees can opt out.
Reflect
What to think about more deeply
Meta’s employees had the leverage to push back because they are engineers at a high-demand employer. Your candidates and employees do not have that leverage. If a tool’s data collection practices would not pass muster with Meta’s staff — who have options — ask yourself whether they should pass muster with your workforce, who have fewer of them.