Confiança e Segurança (C&S), anteriormente conhecido como Defesa da Comunidade, DC ou SuSa,  identifica, constrói e — conforme apropriado — organiza processos que mantêm os nossos usuários seguros; projete, desenvolve e executa em uma estratégia que integra jurídico, produto, engenharia, pesquisa e aprendizagem e avaliação para mitigar riscos de forma proativa, bem como gerenciar a segurança geral das nossas comunidades online e offline quando os incidentes acontecem. A Confiança e Segurança faz parte da ala Resiliência e Sustentabilidade da Comunidade do Departamento Jurídico. O nosso objetivo é fornecer serviços de confiança e segurança compassivos, confiáveis e abrangentes para a Fundação e as comunidades de voluntários e afiliados que ela apoia, mas muito do nosso tempo também é gasto no "combate a incêndios". Para obter mais informações sobre a equipe, consulte a nossa Visão geral.
O que fazemos
A equipe de Confiança e Segurança apoia a equipe, o público e os voluntários em nossa comunidade por meio de aproximadamente 11 fluxos de trabalho em três grandes áreas. A equipe é composta por duas subequipes: Política e Operações. Você pode encontrar mais detalhes em em Programas e Processos.
Confiança e Segurança
The Wikimedia Foundation aims to defer to local and global community processes to govern on-wiki interactions. However, at times, we must step in to protect the safety and integrity of our users, our contributors, and the public. We support a healthy environment on our projects through several work areas. Among other measures, we receive and handle reports of major safety issues on Wikimedia projects, including suicide threats, threats of violence, and child pornography. We also own the policies regarding Wikimedia Foundation bans of users from the projects and from Foundation-funded or supported events, and we work with other Foundation teams to address concerns about user privacy and freedom that do not necessarily rise to the level of bans.
As a part of the Foundation’s commitment to respect community autonomy, the Trust & Safety team does not handle general community or community-member disputes that may be addressed through community processes, nor does it serve as an appeal venue for community-made policies and decisions. While we are happy to assist community members in need of help, many times that help will consist of assisting the person to find the right community venue to solve their problem.
Flowchart detailing the investigation workflow when evaluating a request for an Office action
Regular workflows include:
- Evaluation and reporting:
- General Trust & Safety inquiries and reports of abuse can be submitted through: cawikimedia.org, in line with the Office actions policy.
- Threats of imminent physical harm can be submitted to: emergencywikimedia.org, according to the Threats of harm protocol.
- Assessment of child protection concerns including reports of child pornography filed through: firstname.lastname@example.org, as per Child protection.
- Global & Event bans: Requests, inquiries, investigations & maintenance. (See also log of global bans by T&S.)
- AffCom support: Assist the Affiliations Committee as appropriate in relation to Trust and Safety matters
- Identification and access rights for community: see access to nonpublic personal data noticeboard
- T&S database management: mandatory and best-practice record-keeping
- Trust and Safety Disinformation: The Trust and Safety Disinformation team focuses on supporting communities in identifying and countering disinformation campaigns on Wikimedia Foundation platforms. The team has supported the evaluation of long-standing community concerns about the disinformation issue on Croatian Wikipedia and collaborated closely with English language Wikipedia functionaries ahead of the US presidential election 2020 following the VP incident study.
In close collaboration with Product and other parts of the Legal department, the team leads the Anti-Harassment Program.
Other regular workflows include:
We provide guidance, advice and support to Foundation staff, the Board, and committees. We assist staff routinely with community and content related concerns, including processing DMCA takedown and notification requirements and, where necessary, responding to search warrants and legally valid subpoenas. We manage requests for advanced user rights required for staff members to do their work by assessing needs and liaising with the stewards.
Regular workflows include:
- Supporting Executives: the Executive Director, the Executive Office, Jimmy Wales.
- Liaison work: to the election committee, the cross-wiki Ombuds Commission, the Code of Conduct Committee, and other WMF teams.
- Supporting the staff: Advanced privileges and user rights for staff
- Legal support: DMCA takedown and notification requirements, search warrant and subpoena compliance
Office actions workflow
Flowchart detailing how to report a Wikimedia-related incident
The process leading up to an office action varies considerably based on the action and the circumstances surrounding it. The strongest actions in common use are those taken against users of the websites, typically in the form of global or event bans. These actions are the result of user conduct investigations undertaken by T&S Specialists, which go through a rigorous review cycle as documented in the flowchart to the right.
Other office actions can include deletions of illegal material. This typically consists of sensitive images of minors which violate the laws of the United States. T&S also performs deletions to satisfy the Foundation's DMCA Policy, an archive of which is maintained on Foundation wiki.
In September 2020, a case review committee was created to allow directly involved community members to request review of a community committee of Trust & Safety behavioral investigation outcomes. This committee is equipped to review certain office actions on appeal from individuals directly involved in the case (as the requesting or sanctioned party). For more information, see Office actions#Appeals. This will remain in place until a permanent process is created through the Universal Code of Conduct conversations in 2021.