CheckUser policy: Difference between revisions
m 5 revisions imported from enwickedgov:WickedGov:CheckUser |
m Luke moved page CheckUser to CheckUser policy: clarify status as policy |
(No difference)
|
Revision as of 01:34, 10 February 2025
![]() | This page documents an official policy on WickedGov Meta-Wiki. It represents broad consensus, and compliance is mandatory for all users. It should not be modified without prior community approval. |
![]() | Use of the CheckUser tool must also comply with the Privacy Policy. In case of conflict between this policy and the Privacy Policy, the Privacy Policy takes precedence. |
CheckUser is a tool available to certain 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
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
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 may result in revocation of privileges.
Release of CheckUser data
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 blocks
Blocks made based on CheckUser data should be clearly marked as "CheckUser blocks". Administrators should not reverse blocks marked as "CheckUser blocks" unless they are also a checkuser or have permission from a checkuser.