Skip to main content

NOPE · AI and people

AI incidents

Reports of AI-related harm and adverse experiences affecting people’s safety, wellbeing, rights and livelihoods. Explore what happened and the evidence available.

NOPE’s core concern is when AI communicates with a person, acts on their behalf, or depicts or impersonates them. The tracker also records consequential decisions, claims and privacy harms involving AI. Each case needs a described connection between AI use and the harm, including private information recorded into or disclosed to an AI service. Each account is reviewed for publication; claims may remain uncorroborated or disputed. How we review and count cases

In this selection

Published cases
3
Countries with reported events
1
Located 3 of 3 cases · 0 unknown
Languages in checked sources
1
Recorded for 3 of 3 cases

3 cases have no reviewed AI-to-person relation yet: 0 not yet reviewed and 3 reviewed as unknown. Show all cases

These figures describe the cases collected by NOPE. Coverage varies with discovery, reporting and available evidence. They do not estimate how often AI-related harm occurs.

Response counts currently use each case’s principal recorded outcome. Further proceedings may be described in its account.

Cases in this selection, counted once in their first known event year. A series may continue beyond that year. Reporting and collection dates are excluded. NOPE has searched recent events more thoroughly than earlier years, so bar heights also reflect collection effort.

Reported severity Medium
More filters: AI relation, use, setting, sources and responses
Clear filters

3 of 1099 published cases

Sept 2025RussiaUnidentified AI tools

Moscow Region court rules dismissal of programmer whose employer accused him of abusing AI unlawful and awards him over 1.2 million roubles

A court in Moscow Region, Russia, ruled in favour of a programmer whose employer had disciplined him and ended his employment, according to court materials reported by TASS on 27 October 2026 and relayed by regional outlets. In court the company's representative said the programmer had performed his duties improperly and had abused artificial intelligence when doing work tasks, which the company said its analytical reports showed. The programmer said the employer had pressed him to leave from September 2025 after he refused to sign an agreement moving him to hourly pay, and that he faced five internal inspections and three disciplinary penalties he disputed. The court found that the employer had ignored his written explanations, partly upheld his claim, changed the recorded ground of dismissal to termination at the employee's initiative, adjusted the dismissal date, lifted the penalties and awarded him over 1.2 million roubles in average earnings for the period of forced absence, plus moral damages and costs.

AI relation unknown Medium reported severity Lawsuit Filed

AI involvement reported · Causal attribution supported · 4 sources, 1 underlying account · Added 28/10/2026

2024RussiaUnidentified AI tools

Moscow: courts reinstate a sewing-company manager dismissed after refusing two-hour days that her employer tied to introducing AI, T-Zhurnal reports

T-Zhurnal (T-Bank's magazine) reported on 16 September 2026, in a lawyer's account of two court decisions, that the sewing company employing a Moscow resident as a full-time manager began cost-cutting in mid-2024 and introduced neural-network and AI technology, and told her that from July she would work 09:00 to 11:00, eight hours a week, with pay reduced in proportion. She refused and was dismissed for refusing to continue work after changes to her contract terms. The employer said that since it began introducing AI many of the manager's tasks were done by programs and full-time work was no longer needed, and that she had worked badly; she said the change was a disguised redundancy and that her post was to be cut and partly replaced by programs and AI. According to the article, the district court (case 2-1354/2025) found that other employees confirmed the cost-cutting and that the manager's work was planned to be fully replaced by neural networks, held that the refusal of part-time work had to be treated as a redundancy, and ordered her reinstatement with back pay and moral damages. The Moscow City Court (case 33-34099/2025) upheld the reinstatement and reduced the back-pay calculation; the court's case portal lists that appeal as concluded on 24 July 2025. The amounts are not given.

AI relation unknown Medium reported severity Lawsuit Filed

AI involvement reported · Causal attribution supported · 2 sources · Added 25/10/2026

2025RussiaDeepSeek

Moscow court upholds a sales director's dismissal for disclosing trade secrets, including uploading company reports to DeepSeek, and rejects her severance claim

A Moscow district court upheld an engineering company's dismissal of its head of sales for disclosing trade secrets, according to RAPSI and Pravo.ru reports of 27 July 2026. The grounds included uploading protected internal reports to the Chinese chatbot DeepSeek, forwarding company documents to her personal email and disclosing strategic information to a supplier. The court held that uploading trade secrets to DeepSeek is in itself a disclosure. She had sought a dismissal by mutual agreement and a contractual severance payment of 5 million roubles. The court rejected both, annulled a separate reprimand and awarded her compensation for moral harm. The decision was not yet final.

AI relation unknown Medium reported severity Lawsuit Dismissed

AI involvement reported · Causal attribution alleged · 4 sources, 1 underlying account · Added 19/10/2026

Cases may have several effects and sources. Mixed accounts qualify when they include a reported harm or adverse experience. People are counted within individual cases where sources support a number; we do not publish a collection-wide total of distinct people.

A source’s existence, the experience it reports and AI’s causal role are separate questions. A lawsuit records allegations unless a subsequent finding establishes them.

Methodology and corrections · Subscribe via RSS · Suggest a case or correction · Find support

Last dataset update: 04/11/2026. Dataset available under CC BY 4.0.