CheckUser policy

From WickedGov Meta-Wiki
Jump to navigation Jump to search

CheckUser is a tool available to Stewards and to certain local administrators (called "checkusers"). The tool may be used to reveal the IP addresses associated with a registered account, as well as other technical data about accounts and IP addresses.

Use of the tool[edit | edit source]

CheckUser should be used to prevent or investigate vandalism, sockpuppetry, and other disruption on the WickedGov site. It should never be used to exert political control or threaten other users.

Checkusers are permitted, but not required, to notify the subjects of their checks.

Grounds for checking[edit | edit source]

Checkusers must always be able to cite specific, reasonable grounds for conducting a check. Valid reasons include:

  • Reasonable suspicion of sockpuppetry, even if the primary account is not known.
  • When a history of abusing multiple accounts has been established, checking IP addresses for purposes of detecting sleeper accounts or blocking underlying IPs.

Use of CheckUser without justification is called "fishing" and is prohibited. Fishing or other inappropriate use of CheckUser may result in revocation of privileges.

Release of CheckUser data[edit | edit source]

Per the Privacy Policy, private CheckUser data must not be disclosed, except in the following circumstances:

  • With the consent of the checked user.
  • As necessary to prevent persistent vandalism or abuse to WickedGov. This includes necessary disclosure of IP addresses in order to make IP blocks.

When in doubt, checkusers should provide as little information as possible. Explicit statements such as "User A is connecting from IP address 127.0.0.1" are rarely necessary and should be avoided.

CheckUser access[edit | edit source]

Stewards[edit | edit source]

Stewards are the primary users with access to the CheckUser tool. Stewards are granted CheckUser access on the WickedGov Login Wiki. This allows them to view CheckUser data for log-in and logout actions across all projects.

If required, Stewards are permitted to temporarily grant themselves CheckUser access on other wikis in any of the following circumstances:

  1. Prevention or mitigation of spam or vandalism.
  2. Prevention or mitigation of disruption caused by compromised accounts.
  3. Emergencies and urgent situations.
  4. To investigate cross-wiki abuse or evasion of a global ban, global lock, or global block.
  5. When there are no local checkusers on a wiki, or all local checkusers are inactive.

Unless absolutely necessary, Stewards should avoid using CheckUser on wikis with established CheckUser processes where they are not local checkusers themselves.

Stewards should not self-grant indefinite CheckUser access except on Login Wiki or when there is local consensus.

Local checkusers[edit | edit source]

Sometimes, checkusers may be appointed on individual wikis, subject to the following rules:

  • The local checkuser flag may be granted and removed by Stewards only.
  • Temporary CheckUser access will not be granted,[1] except for Stewards.
  • According to local policies, local checkusers may be appointed either by local consensus or by a local Arbitration Committee or similar body.
  • All users applying for local CheckUser access must either be (a) a local administrator or (b) a member of a local Arbitration Committee or similar body.
  • All checkusers must have two-factor authentication enabled.
  • On any wiki, there must be at least two users with CheckUser access, or none at all. This is so that they can mutually control and confirm their actions. In the case where only one checkuser is left on a wiki (when the only other one retires or is removed), the community must appoint a new checkuser immediately (so that the number of checkusers is at least two). If the community does not do so, the remaining checkuser shall also have access removed.
  • The wiki must be large enough to require local checkusers. Stewards will make the final determination of this point based on criteria including the size of the community and the frequency of checks being necessary.
  • There must be broad consensus for the appointment with numerous users participating. In cases of appointments by arbitration committees, the election of arbitrators must have been well-attended.

Notes[edit | edit source]

  1. This applies to the technical flag only. Notwithstanding this policy, local communities may create periodic review and confirmation processes for checkusers.