Skip to Content
logologo
AI Incident Database
Open TwitterOpen RSS FeedOpen FacebookOpen LinkedInOpen GitHub
Open Menu
発見する
投稿する
  • ようこそAIIDへ
  • インシデントを発見
  • 空間ビュー
  • テーブル表示
  • リスト表示
  • 組織
  • 分類法
  • インシデントレポートを投稿
  • 投稿ランキング
  • ブログ
  • AIニュースダイジェスト
  • リスクチェックリスト
  • おまかせ表示
  • サインアップ
閉じる
発見する
投稿する
  • ようこそAIIDへ
  • インシデントを発見
  • 空間ビュー
  • テーブル表示
  • リスト表示
  • 組織
  • 分類法
  • インシデントレポートを投稿
  • 投稿ランキング
  • ブログ
  • AIニュースダイジェスト
  • リスクチェックリスト
  • おまかせ表示
  • サインアップ
閉じる

インシデント 119: Xsolla Employees Fired by CEO Allegedly via Big Data Analytics of Work Activities

概要: Xsolla CEO fired more than a hundred employees from his company in Perm, Russia, based on big data analysis of their remote digitized-work activity, which critics said was violating employee's privacy, outdated, and extremely ineffective.

ツール

新しいレポート新しいレポート新しいレスポンス新しいレスポンス発見する発見する履歴を表示履歴を表示

組織

すべての組織を表示
Alleged: unknown developed an AI system deployed by Xsolla, which harmed Xsolla employees.

インシデントのステータス

インシデントID
119
レポート数
4
インシデント発生日
2021-08-03
エディタ
Sean McGregor, Khoa Lam
Applied Taxonomies
CSETv1, GMF, MIT

CSETv1 分類法のクラス

分類法の詳細

Incident Number

The number of the incident in the AI Incident Database.
 

119

AI Tangible Harm Level Notes

Notes about the AI tangible harm level assessment
 

Big data analytics was used for the harm. AI is not equivalent to big data analytics.

Special Interest Intangible Harm

An assessment of whether a special interest intangible harm occurred. This assessment does not consider the context of the intangible harm, if an AI was involved, or if there is characterizable class or subgroup of harmed entities. It is also not assessing if an intangible harm occurred. It is only asking if a special interest intangible harm occurred.
 

no

Date of Incident Year

The year in which the incident occurred. If there are multiple harms or occurrences of the incident, list the earliest. If a precise date is unavailable, but the available sources provide a basis for estimating the year, estimate. Otherwise, leave blank. Enter in the format of YYYY
 

2021

Date of Incident Month

The month in which the incident occurred. If there are multiple harms or occurrences of the incident, list the earliest. If a precise date is unavailable, but the available sources provide a basis for estimating the month, estimate. Otherwise, leave blank. Enter in the format of MM
 

07

Date of Incident Day

The day on which the incident occurred. If a precise date is unavailable, leave blank. Enter in the format of DD
 

31

MIT 分類法のクラス

Machine-Classified
分類法の詳細

Risk Subdomain

A further 23 subdomains create an accessible and understandable classification of hazards and harms associated with AI
 

5.2. Loss of human agency and autonomy

Risk Domain

The Domain Taxonomy of AI Risks classifies risks into seven AI risk domains: (1) Discrimination & toxicity, (2) Privacy & security, (3) Misinformation, (4) Malicious actors & misuse, (5) Human-computer interaction, (6) Socioeconomic & environmental harms, and (7) AI system safety, failures & limitations.
 
  1. Human-Computer Interaction

Entity

Which, if any, entity is presented as the main cause of the risk
 

Human

Timing

The stage in the AI lifecycle at which the risk is presented as occurring
 

Post-deployment

Intent

Whether the risk is presented as occurring as an expected or unexpected outcome from pursuing a goal
 

Intentional

インシデントレポート

レポートタイムライン

Incident OccurrenceXsolla fires 150 employees using big data and AI analysis, CEO’s letter causes controversyXsolla fires 150 employees based on big data analysis of their activity – “Many of you might be shocked, but I truly believe that Xsolla is not for you.”+1
Game payment company Xsolla fires 150 employees via controversial email
Xsolla fires 150 employees using big data and AI analysis, CEO’s letter causes controversy

Xsolla fires 150 employees using big data and AI analysis, CEO’s letter causes controversy

gameworldobserver.com

Xsolla fires 150 employees based on big data analysis of their activity – “Many of you might be shocked, but I truly believe that Xsolla is not for you.”

Xsolla fires 150 employees based on big data analysis of their activity – “Many of you might be shocked, but I truly believe that Xsolla is not for you.”

mcvuk.com

Game payment company Xsolla fires 150 employees via controversial email

Game payment company Xsolla fires 150 employees via controversial email

nme.com

Xsolla fires 150 employees following AI-based productivity audit

Xsolla fires 150 employees following AI-based productivity audit

gamedaily.biz

Xsolla fires 150 employees using big data and AI analysis, CEO’s letter causes controversy
gameworldobserver.com · 2021

Russian payment services company Xsolla has fired 150 employees at once. What caused controversy wasn’t the staff reduction itself but the CEO’s letter, in which he tried to explain the reason behind this decision.

The email written by Xsol…

Xsolla fires 150 employees based on big data analysis of their activity – “Many of you might be shocked, but I truly believe that Xsolla is not for you.”
mcvuk.com · 2021

Payment services company Xsolla has reportedly fired 150 of its employees, with workers in the company’s office in Perm, Russia being terminated based on big data analysis of their activity (via Game World Observer).

Making the situation wo…

Game payment company Xsolla fires 150 employees via controversial email
nme.com · 2021

150 people have been fired from Xsolla – a game payment company used by Steam, the Epic Games Store and other game developers – via a controversial email from CEO and founder Aleksandr Agapitov.

Agapitov contacted 150 fired employees throug…

Xsolla fires 150 employees following AI-based productivity audit
gamedaily.biz · 2021

The news raises a number of ethical questions that are especially pertinent in a pandemic-stricken working environment.

Xsolla, the Russia-based games industry payment solution provider, has reportedly laid off upwards of 150 employees foll…

バリアント

「バリアント」は既存のAIインシデントと同じ原因要素を共有し、同様な被害を引き起こし、同じ知的システムを含んだインシデントです。バリアントは完全に独立したインシデントとしてインデックスするのではなく、データベースに最初に投稿された同様なインシデントの元にインシデントのバリエーションとして一覧します。インシデントデータベースの他の投稿タイプとは違い、バリアントではインシデントデータベース以外の根拠のレポートは要求されません。詳細についてはこの研究論文を参照してください

よく似たインシデント

テキスト類似度による

Did our AI mess up? Flag the unrelated incidents

Russian Chatbot Supports Stalin and Violence

Russian AI chatbot found supporting Stalin and violence two weeks after launch

Oct 2017 · 5 レポート
Deepfake Video of Ukrainian President Yielding to Russia Posted on Ukrainian Websites and Social Media

Russian War Report: Hacked news program and deepfake video spread false Zelenskyy claims

Mar 2022 · 9 レポート
Amazon Flex Drivers Allegedly Fired via Automated Employee Evaluations

War veteran fired from Amazon for automated email with no chance to defend himself

Sep 2015 · 5 レポート
前のインシデント次のインシデント

よく似たインシデント

テキスト類似度による

Did our AI mess up? Flag the unrelated incidents

Russian Chatbot Supports Stalin and Violence

Russian AI chatbot found supporting Stalin and violence two weeks after launch

Oct 2017 · 5 レポート
Deepfake Video of Ukrainian President Yielding to Russia Posted on Ukrainian Websites and Social Media

Russian War Report: Hacked news program and deepfake video spread false Zelenskyy claims

Mar 2022 · 9 レポート
Amazon Flex Drivers Allegedly Fired via Automated Employee Evaluations

War veteran fired from Amazon for automated email with no chance to defend himself

Sep 2015 · 5 レポート

リサーチ

  • “AIインシデント”の定義
  • “AIインシデントレスポンス”の定義
  • データベースのロードマップ
  • 関連研究
  • 全データベースのダウンロード

プロジェクトとコミュニティ

  • AIIDについて
  • コンタクトとフォロー
  • アプリと要約
  • エディタのためのガイド

インシデント

  • 全インシデントの一覧
  • フラグの立ったインシデント
  • 登録待ち一覧
  • クラスごとの表示
  • 分類法

2024 - AI Incident Database

  • 利用規約
  • プライバシーポリシー
  • Open twitterOpen githubOpen rssOpen facebookOpen linkedin
  • ecd56df