CheckUser policy
Other languages : Template:CheckUserPolicyLang
This policy was discussed in September and October 2005 (see discussions), and went live in November 2005
CheckUser status
CheckUser is a special 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 this wiki (not on all wikis). By using it, users are able to:
- Determine from which IPs has a user edited the Wikimedia wiki
- Determine the edits on the Wikimedia wiki of a specific IP (even when logged in)
These data are only stored for one week, 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 2005 17:29 UserX got IPs for UserY 5 sep 2005 17:29 UserX got edits for 127.0.0.1
See Help:CheckUser for the user manual.
Wikimedia privacy policy
On Wikimedia projects, privacy policy considerations are of tremendous importance. Unless someone is definitely violating policy with their actions (e.g. massive bot vandalism or spam), revealing their IP, whereabouts or other information sufficient to identify them is likely a violation.
CheckUser requires the level of confidentiality one would apply to our most confidential user data.
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 will not be released by the developers who have access to it, except as follows:
- In response to a valid subpoena or other compulsory request from law enforcement
- With permission of the affected user
- To Jimbo Wales, 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 pages or persistently behaving in a disruptive way, data may be released to assist in the targetting 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.
- Wikimedia policy does not permit public distribution of such information under any circumstances, except as described above.
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 they're on a large ISP (e.g. AOL, NTL, BT, Telstra), they're one of millions and it's not personally identifiable.
- Revealing the country is generally not personally identifiable (e.g. "User:Querulous is coming in from the UK, User:Sockpuppet is coming in from Canada").
- If you're in any doubt, give no detail
Use of the tool
The tool is to be used to fight vandalism or check abuse of sockpuppets, for example when there is a suspicion of illegal voting. It must be used only to prevent damage to one or several of Wikimedia projects.
It is not allowed to use the tool for political control, nor to apply pressure on editors, nor as a threat toward an editor with whom you are in disagreement. There must be a valid motive to check a user (a bare disagreement with the leaders of a wiki is not a valid motive).
It is allowed to check an editor ips upon his specific request, when this user wants to publicly prove his innocence.
As a reminder, sockpuppets are not generally forbidden (editors may edit wikipedia under several accounts). It is the abuse of sockpuppets use (and in particular voting twice under two different names) which is severely frowned upon.
Notification to the one checked is not mandatory, but checkuser may choose to tell the person checked if they feel it best. Similarly, notification of the check to the community is not mandatory, but may be done as long as private information is not released.
Access
Only a very few editors and Stewards are allowed to have the CheckUser status. Editors will only have CheckUser status locally.
On a wiki with a (Wikimedia-approved) Arbitration Committee, only editors approved by the Arbitrators may have CheckUser status. They should be at least two so that they can mutually control their activity. After agreement, simply list the candidate on Requests for permissions.
On a wiki with no Arbitration Committee, two options are possible:
The community must approve at least two CheckUsers per consensus. Activity will be checked mutually. The user requesting check user status must request it within his local community and advertise this request properly (village pump, mailing list when available, ...). The editor must be familiar with the privacy policy. After gaining consensus (70%-80%) in his local community, with at least 25-30 editors approval, the user should list himself under Requests for permissions with a link to the page with the community's decision.
If an unsufficient number of voters do not allow to vote for two checkusers on a wiki, there will be no checkuser on that wiki. Editors will have to ask a Steward to check if UserX is a sockpuppet of UserY. To do so, simply add your request to Request for CheckUser information listing these users and explaining why you ask for such a check (with links). You also need a community consensus (like above). The Steward will answer you if these two users are from the same IP, same proxy, same network, same country, or are they completely unrelated (see discussion for what the Steward should more precisely say to the editor).
Removal of access
Any user account with checkuser status that is inactive for more than a year will see his 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 on each local wiki. On wikis with an arbcom, the arbcom can decide on the removal of access. On wikis without arbcom, the community can vote removal of access. Removal can be done by stewards. The stewards may not decide alone of removal, but can help provide the information necessary to prove the abuse (log). 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.
In case only one checkuser is left on a wiki, the community should elect a new checkuser (so that the number of checkusers is at least two).
Current users with access as of November 2005
- Edit (last updated: 2024-11-13)
Everywhere
- Stewards - upon request or their own initiative, stewards use it by briefly granting the right to themselves; this is logged.
- Some members of the Staff of the Wikimedia Foundation (see global group)
- Members of the Ombuds commission (see automatically generated list):
Arabic Wikipedia
Automatically generated checkusers list
Bengali Wikipedia
Automatically generated checkusers list
Local policy mandates that only users who gain at least 25 votes in favor and 80% support can be appointed (applications will open for no fewer than 30 days).
Catalan 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
Local policy mandates that Stewards are explicitly allowed to process non-emergency CheckUser requests.
English Wikinews
Automatically generated checkusers list
English Wikipedia
Automatically generated checkusers list
- Alison
- AmandaNP
- Aoidh
- Barkeep49
- Blablubbs
- Bradv
- Cabayi
- Callanecc
- CaptainEek
- DatGuy
- Dreamy Jazz
- Drmies
- EdJohnston
- Ferret
- Firefly
- Girth Summit
- Guerillero
- HJ Mitchell
- Ivanvector
- Izno
- Joe Roe
- Jpgordon
- KrakatoaKatie
- Ks0stm
- L235
- Mailer diablo
- Materialscientist
- Mkdw
- Moneytrees
- Mz7
- NinjaRobotPirate
- Oshwah
- PhilKnight
- Ponyo
- Primefac
- Reaper Eternal
- RickinBaltimore
- Risker
- RoySmith
- SQL
- ST47
- Salvio giuliano
- Sdrqaz
- Stwalkerster
- TheresNoTime
- ToBeFree
- Vanamonde93
- Versageek
- Yamla
- Zzuuzz
- Z1720
English Wiktionary
Automatically generated checkusers list
Finnish Wikipedia
Automatically generated checkusers list
French Wikipedia
Automatically generated checkusers list
Under the local policy, CheckUsers are elected for six-month terms.
German Wikipedia
Automatically generated checkusers list
Under the local policy, CheckUsers are elected for one- or two-year terms.
Hebrew Wikipedia
Automatically generated checkusers list
Hungarian Wikipedia
Automatically generated checkusers list (requests and policy)
Indonesian Wikipedia
Automatically generated checkusers list
Italian Wikipedia
Automatically generated checkusers list
Japanese Wikipedia
Automatically generated checkusers list (policy)
Korean Wikipedia
Automatically generated checkusers list (policy and requests)
Malayalam Wikipedia
Automatically generated checkusers list (policy and requests)
Persian Wikipedia
Automatically generated checkusers list
Polish Wikipedia
Automatically generated checkusers list
Due to a new local policy, users who gain 85% of votes in favor may become CheckUsers.
Portuguese Wikipedia
Automatically generated checkusers list
Under the local policy, CheckUsers are elected for two-year terms.
Russian Wikipedia
Automatically generated checkusers list
- Appointed by ArbCom
Serbian Wikipedia
Automatically generated checkusers list
Simple English Wikipedia
Automatically generated checkusers list
Slovene Wikipedia
Automatically generated checkusers list
Spanish Wikipedia
Automatically generated checkusers list
Local policy mandates that only users who gain at least 30 votes in favor and 80% support can be appointed.
Swedish Wikipedia
Automatically generated checkusers list
Thai Wikipedia
Automatically generated checkusers list
Turkish Wikipedia
Automatically generated checkusers list
Ukrainian Wikipedia
Automatically generated checkusers list
- Appointed by ArbCom
Vietnamese Wikipedia
Automatically generated checkusers list
Wikimedia Commons
Automatically generated checkusers list · (information page and requests page)
Wikispecies
Automatically generated checkusers list
Meta
Automatically generated checkusers list · (information page and requests page)
Wikidata
Automatically generated checkusers list · (information page and requests page)