CheckUser policy
From Meta
| ←Policies and guidelines | CheckUser policy |
| This page provides information about CheckUser access and outlines the policy on its use. It was discussed in September and October 2005, and went live in November 2005. |
CheckUser status
CheckUser is an interface for users with the checkuser permission. An editor with CheckUser status on a wiki can in particular check if a user isn't a sockpuppet of another user on that wiki (not on all wikis). By using it, users are able to:
- Determine from which IPs a user has edited the Wikimedia wiki
- Determine the edits on the Wikimedia wiki of a specific IP (even when logged in)
This information is only stored for a short period, so edits made prior to that will not be shown via CheckUser. A log is kept of who has made which queries with the tool. This log is available to those with the checkuser permission:
5 sep 2006 17:29 UserX got IPs for UserY on zzwiki 5 sep 2006 17:29 UserX got edits for 127.0.0.1 on zzwiki
See Help:CheckUser for the user manual.
Use of the tool
The tool is to be used to fight vandalism, to check for sockpuppet abuse, and to limit disruption of the project. It must be used only to prevent damage to any of Wikimedia projects.
The tool should not be used for political control; to apply pressure on editors; or as a threat against another editor in a content dispute. There must be a valid reason to check a user. Note that alternative accounts are not forbidden, so long as they are not used in violation of the policies (for example, to double-vote or to increase the apparent support for any given position).
Notification to the account that is checked is permitted but is not mandatory. Similarly, notification of the check to the community is not mandatory, but may be done subject to the provisions of the privacy policy.
Some wikis allow an editor's IPs to be checked upon his or her request if, for example, there is a need to provide evidence of innocence against a sockpuppet allegation; note, however, that requesting a checkuser in these circumstances is sometimes part of the attempt to disrupt.
Privacy policy
On Wikimedia projects, privacy policy considerations are of tremendous importance. Unless someone is violating policy with their actions (e.g. massive bot vandalism or spam) and revealing information about them is necessary to stop the disruption, it is a violation of the privacy policy to reveal their IP, whereabouts, or other information sufficient to identify them, unless they have already revealed this information themselves on the project. The relevant section of the privacy policy is:
- Policy on release of data derived from page logs
- It is the policy of Wikimedia that personally identifiable data collected in the server logs, or through records in the database via the CheckUser feature, may be released by the system administrators or users with CheckUser access, in the following situations:
-
- In response to a valid subpoena or other compulsory request from law enforcement
- With permission of the affected user
- To the chair of Wikimedia Foundation, his legal counsel, or his designee, when necessary for investigation of abuse complaints.
- Where the information pertains to page views generated by a spider or bot and its dissemination is necessary to illustrate or resolve technical issues.
- Where the user has been vandalising articles or persistently behaving in a disruptive way, data may be released to assist in the targeting of IP blocks, or to assist in the formulation of a complaint to relevant Internet Service Providers
- Where it is reasonably necessary to protect the rights, property or safety of the Wikimedia Foundation, its users or the public.
Information release
Even if the user is committing abuse, it's best not to reveal personal information if possible.
- Generally, do not reveal IPs. Only give information such as same network/not same network or similar. If detailed information is provided, make sure the person you are giving it to is a trusted person and will not reveal it himself.
- If the user has said they're from somewhere and the IP confirms it, it's not releasing private information to confirm it if needed.
- If you're in any doubt, give no detail.
Access to CheckUser
Only Stewards and a very few editors are allowed to have CheckUser status. Editors will only have CheckUser status locally.
If local CheckUsers exist in a project, checks should generally be handled by those. In emergencies, or for multi-project CheckUser checks as in the case of cross-wiki vandalism, Stewards may perform local checks. Stewards should remove CheckUser access on the projects upon completion of the checks and notify the local CheckUsers or the CheckUser e-mail list.
On any wiki, there must be at least two users with CheckUser status, 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), a new CheckUser must be selected immediately (so that the number of CheckUsers is at least two).
Local CheckUser status is granted in a manner agreed upon between the local wiki and the Foundation. On some wikis, CheckUser status is granted by the Arbitration committee; on other wikis, CheckUsers are elected. Please check with the local CheckUser policy on each wiki for details.
Any changes in how CheckUser status is granted on a particular wiki require community and Foundation approval.
Mailing list
For Wikimedia CheckUser users, there is a mailing list, CheckUser-l. This is a closed list. Use this list to ask for help, ideas and second opinions if you're not sure what the data means. All users with CheckUser access should be a member of the list.
Removal of access
Any user account with CheckUser status that is inactive for more than a year will have their CheckUser access be removed.
In case of abusive use of the tool, the Steward or the editor with the CheckUser privilege will immediately have their access removed. This will in particular happen if checks are done routinely on editors without a serious motive to do so (links and proofs of bad behavior should be provided).
Suspicion of abuses of CheckUser should be discussed by each local wiki. On wikis with an approved ArbCom, the ArbCom can decide on the removal of access. On wikis without an approved ArbCom, the community can vote removal of access. Removal can only be done by Stewards. A Steward may not decide to remove access on their own, but can help provide information necessary to prove the abuse (such as logs). If necessary, and in particular in case of lack of respect towards the privacy policy, the Board of Wikimedia Foundation can be asked to declare removal of access as well.
Complaints of abuse of CheckUser or privacy policy breaches may also be brought to the Ombudsman committee.
Current users with access
Everywhere
- Tim Starling
- Stewards - upon request.
- Members of the Ombudsman commission:
Arabic Wikipedia
Automatically generated checkusers list
Bosnian Wikipedia
Automatically generated checkusers list
Catalan Wikipedia
Automatically generated checkusers list
Croatian Wikipedia
Automatically generated checkusers list
Czech Wikipedia
Automatically generated checkusers list
Danish Wikipedia
Automatically generated checkusers list
Dutch Wikipedia
Automatically generated checkusers list
Appointed by Arbcom
English Wikibooks
Automatically generated checkusers list
English Wikinews
Automatically generated checkusers list
English Wikipedia
Automatically generated checkusers list
Appointed by Arbcom
- Alison
- Blnguyen
- David Gerard
- Deskana
- Dmcdevit
- FayssalF
- FloNight
- Fred Bauder
- FT2
- Jayjg
- Jdforrester
- Jpgordon
- Kirill Lokshin
- Lar
- Mackensen
- Morven
- Raul654
- Rebecca
- Redux
- Sam Korn
- Thatcher
- Thebainer
- The Epopt
- Tim Starling
- UninvitedCompany
- Voice of All
Office
English Wikiquote
Automatically generated checkusers list
English Wikisource
Automatically generated checkusers list
- Brion VIBBER (for technical purposes)
- Jayvdb (elected)
- Pathoschild (elected)
English Wikiversity
Automatically generated checkusers list
English Wiktionary
Automatically generated checkusers list
French Wikipedia
Automatically generated checkusers list
Finnish Wikipedia
Automatically generated checkusers list
German Wikipedia
Automatically generated checkusers list
Hungarian Wikipedia
Automatically generated checkusers list (requests and policy)
Hebrew Wikipedia
Automatically generated checkusers list
Indonesian Wikipedia
Automatically generated checkusers list
Italian Wikipedia
Automatically generated checkusers list
Japanese Wikipedia
(ja:Wikipedia:CheckUserの方針) Automatically generated checkusers list
Polish Wikipedia
Automatically generated checkusers list Due to a new policy on the Polish Wikipedia, users who gain 85% of votes in favor may become CheckUsers
Portuguese Wikipedia
Automatically generated checkusers list
Romanian Wikipedia
Automatically generated checkusers list
Russian Wikipedia
Automatically generated checkusers list
Serbian Wikipedia
Automatically generated checkusers list
Simple English Wikipedia
Automatically generated checkusers list
Slovak Wikipedia
Automatically generated checkusers list
Spanish Wikipedia
Automatically generated checkusers list
Swedish Wikipedia
Automatically generated checkusers list
Turkish Wikipedia
Automatically generated checkusers list
Wikimedia Commons
Automatically generated checkusers list
Meta
Automatically generated checkusers list
Elected
For log access
- Anthere
- Brion VIBBER
- Hei ber (on meta, as Ombudsman)
- Jon Harald Søby
- Midom
- Tim Starling
- Yann
See also
- Privacy policy
- Ombudsman commission (processes complaints of privacy violations)
- Requests for CheckUser information and CheckUser status
- Local policies of the projects
- Help:CheckUser user manual
- [Foundation-l] CheckUser (thoughts)
banned user – anonymous user – registered user – bot – administrator – bureaucrat – oversight – checkuser – developer
Global
unified account – Global rollback (proposed) - Global sysops (proposed) – Ombudsmen - steward

