Archive · 26 Jul 2026
Meta's AI Struggles Revealed in Leaked Recordings
Meta, the company that owns Facebook and Instagram, has been trying really hard to make better AI.
They even started a program to track what their employees do on their work computers to help train the AI.
But this made a lot of employees upset because they weren't asked if it was okay.
More than 1,600 employees signed a petition to stop the program.
Later, it was found that the program had a big problem: it accidentally made private employee information available to many internal databases.
A few months later, the CEO, Mark Zuckerberg, admitted in a meeting that the AI project wasn't moving as fast as he hoped.
So, Meta is having a tough time with their AI plans, and it's causing some big problems with their employees.
Meta's AI program tracked employee activity without consent, leading to a petition signed by 1,600+ employees.
The program exposed private employee data across 45,000 internal database tables.
Meta paused the program after the data exposure incident on June 22, 2026.
Mark Zuckerberg admitted in a July 2026 meeting that Meta's AI push hasn't accelerated as expected.
Employees in the UK launched a unionization drive in response to the tracking program.
- Who
- Mark Zuckerberg and Meta employees
- What
- Leaked recordings reveal Meta's AI struggles and employee tracking controversies
- When
- April and July 2026
- Where
- Meta offices in California, New York, and the UK
- Why
- To improve AI models and company efficiency, but faced employee backlash and data security issues
Employee Privacy Advocates
Meta Management
Employee Tracking
Employee Privacy Advocates
Employees should not be tracked without consent, as it violates privacy rights and labor laws.
Meta Management
Tracking employee activity is necessary for improving AI models and company efficiency.
Data Security
Employee Privacy Advocates
The exposure of private employee data highlights the risks of unregulated data collection.
Meta Management
The data exposure was an isolated incident, and measures are being taken to prevent future occurrences.
- Date of First Leak
- April 2026
- Date of Second Leak
- July 2, 2026
- Number of Employees Protesting
- 1,600+
- Data Exposure Incident
- June 22, 2026
- Internal Database Tables Affected
- 45,000