CheckUser policy: Difference between revisions
rv: this is a board-approved policy |
Are you sure? This is not on a list of board-approved policies, and on the board-approved Privacy policy it doesn't state those sentences. |
||
Line 50: | Line 50: | ||
*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. |
*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 the user has said they're from somewhere and the IP confirms it, it's not releasing private information to confirm it if needed. |
||
*Revealing that two users come in from different countries is generally not personally identifiable; "these users come in from far apart" may serve as well. |
|||
*If they're on a large national or international ISP (''e.g.'' AOL, NTL, BT, Telstra) where they're one of millions of users, saying so is unlikely to be 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. |
*If you're in any doubt, give no detail. |
||
Revision as of 19:07, 21 June 2007
Template:Other languages/CheckUser policy
CheckUser status
CheckUser is a 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 one or several 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.
An editor's IPs may be checked upon his or her request if, for example, there is a need to provide evidence of innocence against a sockpuppet allegation, but note 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 Wikipedia. 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.
- Revealing that two users come in from different countries is generally not personally identifiable; "these users come in from far apart" may serve as well.
- If you're in any doubt, give no detail.
Access to checkuser
As of 11 April 2007, Checkusers must be 18 years of age, of legal age in their place of residence, and willing to provide identification to the Wikimedia Foundation in order to qualify. [1] |
Only stewards and a very few editors are allowed to have the CheckUser status. Editors will only have CheckUser status locally.
On a wiki with a (Wikimedia-approved) Arbitration Committee (ArbCom), only editors approved by the Arbitrators may have CheckUser status. There 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 insufficient 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 Requests 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).
Mailing list
For Wikimedia checkers, 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.
Removal of access
Any user account with checkuser status that is inactive for more than a year will see 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 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.
Complaints of abuse of checkuser or privacy policy breaches may also be brought to the Ombudsman committee.
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
- Edit (last updated: 2024-06-06)
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
- Courcelles
- DatGuy
- Doug Weller
- Dreamy Jazz
- Drmies
- EdJohnston
- Ferret
- Firefly
- GeneralNotability
- Girth Summit
- Guerillero
- HJ Mitchell
- Ivanvector
- Joe Roe
- Jpgordon
- KrakatoaKatie
- Ks0stm
- L235
- Mailer diablo
- Materialscientist
- Maxim
- Mkdw
- Moneytrees
- Mz7
- NinjaRobotPirate
- Oshwah
- PhilKnight
- Ponyo
- Primefac
- Reaper Eternal
- RickinBaltimore
- Risker
- RoySmith
- SQL
- ST47
- Salvio giuliano
- Sdrqaz
- Spicy
- Stwalkerster
- 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
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)
Wikitech
Automatically generated checkusers list
See also
- Privacy policy
- Ombudsman commission (processes complaints of privacy violations)
- Requests for CheckUser information and CheckUser status
- Help:CheckUser user manual
- [Foundation-l] CheckUser (thoughts)