Privacy Group Sues Scale AI Over Alleged Freelancer Monitoring

Key points

• noyb filed a privacy lawsuit against Scale AI.
• The complaint alleges keystroke logging and mouse tracking.
• Freelancers using the AI data platform are affected.
• No CVE is assigned; the issue is vendor privacy practice.

Privacy advocacy group noyb has brought a legal challenge against Scale AI, according to the supplied facts. The dispute centers on how the company’s platform for AI data work treats the freelancers who perform tasks on it. The action is described as a privacy lawsuit, and no CVE identifier is associated with the matter.

The allegations concern monitoring of workers. Specifically, the complaint reportedly claims that keystrokes were logged and that mouse activity was tracked. Those practices, if confirmed, would amount to surveillance of freelancers rather than a conventional software vulnerability.

The people affected are freelancers who use the AI data platform. For districts and public agencies, the case is a reminder that vendor privacy terms can carry operational and reputational risk even when no exploit exists. K-12 IT teams should treat input monitoring and telemetry clauses as procurement and contract issues.

Because this is a legal and privacy dispute, not a patched flaw, the immediate response is governance. Watch for court filings, vendor statements, and any changes to Scale AI’s terms or monitoring disclosures. Also watch whether other AI data vendors face similar claims.

What to do now

1. Inventory any current or planned use of Scale AI or similar AI data platforms; document data flows and affected user groups.
2. Review vendor contracts and privacy notices for keystroke, mouse, screen, or productivity monitoring; require written disclosure.
3. Do not enable input-monitoring features on staff or student devices without legal and privacy review.
4. Restrict such platforms to managed devices and least-privilege accounts; block unapproved browser extensions.
5. Ask vendors for retention, access, and deletion details for monitoring data; confirm opt-out or configuration controls.
6. Brief procurement and legal teams; add a privacy-review gate before renewal or pilot expansion.
7. Monitor noyb and vendor updates; escalate if district freelancers or contractors are affected.

Original source

The Record